From f04382344969440e50b84f3facdf8cbe1a44b427 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Fri, 1 May 2009 22:27:03 +0200 Subject: Fix most of the invalid usages of DocBook in the Samba 3 HOWTO. make check FTW! --- docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml | 2 +- docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml | 24 +++++++++++------------ docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml | 4 ++-- docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml | 4 ++-- docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml | 8 ++++---- docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml | 2 +- docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml | 2 +- docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml | 2 +- docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml | 2 +- docs-xml/Samba3-HOWTO/TOSHARG-locking.xml | 1 - 10 files changed, 25 insertions(+), 26 deletions(-) (limited to 'docs-xml') diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml b/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml index 35fdd9ee57..ec3dea7c5b 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-BDC.xml @@ -153,7 +153,7 @@ provided this capability. The technology has become known as the LanMan Netlogon -networklogonservice +networklogonservice Windows NT3.10 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. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml index 50d2f6b32e..70581121fb 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-CUPS-printing.xml @@ -627,11 +627,11 @@ application/octet-stream application/vnd.cups-raw 0 - - The example in Windows Printing to a Local Printer illustrates local Windows + The example in Windows Printing to a Local Printer illustrates local Windows printing. -
+
Windows Printing to a Local Printer. 1small
@@ -714,11 +714,11 @@ application/octet-stream application/vnd.cups-raw 0 - PPD-aware. PPDs are PostScript Printer Description 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 Printing to a PostScript Printer. + there is CUPS. as illustrated in Printing to a PostScript Printer. -
+
Printing to a PostScript Printer. 2small
@@ -742,10 +742,10 @@ application/octet-stream application/vnd.cups-raw 0 - used on UNIX platforms. It is a RIP in software, capable of doing a lot 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 - Ghostscript as a RIP for Non-PostScript Printers. + Ghostscript as a RIP for Non-PostScript Printers. -
+
Ghostscript as a RIP for Non-PostScript Printers. 3small
@@ -1176,11 +1176,11 @@ text/plain application/postscript 33 texttops 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 imagetops filter. Its outcome is always of MIME type application/vnd.cups-postscript (not application/postscript), meaning it has - the print options already embedded into the file. This is shown in Prefiltering in + the print options already embedded into the file. This is shown in Prefiltering in CUPS to Form PostScript. -
+
Prefiltering in CUPS to Form PostScript. 4small
@@ -1202,10 +1202,10 @@ text/plain application/postscript 33 texttops application/vnd.cups-postscript. 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 Adding Device-Specific Print Options. + linkend="f5small">Adding Device-Specific Print Options. -
+
Adding Device-Specific Print Options. 5small
@@ -2213,11 +2213,11 @@ long as Samba has been compiled with CUPS library (libcups) support. If Samba ha support, and if no other print commands are set up, then printing will use the System V AT&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 sysv). This is illustrated in the Printing via +name="classicalprinting">sysv). This is illustrated in the Printing via CUPS/Samba Server diagram. -
+
Printing via CUPS/Samba Server. 13small
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml index 2ff794939c..4781994881 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml @@ -56,9 +56,9 @@ reduced. This works reasonably well if the servers belong to a single domain, an 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 DOMINICUS\FJones must not be given access to the account resources of the user -FRANCISCUS\FJonesSamba local account mode results in both +FRANCISCUS\FJonesSamba local account mode results in both DOMINICUS\FJones and FRANCISCUS\FJones mapping to the UNIX user -FJones. free from inadvertent cross-over, close attention should be given +FJones. free from inadvertent cross-over, close attention should be given to the way that the IDMAP facility is configured. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml index 563550ee9b..58aaa29d17 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml @@ -898,14 +898,14 @@ in &smb.conf; for Not Being a master browser - + &smb.conf; for Not Being a master browser no no no 0 - + diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml index d37edbe17f..a9a81c46e6 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml @@ -80,7 +80,7 @@ to not inflict pain on others. Do your learning on a test network. -single sign-onSSO +single sign-onSSO trust account domainsecurityprotocols @@ -462,7 +462,7 @@ Before we branch into a brief overview of domain control, there are three basic PDC powerful networkperformance -domainmemberserver +domainmemberserver The Primary Domain Controller 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 @@ -486,7 +486,7 @@ database with BDCs. domaincontrollerhierarchy LDAP -accountbackend +accountbackend machine account 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 @@ -500,7 +500,7 @@ LDAP-based user and machine account backend. registry 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.. +Databases. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml index 571ca323ce..48c99c542c 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-ProfileMgmt.xml @@ -571,7 +571,7 @@ and Windows 2003. The UPHClean software package can be downloaded from the User Profile Hive Cleanup -Servicehttp://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en +Servicehttp://www.microsoft.com/downloads/details.aspx?FamilyID=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en web site. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml index 21218ea9da..0a90ff1aa9 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Securing.xml @@ -80,7 +80,7 @@ name="[IPC$]"/> share is used for browsing purposes as well as to establish TCP/ Access Control EntriesACE ACL -controls +controls 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 File, Directory, and Share Access Controls. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml index d1895829a9..ea0ed485c0 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml @@ -1662,7 +1662,7 @@ net rpc share MIGRATE ALL <share-name> -S <source> 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 - . This script is essential to the migration process. + . This script is essential to the migration process. A suitable example script may be obtained from the $SAMBA_SOURCES/examples/scripts 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. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml index adb0ba24d3..33e2697bd3 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml @@ -93,7 +93,7 @@ idmap uid idmap gid idmap backend -LDAP +LDAP 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 diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml b/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml index ee48f8c90d..297585d45d 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-locking.xml @@ -1091,7 +1091,6 @@ tdb(/usr/local/samba_2.2.7/var/locks/locking.tdb): rec_read bad magic - Long Delays Deleting Files over Network with XP SP1 It sometimes takes approximately 35 seconds to delete files over the network after XP SP1 has been applied. -- cgit