From 54d2975708657319e6ca42c44bd1e871abd09d85 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Sun, 5 Sep 2004 14:46:49 +0000 Subject: [PATCH] Better conformance to DocBook standards --- docs/Samba-HOWTO-Collection/Compiling.xml | 10 +++--- docs/Samba-HOWTO-Collection/DomainMember.xml | 2 +- docs/Samba-HOWTO-Collection/NetworkBrowsing.xml | 22 ++++++------- docs/Samba-HOWTO-Collection/PDC.xml | 18 +++++----- docs/Samba-HOWTO-Collection/Passdb.xml | 44 ++++++++++++------------- docs/Samba-HOWTO-Collection/PolicyMgmt.xml | 10 +++--- docs/Samba-HOWTO-Collection/ServerType.xml | 10 +++--- docs/xslt/generate-attributions.xsl | 4 +-- 8 files changed, 59 insertions(+), 61 deletions(-) diff --git a/docs/Samba-HOWTO-Collection/Compiling.xml b/docs/Samba-HOWTO-Collection/Compiling.xml index 4260e7dda0b..b6dea57abb0 100644 --- a/docs/Samba-HOWTO-Collection/Compiling.xml +++ b/docs/Samba-HOWTO-Collection/Compiling.xml @@ -312,8 +312,8 @@ example of what you would not want to see would be: On Debian, you need to install the following packages: - libkrb5-dev - krb5-user + libkrb5-dev + krb5-user @@ -324,9 +324,9 @@ example of what you would not want to see would be: On Red Hat Linux, this means you should have at least: - krb5-workstation (for kinit) - krb5-libs (for linking with) - krb5-devel (because you are compiling from source) + krb5-workstation (for kinit) + krb5-libs (for linking with) + krb5-devel (because you are compiling from source) diff --git a/docs/Samba-HOWTO-Collection/DomainMember.xml b/docs/Samba-HOWTO-Collection/DomainMember.xml index df38cef0b6c..d1f2386d54b 100644 --- a/docs/Samba-HOWTO-Collection/DomainMember.xml +++ b/docs/Samba-HOWTO-Collection/DomainMember.xml @@ -895,7 +895,7 @@ may want to create the machine account within a particular organizational unit. this to be done using the following syntax: &rootprompt; kinit Administrator@your.kerberos.REALM -&rootprompt; net ads join organizational_unit +&rootprompt; net ads join "organizational_unit" diff --git a/docs/Samba-HOWTO-Collection/NetworkBrowsing.xml b/docs/Samba-HOWTO-Collection/NetworkBrowsing.xml index 1855fa1809c..9b93c8a434a 100644 --- a/docs/Samba-HOWTO-Collection/NetworkBrowsing.xml +++ b/docs/Samba-HOWTO-Collection/NetworkBrowsing.xml @@ -99,12 +99,12 @@ The technologies (or methods) employed in making all of this work include: - MS Windows machines register their presence to the network. - Machines announce themselves to other machines on the network. - One or more machine on the network collates the local announcements. - The client machine finds the machine that has the collated list of machines. - The client machine is able to resolve the machine names to IP addresses. - The client machine is able to connect to a target machine. + MS Windows machines register their presence to the network. + Machines announce themselves to other machines on the network. + One or more machine on the network collates the local announcements. + The client machine finds the machine that has the collated list of machines. + The client machine is able to resolve the machine names to IP addresses. + The client machine is able to connect to a target machine. @@ -1184,17 +1184,17 @@ are: - WINS &smbmdash; the best tool. - LMHOSTS &smbmdash; static and hard to maintain. - Broadcast &smbmdash; uses UDP and cannot resolve names across remote segments. + WINS &smbmdash; the best tool. + LMHOSTS &smbmdash; static and hard to maintain. + Broadcast &smbmdash; uses UDP and cannot resolve names across remote segments. Alternative means of name resolution include: -Static /etc/hosts &smbmdash; hard to maintain, and lacks name_type info. -DNS &smbmdash; is a good choice but lacks essential name_type info. +Static /etc/hosts &smbmdash; hard to maintain, and lacks name_type info. +DNS &smbmdash; is a good choice but lacks essential name_type info. diff --git a/docs/Samba-HOWTO-Collection/PDC.xml b/docs/Samba-HOWTO-Collection/PDC.xml index 8a839973471..14f05d7eea0 100644 --- a/docs/Samba-HOWTO-Collection/PDC.xml +++ b/docs/Samba-HOWTO-Collection/PDC.xml @@ -250,7 +250,7 @@ LDAP-based user and machine account backend. 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)See also Account Information Databases.. +the NT4-style SAM database (one of the registry files)See also Account Information Databases.. @@ -299,12 +299,12 @@ management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP environment. However, there are certain compromises: - No machine policy files. - No Group Policy Objects. - No synchronously executed AD logon scripts. - Can't use Active Directory management tools to manage users and machines. - Registry changes tattoo the main registry, while with AD they do not leave permanent changes in effect. - Without AD you cannot perform the function of exporting specific applications to specific users or groups. + No machine policy files. + No Group Policy Objects. + No synchronously executed AD logon scripts. + Can't use Active Directory management tools to manage users and machines. + Registry changes tattoo the main registry, while with AD they do not leave permanent changes in effect. + Without AD you cannot perform the function of exporting specific applications to specific users or groups. @@ -414,7 +414,7 @@ A Domain Controller is an SMB/CIFS server that: It is rather easy to configure Samba to provide these. Each Samba Domain Controller must provide the NETLOGON service that Samba calls the 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 BrowserSee Network Browsing.. +Domain must advertise itself as the Domain Master BrowserSee Network Browsing.. This causes the Primary Domain Controller to claim a domain-specific NetBIOS name that identifies it as a Domain Master Browser for its given domain or workgroup. Local master browsers 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. @@ -836,7 +836,7 @@ Create a user without the $. Then use vipw to the $. Or create the whole entry with vipw if you like; make sure you use a unique user login ID. -The machine account must have the exact name that the workstation has. +The machine account must have the exact name that the workstation has. The UNIX tool vipw is a common tool for directly editing the /etc/passwd file. diff --git a/docs/Samba-HOWTO-Collection/Passdb.xml b/docs/Samba-HOWTO-Collection/Passdb.xml index 53767e92726..0b816744890 100644 --- a/docs/Samba-HOWTO-Collection/Passdb.xml +++ b/docs/Samba-HOWTO-Collection/Passdb.xml @@ -268,10 +268,10 @@ Samba-3 introduces a number of new password backend capabilities. - MS DOS Network client 3.0 with the basic network redirector installed. - Windows 95 with the network redirector update installed. - Windows 98 [Second Edition]. - Windows Me. + MS DOS Network client 3.0 with the basic network redirector installed. + Windows 95 with the network redirector update installed. + Windows 98 [Second Edition]. + Windows Me. @@ -285,11 +285,11 @@ Samba-3 introduces a number of new password backend capabilities. - Windows NT 3.5x. - Windows NT 4.0. - Windows 2000 Professional. - Windows 200x Server/Advanced Server. - Windows XP Professional. + Windows NT 3.5x. + Windows NT 4.0. + Windows 2000 Professional. + Windows 200x Server/Advanced Server. + Windows XP Professional. @@ -481,12 +481,12 @@ called smbpasswd and pdbedit. - add user or machine accounts. - delete user or machine accounts. - enable user or machine accounts. - disable user or machine accounts. - set to NULL user passwords. - manage interdomain trust accounts. + add user or machine accounts. + delete user or machine accounts. + enable user or machine accounts. + disable user or machine accounts. + set to NULL user passwords. + manage interdomain trust accounts. @@ -549,9 +549,9 @@ called smbpasswd and pdbedit. - add, remove or modify user accounts. - list user accounts. - migrate user accounts. + add, remove or modify user accounts. + list user accounts. + migrate user accounts. @@ -1314,10 +1314,10 @@ access to attrs=SambaLMPassword,SambaNTPassword - sambaHomePath - sambaLogonScript - sambaProfilePath - sambaHomeDrive + sambaHomePath + sambaLogonScript + sambaProfilePath + sambaHomeDrive diff --git a/docs/Samba-HOWTO-Collection/PolicyMgmt.xml b/docs/Samba-HOWTO-Collection/PolicyMgmt.xml index 51346846781..c861c4bf123 100644 --- a/docs/Samba-HOWTO-Collection/PolicyMgmt.xml +++ b/docs/Samba-HOWTO-Collection/PolicyMgmt.xml @@ -345,11 +345,11 @@ Common restrictions that are frequently used include: Account Controls - Logon hours - Password aging - Permitted logon from certain machines only - Account type (local or global) - User rights + Logon hours + Password aging + Permitted logon from certain machines only + Account type (local or global) + User rights diff --git a/docs/Samba-HOWTO-Collection/ServerType.xml b/docs/Samba-HOWTO-Collection/ServerType.xml index 28ccd7158b3..8efebcb6c90 100644 --- a/docs/Samba-HOWTO-Collection/ServerType.xml +++ b/docs/Samba-HOWTO-Collection/ServerType.xml @@ -111,15 +111,15 @@ different type of servers: Domain Controller - Primary Domain Controller - Backup Domain Controller - ADS Domain Controller + Primary Domain Controller + Backup Domain Controller + ADS Domain Controller Domain Member Server - Active Directory Domain Server - NT4 Style Domain Domain Server + Active Directory Domain Server + NT4 Style Domain Domain Server Stand-alone Server diff --git a/docs/xslt/generate-attributions.xsl b/docs/xslt/generate-attributions.xsl index 718af13f72d..a6e7f98e16f 100644 --- a/docs/xslt/generate-attributions.xsl +++ b/docs/xslt/generate-attributions.xsl @@ -16,9 +16,7 @@ Attribution - - - + -- 2.11.4.GIT