-This is version 2.0.X of Samba, the free SMB and CIFS client and
+This is a development version of Samba, the free SMB and CIFS client and
server for unix and other operating systems. Samba is maintained by
the Samba Team, who support the original author, Andrew Tridgell.
>>>> about the configuration and use of Samba.
NOTE: Installation instructions may be found in
- docs/textdocs/UNIX_INSTALL.txt
+ docs/htmldocs/UNIX_INSTALL.html
This software is freely distributable under the GNU public license, a
copy of which you should have received with this software (in a file
please join the mailing list. The Samba team accepts patches
(preferably in "diff -u" format, see docs/BUGS.txt for more details)
and are always glad to receive feedback or suggestions to the address
-samba-bugs@samba.org. We have recently put a new bug tracking
-system into place which should help the throughput quite a lot. You
-can also get the Samba sourcecode straight from the CVS tree - see
+samba@lists.samba.org.
+
+You can also get the Samba sourcecode straight from the CVS tree - see
http://samba.org/cvs.html.
-You could also send hardware/software/money/jewelry or pizza
+You could also send hardware/software/money/jewelry or pre-paid pizza
vouchers directly to Andrew. The pizza vouchers would be especially
welcome, in fact there is a special field in the survey for people who
have paid up their pizza :-)
something else. However, as you can see from the user survey quite a lot of
people do seem to like it at the moment :-)
-Andrew Tridgell
-Email: samba-bugs@samba.org
-
-3 Ballow Crescent
-Macgregor, A.C.T.
-2615 Australia
-
-Samba Team
-Email: samba-bugs@samba.org
-
MORE INFO
=========
MAILING LIST
------------
-There is a mailing list for discussion of Samba. To subscribe send
-mail to listproc@samba.org with a body of "subscribe samba Your Name"
-Please do NOT send this request to the list alias instead.
+Please do NOT send subscription/unsubscription requests to the lists!
-To send mail to everyone on the list mail to samba@listproc.anu.edu.au
+There is a mailing list for discussion of Samba. For details go to
+<http://lists.samba.org/> or send mail to <samba-subscribe@lists.samba.org>
There is also an announcement mailing list where new versions are
-announced. To subscribe send mail to listproc@samba.org with a
-body of "subscribe samba-announce Your Name". All announcements also
-go to the samba list.
+announced. To subscribe go to <http://lists.samba.org/> or send mail
+to <samba-announce-subscribe@lists.samba.org>. All announcements also
+go to the samba list, so you only need to be on one.
For details of other Samba mailing lists and for access to archives, see
-http://lists.samba.org/
+<http://lists.samba.org/>
+
+
+MAILING LIST ETIQUETTE
+----------------------
+
+A few tips when submitting to this or any mailing list.
+
+1. Make your subject short and descriptive. Avoid the words "help" or
+ "Samba" in the subject. The readers of this list already know that
+ a) you need help, and b) you are writing about samba (of course,
+ you may need to distinguish between Samba PDC and other file
+ sharing software). Avoid phrases such as "what is" and "how do
+ i". Some good subject lines might look like "Slow response with
+ Excel files" or "Migrating from Samba PDC to NT PDC".
+
+2. If you include the original message in your reply, trim it so that
+ only the relevant lines, enough to establish context, are
+ included. Chances are (since this is a mailing list) we've already
+ read the original message.
+
+3. Trim irrelevant headers from the original message in your
+ reply. All we need to see is a) From, b) Date, and c) Subject. We
+ don't even really need the Subject, if you haven't changed
+ it. Better yet is to just preface the original message with "On
+ [date] [someone] wrote:".
+
+4. Please don't reply to or argue about spam, spam filters or viruses
+ on any Samba lists. We do have a spam filtering system that is
+ working quite well thank you very much but occasionally unwanted
+ messages slip through. Deal with it.
+
+5. Never say "Me too." It doesn't help anyone solve the
+ problem. Instead, if you ARE having the same problem, give more
+ information. Have you seen something that the other writer hasn't
+ mentioned, which may be helpful?
+
+6. If you ask about a problem, then come up with the solution on your
+ own or through another source, by all means post it. Someone else
+ may have the same problem and is waiting for an answer, but never
+ hears of it.
+
+7. Give as much *relevant* information as possible such as Samba
+ release number, OS, kernel version, etc...
+
+8. RTFM. Google. groups.google.com.
NEWS GROUP