summaryrefslogtreecommitdiff
path: root/docs/faq/sambafaq-1.html
diff options
context:
space:
mode:
authorSamba Release Account <samba-bugs@samba.org>1997-06-08 14:44:43 +0000
committerSamba Release Account <samba-bugs@samba.org>1997-06-08 14:44:43 +0000
commit9b5af2ad79448acc97cd44d9446d4ede9dcdd4b8 (patch)
tree6b702f764a6103a69550c2204e7cb5dcab096ec9 /docs/faq/sambafaq-1.html
parenta811a7914fa6bcc155ac8f624df3ced0e9222d87 (diff)
downloadsamba-9b5af2ad79448acc97cd44d9446d4ede9dcdd4b8.tar.gz
samba-9b5af2ad79448acc97cd44d9446d4ede9dcdd4b8.tar.bz2
samba-9b5af2ad79448acc97cd44d9446d4ede9dcdd4b8.zip
FAQ Update
Tidied up some entries with incorrect casing Added NT SP3 entry Updated list of ported systems Updated More Info entry with more web site details and list of all doco files Moved mailing list subscriptions to separate entry Removed reference to 'samba team mailing list' just in case people guessed Updated nmbd -C entry, indicating obsolete. General cleanup of document with indented lists. Added url links where needed. Web docs will not show urls but will link, text files will show file names AND urls Fixed missing info where '\\' was being interpreted as '\' (used [\\]) If I get a warning before 1.9.17 is released, I'll clean up blank lines from the text faq. Don't want to do them now as I may modify the sgml again. For those who don't know, we now maintain the FAQ as an sgml document, and convert/create html and txt FAQs from that. We use LinuxDoc which is now called SGMLtools. Paul. (This used to be commit 37214555db739a7f4ef683d287fe2febe85fee19)
Diffstat (limited to 'docs/faq/sambafaq-1.html')
-rw-r--r--docs/faq/sambafaq-1.html275
1 files changed, 181 insertions, 94 deletions
diff --git a/docs/faq/sambafaq-1.html b/docs/faq/sambafaq-1.html
index 847c758632..4b9e589e84 100644
--- a/docs/faq/sambafaq-1.html
+++ b/docs/faq/sambafaq-1.html
@@ -20,8 +20,8 @@ details</P>
<P>
<A NAME="introduction"></A>
-</P>
-<P>Samba is a suite of programs which work together to allow clients to
+
+Samba is a suite of programs which work together to allow clients to
access to a server's filespace and printers via the SMB (Server
Message Block) protocol. Initially written for Unix, Samba now also
runs on Netware, OS/2 and VMS.</P>
@@ -37,22 +37,15 @@ flexibility designed to make life easier for administrators.</P>
<P>The components of the suite are (in summary):</P>
<P>
<UL>
-<LI> smbd, the SMB server. This handles actual connections from
-clients, doing all the file, permission and username work</LI>
-<LI>nmbd, the Netbios name server, which helps clients locate
-servers, doing the browsing work and managing domains as this
-capability is being built into Samba</LI>
-<LI>smbclient, the Unix-hosted client program</LI>
-<LI>smbrun, a little 'glue' program to help the server run external
-programs</LI>
-<LI>testprns, a program to test server access to printers</LI>
-<LI>testparms, a program to test the Samba configuration file for
-correctness</LI>
-<LI>smb.conf, the Samba configuration file</LI>
-<LI> smbprint, a sample script to allow a Unix host to use smbclient
-to print to an SMB server</LI>
-<LI> documentation! DON'T neglect to read it - you will save a great
-deal of time!</LI>
+<LI><B>smbd</B>, the SMB server. This handles actual connections from clients, doing all the file, permission and username work</LI>
+<LI><B>nmbd</B>, the Netbios name server, which helps clients locate servers, doing the browsing work and managing domains as this capability is being built into Samba</LI>
+<LI><B>smbclient</B>, the Unix-hosted client program</LI>
+<LI><B>smbrun</B>, a little 'glue' program to help the server run external programs</LI>
+<LI><B>testprns</B>, a program to test server access to printers</LI>
+<LI><B>testparms</B>, a program to test the Samba configuration file for correctness</LI>
+<LI><B>smb.conf</B>, the Samba configuration file</LI>
+<LI><B>smbprint</B>, a sample script to allow a Unix host to use smbclient to print to an SMB server</LI>
+<LI><B>Documentation!</B> DON'T neglect to read it - you will save a great deal of time!</LI>
</UL>
</P>
<P>The suite is supplied with full source (of course!) and is GPLed.</P>
@@ -63,10 +56,10 @@ and this FAQ were originally written by Karl Auer.</P>
<H2><A NAME="ss1.2">1.2 What is the current version of Samba? </A></H2>
-<P>
+<P>
<A NAME="current_version"></A>
-</P>
-<P>At time of writing, the current version was 1.9.16. If you want to be
+
+At time of writing, the current version was 1.9.17. If you want to be
sure check the bottom of the change-log file.
<A HREF="ftp://samba.anu.edu.au/pub/samba/alpha/change-log">ftp://samba.anu.edu.au/pub/samba/alpha/change-log</A></P>
<P>For more information see
@@ -77,8 +70,8 @@ sure check the bottom of the change-log file.
<P>
<A NAME="where"></A>
-</P>
-<P>The Samba suite is available via anonymous ftp from
+
+The Samba suite is available via anonymous ftp from
samba.anu.edu.au. The latest and greatest versions of the suite are in
the directory:</P>
<P>/pub/samba/</P>
@@ -96,8 +89,8 @@ do contain Samba binaries for that platform.</P>
<P>
<A NAME="version_nums"></A>
-</P>
-<P>It is not recommended that you run a version of Samba with the word
+
+It is not recommended that you run a version of Samba with the word
"alpha" in its name unless you know what you are doing and are willing
to do some debugging. Many, many people just get the latest
recommended stable release version and are happy. If you are brave, by
@@ -107,34 +100,34 @@ very stable and safe, and this is mostly due to the policy of many
public releases.</P>
<P>How the scheme works:
<OL>
-<LI>when major changes are made the version number is increased. For
+<LI>When major changes are made the version number is increased. For
example, the transition from 1.9.15 to 1.9.16. However, this version
number will not appear immediately and people should continue to use
1.9.15 for production systems (see next point.)
</LI>
-<LI>just after major changes are made the software is considered
+<LI>Just after major changes are made the software is considered
unstable, and a series of alpha releases are distributed, for example
1.9.16alpha1. These are for testing by those who know what they are
doing. The "alpha" in the filename will hopefully scare off those who
are just looking for the latest version to install.
</LI>
-<LI>when Andrew thinks that the alphas have stabilised to the point
+<LI>When Andrew thinks that the alphas have stabilised to the point
where he would recommend new users install it, he renames it to the
same version number without the alpha, for example 1.9.16.
</LI>
-<LI>inevitably bugs are found in the "stable" releases and minor patch
+<LI>Inevitably bugs are found in the "stable" releases and minor patch
levels are released which give us the pXX series, for example 1.9.16p2.</LI>
</OL>
So the progression goes:
<PRE>
- 1.9.15p7 (production)
- 1.9.15p8 (production)
- 1.9.16alpha1 (test sites only)
- :
- 1.9.16alpha20 (test sites only)
- 1.9.16 (production)
- 1.9.16p1 (production)
+ 1.9.15p7 (production)
+ 1.9.15p8 (production)
+ 1.9.16alpha1 (test sites only)
+ :
+ 1.9.16alpha20 (test sites only)
+ 1.9.16 (production)
+ 1.9.16p1 (production)
</PRE>
The above system means that whenever someone looks at the samba ftp
@@ -147,44 +140,49 @@ version.</P>
<P>
<A NAME="platforms"></A>
-</P>
-<P>Many different platforms have run Samba successfully. The platforms
+
+Many different platforms have run Samba successfully. The platforms
most widely used and thus best tested are Linux and SunOS.</P>
<P>At time of writing, the Makefile claimed support for:
<UL>
-<LI> SunOS</LI>
-<LI> Linux with shadow passwords</LI>
-<LI> Linux without shadow passwords</LI>
-<LI> SOLARIS</LI>
-<LI> SOLARIS 2.2 and above (aka SunOS 5)</LI>
-<LI> SVR4</LI>
-<LI> ULTRIX</LI>
-<LI> OSF1 (alpha only)</LI>
-<LI> OSF1 with NIS and Fast Crypt (alpha only)</LI>
-<LI> OSF1 V2.0 Enhanced Security (alpha only)</LI>
+<LI> A/UX 3.0</LI>
<LI> AIX</LI>
-<LI> BSDI</LI>
-<LI> NetBSD</LI>
-<LI> NetBSD 1.0</LI>
-<LI> SEQUENT</LI>
-<LI> HP-UX</LI>
-<LI> SGI</LI>
-<LI> SGI IRIX 4.x.x</LI>
-<LI> SGI IRIX 5.x.x</LI>
+<LI> Altos Series 386/1000</LI>
+<LI> Amiga</LI>
+<LI> Apollo Domain/OS sr10.3</LI>
+<LI> BSDI </LI>
+<LI> B.O.S. (Bull Operating System)</LI>
+<LI> Cray, Unicos 8.0</LI>
+<LI> Convex</LI>
+<LI> DGUX. </LI>
+<LI> DNIX.</LI>
<LI> FreeBSD</LI>
-<LI> NeXT 3.2 and above</LI>
-<LI> NeXT OS 2.x</LI>
-<LI> NeXT OS 3.0</LI>
-<LI> ISC SVR3V4 (POSIX mode)</LI>
-<LI> ISC SVR3V4 (iBCS2 mode)</LI>
-<LI> A/UX 3.0</LI>
-<LI> SCO with shadow passwords.</LI>
-<LI> SCO with shadow passwords, without YP.</LI>
-<LI> SCO with TCB passwords</LI>
-<LI> SCO 3.2v2 (ODT 1.1) with TCP passwords</LI>
-<LI> intergraph</LI>
-<LI> DGUX</LI>
-<LI> Apollo Domain/OS sr10.3 (BSD4.3)</LI>
+<LI> HP-UX</LI>
+<LI> Intergraph. </LI>
+<LI> Linux with/without shadow passwords and quota</LI>
+<LI> LYNX 2.3.0</LI>
+<LI> MachTen (a unix like system for Macintoshes)</LI>
+<LI> Motorola 88xxx/9xx range of machines</LI>
+<LI> NetBSD</LI>
+<LI> NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</LI>
+<LI> OS/2 using EMX 0.9b</LI>
+<LI> OSF1</LI>
+<LI> QNX 4.22</LI>
+<LI> RiscIX. </LI>
+<LI> RISCOs 5.0B</LI>
+<LI> SEQUENT. </LI>
+<LI> SCO (including: 3.2v2, European dist., OpenServer 5)</LI>
+<LI> SGI.</LI>
+<LI> SMP_DC.OSx v1.1-94c079 on Pyramid S series</LI>
+<LI> SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</LI>
+<LI> SUNOS 4</LI>
+<LI> SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</LI>
+<LI> Sunsoft ISC SVR3V4</LI>
+<LI> SVR4</LI>
+<LI> System V with some berkely extensions (Motorola 88k R32V3.2).</LI>
+<LI> ULTRIX.</LI>
+<LI> UNIXWARE</LI>
+<LI> UXP/DS</LI>
</UL>
</P>
@@ -193,26 +191,115 @@ most widely used and thus best tested are Linux and SunOS.</P>
<P>
<A NAME="more"></A>
+
+There are a number of places to look for more information on Samba, including:
+<UL>
+<LI>Two mailing lists devoted to discussion of Samba-related matters. </LI>
+<LI>The newsgroup, comp.protocols.smb, which has a great deal of discussion on Samba. </LI>
+<LI>The WWW site 'SAMBA Web Pages' at
+<A HREF="http://samba.canberra.edu.au/pub/samba/samba.html">http://samba.canberra.edu.au/pub/samba/samba.html</A> includes:
+<UL>
+<LI>Links to man pages and documentation, including this FAQ</LI>
+<LI>A comprehensive survey of Samba users.</LI>
+<LI>A searchable hypertext archive of the Samba mailing list.</LI>
+<LI>Links to Samba source code, binaries, and mirrors of both.</LI>
+</UL>
+</LI>
+<LI>The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/">ftp://samba.anu.edu.au/pub/samba/docs/</A>
+<UL>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Application_Serving.txt">Application_Serving.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/BROWSING.txt">BROWSING.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/BUGS.txt">BUGS.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/DIAGNOSIS.txt">DIAGNOSIS.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/DNIX.txt">DNIX.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/DOMAIN.txt">DOMAIN.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/DOMAIN_CONTROL.txt">CONTROL.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/ENCRYPTION.txt">ENCRYPTION.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Faxing.txt">Faxing.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/GOTCHAS.txt">GOTCHAS.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/HINTS.txt">HINTS.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/INSTALL.sambatar">INSTALL.sambatar</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/INSTALL.txt">INSTALL.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/MIRRORS">MIRRORS</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/NetBIOS.txt">NetBIOS.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/OS2.txt">OS2.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/PROJECTS">PROJECTS</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Passwords.txt">Passwords.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Printing.txt">Printing.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/README.DCEDFS">README.DCEDFS</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/README.OS2">README.OS2</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/README.jis">README.jis</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/README.sambatar">README.sambatar</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/SCO.txt">SCO.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/SMBTAR.notes">SMBTAR.notes</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Speed.txt">Speed.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Support.txt">Support.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/THANKS">THANKS</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Tracing.txt">Tracing.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/UNIX-SMB.txt">SMB.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/Warp.txt">Warp.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/WinNT.txt">WinNT.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/history">history</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/security_level.txt">level.txt</A></LI>
+<LI>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/docs/wfw_slip.htm">slip.htm</A></LI>
+</UL>
+</LI>
+</UL>
</P>
-<P>There are two mailing lists devoted to discussion of Samba-related
-matters. There is also the newsgroup, comp.protocols.smb, which has a
-great deal of discussion on Samba. There is also a WWW site 'SAMBA Web
-Pages' at
-<A HREF="http://samba.canberra.edu.au/pub/samba/samba.html">http://samba.canberra.edu.au/pub/samba/samba.html</A>, under
-which there is a comprehensive survey of Samba users. Another useful
-resource is the hypertext archive of the Samba mailing list.</P>
-<P>Send email to
-<A HREF="mailto:listproc@samba.anu.edu.au">listproc@samba.anu.edu.au</A>. Make sure the subject line is
-blank, and include the following two lines in the body of the message:</P>
+
+
+<H2><A NAME="ss1.7">1.7 How do I subscribe to the Samba Mailing Lists?</A></H2>
+
<P>
+<A NAME="mailinglist"></A>
+
+Send email to
+<A HREF="mailto:listproc@samba.anu.edu.au">listproc@samba.anu.edu.au</A>. Make sure the subject line is
+blank, and include the following two lines in the body of the message:
<BLOCKQUOTE><CODE>
<PRE>
subscribe samba Firstname Lastname
subscribe samba-announce Firstname Lastname
</PRE>
</CODE></BLOCKQUOTE>
-</P>
-<P>Obviously you should substitute YOUR first name for "Firstname" and
+
+Obviously you should substitute YOUR first name for "Firstname" and
YOUR last name for "Lastname"! Try not to send any signature stuff, it
sometimes confuses the list processor.</P>
<P>The samba list is a digest list - every eight hours or so it
@@ -221,30 +308,30 @@ been received by the list since the last time and sends a copy of this
message to all subscribers.</P>
<P>If you stop being interested in Samba, please send another email to
<A HREF="mailto:listproc@samba.anu.edu.au">listproc@samba.anu.edu.au</A>. Make sure the subject line is blank, and
-include the following two lines in the body of the message:</P>
-<P>
+include the following two lines in the body of the message:
<BLOCKQUOTE><CODE>
<PRE>
unsubscribe samba
unsubscribe samba-announce
</PRE>
</CODE></BLOCKQUOTE>
-</P>
-<P>The <B>From:</B> line in your message <EM>MUST</EM> be the same address you used when
+
+The <B>From:</B> line in your message <EM>MUST</EM> be the same address you used when
you subscribed.</P>
-<H2><A NAME="ss1.7">1.7 Something's gone wrong - what should I do? </A></H2>
+<H2><A NAME="ss1.8">1.8 Something's gone wrong - what should I do? </A></H2>
<P>
<A NAME="wrong"></A>
-</P>
-<P><B><F>#</F> *** IMPORTANT! *** <F>#</F></B></P>
+
+<B><F>#</F> *** IMPORTANT! *** <F>#</F></B></P>
<P>DO NOT post messages on mailing lists or in newsgroups until you have
carried out the first three steps given here!</P>
<P>Firstly, see if there are any likely looking entries in this FAQ! If
you have just installed Samba, have you run through the checklist in
-<A HREF="ftp://samba.anu.edu.au/pub/samba/DIAGNOSIS.txt">DIAGNOSIS.txt</A>? It can save you a lot of time and effort.</P>
+<A HREF="ftp://samba.anu.edu.au/pub/samba/DIAGNOSIS.txt">DIAGNOSIS.txt</A>? It can save you a lot of time and effort.
+DIAGNOSIS.txt can also be found in the docs directory of the Samba distribution.</P>
<P>Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
topics that relate to what you are trying to do.</P>
<P>Thirdly, if there is no obvious solution to hand, try to get a look at
@@ -266,16 +353,16 @@ I can incorporate it in the next version.</P>
so that everyone else gets the benefit of your work. This is one of
the most important aspects to the maintainence of Samba. Send all
patches to
-<A HREF="mailto:samba-bugs@samba.anu.edu.au">samba-bugs@samba.anu.edu.au</A>, not Andrew Tridgell or any
-other individual and not the samba team mailing list.</P>
+<A HREF="mailto:samba-bugs@samba.anu.edu.au">samba-bugs@samba.anu.edu.au</A>. Do not send patches to Andrew Tridgell or any
+other individual, they may be lost if you do.</P>
-<H2><A NAME="ss1.8">1.8 Pizza supply details </A></H2>
+<H2><A NAME="ss1.9">1.9 Pizza supply details </A></H2>
<P>
<A NAME="pizza"></A>
-</P>
-<P>Those who have registered in the Samba survey as "Pizza Factory" will
+
+Those who have registered in the Samba survey as "Pizza Factory" will
already know this, but the rest may need some help. Andrew doesn't ask
for payment, but he does appreciate it when people give him
pizza. This calls for a little organisation when the pizza donor is