summaryrefslogtreecommitdiff
path: root/docs/Samba3-HOWTO/TOSHARG-Install.xml
diff options
context:
space:
mode:
authorJohn Terpstra <jht@samba.org>2005-06-16 01:33:35 +0000
committerGerald W. Carter <jerry@samba.org>2008-04-23 08:46:49 -0500
commitfa96398866a4bcdcc13b42ab4f8d3f516cd9238a (patch)
treeca055132ca3289d5b512b8cc3858033be3df3bae /docs/Samba3-HOWTO/TOSHARG-Install.xml
parent77aa4181f19460a6e8b848877edb107c09f574d8 (diff)
downloadsamba-fa96398866a4bcdcc13b42ab4f8d3f516cd9238a.tar.gz
samba-fa96398866a4bcdcc13b42ab4f8d3f516cd9238a.tar.bz2
samba-fa96398866a4bcdcc13b42ab4f8d3f516cd9238a.zip
Stage 1 of PHPTR Edits.
(This used to be commit 64a9e3e8619bf33dcf6b0ff8171b47a3e2581239)
Diffstat (limited to 'docs/Samba3-HOWTO/TOSHARG-Install.xml')
-rw-r--r--docs/Samba3-HOWTO/TOSHARG-Install.xml91
1 files changed, 45 insertions, 46 deletions
diff --git a/docs/Samba3-HOWTO/TOSHARG-Install.xml b/docs/Samba3-HOWTO/TOSHARG-Install.xml
index 1d9445e50b..7ecc33bdce 100644
--- a/docs/Samba3-HOWTO/TOSHARG-Install.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-Install.xml
@@ -19,13 +19,13 @@
<para>
Binary packages of Samba are included in almost any Linux or
UNIX distribution. There are also some packages available at
- <ulink url="http://samba.org/">the Samba home-page</ulink>. Refer to
+ <ulink url="http://samba.org/">the Samba home page</ulink>. Refer to
the manual of your operating system for details on installing packages
for your specific operating system.
</para>
<para>If you need to compile Samba from source, check
- <link linkend="compiling">How to compile Samba.</link>
+ <link linkend="compiling">How to Compile Samba.</link>
</para>
</sect1>
@@ -43,13 +43,13 @@
</para>
<sect2>
- <title>Configuration file syntax</title>
+ <title>Configuration File Syntax</title>
<para>The &smb.conf; file uses the same syntax as the various old
.ini files in Windows 3.1: Each file consists of various sections,
which are started by putting the section name between brackets ([])
- on a new line. Each contains zero or more key/value-pairs separated by an
- equality sign (=). The file is just a plain-text file, so you can
+ on a new line. Each contains zero or more key/value pairs separated by an
+ equality sign (=). The file is just a plaintext file, so you can
open and edit it with your favorite editing tool.</para>
<para>Each section in the &smb.conf; file represents a share
@@ -57,7 +57,7 @@
contains settings that apply to the whole Samba server and not
to one share in particular.</para>
-<para><link linkend="smbconfminimal">Following example</link> contains a very minimal &smb.conf;.
+<para><link linkend="smbconfminimal">A minimal smb.conf</link> contains a very minimal &smb.conf;.
<indexterm><primary>minimal configuration</primary></indexterm>
</para>
@@ -98,8 +98,8 @@
<indexterm><primary>smbd</primary></indexterm>
<indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
This daemon handles all name registration and resolution requests. It is the primary vehicle involved
- in network browsing. It handles all UDP based protocols. The <command>nmbd</command> daemon should
- be the first command started as part of the Samba start-up process.
+ in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
+ be the first command started as part of the Samba startup process.
</para></listitem>
</varlistentry>
@@ -107,8 +107,8 @@
<listitem><para>
<indexterm><primary>nmbd</primary></indexterm>
<indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
- This daemon handles all TCP/IP based connection services for file and print based operations. It also
- manages local authentication. It should be started immediately following the start-up of <command>nmbd</command>.
+ This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
+ manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
</para></listitem>
</varlistentry>
@@ -116,18 +116,18 @@
<listitem><para>
<indexterm><primary>winbindd</primary></indexterm>
<indexterm><primary>starting samba</primary><secondary>winbindd</secondary></indexterm>
- This daemon should be started when Samba is a member of a Windows NT4 or ADS Domain. It is also needed when
- Samba has trust relationships with another Domain. The <command>winbindd</command> daemon will check the
+ This daemon should be started when Samba is a member of a Windows NT4 or ADS domain. It is also needed when
+ Samba has trust relationships with another domain. The <command>winbindd</command> daemon will check the
&smb.conf; file for the presence of the <parameter>idmap uid</parameter> and <parameter>idmap gid</parameter>
- parameters. If they are not found <command>winbindd</command> will bail-out and refuse to start.
+ parameters. If they are not found, <command>winbindd</command> will bail out and refuse to start.
</para></listitem>
</varlistentry>
</variablelist>
<para>
- When Samba has been packaged by an operating system vendor the start-up process is typically a custom feature of its
+ When Samba has been packaged by an operating system vendor, the startup process is typically a custom feature of its
integration into the platform as a whole. Please refer to your operating system platform administration manuals for
- specific information pertaining to correct management of Samba start-up.
+ specific information pertaining to correct management of Samba startup.
</para>
</sect2>
@@ -145,24 +145,22 @@
</para>
<para>
- The simplest useful configuration file would contain something like shown in
- <link linkend="simple-example">the next example</link>.
+ The simplest useful configuration file would contain something like that shown in
+ <link linkend="simple-example">Another simple smb.conf File</link>.
+ <indexterm><primary>simple configuration</primary></indexterm>
</para>
- <para>
- <indexterm><primary>simple configuration</primary></indexterm>
- <example id="simple-example">
- <title>Another simple smb.conf File</title>
- <smbconfblock>
+<example id="simple-example">
+<title>Another simple smb.conf File</title>
+<smbconfblock>
<smbconfsection name="[global]"/>
<smbconfoption name="workgroup">&example.workgroup;</smbconfoption>
<smbconfsection name="[homes]"/>
<smbconfoption name="guest ok">no</smbconfoption>
<smbconfoption name="read only">no</smbconfoption>
- </smbconfblock>
+</smbconfblock>
</example>
- </para>
<para>
This will allow connections by anyone with an account on the server, using either
@@ -177,8 +175,8 @@
<para>
For more information about security settings for the
- <smbconfsection name="[homes]"/> share please refer to
- <link linkend="securing-samba">Securing Samba</link> chapter.
+ <smbconfsection name="[homes]"/> share, please refer to
+ <link linkend="securing-samba">Securing Samba</link>.
</para>
<sect3>
@@ -194,7 +192,7 @@
&rootprompt; testparm /etc/samba/smb.conf
</screen>
- <para>Testparm will parse your configuration file and report
+ <para>testparm will parse your configuration file and report
any unknown parameters or incorrect syntax. </para>
@@ -214,7 +212,7 @@
SWAT is a Web-based interface that can be used to facilitate the configuration of Samba.
SWAT might not be available in the Samba package that shipped with your platform,
but in a separate package. Please read the SWAT man page
- on compiling, installing and configuring SWAT from source.
+ on compiling, installing, and configuring SWAT from source.
</para>
<para>
@@ -226,10 +224,10 @@
<para>
SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote
- machine leaves your connection open to password sniffing as passwords will be sent over the wire in the clear.
+ machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.
</para>
- <para>More information about SWAT can be found in <link linkend="SWAT">corresponding chapter</link>.</para>
+ <para>More information about SWAT can be found in <link linkend="SWAT"></link>.</para>
</sect2>
@@ -239,7 +237,7 @@
<title>List Shares Available on the Server</title>
<para>
- To list shares that are available from the configured Samba server execute the
+ To list shares that are available from the configured Samba server, execute the
following command:
</para>
@@ -251,7 +249,7 @@
something is incorrectly configured. This method can also be used to see what shares
are available on other SMB servers, such as Windows 2000.</para>
- <para>If you choose user-level security you may find that Samba requests a password
+ <para>If you choose user-level security, you may find that Samba requests a password
before it will list the shares. See the <command>smbclient</command> man page for details.
You can force it to list the shares without a password by adding the option
<option>-N</option> to the command line. </para>
@@ -268,7 +266,7 @@
<para>Typically <replaceable>yourhostname</replaceable> is the name of the host on which &smbd;
has been installed. The <replaceable>aservice</replaceable> is any service that has been defined in the &smb.conf;
- file. Try your user name if you just have a <smbconfsection name="[homes]"/> section in the &smb.conf; file.</para>
+ file. Try your username if you just have a <smbconfsection name="[homes]"/> section in the &smb.conf; file.</para>
<para>Example: If the UNIX host is called <replaceable>bambi</replaceable> and a valid login name
is <replaceable>fred</replaceable>, you would type:</para>
@@ -285,15 +283,15 @@
access it from other clients. Within a few minutes, the Samba host
should be listed in the Network Neighborhood on all Windows
clients of its subnet. Try browsing the server from another client
- or 'mounting' it.</para>
+ or "mounting" it.</para>
- <para>Mounting disks from a DOS, Windows or OS/2 client can be done by running a command such as:</para>
+ <para>Mounting disks from a DOS, Windows, or OS/2 client can be done by running a command such as:</para>
<para><screen>
&dosprompt;<userinput>net use d: \\servername\service</userinput>
</screen></para>
- <para>Try printing, e.g.</para>
+ <para>Try printing, for example,</para>
<para>
<screen>
@@ -308,12 +306,13 @@
<sect1>
<title>What If Things Don't Work?</title>
- <para>You might want to read <link linkend="diagnosis">The Samba Checklist</link>.
- If you are still stuck, refer to <link linkend="problems">Analyzing and Solving Samba Problems</link> chapter.
- Samba has been successfully installed at thousands of sites worldwide.
- It is unlikely that your particular problem is unique, so it might be
- productive to perform an Internet search to see if someone else has encountered
- your problem and has found a way to overcome it.</para>
+ <para>
+ You might want to read <link linkend="diagnosis">The Samba Checklist</link>. If you are still
+ stuck, refer to <link linkend="problems">Analyzing and Solving Samba Problems</link>. Samba has
+ been successfully installed at thousands of sites worldwide. It is unlikely that your particular problem is
+ unique, so it might be productive to perform an Internet search to see if someone else has encountered your
+ problem and has found a way to overcome it.
+ </para>
</sect1>
@@ -329,12 +328,12 @@ The following questions and issues are raised repeatedly on the Samba mailing li
<para>
Samba consists of three core programs: &nmbd;, &smbd;, and &winbindd;. &nmbd; is the name server message daemon,
-&smbd; is the server message daemon, and &winbindd; is the daemon that handles communication with Domain Controllers.
+&smbd; is the server message daemon, and &winbindd; is the daemon that handles communication with domain controllers.
</para>
<para>
If Samba is <emphasis>not</emphasis> running as a WINS server, then there will be one single instance of
- &nmbd; running on your system. If it is running as a WINS server then there will be
+ &nmbd; running on your system. If it is running as a WINS server, then there will be
two instances &smbmdash; one to handle the WINS requests.
</para>
@@ -366,11 +365,11 @@ run in <emphasis>split mode</emphasis> (in which case there will be two instance
<title><quote><errorname>The network name cannot be found</errorname></quote></title>
<para>
- This error can be caused by one of these mis-configurations:
+ This error can be caused by one of these misconfigurations:
</para>
<itemizedlist>
- <listitem><para>You specified an non-existing path
+ <listitem><para>You specified a nonexisting path
for the share in &smb.conf;.</para></listitem>
<listitem><para>The user you are trying to access the share with does not