From 8d3a451fd2c1ba831076f0f196c5324db57879a3 Mon Sep 17 00:00:00 2001 From: Christoph Zauner Date: Wed, 11 Jun 2008 14:49:30 +0200 Subject: [PATCH] Samba3-HOWTO: Fix typos. (This used to be commit 2391d999eb733bd8d12631478f4318608225cbb6) --- docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml | 10 +++++----- docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml | 9 ++++++--- docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml | 6 +++--- 3 files changed, 14 insertions(+), 11 deletions(-) diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml b/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml index 48f439deadc..ea68594e241 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml @@ -762,7 +762,7 @@ mystic:/home/hannibal > rm filename Miscellaneous Controls - The parameter documented in Other Controls are often used by administrators + The parameters documented in Other Controls 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. @@ -935,10 +935,10 @@ mystic:/home/hannibal > rm filename ACLs on share Sharing Permissions - On MS Windows NT4/200x/XP 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, + On MS Windows NT4/200x/XP systems, ACLs on the share itself are set using + tools like the MS Explorer. For example, in Windows 200x, right-click on the shared folder, then select Sharing, then click on Permissions. The default - Windows NT4/200x permission allows "Everyone" full control on the share. + Windows NT4/200x permissions allow the group "Everyone" full control on the share. @@ -946,7 +946,7 @@ mystic:/home/hannibal > rm filename MMC tool MS Windows 200x and later versions come with a tool called the Computer Management - snap-in for the MMC. This tool is located by clicking on Control Panel -> + snap-in for the MMC. This tool can be accessed via Control Panel -> Administrative Tools -> Computer Management. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml index 3c86438c2f8..563550ee9bd 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml @@ -1863,9 +1863,12 @@ the DMB (N1_C) with the WINS server as soon as it was started. NetServerEnum2 synchronization browse lists -Once N2_B knows the address of the DMB, it tells it that is the LMB for subnet 2 by sending a -MasterAnnouncement packet as a UDP port 138 packet. It then synchronizes with it by -doing a NetServerEnum2 call. This tells the DMB to send it all the server names it knows +Once N2_B knows the address of the DMB, it tells the DMB that it is the LMB +for subnet 2 by sending the DMB a +MasterAnnouncement packet to UDP port 138. It then +synchronizes with the DMB by +doing a NetServerEnum2 call. This tells the DMB to +send the sender all the server names it knows about. Once the DMB receives the MasterAnnouncement packet, it schedules a synchronization request to the sender of that packet. After both synchronizations are complete, the browse lists look like those in Browse Subnet Example 2 diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml index 8aea1775e35..0b90c925b85 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-ServerType.xml @@ -245,7 +245,7 @@ authentication contexts in this way (WinDD is an example of an application that 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 +not necessarily case-preserving. All Windows NT family systems treat passwords as case-preserving and case-sensitive. @@ -276,8 +276,8 @@ This is the default setting since Samba-2.2.x. 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 +that Samba has to work out what username the client probably wants to use, +because the username is not explicitly sent to the SMB server. 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. -- 2.11.4.GIT