From 42efc1092dcb3042724e280c0bb18e813b3aac98 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Fri, 4 Oct 2002 16:36:40 +0000 Subject: Convert GOTCHAS to SGML (This used to be commit c48207ef0e219680d4e4102256c76189aaf73ebc) --- docs/htmldocs/install.html | 89 ++++++++++++++++++++++++++++++++-------------- 1 file changed, 63 insertions(+), 26 deletions(-) (limited to 'docs/htmldocs/install.html') diff --git a/docs/htmldocs/install.html b/docs/htmldocs/install.html index 97503ad7a7..4b5bf486b9 100644 --- a/docs/htmldocs/install.html +++ b/docs/htmldocs/install.html @@ -5,14 +5,13 @@ >How to Install and Test SAMBAPrev

Chapter 1. How to Install and Test SAMBA

Chapter 1. How to Install and Test SAMBA

1.1. Step 0: Read the man pages

1.1. Step 0: Read the man pages

The man pages distributed with SAMBA contain lots of useful info that will help to get you started. @@ -106,7 +109,9 @@ CLASS="SECT1" >

1.2. Step 1: Building the Binaries

1.2. Step 1: Building the Binaries

To do this, first run the program

1.3. Step 2: The all important step

1.3. Step 2: The all important step

At this stage you must fetch yourself a coffee or other drink you find stimulating. Getting the rest @@ -218,7 +225,9 @@ CLASS="SECT1" >

1.4. Step 3: Create the smb configuration file.

1.4. Step 3: Create the smb configuration file.

There are sample configuration files in the examples subdirectory in the distribution. I suggest you read them @@ -272,7 +281,9 @@ CLASS="SECT1" >

1.5. Step 4: Test your config file with +NAME="AEN74" +>1.5. Step 4: Test your config file with testparm

1.6. Step 5: Starting the smbd and nmbd

1.6. Step 5: Starting the smbd and nmbd

You must choose to start smbd and nmbd either as daemons or from

1.6.1. Step 5a: Starting from inetd.conf

1.6.1. Step 5a: Starting from inetd.conf

NOTE; The following will be different if you use NIS or NIS+ to distributed services maps.

1.6.2. Step 5b. Alternative: starting it as a daemon

1.6.2. Step 5b. Alternative: starting it as a daemon

To start the server as a daemon you should create a script something like this one, perhaps calling @@ -489,7 +506,9 @@ CLASS="SECT1" >

1.7. Step 6: Try listing the shares available on your +NAME="AEN135" +>1.7. Step 6: Try listing the shares available on your server

1.8. Step 7: Try connecting with the unix client

1.8. Step 7: Try connecting with the unix client

1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, +NAME="AEN160" +>1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client

Try mounting disks. eg:

1.10. What If Things Don't Work?

1.10. What If Things Don't Work?

If nothing works and you start to think "who wrote this pile of trash" then I suggest you do step 2 again (and @@ -657,7 +682,9 @@ CLASS="SECT2" >

1.10.1. Diagnosing Problems

1.10.1. Diagnosing Problems

If you have installation problems then go to

1.10.2. Scope IDs

1.10.2. Scope IDs

By default Samba uses a blank scope ID. This means all your windows boxes must also have a blank scope ID. @@ -685,7 +714,9 @@ CLASS="SECT2" >

1.10.3. Choosing the Protocol Level

1.10.3. Choosing the Protocol Level

The SMB protocol has many dialects. Currently Samba supports 5, called CORE, COREPLUS, LANMAN1, @@ -724,7 +755,9 @@ CLASS="SECT2" >

1.10.4. Printing from UNIX to a Client PC

1.10.4. Printing from UNIX to a Client PC

To use a printer that is available via a smb-based server from a unix host with LPR you will need to compile the @@ -743,7 +776,9 @@ CLASS="SECT2" >

1.10.5. Locking

1.10.5. Locking

One area which sometimes causes trouble is locking.

1.10.6. Mapping Usernames

1.10.6. Mapping Usernames

If you have different usernames on the PCs and the unix server then take a look at the "username map" option. @@ -825,7 +862,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" >PrevHome