Your message dated Tue, 25 Oct 2005 10:27:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line #118403: samba-doc: FAQs have grammar and spelling errors
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Nov 2001 23:30:23 +0000
>From [EMAIL PROTECTED] Mon Nov 05 17:30:23 2001
Return-path: <[EMAIL PROTECTED]>
Received: from mercury.mv.net [199.125.85.40] (root)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 160tC8-0005uc-00; Mon, 05 Nov 2001 17:30:20 -0600
Received: from vanzandt.mv.com (vanzandt.mv.com [207.22.43.76]) by
mercury.mv.net (8.8.8/mem-971025) with ESMTP id SAA06217 for <[EMAIL
PROTECTED]>; Mon, 5 Nov 2001 18:30:09 -0500 (EST)
Received: by vanzandt.mv.com
via sendmail with stdio
id <[EMAIL PROTECTED]> (Debian Smail3.2.0.111)
for [EMAIL PROTECTED]; Sun, 4 Nov 2001 20:45:43 -0500 (EST)
Message-Id: <[EMAIL PROTECTED]>
Date: Sun, 4 Nov 2001 20:45:43 -0500 (EST)
From: "James R. Van Zandt" <[EMAIL PROTECTED]>
Subject: samba-doc: FAQs have grammar and spelling errors (with patch)
To: [EMAIL PROTECTED]
X-Mailer: bug 3.3.9
Delivered-To: [EMAIL PROTECTED]
Package: samba-doc
Version: 2.2.2-1
Severity: normal
I suggest these grammar and spelling fixes.
--- ./docs/docbook/projdoc/UNIX_INSTALL.sgml-orig Sun Nov 4 14:52:59 2001
+++ ./docs/docbook/projdoc/UNIX_INSTALL.sgml Sun Nov 4 15:07:02 2001
@@ -168,7 +168,7 @@
</programlisting></para>
<para>The exact syntax of <filename>/etc/inetd.conf</filename>
- varies between unixes. Look at the other entries in inetd.conf
+ varies among unixes. Look at the other entries in inetd.conf
for a guide.</para>
<para>NOTE: Some unixes already have entries like netbios_ns
@@ -190,7 +190,7 @@
arguments, or you should use a script, and start the script
from <command>inetd</command>.</para>
- <para>Restart <command>inetd</command>, perhaps just send
+ <para>Restart <command>inetd</command>, or perhaps just send
it a HUP. If you have installed an earlier version of <command>
nmbd</command> then you may need to kill nmbd as well.</para>
</sect2>
@@ -326,7 +326,7 @@
<title>Choosing the Protocol Level</title>
<para>The SMB protocol has many dialects. Currently
- Samba supports 5, called CORE, COREPLUS, LANMAN1,
+ Samba supports five, called CORE, COREPLUS, LANMAN1,
LANMAN2 and NT1.</para>
<para>You can choose what maximum protocol to support
@@ -379,7 +379,7 @@
The second is the "deny modes" that are specified when a file
is open.</para>
- <para>Record locking semantics under Unix is very
+ <para>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
@@ -409,7 +409,7 @@
to by a client, but if you set "strict locking = yes" then it
will
make lock checking calls on every read and write. </para>
- <para>You can also disable by range locking completely
+ <para>You can also disable byte range locking completely
using "locking = no". This is useful for those shares that
don't support locking or don't need it (such as cdroms). In
this case Samba fakes the return codes of locking calls to
@@ -426,7 +426,7 @@
This may be useful on a heavily loaded server as the share
modes code is very slow. See also the FAST_SHARE_MODES
option in the Makefile for a way to do full share modes
- very fast using shared memory (if your OS supports it).</para>
+ very quickly using shared memory (if your OS supports
it).</para>
</sect2>
<sect2>
--- ./docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml-orig Sun Nov
4 16:00:11 2001
+++ ./docs/docbook/projdoc/PAM-Authentication-And-Samba.sgml Sun Nov 4
16:04:51 2001
@@ -154,10 +154,10 @@
<para>
Note: PAM allows stacking of authentication mechanisms. It is
-also possible to pass information obtained within on PAM module through
+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 implmentations also
+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 very devoted followers
--- ./docs/faq/Samba-Server-FAQ.sgml-orig Sun Nov 4 14:43:06 2001
+++ ./docs/faq/Samba-Server-FAQ.sgml Sun Nov 4 14:45:16 2001
@@ -296,7 +296,7 @@
is, the problem is most likely name resolution.
If your client has a facility to do so, hardcode a mapping between the
-hosts IP and the name you want to use. For example, with Man Manager
+hosts IP and the name you want to use. For example, with Lan Manager
or Windows for Workgroups you would put a suitable entry in the file
LMHOSTS. If this works, the problem is in the communication between
your client and the netbios name server. If it does not work, then
@@ -319,7 +319,7 @@
The first step is to check the exact name of the service you are
trying to connect to (consult your system administrator). Assuming it
-exists and you specified it correctly (read your client's doco on how
+exists and you specified it correctly (read your client's docs on how
to specify a service name correctly), read on:
<itemize>
--- ./docs/faq/sambafaq.sgml-orig Sun Nov 4 14:43:37 2001
+++ ./docs/faq/sambafaq.sgml Sun Nov 4 14:45:23 2001
@@ -371,7 +371,7 @@
is, the problem is most likely name resolution.
If your client has a facility to do so, hardcode a mapping between the
-hosts IP and the name you want to use. For example, with Man Manager
+hosts IP and the name you want to use. For example, with Lan Manager
or Windows for Workgroups you would put a suitable entry in the file
LMHOSTS. If this works, the problem is in the communication between
your client and the netbios name server. If it does not work, then
@@ -394,7 +394,7 @@
The first step is to check the exact name of the service you are
trying to connect to (consult your system administrator). Assuming it
-exists and you specified it correctly (read your client's doco on how
+exists and you specified it correctly (read your client's docs on how
to specify a service name correctly), read on:
<itemize>
Only Ethernet interfaces have MAC addresses. Other IP interfaces
(like PPP) do not.
--- ./docs/docbook/projdoc/Integrating-with-Windows.sgml-orig Sun Nov 4
15:10:20 2001
+++ ./docs/docbook/projdoc/Integrating-with-Windows.sgml Sun Nov 4
20:38:56 2001
@@ -96,11 +96,11 @@
<para>
-Network packets that are sent over the physical network transport
+Network packets that are sent over the Ethernet physical network transport
layer communicate not via IP addresses but rather using the Media
-Access Control address, or MAC address. IP Addresses are currently
+Access Control address, or MAC address. IP addresses are currently
32 bits in length and are typically presented as four (4) decimal
-numbers that are separated by a dot (or period). eg: 168.192.1.1
+numbers that are separated by dots (or periods). eg: 168.192.1.1
</para>
<para>
@@ -110,7 +110,7 @@
</para>
<para>
-Every network interfrace must have an MAC address. Associated with
+Every network interface must have an MAC address. Associated with
a MAC address there may be one or more IP addresses. There is NO
relationship between an IP address and a MAC address, all such assignments
are arbitary or discretionary in nature. At the most basic level all
@@ -132,7 +132,7 @@
<para>
When the IP address of the destination interface has been
-determined a protocol called ARP/RARP isused to identify
+determined a protocol called ARP/RARP is used to identify
the MAC address of the target interface. ARP stands for Address
Resolution Protocol, and is a broadcast oriented method that
uses UDP (User Datagram Protocol) to send a request to all
@@ -257,12 +257,12 @@
the name service switch infrastructure so that 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 (ie: <command>make
+with appropriate arguments to the make command (i.e.: <command>make
nsswitch/libnss_wins.so</command>). The resulting library should
then be installed in the <filename>/lib</filename> directory and
the "wins" parameter needs to be added to the "hosts:" line in
the <filename>/etc/nsswitch.conf</filename> file. At this point it
-will be possible to ping any MS Windows machine by it's NetBIOS
+will be possible to ping any MS Windows machine by its NetBIOS
machine name, so long as that machine is within the workgroup to
which both the samba machine and the MS Windows machine belong.
</para>
@@ -278,10 +278,10 @@
MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
the "computer name", "machine name", "networking name", "netbios name",
-"SMB name". All terms mean the same thing with the exception of
+and "SMB name". All terms mean the same thing with the exception of
"netbios name" which can apply also to the name of the workgroup or the
domain name. The terms "workgroup" and "domain" are really just a
-simply name with which the machine is associated. All NetBIOS names
+simple name with which the machine is associated. All NetBIOS names
are exactly 16 characters in length. The 16th character is reserved.
It is used to store a one byte value that indicates service level
information for the NetBIOS name that is registered. A NetBIOS machine
@@ -324,8 +324,8 @@
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 *<1c>. A logon request is then sent to each
-IP address that is returned in the enumerated list of IP addresses. Which
-ever machine first replies then ends up providing the logon services.
+IP address that is returned in the enumerated list of IP addresses.
+Whichever machine first replies then ends up providing the logon services.
</para>
<para>
@@ -335,7 +335,7 @@
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 use of
-just a password (known as SHARE MORE security). In most situations
+just a password (known as SHARE MODE 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 MODE security in a WORKGROUP environment, thus requiring use
@@ -366,8 +366,8 @@
<para>
All MS Windows machines employ an in memory buffer in which is
-stored the NetBIOS names and their IP addresses for all external
-machines that that the local machine has communicated with over the
+stored the NetBIOS names and IP addresses for all external
+machines that that machine has communicated with over the
past 10-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.
@@ -377,7 +377,7 @@
If a machine whose name is in the local name cache has been shut
down before the name had been expired and flushed from the cache, then
an attempt to exchange a message with that machine will be subject
-to time-out delays. ie: It's name is in the cache, so a name resolution
+to time-out delays. i.e.: Its name is in the cache, so a name resolution
lookup will succeed, but the machine can not respond. This can be
frustrating for users - but it is a characteristic of the protocol.
</para>
@@ -505,15 +505,15 @@
<para>
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 isdependant on what the NetBIOS
-Node Type parameter is configured to. A Node Type of 0 means use
-NetBIOS broadcast (over UDP broadcast) is first used if the name
+configuration facility. If enabled, an elaborate name resolution sequence
+is followed the precise nature of which is dependant 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.
+lookup are used.
</para>
</sect2>
@@ -563,7 +563,7 @@
<para>
As stated above, MS Windows machines register their NetBIOS names
-(ie: the machine name for each service type in operation) on start
+(i.e.: the machine name for each service type in operation) on start
up. Also, as stated above, 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
@@ -594,7 +594,7 @@
master browser (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-15 minutes an election
-is held to determine which machine will be the master browser. By nature of
+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 domain master browser.
@@ -633,20 +633,20 @@
<sect1>
<title>MS Windows security options and how to configure
-Samba for seemless integration</title>
+Samba for seamless integration</title>
<para>
MS Windows clients may use encrypted passwords as part of a
-challenege/response authentication model (a.k.a. NTLMv1) or
+challenge/response authentication model (a.k.a. NTLMv1) 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 plain text or encrypted, but not both in the same
-authentication requets.
+authentication request.
</para>
<para>
-When encrypted passwords are used a password that has been
+When encrypted passwords are used, a password that has been
entered by the user is encrypted in two ways:
</para>
@@ -659,14 +659,14 @@
and then padded or trucated 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 for the LanMan hash.
+ The resulting 16 bytes form the LanMan hash.
</para></listitem>
</itemizedlist>
<para>
You should refer to the <ulink url="ENCRYPTION.html">
Password Encryption</ulink> chapter in this HOWTO collection
-for more details on the inner workings
+for more details on the inner workings.
</para>
<para>
@@ -679,8 +679,8 @@
<para>
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 SMB protocol
-has a mechanism by which the connection can be re-established using
+use the mapped drive connection that has been dropped, the client
+re-establishes the connection using
a cached copy of the password.
</para>
@@ -710,27 +710,27 @@
By default Samba will lower case the username before attempting
to lookup the user in the database of local system accounts.
Because UNIX usernames conventionally only contain lower case
-character, the <parameter>username level</parameter> parameter
+characters, the <parameter>username level</parameter> parameter
is rarely even needed.
</para>
<para>
-However, password on UNIX systems often make use of mixed case
+However, passwords on UNIX systems often make use of mixed case
characters. This means that in order for a user on a Windows 9x
client to connect to a Samba server using clear text authentication,
the <parameter>password level</parameter> must be set to the maximum
-number of upper case letter which <emphasis>could</emphasis> appear
-is a password. Note that is the server OS uses the traditional
+number of upper case letters which <emphasis>could</emphasis> appear
+in a password. Note that if the server OS uses the traditional
DES version of crypt(), then a <parameter>password level</parameter>
of 8 will result in case insensitive passwords as seen from Windows
users. This will also result in longer login times as Samba
-hash to compute the permutations of the password string and
+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
-where ever Samba is used. There are three configuration possibilities
+whereever Samba is used. There are three configuration possibilities
for support of encrypted passwords:
</para>
@@ -752,9 +752,9 @@
<para>
There are two ways of identifying whether or not a username and
-password pair was valid or not. One uses the reply information provided
+password pair was valid. One uses the reply information provided
as part of the authentication messaging process, the other uses
-just and error code.
+just an error code.
</para>
<para>
@@ -813,9 +813,9 @@
<para>
Use of this mode of authentication does require there to be
a standard Unix account for the user in order to assign
-a uid once the account has been authenticated by the remote
+a UID once the account has been authenticated by the remote
Windows DC. This account can be blocked to prevent logons by
-other than MS Windows clients by things such as setting an invalid
+other than MS Windows clients by means such as setting an invalid
shell in the <filename>/etc/passwd</filename> entry.
</para>
@@ -835,7 +835,7 @@
<para>
This mode of authentication demands that there be on the
-Unix/Linux system both a Unix style account as well as and
+Unix/Linux system both a Unix style account as well as an
smbpasswd entry for the user. The Unix system account can be
locked if required as only the encrypted password will be
used for SMB client authentication.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux vanzandt 2.4.4 #1 Fri May 18 22:35:13 EDT 2001 i686
unknown
---------------------------------------
Received: (at 118403-done) by bugs.debian.org; 25 Oct 2005 08:27:27 +0000
>From [EMAIL PROTECTED] Tue Oct 25 01:27:26 2005
Return-path: <[EMAIL PROTECTED]>
Received: from h02.hostsharing.net (pomo.hostsharing.net) [212.21.77.2]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EUK9W-0000Z0-00; Tue, 25 Oct 2005 01:27:26 -0700
Received: from apu.credativ.de (p50896484.dip.t-dialin.net [80.137.100.132])
(using SSLv3 with cipher RC4-MD5 (128/128 bits))
(No client certificate requested)
by pomo.hostsharing.net (Postfix) with ESMTP id 7842CA002FC
for <[EMAIL PROTECTED]>; Tue, 25 Oct 2005 10:27:29 +0200 (CEST)
Subject: #118403: samba-doc: FAQs have grammar and spelling errors
From: =?ISO-8859-1?Q?No=E8l_K=F6the?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="=-AG4a6LchUYM7qBRTlVYh"
Organization: Debian GNU/Linux, www.debian.org
Date: Tue, 25 Oct 2005 10:27:24 +0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-1.0 required=4.0 tests=BAYES_00,RCVD_IN_DSBL
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--=-AG4a6LchUYM7qBRTlVYh
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hello,
I checked the patch with the 3.0.14a documentation and the errors are
fixed in it. So its fixed in sarge, etch and sid.
thx for reporting.
--=20
No=C3=A8l K=C3=B6the <noel debian.org>
Debian GNU/Linux, www.debian.org
--=-AG4a6LchUYM7qBRTlVYh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBDXexs9/DnDzB9Vu0RAsGUAJ9Br90YAyOrwDrU7idE+7gQ4dW5ZgCdH5Ah
J0LAllrwLbJbxwWpguTdImA=
=/JmS
-----END PGP SIGNATURE-----
--=-AG4a6LchUYM7qBRTlVYh--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
