txt: $(TXTDIR) $(TXTDIR)/Samba-HOWTO-Collection.txt $(TXTDIR)/Samba-Developers-Guide.txt
htmlman: $(HTMLDIR) $(MANPAGES_HTML) CSS
htmlfaq: $(HTMLDIR) CSS
- @$(XSLTPROC) --stringparam base.dir "$(FAQDIR)/" --stringparam root.filename samba-faq xslt/html-chunk.xsl $(FAQPROJDOC)/sambafaq.xml
+ $(XSLTPROC) --stringparam base.dir "$(FAQDIR)/" --stringparam root.filename samba-faq xslt/html-chunk.xsl $(FAQPROJDOC)/sambafaq.xml
html-single: $(HTMLDIR) CSS $(HTMLDIR)/Samba-HOWTO-Collection.html $(HTMLDIR)/Samba-Developers-Guide.html
html: $(HTMLDIR) CSS Samba-HOWTO-Collection.xml
- @$(XSLTPROC) -o $(HTMLDIR) xslt/html-chunk.xsl Samba-HOWTO-Collection.xml
+ $(XSLTPROC) -o $(HTMLDIR) xslt/html-chunk.xsl Samba-HOWTO-Collection.xml
manpages: $(MANDIR) $(MANPAGES)
tex: Samba-HOWTO-Collection.tex Samba-Developers-Guide.tex
$(PROJDOC)/attributions.xml: $(PROJDOC)/samba-doc.xml
@echo > $@ # Make sure we don't get recursive dependencies, etc!
- @echo "Generating attributions page"
- @$(XSLTPROC) --output $@ xslt/generate-attributions.xsl $<
+ $(XSLTPROC) --output $@ xslt/generate-attributions.xsl $<
$(DEVDOC)/attributions.xml: $(DEVDOC)/dev-doc.xml
@echo > $@ # Make sure we don't get recursive dependencies, etc!
- @echo "Generating attributions page"
- @$(XSLTPROC) --output $@ xslt/generate-attributions.xsl $<
+ $(XSLTPROC) --output $@ xslt/generate-attributions.xsl $<
clean:
@rm -f *.xml $(MANPAGES) $(TXTDIR)/*.txt $(PSDIR)/*.ps $(PDFDIR)/*.pdf
@rm -f $(SMBDOTCONFDOC)/parameters.*.xml $(DVIDIR)/*.dvi
@rm -f samba-doc.* dev-doc.* $(PROJDOC)/attributions.xml $(DEVDOC)/attributions.xml
- @rm -f $(IMAGEPROJDIR)/*.eps $(MANPROJDIR)/smb.conf.5.xml
+ @rm -f $(IMAGEPROJDIR)/*.eps $(MANPROJDOC)/smb.conf.5.xml
# Text files
$(TXTDIR):
mkdir $(TXTDIR)
$(TXTDIR)/%.txt: %.xml
- @echo "Converting $< to plain text..."
- @$(XMLTO) txt -o $(TXTDIR) $< > $@
+ $(XMLTO) txt -o $(TXTDIR) $< > $@
# Tex files
%.tex: %.xml
- @echo "Converting $< to LaTeX..."
- @$(XSLTPROC) --output $@ xslt/latex.xsl $<
+ $(XSLTPROC) --output $@ xslt/latex.xsl $<
# Adobe PDF files
$(PDFDIR)/%.pdf: %.tex
mv $(patsubst %.tex,%.dvi,$<) $@
%.eps: %.png
- @$(PNGTOPNM) $< | $(PNMTOPS) > $@
+ $(PNGTOPNM) $< | $(PNMTOPS) > $@
# PostScript files
$(PSDIR)/%.ps: $(DVIDIR)/%.dvi
# Single large HTML files
$(HTMLDIR):
- @mkdir $(HTMLDIR)
+ mkdir $(HTMLDIR)
CSS: $(HTMLDIR) xslt/html/samba.css
- @cp xslt/html/samba.css $(HTMLDIR)/
+ cp xslt/html/samba.css $(HTMLDIR)/
$(HTMLDIR)/Samba-HOWTO-Collection.html: Samba-HOWTO-Collection.xml $(PROJDOC_DEPS) $(PROJDOC_IMAGES_PNG)
- @$(XSLTPROC) --output $@ xslt/html.xsl $<
+ $(XSLTPROC) --output $@ xslt/html.xsl $<
$(HTMLDIR)/Samba-Developers-Guide.html: Samba-Developers-Guide.xml $(DEVDOC_DEPS)
- @$(XSLTPROC) --output $@ xslt/html.xsl $<
+ $(XSLTPROC) --output $@ xslt/html.xsl $<
$(HTMLDIR)/%.html: $(MANPROJDOC)/%.xml
- @$(XSLTPROC) --output $@ xslt/html.xsl $<
+ $(XSLTPROC) xslt/expand-sambadoc.xsl $< | $(XSLTPROC) --output $@ xslt/html.xsl -
# Manpages
$(SMBDOTCONFDOC)/parameters.all.xml: $(SMBDOTCONFDOC)/generate-file-list.sh
generate-context.xsl parameters.all.xml && \
cd ..
-smb.conf.5.xml: $(SMBDOTCONFDOC)/smb.conf.5.xml $(SMBDOTCONFDOC)/parameters.all.xml \
+$(MANPROJDOC)/smb.conf.5.xml: $(SMBDOTCONFDOC)/smb.conf.5.xml $(SMBDOTCONFDOC)/parameters.all.xml \
$(SMBDOTCONFDOC)/parameters.global.xml $(SMBDOTCONFDOC)/parameters.service.xml
- @$(XSLTPROC) --xinclude --output $@ xslt/expand-sambadoc.xsl $<
-
-$(MANPROJDIR)/smb.conf.5.xml: smb.conf.5.xml
- @cp $< $@
+ $(XSLTPROC) --xinclude --output $@ xslt/expand-sambadoc.xsl $<
+ -ln -s global.ent $(MANPROJDOC)/global.ent
$(MANDIR):
mkdir $(MANDIR)
$(MANDIR)/%: $(MANPROJDOC)/%.xml
- @$(XSLTPROC) xslt/expand-sambadoc.xsl $< | $(XSLTPROC) xslt/man.xsl - > $@
-
-$(MANDIR)/smb.conf.5: smb.conf.5.xml
- @$(XSLTPROC) xslt/man.xsl $< > $@
+ $(XSLTPROC) xslt/expand-sambadoc.xsl $< | $(XSLTPROC) xslt/man.xsl - > $@
undocumented: $(SMBDOTCONFDOC)/parameters.all.xml
$(PERL) scripts/find_missing_doc.pl ../..
<title>SAMBA Developers Guide</title>
<bookinfo>
- <author>
- <surname>SAMBA Team</surname>
- </author>
- <address><email>samba@samba.org</email></address>
<abstract>
<para>
<emphasis>Last Update</emphasis> : Fri Jun 6 00:45:54 CEST 2003
</abstract>
-<legalnotice>
-
-<formalpara>
+</bookinfo>
+<preface>
<title>Attributions</title>
- <para>
&attributions-dev;
- </para>
-</formalpara>
+</preface>
-</legalnotice>
-</bookinfo>
<!-- Contents -->
<toc/>
</para>
<para>
- An overview of the permissions field can be found in <link linkend="access1"/>.
+ An overview of the permissions field can be found in <link linkend="access1">the image below</link>.
</para>
<image scale="40"><imagedescription>Overview of unix permissions field</imagedescription><imagefile>access1</imagefile></image>
</itemizedlist>
<para>
- The resulting filter chain therefore is as drawn in <link linkend="pdftosocket"/>.
+ The resulting filter chain therefore is as drawn in <link linkend="pdftosocket">the image below</link>.
</para>
<image><imagefile>pdftosocket</imagefile><imagedescription>PDF to socket chain</imagedescription></image>
</itemizedlist>
<para>
- The resulting filter chain therefore is as drawn in <link linkend="pdftoepsonusb"/>.
+ The resulting filter chain therefore is as drawn in <link linkend="pdftoepsonusb">the image below</link>.
</para>
<image><imagefile>pdftoepsonusb</imagefile><imagedescription>PDF to USB chain</imagedescription></image>
<indexterm><primary>rpcclient</primary><secondary>setdriver</secondary></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="printing"/>: either change
+as described in <link linkend="printing">the printing chapter</link>: either change
a driver for an existing printer by running the "Printer Properties"
dialog, or use <command>rpcclient</command> with the
<command>setdriver</command> sub-command.
<title>Samba</title>
<para>Joining a Samba client to a domain is documented in
- <link linkend="domain-member-server"></link>.
+ <link linkend="domain-member-server">the domain member chapter</link>.
</para>
</sect3>
</para>
<para>
-Please refer to <link linkend="samba-pdc"></link>
+Please refer to <link linkend="samba-pdc">the chapter on setting up a PDC</link>
for more information regarding how to create a domain
machine account for a domain member server as well as for information
regarding how to enable the Samba domain member machine to join the domain and
</para>
<para>
-Please refer to <link linkend="winbind"></link> for information on a system
+ Please refer to <link linkend="winbind">the chapter on winbind</link> for information on a system
to automatically assign UNIX uids and gids to Windows NT Domain users and groups.
</para>
</para>
<para>For information about setting up Samba as a WINS server, read
-<link linkend="NetworkBrowsing"/>.</para>
+ <link linkend="NetworkBrowsing">the chapter on network browsing</link>.</para>
</sect2>
</sect1>
</para>
<para>
- Consider a network set up as <link linkend="browsing1"/>.
+ Consider a network set up as <link linkend="browsing1">in the diagram below</link>.
</para>
<image><imagedescription>Cross subnet browsing example</imagedescription><imagefile>browsing1</imagefile></image>
<para>
Before you continue reading in this section, please make sure that you are comfortable
-with configuring a Samba Domain Controller as described in <link linkend="samba-pdc"></link>.
+with configuring a Samba Domain Controller as described in <link linkend="samba-pdc">chapter on setting up Samba as a PDC</link>.
</para>
<sect1>
Several other things like a <smbconfsection>[homes]</smbconfsection> and a
<smbconfsection>[netlogon]</smbconfsection> share also need to be set along with
settings for the profile path, the users home drive, etc.. This will not be covered in this
-chapter, for more information please refer to <link linkend="samba-pdc"></link>.
+chapter, for more information please refer to <link linkend="samba-pdc">the chapter about samba as a PDC</link>.
</para>
</sect3>
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). Please refer to the chapter on
-<link linkend="domain-member"></link> for more information.
+<link linkend="domain-member">setting up samba as a domain member</link> for more information.
</para></note>
<para>
<para>
Samba-3 has an implementation of 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"></link>.
+discussed more fully in <link linkend="groupmapping">the chapter on group mapping</link>.
</para>
<para>
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 <link linkend="machine-trust-accounts"></link>. With Samba-3 there can be multiple
+Refer <link linkend="machine-trust-accounts">to the section on machine trust accounts</link>. With Samba-3 there can be multiple
back-ends for this. A complete discussion of account database backends can be found in
-<link linkend="passdb"></link>.
+<link linkend="passdb">the chapter on Account Information Databases</link>.
</para>
</sect1>
<para>
New to Samba-3 is the ability to use a back-end database that holds the same type of data as
the NT4 style SAM (Security Account Manager) database (one of the registry files).
-<footnote><para>See also <link linkend="passdb"/>.</para></footnote>
+<footnote><para>See also <link linkend="passdb">the chapter on Account Information Databases</link>.</para></footnote>
</para>
<para>
When running a Domain all MS Windows NT / 200x / XP Professional clients should be configured
as full Domain Members - IF A SECURE NETWORK IS WANTED. If the machine is NOT made a member of the
Domain, then it will operate like a workgroup (stand-alone) machine. Please refer to
-<link linkend="domain-member"></link> for information regarding HOW to make your MS Windows clients Domain members.
+<link linkend="domain-member">the chapter on domain membership</link> for information regarding HOW to make your MS Windows clients Domain members.
</para></note>
<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</name><value>user</value></smbconfoption>)</para></listitem>
- <listitem><para>Consistent configuration of Name Resolution (See chapter on <link linkend="NetworkBrowsing"></link> and on
- <link linkend="integrate-ms-networks"></link>)</para></listitem>
+ <listitem><para>Consistent configuration of Name Resolution (See chapter on <link linkend="NetworkBrowsing">Network Browsing</link> and on
+ <link linkend="integrate-ms-networks">Integrating Unix into Windows networks</link>)</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>
<note><para>
Roaming Profiles and System/Network policies are advanced network administration topics
-that are covered in the <link linkend="ProfileMgmt"></link> and
-<link linkend="PolicyMgmt"></link> chapters of this document. However, these are not
+that are covered in the <link linkend="ProfileMgmt">Profile Management</link> and
+<link linkend="PolicyMgmt">Policy Management</link> chapters 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>
For Samba to provide these is rather easy to configure. Each Samba Domain Controller must provide
the NETLOGON service which Samba calls the <smbconfoption><name>domain logons</name></smbconfoption> functionality
(after the name of the parameter in the &smb.conf; file). Additionally, one (1) server in a Samba-3
-Domain must advertise itself as the domain master browser<footnote><para>See also <link linkend="NetworkBrowsing"/></para></footnote>. This causes the Primary Domain Controller
+Domain must advertise itself as the domain master browser<footnote><para>See also <link linkend="NetworkBrowsing">the chapter about network browsing</link></para></footnote>. This causes the Primary Domain Controller
to claim domain specific NetBIOS name that identifies it as a domain master browser for its given
domain/workgroup. Local master browsers in the same domain/workgroup on broadcast-isolated subnets
then ask for a complete copy of the browse list for the whole wide area network. Browser clients
<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 example
-<link linkend="pdc-example"/>.
+in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in the example
+<link linkend="pdc-example">for being a PDC</link>.
</para>
<para>
must be the domain master browser, 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"></link>.
+ to do this, refer to <link linkend="passdb">the chapter on account information databases</link>.
</para></listitem>
</varlistentry>
<varlistentry><term>Environment Parameters</term>
so. You should remember that the DC must register the DOMAIN<#1b> NetBIOS
name. This is the name used by Windows clients to locate the DC.
Windows clients do not distinguish between the DC and the DMB.
-A DMB is a Domain Master Browser - see <link linkend="DMB"></link>.
+A DMB is a Domain Master Browser - see <link linkend="DMB">Domain Master Browser</link>.
For this reason, it is very wise to configure the Samba DC as the DMB.
</para>
<para>
An alternative to assigning UIDs to Windows users on a Samba member server is
-presented in <link linkend="winbind"></link>.
+presented in <link linkend="winbind">the chapter about winbind</link>.
</para>
<para>
-For more information of being a domain member, see <link linkend="domain-member"></link>.
+ For more information of being a domain member, see <link linkend="domain-member">the chapter about domain membership</link>.
</para>
</sect3>
</smbconfblock></para>
<para>
-Please refer to <link linkend="domain-member"></link> and <link linkend="ads-member"></link>
+Please refer to <link linkend="domain-member">the chapter on domain membership</link>
for more information regarding this configuration option.
</para>
<para>
Guess! So many others do. But whatever you do, do NOT think that <smbconfoption><name>security</name><value>user</value></smbconfoption>
makes Samba act as a domain member. Read the manufacturers manual before the warranty expires! See
-<link linkend="domain-member"></link> for more information.
+<link linkend="domain-member">the chapter about domain membership</link> for more information.
</para>
</sect2>
<listitem><para>
The print spooling and processing system on our print server will be CUPS.
- (Please refer to <link linkend="CUPS-printing"></link> for more information).
+ (Please refer to <link linkend="CUPS-printing">the chapter about CUPS</link> for more information).
</para></listitem>
<listitem><para>
</para>
<para>If you need to compile samba from source, check
- <link linkend="compiling"></link>.</para>
+ <link linkend="compiling">the chapter about compiling samba from scratch</link>.</para>
<para>If you have already installed samba, or if your operating system
was pre-installed with samba, then you may not need to bother with this
<para>
For more information about security settings for the
<smbconfsection>[homes]</smbconfsection> share please refer to
- <link linkend="securing-samba"></link>.
+ <link linkend="securing-samba">"Securing Samba"</link>.
</para>
<sect3>
<sect1>
<title>What If Things Don't Work?</title>
- <para>Then you might read the file chapter <link linkend="diagnosis"></link>
- and the FAQ. If you are still stuck then refer to <link linkend="problems"></link>.
+ <para>Then you might read the file chapter <link linkend="diagnosis">diagnosis</link>
+ and the FAQ. If you are still stuck then refer to <link linkend="problems">"Analysing and solving problems"</link>.
Samba has been successfully installed at thousands of sites worldwide,
so maybe someone else has hit your problem and has overcome it.</para>
<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</name></smbconfoption>. Read the section <link linkend="acctmgmttools"/> for details.</para>
+ <para>Make sure your user has been added to the current samba <smbconfoption><name>passdb backend</name></smbconfoption>. Read the section <link linkend="acctmgmttools">Account Management Tools</link> for details.</para>
</sect2>
<title>Extended Sample Configuration to Print</title>
<para>
- In <link linkend="extbsdpr"/> we show a more verbose example configuration for print related
+ In <link linkend="extbsdpr">the extended BSD configuration example</link> we show a more verbose example configuration for print related
settings in BSD-printing style environment . Below is a discussion
and explanation of the various parameters. We chose to use BSD-style
printing here, because we guess it is still the most commonly used
</para>
</abstract>
-<legalnotice>
+</bookinfo>
+
+<preface>
+ <title>Legal Notice</title>
<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>
+</preface>
-<formalpara>
+<preface>
<title>Attributions</title>
- <para>
&attributions;
- </para>
-</formalpara>
-
-</legalnotice>
-</bookinfo>
+</preface>
<!-- Contents -->
<toc/>
<part id="troubleshooting">
<title>Troubleshooting</title>
+
&Diagnosis;
&problems;
&BUGS;
</part>
<part id="Appendixes">
-<title>Appendixes</title>
+ <title>Appendixes</title>
&Compiling;
-&Portability;
+ &Portability;
&Other-Clients;
&SPEED;
&DNS-DHCP-Configuration;
storage backends
(<smbconfoption><name>passdb backend</name></smbconfoption>).
Please refer to the &smb.conf;
- man page and <link linkend="passdb"/> for details. While both parameters assume sane default
+ man page and <link linkend="passdb">the chapter about 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>
<xsl:apply-templates select="@*|node()"/>
</xsl:template>
-<xsl:template match="book">
- <xsl:element name="variablelist">
- <xsl:apply-templates/>
- </xsl:element>
-</xsl:template>
-
<xsl:template match="chapter">
- <xsl:element name="varlistentry">
- <xsl:element name="term">
- <xsl:element name="link">
- <xsl:attribute name="linkend"><xsl:value-of select="@id"/></xsl:attribute>
- <xsl:value-of select="title"/>
- </xsl:element>
- </xsl:element>
- <xsl:element name="listitem">
+ <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:element name="itemizedlist">
- <xsl:apply-templates/>
+ <xsl:apply-templates/>
</xsl:element>
</xsl:element>
- </xsl:element>
- </xsl:element>
+ </xsl:when>
+ </xsl:choose>
</xsl:template>
<xsl:template match="author">
<xsl:element name="listitem">
<xsl:element name="para">
- <xsl:value-of select="firstname"/><xsl:text> </xsl:text><xsl:value-of select="surname"/>
+ <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:text> <</xsl:text>
<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:choose>
</xsl:element>
</xsl:element>
+ <xsl:text>
+ </xsl:text>
</xsl:template>
</xsl:stylesheet>
<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:stylesheet>
git.samba.org / gd / samba / .git / commitdiff