From 4480ee713f3ebaaf6852c2e3a5967b30e587f7db Mon Sep 17 00:00:00 2001
From: cvs2svn Import User
Date: Fri, 10 Oct 1997 14:46:44 +0000
Subject: [PATCH] This commit was manufactured by cvs2svn to create tag
'samba'.
---
COPYING | 339 --
Manifest | 66 -
README | 152 -
Read-Manifest-Now | 0
Roadmap | 30 -
WHATSNEW.txt | 106 -
docs/NT4_PlainPassword.reg | 11 -
docs/THANKS | 137 -
docs/Win95_PlainPassword.reg | 4 -
docs/announce | 133 -
docs/faq/Samba-Server-FAQ-1.html | 77 -
docs/faq/Samba-Server-FAQ-2.html | 500 ---
docs/faq/Samba-Server-FAQ.html | 88 -
docs/faq/Samba-Server-FAQ.sgml | 492 ---
docs/faq/Samba-meta-FAQ-1.html | 160 -
docs/faq/Samba-meta-FAQ-2.html | 384 --
docs/faq/Samba-meta-FAQ-3.html | 101 -
docs/faq/Samba-meta-FAQ-4.html | 215 --
docs/faq/Samba-meta-FAQ-5.html | 30 -
docs/faq/Samba-meta-FAQ-6.html | 30 -
docs/faq/Samba-meta-FAQ.html | 102 -
docs/faq/Samba-meta-FAQ.sgml | 771 ----
docs/faq/Samba-meta-FAQ.txt | 924 -----
docs/faq/sambafaq-1.html | 392 --
docs/faq/sambafaq-2.html | 239 --
docs/faq/sambafaq-3.html | 322 --
docs/faq/sambafaq-4.html | 37 -
docs/faq/sambafaq-5.html | 30 -
docs/faq/sambafaq.html | 115 -
docs/faq/sambafaq.sgml | 792 ----
docs/faq/sambafaq.txt | 1122 ------
docs/history | 196 -
docs/htmldocs/wfw_slip.htm | 175 -
docs/manpages/nmbd.8 | 231 --
docs/manpages/samba.7 | 202 --
docs/manpages/smb.conf.5 | 3643 -------------------
docs/manpages/smbclient.1 | 1211 -------
docs/manpages/smbd.8 | 428 ---
docs/manpages/smbpasswd.8 | 112 -
docs/manpages/smbrun.1 | 74 -
docs/manpages/smbstatus.1 | 70 -
docs/manpages/smbtar.1 | 179 -
docs/manpages/testparm.1 | 109 -
docs/manpages/testprns.1 | 112 -
docs/samba.lsm | 26 -
docs/textdocs/Application_Serving.txt | 50 -
docs/textdocs/BROWSING.txt | 548 ---
docs/textdocs/BUGS.txt | 135 -
docs/textdocs/DIAGNOSIS.txt | 260 --
docs/textdocs/DNIX.txt | 69 -
docs/textdocs/DOMAIN.txt | 361 --
docs/textdocs/DOMAIN_CONTROL.txt | 108 -
docs/textdocs/ENCRYPTION.txt | 324 --
docs/textdocs/Faxing.txt | 220 --
docs/textdocs/GOTCHAS.txt | 68 -
docs/textdocs/HINTS.txt | 209 --
docs/textdocs/INSTALL.sambatar | 33 -
docs/textdocs/MIRRORS.txt | 90 -
docs/textdocs/NetBIOS.txt | 152 -
docs/textdocs/OS2-Client-HOWTO.txt | 61 -
docs/textdocs/PROJECTS | 88 -
docs/textdocs/Passwords.txt | 46 -
docs/textdocs/Printing.txt | 93 -
docs/textdocs/README.DCEDFS | 78 -
docs/textdocs/README.jis | 149 -
docs/textdocs/README.sambatar | 23 -
docs/textdocs/SCO.txt | 19 -
docs/textdocs/SMBTAR.notes | 46 -
docs/textdocs/Speed.txt | 333 --
docs/textdocs/Support.txt | 1847 ----------
docs/textdocs/Tracing.txt | 93 -
docs/textdocs/UNIX-SMB.txt | 231 --
docs/textdocs/UNIX_INSTALL.txt | 343 --
docs/textdocs/Win95.txt | 74 -
docs/textdocs/WinNT.txt | 74 -
docs/textdocs/security_level.txt | 96 -
examples/README | 11 -
examples/dce-dfs/README | 4 -
examples/dce-dfs/smb.conf | 42 -
examples/misc/extra_smbstatus | 50 -
examples/misc/wall.perl | 69 -
examples/printer-accounting/README | 63 -
examples/printer-accounting/acct-all | 9 -
examples/printer-accounting/acct-sum | 29 -
examples/printer-accounting/hp5-redir | 43 -
examples/printer-accounting/lp-acct | 38 -
examples/printer-accounting/printcap | 22 -
examples/printing/smbprint | 77 -
examples/printing/smbprint.sysv | 52 -
examples/simple/README | 2 -
examples/simple/smb.conf | 167 -
examples/smb.conf.default | 235 --
examples/svr4-startup/README | 24 -
examples/svr4-startup/samba.server | 38 -
examples/thoralf/smb.conf | 152 -
examples/tridge/README | 8 -
examples/tridge/smb.conf | 101 -
examples/tridge/smb.conf.WinNT | 14 -
examples/tridge/smb.conf.fjall | 21 -
examples/tridge/smb.conf.lapland | 14 -
examples/tridge/smb.conf.vittjokk | 14 -
examples/validchars/msdos70.out | 257 --
examples/validchars/nwdos70.out | 257 --
examples/validchars/readme | 101 -
examples/validchars/validchr.c | 123 -
examples/validchars/validchr.com | Bin 9792 -> 0 bytes
packaging/README | 34 -
packaging/SGI/Makefile | 722 ----
packaging/SGI/README | 38 -
packaging/SGI/inetd.sh | 29 -
packaging/SGI/legal_notice.html | 53 -
packaging/SGI/mkman | 22 -
packaging/SGI/mkprintcap.sh | 15 -
packaging/SGI/mkrelease.sh | 25 -
packaging/SGI/printcap | 5 -
packaging/SGI/psfixes.sed | 4 -
packaging/SGI/relnotes.html | 234 --
packaging/SGI/samba.config | 1 -
packaging/SGI/samba.idb | 394 --
packaging/SGI/samba.rc | 42 -
packaging/SGI/samba.spec | 45 -
packaging/SGI/sambalp | 21 -
packaging/SGI/smb.conf | 84 -
packaging/SGI/smbpasswd | 1 -
packaging/SGI/smbprint | 52 -
packaging/Solaris/pkg-specs/Packaging.script | 5 -
packaging/Solaris/pkg-specs/mkprototype | 31 -
packaging/Solaris/pkg-specs/pkginfo | 12 -
packaging/Solaris/pkg-specs/postinstall | 37 -
packaging/Solaris/pkg-specs/postremove | 30 -
source/.cvsignore | 12 -
source/arcfour.c | 91 -
source/arcfour.h | 39 -
source/cgi.c | 163 -
source/change-log | 1878 ----------
source/client/client.c | 4910 -------------------------
source/client/clientutil.c | 1040 ------
source/client/clitar.c | 1771 ---------
source/codepages/codepage_def.437 | 70 -
source/codepages/codepage_def.850 | 54 -
source/codepages/codepage_def.852 | 63 -
source/codepages/codepage_def.932 | 24 -
source/include/byteorder.h | 200 -
source/include/charset.h | 75 -
source/include/clitar.h | 17 -
source/include/includes.h | 1290 -------
source/include/kanji.h | 133 -
source/include/local.h | 167 -
source/include/nameserv.h | 427 ---
source/include/nterr.h | 505 ---
source/include/proto.h | 1057 ------
source/include/smb.h | 1694 ---------
source/include/trans2.h | 251 --
source/include/version.h | 1 -
source/include/vt_mode.h | 48 -
source/internals.doc | 212 --
source/lib/access.c | 289 --
source/lib/charcnv.c | 164 -
source/lib/charset.c | 383 --
source/lib/fault.c | 82 -
source/lib/getsmbpass.c | 165 -
source/lib/interface.c | 457 ---
source/lib/kanji.c | 868 -----
source/lib/md4.c | 171 -
source/lib/replace.c | 325 --
source/lib/system.c | 413 ---
source/lib/time.c | 495 ---
source/lib/ufc.c | 782 ----
source/lib/username.c | 324 --
source/lib/util.c | 4392 ----------------------
source/libsmb/credentials.c | 101 -
source/libsmb/namequery.c | 295 --
source/libsmb/nmblib.c | 731 ----
source/libsmb/smbdes.c | 320 --
source/libsmb/smbencrypt.c | 111 -
source/locking/locking.c | 1535 --------
source/locking/shmem.c | 844 -----
source/lsaparse.c | 468 ---
source/nameannounce.c | 528 ---
source/nameannounce.doc | 265 --
source/namebrowse.c | 246 --
source/namebrowse.doc | 149 -
source/nameconf.c | 350 --
source/namedbname.c | 601 ---
source/namedbname.doc | 182 -
source/namedbresp.c | 166 -
source/namedbresp.doc | 100 -
source/namedbserver.c | 212 --
source/namedbsubnet.c | 367 --
source/namedbwork.c | 245 --
source/nameelect.c | 855 -----
source/nameelect.doc | 256 --
source/namelogon.c | 145 -
source/namelogon.doc | 36 -
source/namepacket.c | 637 ----
source/namepacket.doc | 133 -
source/namequery.doc | 83 -
source/nameresp.c | 324 --
source/nameresp.doc | 178 -
source/nameserv.c | 506 ---
source/nameserv.doc | 159 -
source/nameservreply.c | 667 ----
source/nameservreply.doc | 213 --
source/nameservresp.c | 848 -----
source/nameservresp.doc | 191 -
source/namework.c | 723 ----
source/namework.doc | 363 --
source/nmbd/nmbd.c | 647 ----
source/nmbsync.c | 191 -
source/param/loadparm.c | 2361 ------------
source/param/params.c | 566 ---
source/passdb/smbpass.c | 293 --
source/printing/pcap.c | 381 --
source/printing/printing.c | 1102 ------
source/script/addtosmbpass | 74 -
source/script/installbin.sh | 44 -
source/script/installcp.sh | 36 -
source/script/installman.sh | 38 -
source/script/installscripts.sh | 43 -
source/script/mkproto.awk | 82 -
source/script/mksmbpasswd.sh | 6 -
source/script/revert.sh | 15 -
source/script/smbtar | 140 -
source/script/uninstallbin.sh | 43 -
source/script/uninstallcp.sh | 33 -
source/script/uninstallman.sh | 31 -
source/script/uninstallscripts.sh | 37 -
source/script/updatesmbpasswd.sh | 14 -
source/smbadduser | 74 -
source/smbd/chgpasswd.c | 400 --
source/smbd/dir.c | 996 -----
source/smbd/ipc.c | 3133 ----------------
source/smbd/mangle.c | 673 ----
source/smbd/message.c | 201 --
source/smbd/password.c | 1707 ---------
source/smbd/pipes.c | 1196 ------
source/smbd/predict.c | 158 -
source/smbd/quotas.c | 657 ----
source/smbd/reply.c | 3821 --------------------
source/smbd/server.c | 5024 --------------------------
source/smbd/smbrun.c | 97 -
source/smbd/trans2.c | 1794 ---------
source/smbd/uid.c | 478 ---
source/smbd/vt_mode.c | 490 ---
source/smbparse.c | 551 ---
source/utils/make_smbcodepage.c | 472 ---
source/utils/nmblookup.c | 241 --
source/utils/smbpasswd.c | 581 ---
source/utils/status.c | 526 ---
source/utils/testparm.c | 112 -
source/utils/testprns.c | 72 -
source/web/cgi.c | 163 -
source/wsmbconf.c | 251 --
source/wsmbstatus.c | 87 -
254 files changed, 94730 deletions(-)
delete mode 100644 COPYING
delete mode 100644 Manifest
delete mode 100644 README
delete mode 100644 Read-Manifest-Now
delete mode 100644 Roadmap
delete mode 100644 WHATSNEW.txt
delete mode 100644 docs/NT4_PlainPassword.reg
delete mode 100644 docs/THANKS
delete mode 100644 docs/Win95_PlainPassword.reg
delete mode 100644 docs/announce
delete mode 100644 docs/faq/Samba-Server-FAQ-1.html
delete mode 100644 docs/faq/Samba-Server-FAQ-2.html
delete mode 100644 docs/faq/Samba-Server-FAQ.html
delete mode 100644 docs/faq/Samba-Server-FAQ.sgml
delete mode 100644 docs/faq/Samba-meta-FAQ-1.html
delete mode 100644 docs/faq/Samba-meta-FAQ-2.html
delete mode 100644 docs/faq/Samba-meta-FAQ-3.html
delete mode 100644 docs/faq/Samba-meta-FAQ-4.html
delete mode 100644 docs/faq/Samba-meta-FAQ-5.html
delete mode 100644 docs/faq/Samba-meta-FAQ-6.html
delete mode 100644 docs/faq/Samba-meta-FAQ.html
delete mode 100644 docs/faq/Samba-meta-FAQ.sgml
delete mode 100644 docs/faq/Samba-meta-FAQ.txt
delete mode 100644 docs/faq/sambafaq-1.html
delete mode 100644 docs/faq/sambafaq-2.html
delete mode 100644 docs/faq/sambafaq-3.html
delete mode 100644 docs/faq/sambafaq-4.html
delete mode 100644 docs/faq/sambafaq-5.html
delete mode 100644 docs/faq/sambafaq.html
delete mode 100644 docs/faq/sambafaq.sgml
delete mode 100644 docs/faq/sambafaq.txt
delete mode 100644 docs/history
delete mode 100644 docs/htmldocs/wfw_slip.htm
delete mode 100644 docs/manpages/nmbd.8
delete mode 100644 docs/manpages/samba.7
delete mode 100644 docs/manpages/smb.conf.5
delete mode 100644 docs/manpages/smbclient.1
delete mode 100644 docs/manpages/smbd.8
delete mode 100644 docs/manpages/smbpasswd.8
delete mode 100644 docs/manpages/smbrun.1
delete mode 100644 docs/manpages/smbstatus.1
delete mode 100644 docs/manpages/smbtar.1
delete mode 100644 docs/manpages/testparm.1
delete mode 100644 docs/manpages/testprns.1
delete mode 100644 docs/samba.lsm
delete mode 100644 docs/textdocs/Application_Serving.txt
delete mode 100644 docs/textdocs/BROWSING.txt
delete mode 100644 docs/textdocs/BUGS.txt
delete mode 100644 docs/textdocs/DIAGNOSIS.txt
delete mode 100644 docs/textdocs/DNIX.txt
delete mode 100644 docs/textdocs/DOMAIN.txt
delete mode 100644 docs/textdocs/DOMAIN_CONTROL.txt
delete mode 100644 docs/textdocs/ENCRYPTION.txt
delete mode 100644 docs/textdocs/Faxing.txt
delete mode 100644 docs/textdocs/GOTCHAS.txt
delete mode 100644 docs/textdocs/HINTS.txt
delete mode 100644 docs/textdocs/INSTALL.sambatar
delete mode 100755 docs/textdocs/MIRRORS.txt
delete mode 100644 docs/textdocs/NetBIOS.txt
delete mode 100644 docs/textdocs/OS2-Client-HOWTO.txt
delete mode 100644 docs/textdocs/PROJECTS
delete mode 100644 docs/textdocs/Passwords.txt
delete mode 100644 docs/textdocs/Printing.txt
delete mode 100644 docs/textdocs/README.DCEDFS
delete mode 100644 docs/textdocs/README.jis
delete mode 100644 docs/textdocs/README.sambatar
delete mode 100644 docs/textdocs/SCO.txt
delete mode 100644 docs/textdocs/SMBTAR.notes
delete mode 100644 docs/textdocs/Speed.txt
delete mode 100644 docs/textdocs/Support.txt
delete mode 100644 docs/textdocs/Tracing.txt
delete mode 100644 docs/textdocs/UNIX-SMB.txt
delete mode 100644 docs/textdocs/UNIX_INSTALL.txt
delete mode 100644 docs/textdocs/Win95.txt
delete mode 100644 docs/textdocs/WinNT.txt
delete mode 100644 docs/textdocs/security_level.txt
delete mode 100644 examples/README
delete mode 100644 examples/dce-dfs/README
delete mode 100644 examples/dce-dfs/smb.conf
delete mode 100644 examples/misc/extra_smbstatus
delete mode 100644 examples/misc/wall.perl
delete mode 100644 examples/printer-accounting/README
delete mode 100644 examples/printer-accounting/acct-all
delete mode 100644 examples/printer-accounting/acct-sum
delete mode 100644 examples/printer-accounting/hp5-redir
delete mode 100644 examples/printer-accounting/lp-acct
delete mode 100644 examples/printer-accounting/printcap
delete mode 100755 examples/printing/smbprint
delete mode 100644 examples/printing/smbprint.sysv
delete mode 100644 examples/simple/README
delete mode 100644 examples/simple/smb.conf
delete mode 100644 examples/smb.conf.default
delete mode 100644 examples/svr4-startup/README
delete mode 100755 examples/svr4-startup/samba.server
delete mode 100644 examples/thoralf/smb.conf
delete mode 100644 examples/tridge/README
delete mode 100644 examples/tridge/smb.conf
delete mode 100644 examples/tridge/smb.conf.WinNT
delete mode 100644 examples/tridge/smb.conf.fjall
delete mode 100644 examples/tridge/smb.conf.lapland
delete mode 100644 examples/tridge/smb.conf.vittjokk
delete mode 100644 examples/validchars/msdos70.out
delete mode 100644 examples/validchars/nwdos70.out
delete mode 100644 examples/validchars/readme
delete mode 100644 examples/validchars/validchr.c
delete mode 100644 examples/validchars/validchr.com
delete mode 100644 packaging/README
delete mode 100644 packaging/SGI/Makefile
delete mode 100644 packaging/SGI/README
delete mode 100755 packaging/SGI/inetd.sh
delete mode 100644 packaging/SGI/legal_notice.html
delete mode 100755 packaging/SGI/mkman
delete mode 100755 packaging/SGI/mkprintcap.sh
delete mode 100755 packaging/SGI/mkrelease.sh
delete mode 100644 packaging/SGI/printcap
delete mode 100644 packaging/SGI/psfixes.sed
delete mode 100644 packaging/SGI/relnotes.html
delete mode 100644 packaging/SGI/samba.config
delete mode 100644 packaging/SGI/samba.idb
delete mode 100644 packaging/SGI/samba.rc
delete mode 100644 packaging/SGI/samba.spec
delete mode 100644 packaging/SGI/sambalp
delete mode 100644 packaging/SGI/smb.conf
delete mode 100644 packaging/SGI/smbpasswd
delete mode 100644 packaging/SGI/smbprint
delete mode 100644 packaging/Solaris/pkg-specs/Packaging.script
delete mode 100644 packaging/Solaris/pkg-specs/mkprototype
delete mode 100644 packaging/Solaris/pkg-specs/pkginfo
delete mode 100644 packaging/Solaris/pkg-specs/postinstall
delete mode 100644 packaging/Solaris/pkg-specs/postremove
delete mode 100644 source/.cvsignore
delete mode 100644 source/arcfour.c
delete mode 100644 source/arcfour.h
delete mode 100644 source/cgi.c
delete mode 100644 source/change-log
delete mode 100644 source/client/client.c
delete mode 100644 source/client/clientutil.c
delete mode 100644 source/client/clitar.c
delete mode 100644 source/codepages/codepage_def.437
delete mode 100644 source/codepages/codepage_def.850
delete mode 100644 source/codepages/codepage_def.852
delete mode 100644 source/codepages/codepage_def.932
delete mode 100644 source/include/byteorder.h
delete mode 100644 source/include/charset.h
delete mode 100644 source/include/clitar.h
delete mode 100644 source/include/includes.h
delete mode 100644 source/include/kanji.h
delete mode 100644 source/include/local.h
delete mode 100644 source/include/nameserv.h
delete mode 100644 source/include/nterr.h
delete mode 100644 source/include/proto.h
delete mode 100644 source/include/smb.h
delete mode 100644 source/include/trans2.h
delete mode 100644 source/include/version.h
delete mode 100644 source/include/vt_mode.h
delete mode 100644 source/internals.doc
delete mode 100644 source/lib/access.c
delete mode 100644 source/lib/charcnv.c
delete mode 100644 source/lib/charset.c
delete mode 100644 source/lib/fault.c
delete mode 100644 source/lib/getsmbpass.c
delete mode 100644 source/lib/interface.c
delete mode 100644 source/lib/kanji.c
delete mode 100644 source/lib/md4.c
delete mode 100644 source/lib/replace.c
delete mode 100644 source/lib/system.c
delete mode 100644 source/lib/time.c
delete mode 100644 source/lib/ufc.c
delete mode 100644 source/lib/username.c
delete mode 100644 source/lib/util.c
delete mode 100644 source/libsmb/credentials.c
delete mode 100644 source/libsmb/namequery.c
delete mode 100644 source/libsmb/nmblib.c
delete mode 100644 source/libsmb/smbdes.c
delete mode 100644 source/libsmb/smbencrypt.c
delete mode 100644 source/locking/locking.c
delete mode 100644 source/locking/shmem.c
delete mode 100644 source/lsaparse.c
delete mode 100644 source/nameannounce.c
delete mode 100644 source/nameannounce.doc
delete mode 100644 source/namebrowse.c
delete mode 100644 source/namebrowse.doc
delete mode 100644 source/nameconf.c
delete mode 100644 source/namedbname.c
delete mode 100644 source/namedbname.doc
delete mode 100644 source/namedbresp.c
delete mode 100644 source/namedbresp.doc
delete mode 100644 source/namedbserver.c
delete mode 100644 source/namedbsubnet.c
delete mode 100644 source/namedbwork.c
delete mode 100644 source/nameelect.c
delete mode 100644 source/nameelect.doc
delete mode 100644 source/namelogon.c
delete mode 100644 source/namelogon.doc
delete mode 100644 source/namepacket.c
delete mode 100644 source/namepacket.doc
delete mode 100644 source/namequery.doc
delete mode 100644 source/nameresp.c
delete mode 100644 source/nameresp.doc
delete mode 100644 source/nameserv.c
delete mode 100644 source/nameserv.doc
delete mode 100644 source/nameservreply.c
delete mode 100644 source/nameservreply.doc
delete mode 100644 source/nameservresp.c
delete mode 100644 source/nameservresp.doc
delete mode 100644 source/namework.c
delete mode 100644 source/namework.doc
delete mode 100644 source/nmbd/nmbd.c
delete mode 100644 source/nmbsync.c
delete mode 100644 source/param/loadparm.c
delete mode 100644 source/param/params.c
delete mode 100644 source/passdb/smbpass.c
delete mode 100644 source/printing/pcap.c
delete mode 100644 source/printing/printing.c
delete mode 100644 source/script/addtosmbpass
delete mode 100755 source/script/installbin.sh
delete mode 100755 source/script/installcp.sh
delete mode 100755 source/script/installman.sh
delete mode 100755 source/script/installscripts.sh
delete mode 100644 source/script/mkproto.awk
delete mode 100755 source/script/mksmbpasswd.sh
delete mode 100755 source/script/revert.sh
delete mode 100644 source/script/smbtar
delete mode 100755 source/script/uninstallbin.sh
delete mode 100755 source/script/uninstallcp.sh
delete mode 100755 source/script/uninstallman.sh
delete mode 100755 source/script/uninstallscripts.sh
delete mode 100755 source/script/updatesmbpasswd.sh
delete mode 100755 source/smbadduser
delete mode 100644 source/smbd/chgpasswd.c
delete mode 100644 source/smbd/dir.c
delete mode 100644 source/smbd/ipc.c
delete mode 100644 source/smbd/mangle.c
delete mode 100644 source/smbd/message.c
delete mode 100644 source/smbd/password.c
delete mode 100644 source/smbd/pipes.c
delete mode 100644 source/smbd/predict.c
delete mode 100644 source/smbd/quotas.c
delete mode 100644 source/smbd/reply.c
delete mode 100644 source/smbd/server.c
delete mode 100644 source/smbd/smbrun.c
delete mode 100644 source/smbd/trans2.c
delete mode 100644 source/smbd/uid.c
delete mode 100644 source/smbd/vt_mode.c
delete mode 100644 source/smbparse.c
delete mode 100644 source/utils/make_smbcodepage.c
delete mode 100644 source/utils/nmblookup.c
delete mode 100644 source/utils/smbpasswd.c
delete mode 100644 source/utils/status.c
delete mode 100644 source/utils/testparm.c
delete mode 100644 source/utils/testprns.c
delete mode 100644 source/web/cgi.c
delete mode 100644 source/wsmbconf.c
delete mode 100644 source/wsmbstatus.c
diff --git a/COPYING b/COPYING
deleted file mode 100644
index a43ea2126fb..00000000000
--- a/COPYING
+++ /dev/null
@@ -1,339 +0,0 @@
- GNU GENERAL PUBLIC LICENSE
- Version 2, June 1991
-
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 675 Mass Ave, Cambridge, MA 02139, USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
- Preamble
-
- The licenses for most software are designed to take away your
-freedom to share and change it. By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users. This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it. (Some other Free Software Foundation software is covered by
-the GNU Library General Public License instead.) You can apply it to
-your programs, too.
-
- When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
- To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
- For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have. You must make sure that they, too, receive or can get the
-source code. And you must show them these terms so they know their
-rights.
-
- We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
- Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software. If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
- Finally, any free program is threatened constantly by software
-patents. We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary. To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
- The precise terms and conditions for copying, distribution and
-modification follow.
-
- GNU GENERAL PUBLIC LICENSE
- TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
- 0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License. The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language. (Hereinafter, translation is included without limitation in
-the term "modification".) Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope. The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
- 1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
- 2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
- a) You must cause the modified files to carry prominent notices
- stating that you changed the files and the date of any change.
-
- b) You must cause any work that you distribute or publish, that in
- whole or in part contains or is derived from the Program or any
- part thereof, to be licensed as a whole at no charge to all third
- parties under the terms of this License.
-
- c) If the modified program normally reads commands interactively
- when run, you must cause it, when started running for such
- interactive use in the most ordinary way, to print or display an
- announcement including an appropriate copyright notice and a
- notice that there is no warranty (or else, saying that you provide
- a warranty) and that users may redistribute the program under
- these conditions, and telling the user how to view a copy of this
- License. (Exception: if the Program itself is interactive but
- does not normally print such an announcement, your work based on
- the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole. If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works. But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
- 3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
- a) Accompany it with the complete corresponding machine-readable
- source code, which must be distributed under the terms of Sections
- 1 and 2 above on a medium customarily used for software interchange; or,
-
- b) Accompany it with a written offer, valid for at least three
- years, to give any third party, for a charge no more than your
- cost of physically performing source distribution, a complete
- machine-readable copy of the corresponding source code, to be
- distributed under the terms of Sections 1 and 2 above on a medium
- customarily used for software interchange; or,
-
- c) Accompany it with the information you received as to the offer
- to distribute corresponding source code. (This alternative is
- allowed only for noncommercial distribution and only if you
- received the program in object code or executable form with such
- an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it. For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable. However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
- 4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License. Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
- 5. You are not required to accept this License, since you have not
-signed it. However, nothing else grants you permission to modify or
-distribute the Program or its derivative works. These actions are
-prohibited by law if you do not accept this License. Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
- 6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions. You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
- 7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all. For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices. Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
- 8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded. In such case, this License incorporates
-the limitation as if written in the body of this License.
-
- 9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time. Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation. If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
- 10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission. For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this. Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
- NO WARRANTY
-
- 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
- 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
- END OF TERMS AND CONDITIONS
-
- Appendix: How to Apply These Terms to Your New Programs
-
- If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
- To do so, attach the following notices to the program. It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-
- Copyright (C) 19yy
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
- Gnomovision version 69, Copyright (C) 19yy name of author
- Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
- This is free software, and you are welcome to redistribute it
- under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License. Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. Here is a sample; alter the names:
-
- Yoyodyne, Inc., hereby disclaims all copyright interest in the program
- `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
- , 1 April 1989
- Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs. If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library. If this is what you want to do, use the GNU Library General
-Public License instead of this License.
diff --git a/Manifest b/Manifest
deleted file mode 100644
index 7e8dc0106f6..00000000000
--- a/Manifest
+++ /dev/null
@@ -1,66 +0,0 @@
-Copyright (C) 1997 - Samba-Team
-
-The Samba package you have just unpacked contains the following:
-
-Directory Notes:
-========= ======
-docs (Samba Documentation):
---------------------------------------
-
- The Samba documentation for 1.9.17 has had some of its content
- updated and a new structure has been put in place. However, since
- this is all rather new the documentation format of previous
- versions will remain in place.
-
- Note in particular two files - _INSTALL.txt and DIAGNOSIS.txt
- There is the potential for there to be many *INSTALL.txt files, one
- for each OS that Samba supports. However we are moving all this into
- the new structure. For now, most people will be using UNIX_INSTALL.txt.
-
- You pay close attention to all the files with a
- .txt extension. Most problems can be solved by reference to the
- two files mentioned.
-
- The new documentation can be accessed starting from Samba-meta-FAQ.html,
- in the docs/faq directory. This is incomplete, but to quote from the
- abstract, it:
-
- "contains overview information for the Samba suite of programs,
- a quick-start guide, and pointers to all other Samba documentation.
- Other FAQs exist for specific client and server issues, and HOWTO
- documents for more extended topics to do with Samba software."
-
-
-examples (Example configuration files):
-----------------------------------------------
- Please pay close attention to the reference smb.conf file
- smb.conf.default that has now been included as the master guide.
-
- Do read the smb.conf manual page in considering what settings are
- appropriate for your site.
-
-
-packaging (Only for those wishing to build binary distributions):
------------------------------------------------------------------------
- Currently support is included only for RedHat Linux. We hope that
- other Unix OS vendors will contribute their binary distribution
- packaging control files - and we hope to make their binary packages
- available on the master ftp site under:
- samba.anu.edu.au/pub/samba/Binary_Packages/"OS_Vendor"
-
-
-source (The official Samba source files - expect more of these!):
---------------------------------------------------------------------------
- To build your own binary files you will need a suitable ansi C
- compiler. Also, you must edit the enclosed "Makefile" as required
- for your operating system platform. Then just run:
- a) make
- b) make install
- then
- c) set up your configuration files.
-
- NOTE: OS Vendors who provide Samba binary packages will generally
- integrate all Samba files into their preferred directory locations.
- These may differ from the default location ALWAYS used by the Samba
- sources. Please be careful when upgrading a vendor provided binary
- distribution from files you have built yourself.
diff --git a/README b/README
deleted file mode 100644
index 30103241841..00000000000
--- a/README
+++ /dev/null
@@ -1,152 +0,0 @@
-This is version 1.9.17 of Samba, the free SMB client and server for unix
-and other operating systems. Samba is maintained by the Samba Team,
-who support the original author, Andrew Tridgell.
-
->>>> Please read THE WHOLE of this file as it gives important information
->>>> about the configuration and use of Samba.
-
-This software is freely distributable under the GNU public license, a
-copy of which you should have received with this software (in a file
-called COPYING).
-
-WHAT IS SMB?
-============
-
-This is a big question.
-
-The very short answer is that it is the protocol by which a lot of
-PC-related machines share files and printers and other informatiuon
-such as lists of available files and printers. Operating systems that
-support this natively include Windows NT, OS/2, and Linux and add on
-packages that achieve the same thing are available for DOS, Windows,
-VMS, Unix of all kinds, MVS, and more. Apple Macs and some Web Browsers
-can speak this protocol as well. Alternatives to SMB include
-Netware, NFS, Appletalk, Banyan Vines, Decnet etc; many of these have
-advantages but none are both public specifications and widely
-implemented in desktop machines by default.
-
-The Common Internet Filesystem is what the new SMB initiative is
-called. For details watch http://samba.anu.edu.au/cifs.
-
-WHAT CAN SAMBA DO?
-==================
-
-Here is a very short list of what samba includes, and what it does.
-
-- a SMB server, to provide Windows NT and LAN Manager-style file and print
- services to SMB clients such as Windows 95, Warp Server, smbfs and others.
-
-- a Netbios (rfc1001/1002) nameserver, which among other things gives
- browsing support. Samba can be the master browser on your LAN if you wish.
-
-- a ftp-like SMB client so you can access PC resources (disks and
-printers) from unix, Netware and other operating systems
-
-- a tar extension to the client for backing up PCs
-
-For a much better overview have a look at the web site at
-http://samba.anu.edu.au/samba, and browse the user survey.
-
-Related packages include:
-
-- smbfs, a linux-only filesystem allowing you to mount remote SMB
-filesystems from PCs on your linux box. This is included as standard with
-Linux 2.0 and later.
-
-- tcpdump-smb, a extension to tcpdump to allow you to investigate SMB
-networking problems over netbeui and tcp/ip.
-
-- smblib, a library of smb functions which are designed to make it
-easy to smb-ise any particular application. See
-ftp://samba.anu.edu.au/pub/samba/smblib.
-
-CONTRIBUTIONS
-=============
-
-If you want to contribute to the development of the software then
-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.anu.edu.au.
-
-You could also send hardware/software/money/jewelry or 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 :-)
-
-If you like a particular feature then look through the change-log and
-see who added it, then send them an email.
-
-Remember that free software of this kind lives or dies by the response
-we get. If noone tells us they like it then we'll probably move onto
-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.anu.edu.au
-
-3 Ballow Crescent
-Macgregor, A.C.T.
-2615 Australia
-
-Samba Team
-Email: samba-bugs@samba.anu.edu.au
-
-MORE INFO
-=========
-
-DOCUMENTATION
--------------
-
-There is quite a bit of documentation included with the package,
-including man pages, and lots of .txt files with hints and useful
-info. This is also available from the web page. There is a growing
-collection of information under docs/faq; by the next release expect
-this to be the default starting point.
-
-FTP SITE
---------
-
-Please use a mirror site! The list of mirrors is in docs/MIRRORS.txt.
-The master ftp site is samba.anu.edu.au in the directory pub/samba.
-
-MAILING LIST
-------------
-
-There is a mailing list for discussion of Samba. To subscribe send
-mail to listproc@samba.anu.edu.au with a body of "subscribe samba Your Name"
-Please do NOT send this request to the list alias instead.
-
-To send mail to everyone on the list mail to samba@listproc.anu.edu.au
-
-There is also an announcement mailing list where new versions are
-announced. To subscribe send mail to listproc@samba.anu.edu.au with a
-body of "subscribe samba-announce Your Name". All announcements also
-go to the samba list.
-
-
-NEWS GROUP
-----------
-
-You might also like to look at the usenet news group
-comp.protocols.smb as it often contains lots of useful info and is
-frequented by lots of Samba users. The newsgroup was initially setup
-by people on the Samba mailing list. It is not, however, exclusive to
-Samba, it is a forum for discussing the SMB protocol (which Samba
-implements). The samba list is gatewayed to this newsgroup.
-
-
-WEB SITE
---------
-
-A Samba WWW site has been setup with lots of useful info. Connect to:
-
-http://samba.anu.edu.au/samba/
-
-As well as general information and documentation, this also has searchable
-archives of the mailing list and a user survey that shows who else is using
-this package. Have you registered with the survey yet? :-)
-
-It is maintained by Paul Blackman (thanks Paul!). You can contact him
-at ictinus@samba.anu.edu.au.
-
diff --git a/Read-Manifest-Now b/Read-Manifest-Now
deleted file mode 100644
index e69de29bb2d..00000000000
diff --git a/Roadmap b/Roadmap
deleted file mode 100644
index 52902d556e4..00000000000
--- a/Roadmap
+++ /dev/null
@@ -1,30 +0,0 @@
-Copyright (C) 1997 - Samba-Team
-
-The Samba-Team are committed to an agressive program to deliver quality
-controlled software to a well defined roadmap.
-
-The current Samba release 1.9.17 is called the "Browse Fix Release"
-The following development objectives are in place:
-
-Version / Codename Notes
------------------- ----------------------------------------------------
-1.9.18 This version will feature two main areas of improvement
-"Perf-Lock Release" - introduction of OpLock support
- - introduction of new browse list and WINS methods
-
-1.9.19 An authentication update release to offer improved
-"Auth Code Release" security and password synchronisation capabilities
-
-1.9.20 Introduction of new managment tools
-"GUI Config Release" Improved multi-language support.
-
-2.0 The next generation Directory Services update
-"DSA Release"
-
-While no release date or content promises are made we are hoping to release
-the remainder of the 1.9 series relases within short time frame.
-
-Should a budding contributor spring into gear and deliver any of the above
-ahead of the above release sequence then we reserve the option to make an
-out of sequence release (but always keeping to a logical sequence code number).
-
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
deleted file mode 100644
index 072679d0401..00000000000
--- a/WHATSNEW.txt
+++ /dev/null
@@ -1,106 +0,0 @@
- WHATS NEW IN 1.9.17 - August 25th 1997
- ======================================
-
-New stable release of Samba.
-----------------------------
-
-This is the new stable release of Samba, superceding
-the last stable release 1.9.16p11. All users are
-encouraged to upgrade to this new release as there have
-been many improvements to the code since that time.
-See the Frequently Asked Questions (under docs/faq) for
-an explanation of how the version numbering scheme works,
-distinguishing between stable and development releases.
-
-Changes since 1.9.16p11.
-------------------------
-
-Improved browsing support.
---------------------------
-
-Samba now should support propagation of browse lists
-across subnets correctly. Look in the file docs/BROWSING.txt
-as it has been largely re-written to explain how to do this.
-
-*IMPORTANT* All Samba servers acting as local/domain master
-browsers must be running 1.9.17 (or later).
-
-Thanks to Silicon Graphics for allowing us to test the new
-code on their corporate network.
-
-
-Improved share mode handling
-----------------------------
-
-The handling of share modes has been completely rewritten.
-Samba can now run agressive PC Benchmarks (Ziff-Davis
-NetBench) correctly with many hundreds of concurrent PC's.
-The confidence level on share mode handling in Samba
-is now much higher than it was previously. PC database
-packages should be safe when run against a Samba share.
-Thanks to Silicon Graphics for testing this code for us.
-
-If at all possible compile Samba to use the new share
-mode handling with shared memory (set the flags
-FAST_SHARE_MODES in the Makefile). This will be *much* faster
-than old file-based share modes. FAST_SHARE_MODES have
-been turned on by default on the following platforms in
-the Makefile :
-
- Linux
- Solaris
- BSDI
- IRIX 5.x.x
- FreeBSD
-
-Roving profile support.
------------------------
-
-Roving profiles are believed to work correctly
-with Windows NT 4.x and Windows 95. Domain logons
-are fully implemented *for Windows 95 machines only*.
-
-
-Updated documentation
----------------------
-All options are now documented in the smb.conf man page
-we believe. Much work has been done by Samba Team members
-to improve the quality and quantity of the Samba documentation.
-
-A draft new structure for documentation is being worked on: see
-docs/faq/Samba-meta-FAQ for details. This will soon be a master
-reference to all Samba documentation.
-
-Many bugfixes and improvements
-------------------------------
-From around the 'net around the world. Many
-thanks to everyone who contributed.
-
-Commercial thanks.
-------------------
-
-Thanks to Cisco for the new netbios alias code support.
-Thanks to Silicon Graphics for the help with the cross
-subnet browsing and NetBench code.
-Thanks to Whistle for funding one of the Samba Team
-members.
-
-Reporting bugs
---------------
-
-The Samba Team believes that this is a stable
-production release, but all software has bugs.
-If you have problems, or think you have found a
-bug please email a report to :
-
-samba-bugs@samba.anu.edu.au
-
-Stating the version number of Samba that you
-are running, and *full details* of the steps
-we need to reproduce the problem.
-
-As always, all bugs are our responsibility.
-
-Regards,
-
- The Samba Team.
diff --git a/docs/NT4_PlainPassword.reg b/docs/NT4_PlainPassword.reg
deleted file mode 100644
index b30db150c24..00000000000
--- a/docs/NT4_PlainPassword.reg
+++ /dev/null
@@ -1,11 +0,0 @@
-REGEDIT4
-
-;Contributor: Tim Small (tim.small@virgin.net)
-;Updated: 20 August 1997
-;Status: Current
-;
-;Subject: Registry file to enable plain text passwords in NT4-SP3 and later
-
-[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rdr\Parameters]
-"EnablePlainTextPassword"=dword:00000001
-
diff --git a/docs/THANKS b/docs/THANKS
deleted file mode 100644
index 19c11dc432f..00000000000
--- a/docs/THANKS
+++ /dev/null
@@ -1,137 +0,0 @@
-=====================================================================
-This file is for thanks to individuals or organisations who have
-helped with the development of Samba, other than by coding or bug
-reports. Their contributions are gratefully acknowledged.
-
-Please refer to the manual pages and change-log for a list of those
-who have contributed in the form of patches, bug fixes or other
-direct changes to the package.
-
-Contributions of any kind are welcomed. If you want to help then
-please contact Andrew.Tridgell@anu.edu.au, or via normal mail at
-
- Andrew Tridgell
- 3 Ballow Crescent
- Macgregor, A.C.T
- 2615 Australia
-=====================================================================
-
-
-Lee Fisher (leefi@microsoft.com)
-Charles Fox (cfox@microsoft.com)
-Dan Perry (danp@exchnge.microsoft.com)
-Paul Leach (paulle@microsoft.com)
-Isaac Heizer (isaache@microsoft.com)
-
- These Microsoft people have been very helpful and supportive of
- the development of Samba over some years.
-
- Lee very kindly supplied me with a copy of the X/Open SMB
- specs. These have been invaluable in getting the details of the
- implementation right. They will become even more important as we move
- towards a Lanman 2.1 compliant server. Lee has provided very
- useful advice on several aspects of the server.
- Lee has also provided me with copies of Windows NTAS 3.1, Visual C
- and a developers CD-ROM. Being able to run NT at home is a
- great help.
-
- Charles has helped out in numerous ways with the provision of SMB
- specifications and helpful advice. He has been following the
- discussion of Samba on the mailing list and has stepped in
- regularly to clarify points and to offer help.
-
- Dan has put me in touch with NT developers to help sort out bugs and
- compatability issues. He has also supplied me with a copy of the
- NT browsing spec, which will help a lot in the development of the
- Samba browser code.
-
- Paul was responsible for Microsoft paying my flight to Seattle for the
- first CIFS conference (see http://samba.anu.edu.au/cifs) and has been
- generally helpful and cooperative as the SMB community moves towards
- an Internet-ready specification. Isaac has regularly provided help on
- the behaviour of NT networks.
-
-Bruce Perens (bruce@pixar.com)
-
- In appreciation of his effort on Samba we have sent Andrew copies of
- various Pixar computer-graphics software products. Pixar is best known
- for its "Renderman" product, the 3-D renderer used by ILM to make special
- effects for "Terminator II" and "Jurassic Park". We won the first Oscar
- given to a computer graphic animated feature for our short film "Tin Toy".
- Our retail products "Typestry" and "Showplace", incorporate the same
- renderer used on the films, and are available on Windows and the
- Macintosh.
-
-
-
-Henry Lee (hyl@microplex.co)
-
- Henry sent me a M202 ethernet print server, making my little lan
- one of the few home networks to have it's own print server!
-
- ``Microplex Systems Ltd. is a manufacturer of local and wide area
- network communications equipment based in beautiful Vancouver, British
- Columbia, Canada. Microplex's first products were synchronous wide
- area network devices used in the mainframe communication networks. In
- August 1991 Microplex introduced its first LAN product, the M200 print
- server, the first high performance print server under US$1,000.''
-
-
-Tom Haapanen (tomh@metrics.com)
-
- Tom sent me two 16 bit SMC ethernet cards to replace my ancient 8
- bit ones. The performance is much better!
-
- Software Metrics Inc. is a small custom software development and
- consulting firm located in Waterloo, Ontario, Canada. We work
- with a variety of environments (such as Windows, Windows NT and
- Unix), tools and application areas, and can provide assistance for
- development work ranging from a few days to to multiple man-year
- projects. You can find more information at http://www.metrics.com/.
-
-
-Steve Kennedy (steve@gbnet.net)
-
- Steve sent me 16Mb of ram so that I could install/test
- NT3.5. I previous had only 8Mb ram in my test machine, which
- wasn't enough to install a properly functioning copy of
- NTAS. Being able to directly test NT3.5 allowed me to solve
- several long standing NT<->Samba problems. Thanks Steve!
-
-John Terpstra (jht@aquasoft.com.au)
-
- Aquasoft are a specialist consulting company whose Samba-using
- customers span the world.
-
- Aquasoft have been avid supporters of the Samba project. As a
- token of appreciation Aquasoft have donated a 486DX2/66 PC with
- a 540MB EIDE drive and 20MB RAM.
-
- John has helped to isolate quite a few little glitches over time
- and has managed to implement some very interesting installations
- of Samba.
-
- The donation of the new PC will make it possible to more fully
- diagnose and observe the behaviour of Samba in conjuction with
- other SMB protocol utilising systems.
-
-
-Timothy F. Sipples (tsipple@vnet.IBM.COM)
-Steve Withers (swithers@vnet.IBM.COM)
-
- Tim and Steve from IBM organised a copy of the OS/2 developers
- connection CD set for me, and gave lots of help in getting
- OS/2 Warp installed. I hope this will allow me to finally fix
- up those annoying OS/2 related Samba bugs that I have been
- receiving reports of.
-
-Keith Wilkins (wilki1k@nectech.co.uk)
-
- Keith from NEC in England very generously supplied a PC to
- Luke Leighton to help with his nmbd development work. At the
- same time Keith offered to help me with some new hardware, and
- he sent me a pentium motherboard with 32MB of ram
- onboard. This was very helpful as it allowed me to upgrade
- my aging server to be a very powerful system. Thanks!
-
-
diff --git a/docs/Win95_PlainPassword.reg b/docs/Win95_PlainPassword.reg
deleted file mode 100644
index 9dd3103689c..00000000000
--- a/docs/Win95_PlainPassword.reg
+++ /dev/null
@@ -1,4 +0,0 @@
-REGEDIT4
-
-[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\VNETSUP]
-"EnablePlainTextPassword"=dword:00000001
diff --git a/docs/announce b/docs/announce
deleted file mode 100644
index a03ddcd0e6a..00000000000
--- a/docs/announce
+++ /dev/null
@@ -1,133 +0,0 @@
- Announcing Samba version 1.9
- ============================
-
-What is Samba?
---------------
-
-Samba is a SMB file server that runs on Unix and other operating systems.
-It allows these operating systems (currently Unix, Netware, OS/2 and
-AmigaDOS) to act as a file and print server for SMB clients. There are many
-Lan-Manager compatible clients such as LanManager for DOS, Windows for
-Workgroups, Windows NT, Windows 95, OS/2, Pathworks and many more.
-
-The package also includes a SMB client for accessing other SMB servers
-and a netbios nameserver for browsing support.
-
-What can it do for me?
-----------------------
-
-If you have any PCs running SMB clients, such as a PC running Windows
-for Workgroups, then you can mount file space or printers on a Samba
-host, so that directories, files and printers on the host are
-available on the PC.
-
-The client part of the package will also allow you to attach to other
-SMB-based servers (such as windows NT and windows for workgroups) so
-that you can copy files to and from your unix host. The client also
-allows you to access a SMB printer (such as one attached to an OS/2 or
-WfWg server) from Unix, using an entry in /etc/printcap, or by
-explicitly specifying the command used to print files.
-
-What are its features?
-------------------------
-
-Samba supports many features that are not supported in other SMB
-implementations (all of which are commercial). Some of it's features
-include host as well as username/password security, a client,
-automatic home directory exporting, automatic printer exporting, dead
-connection timeouts, umask support, guest connections, name mangling
-and hidden and system attribute mapping. Look at the man pages
-included with the package for a full list of features.
-
-What's new since 1.8?
----------------------
-
-Lots of stuff. See the change log and man pages for details.
-
-Where can I get a client for my PC?
------------------------------------
-
-There is a free client for MS-DOS based PCs available from
-ftp.microsoft.com in the directory bussys/Clients/MSCLIENT/. Please
-read the licencing information before downloading. The built in
-Windows for Workgroups client is also very good.
-
-What network protocols are supported?
--------------------------------------
-
-Currently only TCP/IP is supported. There has been some discussion
-about ports to other protocols but nothing is yet available.
-
-There is a free TCP/IP implementation for Windows for Workgroups
-available from ftp.microsoft.com (it's small, fast and quite reliable).
-
-How much does it cost?
-----------------------
-
-Samba software is free software. It is available under the
-GNU Public licence in source code form at no cost. Please read the
-file COPYING that comes with the package for more information.
-
-What operating systems does it support?
----------------------------------------
-
-The code has been written to be as portable as possible. It has been
-"ported" to many unixes, which mostly required changing only a few
-lines of code. It has been run (to my knowledge) on at least these
-unixes:
-
-Linux, SunOS, Solaris, SVR4, Ultrix, OSF1, AIX, BSDI, NetBSD,
-Sequent, HP-UX, SGI, FreeBSD, NeXT, ISC, A/UX, SCO, Intergraph,
-Silicon Graphics Inc., Domain/OS and DGUX.
-
-Some of these have received more testing than others. If it doesn't
-work with your unix then it should be easy to fix. It has also been ported
-to Netware, OS/2 and the Amiga. A VMS port is available too. See the web site
-for more details.
-
-Who wrote it?
--------------
-
-Many people on the internet have contributed to the development of
-Samba. The maintainer and original author is Andrew Tridgell, but
-large parts of the package were contributed by several people from all
-over the world. Please look at the file `change-log' for information
-on who did what bits.
-
-Where can I get it?
--------------------
-
-The package is available via anonymous ftp from samba.anu.edu.au in
-the directory pub/samba/.
-
-What about SMBServer?
----------------------
-
-Samba used to be known as SMBServer, until it was pointed out that
-Syntax, who make a commercial Unix SMB based server, have trademarked
-that name. The name was then changed to Samba. Also, in 1992 a very
-early incarnation of Samba was distributed as nbserver.
-
-If you see any copies of nbserver or smbserver on ftp sites please let
-me or the ftp archive maintainer know, as I want to get them deleted.
-
-Where can I get more info?
----------------------------
-
-Please join the mailing list if you want to discuss the development or
-use of Samba. To join the mailing list send mail to
-listproc@listproc.anu.edu.au with a body of "subscribe samba Your
-Name".
-
-There is also an announcement mailing list for new version
-announcements. Subscribe as above but with "subscribe samba-announce
-Your Name".
-
-There is also often quite a bit of discussion about Samba on the
-newsgroup comp.protocols.smb.
-
-A WWW site with lots of Samba info can be found at
-http://samba.anu.edu.au/samba/
-
-The Samba Team (Contact: samba-bugs@samba.anu.edu.au)
-June 1996
diff --git a/docs/faq/Samba-Server-FAQ-1.html b/docs/faq/Samba-Server-FAQ-1.html
deleted file mode 100644
index 0bf7f046109..00000000000
--- a/docs/faq/Samba-Server-FAQ-1.html
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
- Samba Server FAQ: What is Samba?
-
-
-Previous
-Next
-Table of Contents
-
-
Samba has many features that are not supported in other CIFS and SMB
-implementations, all of which are commercial. It approaches some
-problems from a different angle.
-
Some of its features include:
-
-
extremely dynamic runtime configuration
-
host as well as username/password security
-
scriptable SMB client
-
automatic home directory exporting
-
automatic printer exporting
-
intelligent dead connection timeouts
-
guest connections
-
-
-
Look at the
-manual pages included with the package for a full list of
-features. The components of the suite are (in summary):
-
-
-
-
smbd
the SMB server. This handles actual connections from clients,
-doing all the interfacing with the
-authentication database for file, permission and username work.
-
-
nmbd
the NetBIOS name server, which helps clients locate servers,
-maintaining the
-authentication database doing the browsing work and managing
-domains as this capability is being built into Samba.
-
-
smbclient
the scriptable commandline SMB client program.
-Useful for automated work, printer filters and testing purposes. It is
-more CIFS-compliant than most commercial implementations. Note that this
-is not a filesystem. The Samba team does not supply a network filesystem
-driver, although the smbfs filesystem for Linux is derived from
-smbclient code.
-
-
smbrun
a little 'glue' program to help the server run
-external programs.
-
-
testprns
a program to test server access to printers
-
-
testparms
a program to test the Samba configuration file
-for correctness
-
-
smb.conf
the Samba configuration file
-
-
examples
many examples have been put together for the different
-operating systems that Samba supports.
-
-
Documentation!
DON'T neglect to read it - you will save a great
-deal of time!
-
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-Server-FAQ-2.html b/docs/faq/Samba-Server-FAQ-2.html
deleted file mode 100644
index 731391a9987..00000000000
--- a/docs/faq/Samba-Server-FAQ-2.html
+++ /dev/null
@@ -1,500 +0,0 @@
-
-
- Samba Server FAQ: How do I get the CIFS, SMB and NetBIOS protocols?
-
-
-Previous
-Next
-Table of Contents
-
-
CIFS and SMB are implemented by the main Samba fileserving daemon, smbd.
-.....
-
nmbd speaks a limited amount of CIFS (...) but is mostly concerned with
-NetBIOS. NetBIOS is ....
-
RFC1001, RFC1002 ...
-
So, provided you have got Samba correctly installed and running you have
-all three of these protocols. Some operating systems already come with
-stacks for all or some of these, such as SCO Unix, OS/2 and ... In this
-case you must ...
At the last count, Samba runs on about 40 operating systems! This
-section looks at general questions about running Samba on the different
-platforms. Issues specific to particular operating systems are dealt
-with in elsewhere in this document.
-
Many of the ports have been done by people outside the Samba team keen
-to get the advantages of Samba. The Samba team is currently trying to
-bring as many of these ports as possible into the main source tree and
-integrate the documentation. Samba is an integration tool, and so it has
-been made as easy as possible to port. The platforms most widely used
-and thus best tested are Linux and SunOS.
-
This migration has not been completed yet. This means that some
-documentation is on web sites ...
-
There are two main families of Samba ports, Unix and other. The Unix
-ports cover anything that remotely resembles Unix and includes some
-extremely old products as well as best-sellers, tiny PCs to massive
-multiprocessor machines supporting hundreds of thousands of users. Samba
-has been run on more than 30 Unix and Unix-like operating systems.
-
-
Running Samba on a Unix or Unix-like system
-
-
-
-
-
-../UNIX-SMB.txt describes some of the issues that confront a
-SMB implementation on unix, and how Samba copes with them. They may help
-people who are looking at unix<->PC interoperability.
-
There is great variation between Unix implementations, especially those
-not adhering to the Common Unix Specification agreed to in 1996. Things
-that can be quite tricky are .....
-
There are also some considerable advantages conferred on Samba running
-under Unix compared to, say, Windows NT or LAN Server. Unix has ...
-
At time of writing, the Makefile claimed support for:
-
-
A/UX 3.0
-
AIX
-
Altos Series 386/1000
-
Amiga
-
Apollo Domain/OS sr10.3
-
BSDI
-
B.O.S. (Bull Operating System)
-
Cray, Unicos 8.0
-
Convex
-
DGUX.
-
DNIX.
-
FreeBSD
-
HP-UX
-
Intergraph.
-
Linux with/without shadow passwords and quota
-
LYNX 2.3.0
-
MachTen (a unix like system for Macintoshes)
-
Motorola 88xxx/9xx range of machines
-
NetBSD
-
NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
-
OS/2 using EMX 0.9b
-
OSF1
-
QNX 4.22
-
RiscIX.
-
RISCOs 5.0B
-
SEQUENT.
-
SCO (including: 3.2v2, European dist., OpenServer 5)
-
SGI.
-
SMP_DC.OSx v1.1-94c079 on Pyramid S series
-
SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
-
SUNOS 4
-
SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
-
Sunsoft ISC SVR3V4
-
SVR4
-
System V with some berkely extensions (Motorola 88k R32V3.2).
-
ULTRIX.
-
UNIXWARE
-
UXP/DS
-
-
-
-
-
Running Samba on systems unlike Unix
-
-
-
-
-
More recently Samba has been ported to a number of operating systems
-which can provide a BSD Unix-like implementation of TCP/IP sockets.
-These include OS/2, Netware, VMS, StratOS, Amiga and MVS. BeOS,
-Windows NT and several others are being worked on but not yet available
-for use.
Files, printers, CD ROMs and other local devices. Network devices,
-including networked filesystems and remote printer queues. Other devices
-such as ....
-
1.4) Configuring SHARES
-1.4.1) Homes service
-1.4.2) Public services
-1.4.3) Application serving
-1.4.4) Team sharing a Samba resource
-
1.5) Printer configuration
-1.5.1) Berkeley LPR/LPD systems
-1.5.2) ATT SysV lp systems
-1.5.3) Using a private printcap file
-1.5.4) Use of the smbprint utility
-1.5.5) Printing from Windows to Unix
-1.5.6) Printing from Unix to Windows
Samba compiled with libdes - enabling encrypted passwords
-
-
-
Laws in different countries affecting Samba
-
-
-
-
-
-
Relationship between encryption and Domain Authentication
-
-
-
-
-
2.5 Files and record locking 3.1.1) Old DOS clients 3.1.2) Opportunistic locking and the consequences 3.1.3) Files caching under Windows for Workgroups, Win95 and NT Some of the foregoing links into Client-FAQ
-
-
-See
-BROWSING.txt
-for more information on browsing. Browsing.txt can also be found
-in the docs directory of the Samba source.
-
If your GUI client does not permit you to select non-browsable
-servers, you may need to do so on the command line. For example, under
-Lan Manager you might connect to the above service as disk drive M:
-thusly:
-
-
- net use M: \\mary\fred
-
-
-
-The details of how to do this and the specific syntax varies from
-client to client - check your client's documentation.
-
-
-
-
-
-If you check what files are not showing up, you will note that they
-are files which contain upper case letters or which are otherwise not
-DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
The Samba server can be configured either to ignore such files
-completely, or to present them to the client in "mangled" form. If you
-are not seeing the files at all, the Samba server has most likely been
-configured to ignore them. Consult the man page smb.conf(5) for
-details of how to change this - the parameter you need to set is
-"mangled names = yes".
-
-
-This indicates one of three things: You supplied an incorrect server
-name, the underlying TCP/IP layer is not working correctly, or the
-name you specified cannot be resolved.
-
After carefully checking that the name you typed is the name you
-should have typed, try doing things like pinging a host or telnetting
-to somewhere on your network to see if TCP/IP is functioning OK. If it
-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
-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
-there is something fundamental wrong with your naming and the solution
-is beyond the scope of this document.
-
If you do not have any server on your subnet supplying netbios name
-resolution, hardcoded mappings are your only option. If you DO have a
-netbios name server running (such as the Samba suite's nmbd program),
-the problem probably lies in the way it is set up. Refer to Section
-Two of this FAQ for more ideas.
-
By the way, remember to REMOVE the hardcoded mapping before further
-tests :-)
-
-
-This message indicates that your client CAN locate the specified
-server, which is a good start, but that it cannot find a service of
-the name you gave.
-
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
-to specify a service name correctly), read on:
-
-
-
Many clients cannot accept or use service names longer than eight characters.
-
Many clients cannot accept or use service names containing spaces.
-
Some servers (not Samba though) are case sensitive with service names.
-
-
-Nothing is wrong - Samba does not implement the primary domain name
-controller stuff for several reasons, including the fact that the
-whole concept of a primary domain controller and "logging in to a
-network" doesn't fit well with clients possibly running on multiuser
-machines (such as users of smbclient under Unix). Having said that,
-several developers are working hard on building it in to the next
-major version of Samba. If you can contribute, send a message to
-samba-bugs@anu.edu.au !
-
Seeing this message should not affect your ability to mount redirected
-disks and printers, which is really what all this is about.
-
For many clients (including Windows for Workgroups and Lan Manager),
-setting the domain to STANDALONE at least gets rid of the message.
Make sure that the specified print command for the service you are
-connecting to is correct and that it has a fully-qualified path (eg.,
-use "/usr/bin/lpr" rather than just "lpr", if you happen to be using
-Unix).
-
Make sure that the spool directory specified for the service is
-writable by the user connected to the service.
-
Make sure that the user specified in the service is permitted to use
-the printer.
-
Check the debug log produced by smbd. Search for the printer name and
-see if the log turns up any clues. Note that error messages to do with
-a service ipc$ are meaningless - they relate to the way the client
-attempts to retrieve status information when using the LANMAN1
-protocol.
-
If using WfWg then you need to set the default protocol to TCP/IP, not
-Netbeui. This is a WfWg bug.
-
If using the Lanman1 protocol (the default) then try switching to
-coreplus. Also not that print status error messages don't mean
-printing won't work. The print status is received by a different
-mechanism.
-
-
-There are numerous possible reasons for this, but one MAJOR
-possibility is that your software uses locking. Make sure you are
-using Samba 1.6.11 or later. It may also be possible to work around
-the problem by setting "locking=no" in the Samba configuration file
-for the service the software is installed on. This should be regarded
-as a strictly temporary solution.
-
In earlier Samba versions there were some difficulties with the very
-latest Microsoft products, particularly Excel 5 and Word for Windows
-6. These should have all been solved. If not then please let Andrew
-Tridgell know via email at
-samba-bugs@anu.edu.au.
-
-
-Your guest account is probably invalid for some reason. Samba uses the
-guest account for browsing in smbd. Check that your guest account is
-valid.
The user "nobody" often has problems with printing, even if it worked
-with an earlier version of Samba. Try creating another guest user other
-than "nobody".
-
-
Log message "you appear to have a trapdoor uid system"
-
-
-
-
-This can have several causes. It might be because you are using a uid
-or gid of 65535 or -1. This is a VERY bad idea, and is a big security
-hole. Check carefully in your /etc/passwd file and make sure that no
-user has uid 65535 or -1. Especially check the "nobody" user, as many
-broken systems are shipped with nobody setup with a uid of 65535.
-
It might also mean that your OS has a trapdoor uid/gid system :-)
-
This means that once a process changes effective uid from root to
-another user it can't go back to root. Unfortunately Samba relies on
-being able to change effective uid from root to non-root and back
-again to implement its security policy. If your OS has a trapdoor uid
-system this won't work, and several things in Samba may break. Less
-things will break if you use user or server level security instead of
-the default share level security, but you may still strike
-problems.
-
The problems don't give rise to any security holes, so don't panic,
-but it does mean some of Samba's capabilities will be unavailable.
-In particular you will not be able to connect to the Samba server as
-two different uids at once. This may happen if you try to print as a
-"guest" while accessing a share as a normal user. It may also affect
-your ability to list the available shares as this is normally done as
-the guest user.
-
Complain to your OS vendor and ask them to fix their system.
-
Note: the reason why 65535 is a VERY bad choice of uid and gid is that
-it casts to -1 as a uid, and the setreuid() system call ignores (with
-no error) uid changes to -1. This means any daemon attempting to run
-as uid 65535 will actually run as root. This is not good!
Send an email to rask-samba-request@kampsax.dtu.dk with the word subscribe
-in the message. The list server will use the address in the Reply-To: or
-From: header field, in that order.
-
Unsubscribing.
-
Send an email to rask-samba-request@kampsax.dtu.dk with the word
-unsubscribe in the message. The list server will use the address in the
-Reply-To: or From: header field, in that order. If you are unsure which
-address you are subscribed with, look at the headers. You should see a
-"From " (no colon) or Return-Path: header looking something like
-
rask-samba-owner-myname=my.domain@kampsax.dtu.dk
-
where myname=my.domain gives you the address myname@my.domain. This also
-means that I will always be able to find out which address is causing
-bounces, for example.
-List archive.
Dan Shearer & Paul Blackman, ictinus@samba.anu.edu.au
v 0.3, 7 Oct '97
- This is the Server Frequently Asked Questions (FAQ)
-document for Samba, the free and very popular SMB and CIFS server
-product. A general
-meta FAQ
-exists and also a companion
-Client FAQ, together with more detailed HOWTO documents on
-topics to do with Samba software. This is current to Samba version
-1.9.17. Please send any corrections to the author.
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-Server-FAQ.sgml b/docs/faq/Samba-Server-FAQ.sgml
deleted file mode 100644
index 020d5322811..00000000000
--- a/docs/faq/Samba-Server-FAQ.sgml
+++ /dev/null
@@ -1,492 +0,0 @@
-
-
-
-
-
-
- Samba Server FAQ
-
-Dan Shearer & Paul Blackman, ictinus@samba.anu.edu.au
-
-v 0.3, 7 Oct '97
-
- This is the Server Frequently Asked Questions (FAQ)
-document for Samba, the free and very popular SMB and CIFS server
-product. A general
-exists and also a companion , together with more detailed HOWTO documents on
-topics to do with Samba software. This is current to Samba version
-1.9.17. Please send any corrections to the author.
-
-
-
-
-
-What is Samba?
diff --git a/docs/faq/Samba-meta-FAQ-1.html b/docs/faq/Samba-meta-FAQ-1.html
deleted file mode 100644
index 80610fb59ed..00000000000
--- a/docs/faq/Samba-meta-FAQ-1.html
+++ /dev/null
@@ -1,160 +0,0 @@
-
-
- Samba meta FAQ: Quick Reference Guides to Samba Documentation
-
-
-Previous
-Next
-Table of Contents
-
-
We are endeavouring to provide links here to every major class of
-information about Samba or things related to Samba. We cannot list every
-document, but we are aiming for all documents to be at most two
-referrals from those listed here. This needs constant maintaining, so
-please send the author your feedback.
You know you should read the documentation but can't wait to start? What
-you need to do then is follow the instructions in the following
-documents in the order given. This should be enough to get a fairly
-simple site going quickly. If you have any problems, refer back to this
-meta-FAQ and follow the links to find more reading material.
-
-
-
-
-
-
Getting Samba:
The fastest way to get Samba
-going is and install it is to have an operating system for which the
-Samba team has put together an installation package. To see if your OS
-is included have a look at the directory
-/pub/samba/Binary_Packages/"OS_Vendor" on your nearest
-mirror site. If it is included follow the
-installation instructions in the README file there and then do some
-basic testing. If you are not so fortunate, follow the normal
-download instructions and then continue with
-building and installing Samba.
-
-
-
-
Building and Installing Samba:
At the moment
-there are two kinds of Samba server installs besides the prepackaged
-binaries mentioned in the previous step. You need to decide if you have a
-Unix or close relative or
-other supported operating system.
-
-
-
-
Basic Testing:
Try to connect using the
-supplied smbclient command-line program. You need to know the IP
-hostname of your server. A service name must be defined in smb.conf, as
-given in the examples (under many operating systems if there is a
-homes service you can just use a valid username.) Then type
-smbclient \\hostname\servicename
-Under most Unixes you will need to put the parameters within quotation
-marks. If this works, try connecting from one of the SMB clients you
-were planning to use with Samba.
-
-
-
-
Debug sequence:
If you think you have completed the
-previous step and things aren't working properly work through
-the diagnosis recipe.
-
-
-
-
Exporting files to SMB clients:
You should read the manual pages
-for smb.conf, but here is a
-quick answer guide.
-
-
-
-
Controlling user access:
the quickest and dirtiest way of sharing
-resources is to use
-share level security. If you want to spend more time and have a proper username
-and password database you must read the paragraph on
-domain mode security. If you want
-encryption (eg you are using Windows NT clients) follow the
-SMB encryption instructions.
-
-
-
-
Browsing:
if you are happy to type in "\\samba-server\sharename"
-at the client end then do not read any further. Otherwise you need to
-understand the
-browsing terminology
-and read
-Samba-Server-FAQ.html#NameBrowsing.
If you have got everything working to this point, you can expect Samba
-to be stable and secure: these are its greatest strengths. However Samba
-has a great deal to offer and to go further you must do some more
-reading. Speed and security optimisations, printer accounting, network
-logons, roving profiles, browsing across multiple subnets and so on are
-all covered either in this document or in those it refers to.
Meta-FAQ. This is the mother of all documents, and is the one you
-are reading now. The latest version is always at
-http://samba.anu.edu.au/[.....] but there is probably a much
-nearer
-mirror site which you should use
-instead.
-
-
-Samba-Server-FAQ.html is the best starting point for
-information about server-side issues. Includes configuration tips and
-pointers for Samba on particular operating systems (with 40 to choose
-from...)
-
-
-Samba-Client-FAQ.html is the best starting point for
-information about client-side issues, includes a list of all clients
-that are known to work with Samba.
-
-
-manual pages contains
-descriptions of and links to all the Samba manual pages, in Unix man and
-postscript format.
-
-
-samba-txt-index.html has descriptions of and links to
-a large number of text files have been contributed to samba covering
-many topics. These are gradually being absorbed into the FAQs and HOWTOs
-but in the meantime you might find helpful answers here.
-
-
-
-
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-meta-FAQ-2.html b/docs/faq/Samba-meta-FAQ-2.html
deleted file mode 100644
index ac760380067..00000000000
--- a/docs/faq/Samba-meta-FAQ-2.html
+++ /dev/null
@@ -1,384 +0,0 @@
-
-
- Samba meta FAQ: General Information
-
-
-Previous
-Next
-Table of Contents
-
-
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) and CIFS (Common Internet Filesystem) protocols. Initially
-written for Unix, Samba now also runs on Netware, OS/2, VMS, StratOS and
-Amigas. Ports to BeOS and other operating systems are underway. Samba
-gives the capability for these operating systems to behave much like a
-LAN Server, Windows NT Server or Pathworks machine, only with added
-functionality and flexibility designed to make life easier for
-administrators.
-
This means that using Samba you can share a server's disks and printers
-to many sorts of network clients, including Lan Manager, Windows for
-Workgroups, Windows NT, Linux, OS/2, and AIX. There is also a generic
-client program supplied as part of the Samba suite which gives a user on
-the server an ftp-like interface to access filespace and printers on any
-other SMB/CIFS servers.
-
SMB has been implemented over many protocols, including XNS, NBT, IPX,
-NetBEUI and TCP/IP. Samba only uses TCP/IP. This is not likely to change
-although there have been some requests for NetBEUI support.
-
Many users report that compared to other SMB implementations Samba is
-more stable, faster, and compatible with more clients. Administrators of
-some large installations say that Samba is the only SMB server available
-which will scale to many tens of thousands of users without crashing.
-The easy way to test these claims is to download it and try it for
-yourself!
-
The suite is supplied with full source code under the
-GNU Public License. The GPL means that you can
-use Samba for whatever purpose you wish (including changing the source
-or selling it for money) but under all circumstances the source code
-must be made freely available. A copy of the GPL must always be included
-in any copy of the package.
-
The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer.
The Samba suite is available via anonymous ftp from samba.anu.edu.au and
-many
-mirror sites. You will get much
-faster performance if you use a mirror site. The latest and greatest
-versions of the suite are in the directory:
-
/pub/samba/
-
Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are available
-in the directory:
-
/pub/samba/alpha
-
Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Most Linux distributions, for example, do contain Samba
-binaries for that platform. The VMS, OS/2, Netware and Amiga and other
-ports typically have binaries made available.
-
A special case is vendor-provided binary packages. Samba binaries and
-default configuration files are put into packages for a specific
-operating system. RedHat Linux and Sun Solaris (Sparc and x86) is
-already included, and others such as OS/2 may follow. All packages are
-in the directory:
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
-all means take the plunge and help with the testing and development -
-but don't install it on your departmental server. Samba is typically
-very stable and safe, and this is mostly due to the policy of many
-public releases.
-
How the scheme works:
-
-
-
When major changes are made the version number is increased. For
-example, the transition from 1.9.16 to 1.9.17. However, this version
-number will not appear immediately and people should continue to use
-1.9.15 for production systems (see next point.)
-
-
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.
-
-
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.17.
-
-
Inevitably bugs are found in the "stable" releases and minor patch
-levels are released which give us the pXX series, for example 1.9.17p2.
-
The above system means that whenever someone looks at the samba ftp
-site they will be able to grab the highest numbered release without an
-alpha in the name and be sure of getting the current recommended
-version.
Obviously you should substitute YOUR first name for "Firstname" and
-YOUR last name for "Lastname"! Try not to send any signature, it
-sometimes confuses the list processor.
-
The samba list is a digest list - every eight hours or so it sends a
-single message containing all the messages that have been received by
-the list since the last time and sends a copy of this message to all
-subscribers. There are thousands of people on this list.
-
If you stop being interested in Samba, please send another email to
-listproc@samba.anu.edu.au. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
-
-
-unsubscribe samba
-unsubscribe samba-announce
-
-
-
-
The From: line in your message MUST be the same
-address you used when you subscribed.
DO NOT post messages on mailing lists or in newsgroups until you have
-carried out the first three steps given here!
-
-
-
See if there are any likely looking entries in this FAQ!
-If you have just installed Samba, have you run through the checklist in
-DIAGNOSIS.txt? It can save you a lot of time and effort.
-DIAGNOSIS.txt can also be found in the docs directory of the Samba
-distribution.
-
-
Read the man pages for smbd, nmbd and smb.conf, looking for
-topics that relate to what you are trying to do.
-
-
If there is no obvious solution to hand, try to get a look at
-the log files for smbd and/or nmbd for the period during which you
-were having problems. You may need to reconfigure the servers to
-provide more extensive debugging information - usually level 2 or
-level 3 provide ample debugging info. Inspect these logs closely,
-looking particularly for the string "Error:".
-
-
If you need urgent help and are willing to pay for it see
-Paid Support.
-
-
-
-
If you still haven't got anywhere, ask the mailing list or newsgroup. In
-general nobody minds answering questions provided you have followed the
-preceding steps. It might be a good idea to scan the archives of the
-mailing list, which are available through the Samba web site described
-in the previous section. When you post be sure to include a good
-description of your environment and your problem.
-
If you successfully solve a problem, please mail the FAQ maintainer a
-succinct description of the symptom, the problem and the solution, so
-that an explanation can be incorporated into the next version.
If you make changes to the source code, please submit these patches
-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
-samba-bugs@samba.anu.edu.au. Do not send patches to Andrew Tridgell or any
-other individual, they may be lost if you do.
-
Patch format
-------------
-
If you are sending a patch to fix a problem then please don't just use
-standard diff format. As an example, samba-bugs received this patch from
-someone:
-
382a
-#endif
-..
-381a
-#if !defined(NEWS61)
-
How are we supposed to work out what this does and where it goes? These
-sort of patches only work if we both have identical files in the first
-place. The Samba sources are constantly changing at the hands of multiple
-developers, so it doesn't work.
-
Please use either context diffs or (even better) unified diffs. You
-get these using "diff -c4" or "diff -u". If you don't have a diff that
-can generate these then please send manualy commented patches to I
-know what is being changed and where. Most patches are applied by hand so
-the info must be clear.
-
This is a basic guideline that will assist us with assessing your problem
-more efficiently :
-
Machine Arch:
-Machine OS:
-OS Version:
-Kernel:
-
Compiler:
-Libc Version:
-
Samba Version:
-
Network Layout (description):
-
What else is on machine (services, etc):
-
Some extras :
-
-
-
what you did and what happened
-
-
relevant parts of a debugging output file with debuglevel higher.
-If you can't find the relevant parts, please ask before mailing
-huge files.
-
-
anything else you think is useful to trace down the bug
-
If you have spotted something very serious and believe that it is
-important to contact the developers quickly send a message to
-samba-urgent@samba.anu.edu.au. This will be processed more quickly than
-mail to samba-bugs. Please think carefully before using this address. An
-example of its use might be to report a security hole.
-
Examples of things not to send to samba-urgent include problems
-getting Samba to work at all and bugs that cannot potentially cause damage.
Samba has a large network of consultants who provide Samba support on a
-commercial basis. The list is included in the package in
-../Support.txt, and the latest version will always be on the main
-samba ftp site. Any company in the world can request that the samba team
-include their details in Support.txt so we can give no guarantee of
-their services.
-
-
-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
-twenty thousand kilometres away, but it has been done.
-
-
-
Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US.
-
-
Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
-
Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
-
Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-meta-FAQ-3.html b/docs/faq/Samba-meta-FAQ-3.html
deleted file mode 100644
index 63adff35f92..00000000000
--- a/docs/faq/Samba-meta-FAQ-3.html
+++ /dev/null
@@ -1,101 +0,0 @@
-
-
- Samba meta FAQ: About the CIFS and SMB Protocols
-
-
-Previous
-Next
-Table of Contents
-
-
SMB is a filesharing protocol that has had several maintainers and
-contributors over the years including Xerox, 3Com and most recently
-Microsoft. Names for this protocol include LAN Manager and Microsoft
-Networking. Parts of the specification has been made public at several
-versions including in an X/Open document, as listed at
-ftp://ftp.microsoft.com/developr/drg/CIFS/. No specification
-releases were made between 1992 and 1996, and during that period
-Microsoft became the SMB implementor with the largest market share.
-Microsoft developed the specification further for its products but for
-various reasons connected with developer's workload rather than market
-strategy did not make the changes public. This culminated with the
-"Windows NT 0.12" version released with NT 3.5 in 1995 which had significant
-improvements and bugs. Because Microsoft client systems are so popular,
-it is fair to say that what Microsoft with Windows affects all suppliers
-of SMB server products.
-
From 1994 Andrew Tridgell began doing some serious work on his
-Smbserver (now Samba) product and with some helpers started to
-implement more and more of these protocols. Samba began to take
-a significant share of the SMB server market.
The initial pressure for Microsoft to document their current SMB
-implementation came from the Samba team, who kept coming across things
-on the wire that Microsoft either didn't know about or hadn't documented
-anywhere (even in the sourcecode to Windows NT.) Then Sun Microsystems
-came out with their WebNFS initiative, designed to replace FTP for file
-transfers on the Internet. There are many drawbacks to WebNFS (including
-its scope - it aims to replace HTTP as well!) but the concept was
-attractive. FTP is not very clever, and why should it be harder to get
-files from across the world than across the room?
-
Some hasty revisions were made and an Internet Draft for the Common
-Internet Filesystem (CIFS) was released. Note that CIFS is not an
-Internet standard and is a very long way from becoming one, BUT the
-protocol specification is in the public domain and ongoing discussions
-concerning the spec take place on a public mailing list according to the
-rules of the Internet Engineering Task Force. For more information and
-pointers see
-http://samba.anu.edu.au/cifs/
- CIFS defines a standard remote file system access protocol for use
- over the Internet, enabling groups of users to work together and
- share documents across the Internet or within their corporate
- intranets. CIFS is an open, cross-platform technology based on the
- native file-sharing protocols built into Microsoft® Windows® and
- other popular PC operating systems, and supported on dozens of
- other platforms, including UNIX®. With CIFS, millions of computer
- users can open and share remote files on the Internet without having
- to install new software or change the way they work."
-
-
-
If you consider CIFS as a backwardsly-compatible refinement of SMB that
-will work reasonably efficiently over the Internet you won't be too far
-wrong.
-
The net effect is that Microsoft is now documenting large parts of their
-Windows NT fileserver protocols. The security concepts embodied in
-Windows NT are part of the specification, which is why Samba
-documentation often talks in terms of Windows NT. However there is no
-reason why a site shouldn't conduct all its file and printer sharing
-with CIFS and yet have no Microsoft products at all.
The term "Browsing" causes a lot of confusion. It is the part of the
-SMB/CIFS protocol which allows for resource discovery. For example, in
-the Windows NT Explorer it is possible to see a "Network Neighbourhood"
-of computers in the same SMB workgroup. Clicking on the name of one of
-these machines brings up a list of file and printer resources for
-connecting to. In this way you can cruise the network, seeing what
-things are available. How this scales to the Internet is a subject for
-debate. Look at the CIFS list archives to see what the experts think.
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-meta-FAQ-4.html b/docs/faq/Samba-meta-FAQ-4.html
deleted file mode 100644
index 73a9eea8471..00000000000
--- a/docs/faq/Samba-meta-FAQ-4.html
+++ /dev/null
@@ -1,215 +0,0 @@
-
-
- Samba meta FAQ: Designing A SMB and CIFS Network
-
-
-Previous
-Next
-Table of Contents
-
-
The big issues for installing any network of LAN or WAN file and print
-servers are
-
-
-
How and where usernames, passwords and other security information
-is stored
-
-
What method can be used for locating the resources that users have
-permission to use
-
-
What protocols the clients can converse with
-
-
-
-
If you buy Netware, Windows NT or just about any other LAN fileserver
-product you are expected to lock yourself into the product's preferred
-answers to these questions. This tendancy is restrictive and often very
-expensive for a site where there is only one kind of client or server,
-and for sites with a mixture of operating systems it often makes it
-impossible to share resources between some sets of users.
-
The Samba philosophy is to make things as easy as possible for
-administators, which means allowing as many combinations of clients,
-servers, operating systems and protocols as possible.
From the point of view of networking implementation, Domains and
-Workgroups are exactly the same, except for the client logon
-sequence. Some kind of distributed authentication database is associated
-with a domain (there are quite a few choices) and this adds so much
-flexibility that many people think of a domain as a completely different
-entity to a workgroup. From Samba's point of view a client connecting to
-a service presents an authentication token, and it if it is valid they
-have access. Samba does not care what mechanism was used to generate
-that token in the first place.
-
The SMB client logging on to a domain has an expectation that every other
-server in the domain should accept the same authentication information.
-However the network browsing functionality of domains and workgroups is
-identical and is explained in
-../BROWSING.txt.
-
There are some implementation differences: Windows 95 can be a member of
-both a workgroup and a domain, but Windows NT cannot. Windows 95 also
-has the concept of an "alternative workgroup". Samba can only be a
-member of a single workgroup or domain, although this is due to change
-with a future version when nmbd will be split into two daemons, one for
-WINS and the other for browsing (
-../NetBIOS.txt explains
-what WINS is.)
-
-
Defining the Terms
-
-
-
-
-
-
-
-
Workgroup
means a collection of machines that maintain a common
-browsing database containing information about their shared resources.
-They do not necessarily have any security information in common (if they
-do, it gets called a Domain.) The browsing database is dynamic, modified
-as servers come and go on the network and as resources are added or
-deleted. The term "browsing" refers to a user accessing the database via
-whatever interface the client provides, eg the OS/2 Workplace Shell or
-Windows 95 Explorer. SMB servers agree between themselves as to which
-ones will maintain the browsing database. Workgroups can be anywhere on
-a connected TCP/IP network, including on different subnets or even on
-the Interet. This is a very tricky part of SMB to implement.
-
-
Master Browsers
are machines which holds the master browsing
-database for a workgroup or domain. There are two kinds of Master Browser:
-
-
-
Domain Master Browser, which holds the master browsing
-information for an entire domain, which may well cross multiple TCP/IP
-subnets.
-
-
Local Master Browser, which holds the master browsing database
-for a particular subnet and communicates with the Domain Master Browser
-to get information on other subnets.
-
-
-
-
Subnets are differentiated because browsing is based on broadcasts, and
-broadcasts do not pass through routers. Subnets are not routed: while it
-is possible to have more than one subnet on a single network segment
-this is regarded as very bad practice.
-
Master Browsers (both Domain and Local) are elected dynamically
-according to an algorithm which is supposed to take into account the
-machine's ability to sustain the browsing load. Samba can be configured
-to always act as a master browser, ie it always wins elections under all
-circumstances, even against systems such as a Windows NT Primary Domain
-Controller which themselves expect to win.
-
There are also Backup Browsers which are promoted to Master Browsers in
-the event of a Master Browser disappearing from the network.
-
Alternative terms include confusing variations such as "Browse Master",
-and "Master Browser" which we are trying to eliminate from the Samba
-documentation.
-
-
Domain Controller
is a term which comes from the Microsoft and IBM
-etc implementation of the LAN Manager protocols. It is tied to
-authentication. There are other ways of doing domain authentication, but
-the Windows NT method has a large market share. The general issues are
-discussed in
-../DOMAIN.txt and a Windows NT-specific
-discussion is in
-../DOMAIN_CONTROL.txt.
-
-
-
-
-
Sharelevel (Workgroup) Security Services
-
-
-
-
-
With the Samba setting "security = SHARE", all shared resources
-information about what password is associated with them but only hints
-as to what usernames might be valid (the hint can be 'all users', in
-which case any username will work. This is usually a bad idea, but
-reflects both the initial implementations of SMB in the mid-80s and
-its reincarnation with Windows for Workgroups in 1992. The idea behind
-workgroup security was that small independant groups of people could
-share information on an ad-hoc basis without there being an
-authentication infrastructure present or requiring them to do more than
-fill in a dialogue box.
-
-
Authentication Domain Mode Services
-
-
-
-
-
With the Samba settings "security = USER" or "security = SERVER"
-accesses to all resources are checked for username/password pair matches
-in a more rigorous manner. To the client, this has the effect of
-emulating a Microsoft Domain. The client is not concerned whether or not
-Samba looks up a Windows NT SAM or does it in some other way.
In the simple case authentication information is stored on a single
-server and the user types a password on connecting for the first time.
-However client operating systems often require a password before they
-can be used at all, and in addition users usually want access to more
-than one server. Asking users to remember many different passwords in
-different contexts just does not work. Some kind of distributed
-authentication database is needed. It must cope with password changes
-and provide for assigning groups of users the same level of access
-permissions. This is why Samba installations often choose to implement a
-Domain model straight away.
-
Authentication decisions are some of the biggest in designing a network.
-Are you going to use a scheme native to the client operating system,
-native to the server operating system, or newly installed on both? A
-list of options relevant to Samba (ie that make sense in the context of
-the SMB protocol) follows. Any experiences with other setups would be
-appreciated. refer to server FAQ for "passwd chat" passwd program
-password server etc etc...
-
-
NIS
-
-
-
For Windows 95, Windows for Workgroups and most other clients Samba can
-be a domain controller and share the password database via NIS
-transparently. Windows NT is different.
-Free NIS NT client
Dan Shearer & Paul Blackman, ictinus@samba.anu.edu.au
v 0.3, 7 Oct '97
- This is the meta-Frequently Asked Questions (FAQ) document
-for Samba, the free and very popular SMB and CIFS server product. It
-contains overview information for the Samba suite of programs, a
-quick-start guide, and pointers to all other Samba documentation. Other
-FAQs exist for specific client and server issues, and HOWTO documents
-for more extended topics to do with Samba software. Current to version
-Samba 1.9.17. Please send any corrections to the author.
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/Samba-meta-FAQ.sgml b/docs/faq/Samba-meta-FAQ.sgml
deleted file mode 100644
index 75038f19f53..00000000000
--- a/docs/faq/Samba-meta-FAQ.sgml
+++ /dev/null
@@ -1,771 +0,0 @@
-
-
-
-
-
- Samba meta FAQ
-
-Dan Shearer & Paul Blackman, ictinus@samba.anu.edu.au
-
-v 0.3, 7 Oct '97
-
- This is the meta-Frequently Asked Questions (FAQ) document
-for Samba, the free and very popular SMB and CIFS server product. It
-contains overview information for the Samba suite of programs, a
-quick-start guide, and pointers to all other Samba documentation. Other
-FAQs exist for specific client and server issues, and HOWTO documents
-for more extended topics to do with Samba software. Current to version
-Samba 1.9.17. Please send any corrections to the author.
-
-
-
-
- Quick Reference Guides to Samba Documentation
-
-We are endeavouring to provide links here to every major class of
-information about Samba or things related to Samba. We cannot list every
-document, but we are aiming for all documents to be at most two
-referrals from those listed here. This needs constant maintaining, so
-please send the author your feedback.
-
- Samba for the Impatient
-
-You know you should read the documentation but can't wait to start? What
-you need to do then is follow the instructions in the following
-documents in the order given. This should be enough to get a fairly
-simple site going quickly. If you have any problems, refer back to this
-meta-FAQ and follow the links to find more reading material.
-
-
-
-. If it is included follow the
-installation instructions in the README file there and then do some . If you are not so fortunate, follow the normal and then continue with .
-
- or .
-
-
- smbclient \\hostname\servicename
-
-Under most Unixes you will need to put the parameters within quotation
-marks. If this works, try connecting from one of the SMB clients you
-were planning to use with Samba.
-
-
-
-
-
- If you want to spend more time and have a proper username
-and password database you must read the paragraph on If you want
-encryption (eg you are using Windows NT clients) follow the
-
-
-and read .
-
-
-
-
-
-If you have got everything working to this point, you can expect Samba
-to be stable and secure: these are its greatest strengths. However Samba
-has a great deal to offer and to go further you must do some more
-reading. Speed and security optimisations, printer accounting, network
-logons, roving profiles, browsing across multiple subnets and so on are
-all covered either in this document or in those it refers to.
-
- All Samba Documentation
-
-
-
- Meta-FAQ. This is the mother of all documents, and is the one you
-are reading now. The latest version is always at but there is probably a much
-nearer which you should use
-instead.
-
- is the best starting point for
-information about server-side issues. Includes configuration tips and
-pointers for Samba on particular operating systems (with 40 to choose
-from...)
-
- is the best starting point for
-information about client-side issues, includes a list of all clients
-that are known to work with Samba.
-
- contains
-descriptions of and links to all the Samba manual pages, in Unix man and
-postscript format.
-
- has descriptions of and links to
-a large number of text files have been contributed to samba covering
-many topics. These are gradually being absorbed into the FAQs and HOWTOs
-but in the meantime you might find helpful answers here.
-
-
-
-
-
- General Information
-
-All about Samba - what it is, how to get it, related sources of
-information, how to understand the numbering scheme, pizza
-details.
-
- What is Samba?
-
-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) and CIFS (Common Internet Filesystem) protocols. Initially
-written for Unix, Samba now also runs on Netware, OS/2, VMS, StratOS and
-Amigas. Ports to BeOS and other operating systems are underway. Samba
-gives the capability for these operating systems to behave much like a
-LAN Server, Windows NT Server or Pathworks machine, only with added
-functionality and flexibility designed to make life easier for
-administrators.
-
-This means that using Samba you can share a server's disks and printers
-to many sorts of network clients, including Lan Manager, Windows for
-Workgroups, Windows NT, Linux, OS/2, and AIX. There is also a generic
-client program supplied as part of the Samba suite which gives a user on
-the server an ftp-like interface to access filespace and printers on any
-other SMB/CIFS servers.
-
-SMB has been implemented over many protocols, including XNS, NBT, IPX,
-NetBEUI and TCP/IP. Samba only uses TCP/IP. This is not likely to change
-although there have been some requests for NetBEUI support.
-
-Many users report that compared to other SMB implementations Samba is
-more stable, faster, and compatible with more clients. Administrators of
-some large installations say that Samba is the only SMB server available
-which will scale to many tens of thousands of users without crashing.
-The easy way to test these claims is to download it and try it for
-yourself!
-
-The suite is supplied with full source code under the . The GPL means that you can
-use Samba for whatever purpose you wish (including changing the source
-or selling it for money) but under all circumstances the source code
-must be made freely available. A copy of the GPL must always be included
-in any copy of the package.
-
-The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer.
-
- What is the current version of Samba?
-
-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.
-
-For more information see
-
- Where can I get it?
-
-The Samba suite is available via anonymous ftp from samba.anu.edu.au and
-many sites. You will get much
-faster performance if you use a mirror site. The latest and greatest
-versions of the suite are in the directory:
-
-/pub/samba/
-
-Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are available
-in the directory:
-
-/pub/samba/alpha
-
-Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Most Linux distributions, for example, do contain Samba
-binaries for that platform. The VMS, OS/2, Netware and Amiga and other
-ports typically have binaries made available.
-
-A special case is vendor-provided binary packages. Samba binaries and
-default configuration files are put into packages for a specific
-operating system. RedHat Linux and Sun Solaris (Sparc and x86) is
-already included, and others such as OS/2 may follow. All packages are
-in the directory:
-
-/pub/samba/Binary_Packages/"OS_Vendor"
-
-What do the version numbers mean?
-
-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
-all means take the plunge and help with the testing and development -
-but don't install it on your departmental server. Samba is typically
-very stable and safe, and this is mostly due to the policy of many
-public releases.
-
-How the scheme works:
-
-
-
-When major changes are made the version number is increased. For
-example, the transition from 1.9.16 to 1.9.17. However, this version
-number will not appear immediately and people should continue to use
-1.9.15 for production systems (see next point.)
-
-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.
-
-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.17.
-
-Inevitably bugs are found in the "stable" releases and minor patch
-levels are released which give us the pXX series, for example 1.9.17p2.
-
-
-
-So the progression goes:
-
-
- 1.9.16p10 (production)
- 1.9.16p11 (production)
- 1.9.17alpha1 (test sites only)
- :
- 1.9.17alpha20 (test sites only)
- 1.9.17 (production)
- 1.9.17p1 (production)
-
-
-The above system means that whenever someone looks at the samba ftp
-site they will be able to grab the highest numbered release without an
-alpha in the name and be sure of getting the current recommended
-version.
-
- Where can I go for further information?
-
-There are a number of places to look for more information on Samba,
-including:
-
-
-
-Two mailing lists devoted to discussion of Samba-related matters.
-See below for subscription information.
-
-The newsgroup comp.protocols.smb, which has a great deal of
-discussion about Samba.
-
-The WWW site 'SAMBA Web Pages' at includes:
-
-
- Links to man pages and documentation, including this FAQ
- A comprehensive survey of Samba users
- A searchable hypertext archive of the Samba mailing list
- Links to Samba source code, binaries, and mirrors of both
- This FAQ and the rest in its family
-
-
-
-
-How do I subscribe to the Samba Mailing Lists?
-
-Send email to . Make sure the subject line is blank,
-and include the following two lines in the body of the message:
-
-
-subscribe samba Firstname Lastname
-subscribe samba-announce Firstname Lastname
-
-
-Obviously you should substitute YOUR first name for "Firstname" and
-YOUR last name for "Lastname"! Try not to send any signature, it
-sometimes confuses the list processor.
-
-The samba list is a digest list - every eight hours or so it sends a
-single message containing all the messages that have been received by
-the list since the last time and sends a copy of this message to all
-subscribers. There are thousands of people on this list.
-
-If you stop being interested in Samba, please send another email to
-. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
-
-unsubscribe samba
-unsubscribe samba-announce
-
-
-The From: line in your message MUST be the same
-address you used when you subscribed.
-
- Something's gone wrong - what should I do?
-
-[#] *** IMPORTANT! *** [#]
-
-
-DO NOT post messages on mailing lists or in newsgroups until you have
-carried out the first three steps given here!
-
- See if there are any likely looking entries in this FAQ!
-If you have just installed Samba, have you run through the checklist in
-? It can save you a lot of time and effort.
-DIAGNOSIS.txt can also be found in the docs directory of the Samba
-distribution.
-
- Read the man pages for smbd, nmbd and smb.conf, looking for
-topics that relate to what you are trying to do.
-
- If there is no obvious solution to hand, try to get a look at
-the log files for smbd and/or nmbd for the period during which you
-were having problems. You may need to reconfigure the servers to
-provide more extensive debugging information - usually level 2 or
-level 3 provide ample debugging info. Inspect these logs closely,
-looking particularly for the string "Error:".
-
- If you need urgent help and are willing to pay for it see
-.
-
-
-
-If you still haven't got anywhere, ask the mailing list or newsgroup. In
-general nobody minds answering questions provided you have followed the
-preceding steps. It might be a good idea to scan the archives of the
-mailing list, which are available through the Samba web site described
-in the previous section. When you post be sure to include a good
-description of your environment and your problem.
-
-If you successfully solve a problem, please mail the FAQ maintainer a
-succinct description of the symptom, the problem and the solution, so
-that an explanation can be incorporated into the next version.
-
- How do I submit patches or bug reports?
-
-If you make changes to the source code, please submit these patches
-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 . Do not send patches to Andrew Tridgell or any
-other individual, they may be lost if you do.
-
-Patch format
-------------
-
-If you are sending a patch to fix a problem then please don't just use
-standard diff format. As an example, samba-bugs received this patch from
-someone:
-
-382a
-#endif
-..
-381a
-#if !defined(NEWS61)
-
-How are we supposed to work out what this does and where it goes? These
-sort of patches only work if we both have identical files in the first
-place. The Samba sources are constantly changing at the hands of multiple
-developers, so it doesn't work.
-
-Please use either context diffs or (even better) unified diffs. You
-get these using "diff -c4" or "diff -u". If you don't have a diff that
-can generate these then please send manualy commented patches to I
-know what is being changed and where. Most patches are applied by hand so
-the info must be clear.
-
-This is a basic guideline that will assist us with assessing your problem
-more efficiently :
-
-Machine Arch:
-Machine OS:
-OS Version:
-Kernel:
-
-Compiler:
-Libc Version:
-
-Samba Version:
-
-Network Layout (description):
-
-What else is on machine (services, etc):
-
-Some extras :
-
-
-
- what you did and what happened
-
- relevant parts of a debugging output file with debuglevel higher.
- If you can't find the relevant parts, please ask before mailing
- huge files.
-
- anything else you think is useful to trace down the bug
-
-
-
- What if I have an URGENT message for the developers?
-
-If you have spotted something very serious and believe that it is
-important to contact the developers quickly send a message to
-samba-urgent@samba.anu.edu.au. This will be processed more quickly than
-mail to samba-bugs. Please think carefully before using this address. An
-example of its use might be to report a security hole.
-
-Examples of things not to send to samba-urgent include problems
-getting Samba to work at all and bugs that cannot potentially cause damage.
-
- What if I need paid-for support?
-
-Samba has a large network of consultants who provide Samba support on a
-commercial basis. The list is included in the package in , and the latest version will always be on the main
-samba ftp site. Any company in the world can request that the samba team
-include their details in Support.txt so we can give no guarantee of
-their services.
-
- Pizza supply details
-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
-twenty thousand kilometres away, but it has been done.
-
-
- Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US.
-
-Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
-Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
-Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-
-
-About the CIFS and SMB Protocols
-
- What is the Server Message Block (SMB) Protocol?
-SMB is a filesharing protocol that has had several maintainers and
-contributors over the years including Xerox, 3Com and most recently
-Microsoft. Names for this protocol include LAN Manager and Microsoft
-Networking. Parts of the specification has been made public at several
-versions including in an X/Open document, as listed at
-. No specification
-releases were made between 1992 and 1996, and during that period
-Microsoft became the SMB implementor with the largest market share.
-Microsoft developed the specification further for its products but for
-various reasons connected with developer's workload rather than market
-strategy did not make the changes public. This culminated with the
-"Windows NT 0.12" version released with NT 3.5 in 1995 which had significant
-improvements and bugs. Because Microsoft client systems are so popular,
-it is fair to say that what Microsoft with Windows affects all suppliers
-of SMB server products.
-
-From 1994 Andrew Tridgell began doing some serious work on his
-Smbserver (now Samba) product and with some helpers started to
-implement more and more of these protocols. Samba began to take
-a significant share of the SMB server market.
-
- What is the Common Internet Filesystem (CIFS)?
-The initial pressure for Microsoft to document their current SMB
-implementation came from the Samba team, who kept coming across things
-on the wire that Microsoft either didn't know about or hadn't documented
-anywhere (even in the sourcecode to Windows NT.) Then Sun Microsystems
-came out with their WebNFS initiative, designed to replace FTP for file
-transfers on the Internet. There are many drawbacks to WebNFS (including
-its scope - it aims to replace HTTP as well!) but the concept was
-attractive. FTP is not very clever, and why should it be harder to get
-files from across the world than across the room?
-
-Some hasty revisions were made and an Internet Draft for the Common
-Internet Filesystem (CIFS) was released. Note that CIFS is not an
-Internet standard and is a very long way from becoming one, BUT the
-protocol specification is in the public domain and ongoing discussions
-concerning the spec take place on a public mailing list according to the
-rules of the Internet Engineering Task Force. For more information and
-pointers see
-
-The following is taken from
-
-
- CIFS defines a standard remote file system access protocol for use
- over the Internet, enabling groups of users to work together and
- share documents across the Internet or within their corporate
- intranets. CIFS is an open, cross-platform technology based on the
- native file-sharing protocols built into Microsoft® Windows® and
- other popular PC operating systems, and supported on dozens of
- other platforms, including UNIX®. With CIFS, millions of computer
- users can open and share remote files on the Internet without having
- to install new software or change the way they work."
-
-
-If you consider CIFS as a backwardsly-compatible refinement of SMB that
-will work reasonably efficiently over the Internet you won't be too far
-wrong.
-
-The net effect is that Microsoft is now documenting large parts of their
-Windows NT fileserver protocols. The security concepts embodied in
-Windows NT are part of the specification, which is why Samba
-documentation often talks in terms of Windows NT. However there is no
-reason why a site shouldn't conduct all its file and printer sharing
-with CIFS and yet have no Microsoft products at all.
-
- What is Browsing?
-The term "Browsing" causes a lot of confusion. It is the part of the
-SMB/CIFS protocol which allows for resource discovery. For example, in
-the Windows NT Explorer it is possible to see a "Network Neighbourhood"
-of computers in the same SMB workgroup. Clicking on the name of one of
-these machines brings up a list of file and printer resources for
-connecting to. In this way you can cruise the network, seeing what
-things are available. How this scales to the Internet is a subject for
-debate. Look at the CIFS list archives to see what the experts think.
-
-Designing A SMB and CIFS Network
-
-The big issues for installing any network of LAN or WAN file and print
-servers are
-
-
-
-How and where usernames, passwords and other security information
-is stored
-
-What method can be used for locating the resources that users have
-permission to use
-
-What protocols the clients can converse with
-
-
-
-If you buy Netware, Windows NT or just about any other LAN fileserver
-product you are expected to lock yourself into the product's preferred
-answers to these questions. This tendancy is restrictive and often very
-expensive for a site where there is only one kind of client or server,
-and for sites with a mixture of operating systems it often makes it
-impossible to share resources between some sets of users.
-
-The Samba philosophy is to make things as easy as possible for
-administators, which means allowing as many combinations of clients,
-servers, operating systems and protocols as possible.
-
-Workgroups, Domains, Authentication and Browsing
-
-From the point of view of networking implementation, Domains and
-Workgroups are exactly the same, except for the client logon
-sequence. Some kind of distributed authentication database is associated
-with a domain (there are quite a few choices) and this adds so much
-flexibility that many people think of a domain as a completely different
-entity to a workgroup. From Samba's point of view a client connecting to
-a service presents an authentication token, and it if it is valid they
-have access. Samba does not care what mechanism was used to generate
-that token in the first place.
-
-The SMB client logging on to a domain has an expectation that every other
-server in the domain should accept the same authentication information.
-However the network browsing functionality of domains and workgroups is
-identical and is explained in .
-
-There are some implementation differences: Windows 95 can be a member of
-both a workgroup and a domain, but Windows NT cannot. Windows 95 also
-has the concept of an "alternative workgroup". Samba can only be a
-member of a single workgroup or domain, although this is due to change
-with a future version when nmbd will be split into two daemons, one for
-WINS and the other for browsing ( explains
-what WINS is.)
-
- Defining the Terms
-
-
-
-
-
- Domain Master Browser, which holds the master browsing
-information for an entire domain, which may well cross multiple TCP/IP
-subnets.
-
- Local Master Browser, which holds the master browsing database
-for a particular subnet and communicates with the Domain Master Browser
-to get information on other subnets.
-
-
-
-Subnets are differentiated because browsing is based on broadcasts, and
-broadcasts do not pass through routers. Subnets are not routed: while it
-is possible to have more than one subnet on a single network segment
-this is regarded as very bad practice.
-
-Master Browsers (both Domain and Local) are elected dynamically
-according to an algorithm which is supposed to take into account the
-machine's ability to sustain the browsing load. Samba can be configured
-to always act as a master browser, ie it always wins elections under all
-circumstances, even against systems such as a Windows NT Primary Domain
-Controller which themselves expect to win.
-
-There are also Backup Browsers which are promoted to Master Browsers in
-the event of a Master Browser disappearing from the network.
-
-Alternative terms include confusing variations such as "Browse Master",
-and "Master Browser" which we are trying to eliminate from the Samba
-documentation.
-
- and a Windows NT-specific
-discussion is in .
-
-
-
-Sharelevel (Workgroup) Security Services
-
-With the Samba setting "security = SHARE", all shared resources
-information about what password is associated with them but only hints
-as to what usernames might be valid (the hint can be 'all users', in
-which case any username will work. This is usually a bad idea, but
-reflects both the initial implementations of SMB in the mid-80s and
-its reincarnation with Windows for Workgroups in 1992. The idea behind
-workgroup security was that small independant groups of people could
-share information on an ad-hoc basis without there being an
-authentication infrastructure present or requiring them to do more than
-fill in a dialogue box.
-
-Authentication Domain Mode Services
-
-With the Samba settings "security = USER" or "security = SERVER"
-accesses to all resources are checked for username/password pair matches
-in a more rigorous manner. To the client, this has the effect of
-emulating a Microsoft Domain. The client is not concerned whether or not
-Samba looks up a Windows NT SAM or does it in some other way.
-
-Authentication Schemes
-
-In the simple case authentication information is stored on a single
-server and the user types a password on connecting for the first time.
-However client operating systems often require a password before they
-can be used at all, and in addition users usually want access to more
-than one server. Asking users to remember many different passwords in
-different contexts just does not work. Some kind of distributed
-authentication database is needed. It must cope with password changes
-and provide for assigning groups of users the same level of access
-permissions. This is why Samba installations often choose to implement a
-Domain model straight away.
-
-Authentication decisions are some of the biggest in designing a network.
-Are you going to use a scheme native to the client operating system,
-native to the server operating system, or newly installed on both? A
-list of options relevant to Samba (ie that make sense in the context of
-the SMB protocol) follows. Any experiences with other setups would be
-appreciated. [refer to server FAQ for "passwd chat" passwd program
-password server etc etc...]
-
-NIS
-
-For Windows 95, Windows for Workgroups and most other clients Samba can
-be a domain controller and share the password database via NIS
-transparently. Windows NT is different.
-
-
-Kerberos
-
-Kerberos for US users only:
-
-
-
-FTP
-
-Other NT w/s logon hack via NT
-
-Default Server Method
-
-Samba is an important tool for...
-
-It is possible to...
-
-File protocol gateways...
-
-"Setting up a Linux File Server" http://vetrec.mit.edu/people/narf/linux.html
-
-Two free implementations of Appletalk for Unix are Netatalk, , and CAP, . What Samba offers MS
-Windows users, these packages offer to Macs. For more info on these
-packages, Samba, and Linux (and other UNIX-based systems) see 3.5) Sniffing your nework
-
-
-Miscellaneous
-Is Samba Year 2000 compliant?
-The CIFS protocol that Samba implements
-negotiates times in various formats, all of which
-are able to cope with dates beyond 2000.
-
-
diff --git a/docs/faq/Samba-meta-FAQ.txt b/docs/faq/Samba-meta-FAQ.txt
deleted file mode 100644
index 65d9a57ff62..00000000000
--- a/docs/faq/Samba-meta-FAQ.txt
+++ /dev/null
@@ -1,924 +0,0 @@
- Samba meta FAQ
- Dan Shearer & Paul Blackman, ictinus@samba.anu.edu.au
- v 0.3, 7 Oct '97
-
- This is the meta-Frequently Asked Questions (FAQ) document for Samba,
- the free and very popular SMB and CIFS server product. It contains
- overview information for the Samba suite of programs, a quick-start
- guide, and pointers to all other Samba documentation. Other FAQs exist
- for specific client and server issues, and HOWTO documents for more
- extended topics to do with Samba software. Current to version Samba
- 1.9.17. Please send any corrections to the author.
- ______________________________________________________________________
-
- Table of Contents:
-
- 1. Quick Reference Guides to Samba Documentation
-
- 1.1. Samba for the Impatient
-
- 1.2. All Samba Documentation
-
- 2. General Information
-
- 2.1. What is Samba?
-
- 2.2. What is the current version of Samba?
-
- 2.3. Where can I get it?
-
- 2.4. What do the version numbers mean?
-
- 2.5. Where can I go for further information?
-
- 2.6. How do I subscribe to the Samba Mailing Lists?
-
- 2.7. Something's gone wrong - what should I do?
-
- 2.8. How do I submit patches or bug reports?
-
- 2.9. What if I have an URGENT message for the developers?
-
- 2.10. What if I need paid-for support?
-
- 2.11. Pizza supply details
-
- 3. About the CIFS and SMB Protocols
-
- 3.1. What is the Server Message Block (SMB) Protocol?
-
- 3.2. What is the Common Internet Filesystem (CIFS)?
-
- 3.3. What is Browsing?
-
- 4. Designing A SMB and CIFS Network
-
- 4.1. Workgroups, Domains, Authentication and Browsing
-
- 4.1.1. Defining the Terms
-
- 4.1.2. Sharelevel (Workgroup) Security Services
-
- 4.1.3. Authentication Domain Mode Services
-
- 4.2. Authentication Schemes
-
-
- 4.2.1. NIS
-
- 4.2.2. Kerberos
-
- 4.2.3. FTP
-
- 4.2.4. Default Server Method
-
- 4.2.5. Client-side Database Only
-
- 4.3. Post-Authentication: Netlogon, Logon Scripts, Profiles
-
- 5. Cross-Protocol File Sharing
-
- 6. Miscellaneous
-
- 6.1. Is Samba Year 2000 compliant?
- ______________________________________________________________________
-
- 11.. QQuuiicckk RReeffeerreennccee GGuuiiddeess ttoo SSaammbbaa DDooccuummeennttaattiioonn
-
-
- We are endeavouring to provide links here to every major class of
- information about Samba or things related to Samba. We cannot list
- every document, but we are aiming for all documents to be at most two
- referrals from those listed here. This needs constant maintaining, so
- please send the author your feedback.
-
-
- 11..11.. SSaammbbaa ffoorr tthhee IImmppaattiieenntt
-
-
- You know you should read the documentation but can't wait to start?
- What you need to do then is follow the instructions in the following
- documents in the order given. This should be enough to get a fairly
- simple site going quickly. If you have any problems, refer back to
- this meta-FAQ and follow the links to find more reading material.
-
-
-
- GGeettttiinngg SSaammbbaa::
- The fastest way to get Samba going is and install it is to have
- an operating system for which the Samba team has put together an
- installation package. To see if your OS is included have a look
- at the directory /pub/samba/Binary_Packages/"OS_Vendor" on your
- nearest mirror site <../MIRRORS>. If it is included follow the
- installation instructions in the README file there and then do
- some ``basic testing''. If you are not so fortunate, follow the
- normal ``download instructions'' and then continue with
- ``building and installing Samba''.
-
-
- BBuuiillddiinngg aanndd IInnssttaalllliinngg SSaammbbaa::
- At the moment there are two kinds of Samba server installs
- besides the prepackaged binaries mentioned in the previous step.
- You need to decide if you have a Unix or close relative
- <../UNIX_INSTALL.txt> or other supported operating system
- .
-
-
- BBaassiicc TTeessttiinngg::
- Try to connect using the supplied smbclient command-line
- program. You need to know the IP hostname of your server. A
- service name must be defined in smb.conf, as given in the
- examples (under many operating systems if there is a homes
- service you can just use a valid username.) Then type smbclient
- \hostnamevicename Under most Unixes you will need to put the
- parameters within quotation marks. If this works, try connecting
- from one of the SMB clients you were planning to use with Samba.
-
-
- DDeebbuugg sseeqquueennccee::
- If you think you have completed the previous step and things
- aren't working properly work through the diagnosis recipe.
- <../DIAGNOSIS.txt>
-
-
- EExxppoorrttiinngg ffiilleess ttoo SSMMBB cclliieennttss::
- You should read the manual pages for smb.conf, but here is a
- quick answer guide.
-
-
- CCoonnttrroolllliinngg uusseerr aacccceessss::
- the quickest and dirtiest way of sharing resources is to use
- ``share level security.'' If you want to spend more time and
- have a proper username and password database you must read the
- paragraph on ``domain mode security.'' If you want encryption
- (eg you are using Windows NT clients) follow the SMB encryption
- instructions.
-
-
- BBrroowwssiinngg::
- if you are happy to type in "\samba-serverrename" at the client
- end then do not read any further. Otherwise you need to
- understand the ``browsing terminology'' and read .
-
-
- PPrriinnttiinngg::
- See the printing quick answer guide.
-
-
- If you have got everything working to this point, you can expect Samba
- to be stable and secure: these are its greatest strengths. However
- Samba has a great deal to offer and to go further you must do some
- more reading. Speed and security optimisations, printer accounting,
- network logons, roving profiles, browsing across multiple subnets and
- so on are all covered either in this document or in those it refers
- to.
-
-
- 11..22.. AAllll SSaammbbaa DDooccuummeennttaattiioonn
-
-
-
- +o Meta-FAQ. This is the mother of all documents, and is the one you
- are reading now. The latest version is always at
- but there is probably a much
- nearer mirror site <../MIRRORS> which you should use instead.
-
- +o is the best starting point for information
- about server-side issues. Includes configuration tips and pointers
- for Samba on particular operating systems (with 40 to choose
- from...)
-
- +o is the best starting point for information
- about client-side issues, includes a list of all clients that are
- known to work with Samba.
-
- +o manual pages contains descriptions of and
- links to all the Samba manual pages, in Unix man and postscript
- format.
-
- +o has descriptions of and links to a large
- number of text files have been contributed to samba covering many
- topics. These are gradually being absorbed into the FAQs and HOWTOs
- but in the meantime you might find helpful answers here.
-
- +o
-
-
- 22.. GGeenneerraall IInnffoorrmmaattiioonn
-
-
- All about Samba - what it is, how to get it, related sources of
- information, how to understand the numbering scheme, pizza details.
-
-
- 22..11.. WWhhaatt iiss SSaammbbaa??
-
-
- 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) and CIFS (Common Internet Filesystem) protocols.
- Initially written for Unix, Samba now also runs on Netware, OS/2, VMS,
- StratOS and Amigas. Ports to BeOS and other operating systems are
- underway. Samba gives the capability for these operating systems to
- behave much like a LAN Server, Windows NT Server or Pathworks machine,
- only with added functionality and flexibility designed to make life
- easier for administrators.
-
- This means that using Samba you can share a server's disks and
- printers to many sorts of network clients, including Lan Manager,
- Windows for Workgroups, Windows NT, Linux, OS/2, and AIX. There is
- also a generic client program supplied as part of the Samba suite
- which gives a user on the server an ftp-like interface to access
- filespace and printers on any other SMB/CIFS servers.
-
- SMB has been implemented over many protocols, including XNS, NBT, IPX,
- NetBEUI and TCP/IP. Samba only uses TCP/IP. This is not likely to
- change although there have been some requests for NetBEUI support.
-
- Many users report that compared to other SMB implementations Samba is
- more stable, faster, and compatible with more clients. Administrators
- of some large installations say that Samba is the only SMB server
- available which will scale to many tens of thousands of users without
- crashing. The easy way to test these claims is to download it and try
- it for yourself!
-
- The suite is supplied with full source code under the GNU Public
- License <../COPYING>. The GPL means that you can use Samba for
- whatever purpose you wish (including changing the source or selling it
- for money) but under all circumstances the source code must be made
- freely available. A copy of the GPL must always be included in any
- copy of the package.
-
- The primary creator of the Samba suite is Andrew Tridgell. Later
- versions incorporate much effort by many net.helpers. The man pages
- and this FAQ were originally written by Karl Auer.
-
-
- 22..22.. WWhhaatt iiss tthhee ccuurrrreenntt vveerrssiioonn ooff SSaammbbaa??
-
-
- 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.
-
- For more information see ``What do the version numbers mean?''
-
-
- 22..33.. WWhheerree ccaann II ggeett iitt??
-
-
- The Samba suite is available via anonymous ftp from samba.anu.edu.au
- and many mirror <../MIRRORS> sites. You will get much faster
- performance if you use a mirror site. The latest and greatest versions
- of the suite are in the directory:
-
- /pub/samba/
-
- Development (read "alpha") versions, which are NOT necessarily stable
- and which do NOT necessarily have accurate documentation, are
- available in the directory:
-
- /pub/samba/alpha
-
- Note that binaries are NOT included in any of the above. Samba is
- distributed ONLY in source form, though binaries may be available from
- other sites. Most Linux distributions, for example, do contain Samba
- binaries for that platform. The VMS, OS/2, Netware and Amiga and other
- ports typically have binaries made available.
-
- A special case is vendor-provided binary packages. Samba binaries and
- default configuration files are put into packages for a specific
- operating system. RedHat Linux and Sun Solaris (Sparc and x86) is
- already included, and others such as OS/2 may follow. All packages are
- in the directory:
-
- /pub/samba/Binary_Packages/"OS_Vendor"
-
-
- 22..44.. WWhhaatt ddoo tthhee vveerrssiioonn nnuummbbeerrss mmeeaann??
-
-
- 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
- all means take the plunge and help with the testing and development -
- but don't install it on your departmental server. Samba is typically
- very stable and safe, and this is mostly due to the policy of many
- public releases.
-
- How the scheme works:
-
-
- 1. When major changes are made the version number is increased. For
- example, the transition from 1.9.16 to 1.9.17. However, this
- version number will not appear immediately and people should
- continue to use 1.9.15 for production systems (see next point.)
-
- 2. 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.
-
- 3. 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.17.
-
- 4. Inevitably bugs are found in the "stable" releases and minor patch
- levels are released which give us the pXX series, for example
- 1.9.17p2.
-
- So the progression goes:
-
-
- 1.9.16p10 (production)
- 1.9.16p11 (production)
- 1.9.17alpha1 (test sites only)
- :
- 1.9.17alpha20 (test sites only)
- 1.9.17 (production)
- 1.9.17p1 (production)
-
-
-
- The above system means that whenever someone looks at the samba ftp
- site they will be able to grab the highest numbered release without an
- alpha in the name and be sure of getting the current recommended
- version.
-
-
- 22..55.. WWhheerree ccaann II ggoo ffoorr ffuurrtthheerr iinnffoorrmmaattiioonn??
-
-
- There are a number of places to look for more information on Samba,
- including:
-
-
- +o Two mailing lists devoted to discussion of Samba-related matters.
- See below for subscription information.
-
- +o The newsgroup comp.protocols.smb, which has a great deal of
- discussion about Samba.
-
- +o The WWW site 'SAMBA Web Pages' at
- includes:
-
-
- +o Links to man pages and documentation, including this FAQ
-
- +o A comprehensive survey of Samba users
-
- +o A searchable hypertext archive of the Samba mailing list
-
- +o Links to Samba source code, binaries, and mirrors of both
-
- +o This FAQ and the rest in its family
-
-
-
- 22..66.. HHooww ddoo II ssuubbssccrriibbee ttoo tthhee SSaammbbaa MMaaiilliinngg LLiissttss??
-
-
- Send email to listproc@samba.anu.edu.au. Make sure the subject line is
- blank, and include the following two lines in the body of the message:
-
-
-
- subscribe samba Firstname Lastname
- subscribe samba-announce Firstname Lastname
-
-
-
-
- Obviously you should substitute YOUR first name for "Firstname" and
- YOUR last name for "Lastname"! Try not to send any signature, it
- sometimes confuses the list processor.
-
- The samba list is a digest list - every eight hours or so it sends a
- single message containing all the messages that have been received by
- the list since the last time and sends a copy of this message to all
- subscribers. There are thousands of people on this list.
-
- If you stop being interested in Samba, please send another email to
- listproc@samba.anu.edu.au. Make sure the subject line is blank, and
- include the following two lines in the body of the message:
-
-
-
- unsubscribe samba
- unsubscribe samba-announce
-
-
-
-
- The FFrroomm:: line in your message _M_U_S_T be the same address you used when
- you subscribed.
-
-
- 22..77.. SSoommeetthhiinngg''ss ggoonnee wwrroonngg -- wwhhaatt sshhoouulldd II ddoo??
-
-
- ## ****** IIMMPPOORRTTAANNTT!! ****** ##
-
-
- DO NOT post messages on mailing lists or in newsgroups until you have
- carried out the first three steps given here!
-
-
- 1. See if there are any likely looking entries in this FAQ! If you
- have just installed Samba, have you run through the checklist in
- DIAGNOSIS.txt ? It
- can save you a lot of time and effort. DIAGNOSIS.txt can also be
- found in the docs directory of the Samba distribution.
-
- 2. Read the man pages for smbd, nmbd and smb.conf, looking for topics
- that relate to what you are trying to do.
-
- 3. If there is no obvious solution to hand, try to get a look at the
- log files for smbd and/or nmbd for the period during which you were
- having problems. You may need to reconfigure the servers to provide
- more extensive debugging information - usually level 2 or level 3
- provide ample debugging info. Inspect these logs closely, looking
- particularly for the string "Error:".
-
- 4. If you need urgent help and are willing to pay for it see ``Paid
- Support''.
-
- If you still haven't got anywhere, ask the mailing list or newsgroup.
- In general nobody minds answering questions provided you have followed
- the preceding steps. It might be a good idea to scan the archives of
- the mailing list, which are available through the Samba web site
- described in the previous section. When you post be sure to include a
- good description of your environment and your problem.
-
- If you successfully solve a problem, please mail the FAQ maintainer a
- succinct description of the symptom, the problem and the solution, so
- that an explanation can be incorporated into the next version.
-
-
-
-
- 22..88.. HHooww ddoo II ssuubbmmiitt ppaattcchheess oorr bbuugg rreeppoorrttss??
-
-
- If you make changes to the source code, _p_l_e_a_s_e submit these patches 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 samba-bugs@samba.anu.edu.au. Do not send patches to Andrew Tridgell
- or any other individual, they may be lost if you do.
-
- Patch format ------------
-
- If you are sending a patch to fix a problem then please don't just use
- standard diff format. As an example, samba-bugs received this patch
- from someone:
-
- 382a #endif 381a #if !defined(NEWS61)
-
- How are we supposed to work out what this does and where it goes?
- These sort of patches only work if we both have identical files in the
- first place. The Samba sources are constantly changing at the hands of
- multiple developers, so it doesn't work.
-
- Please use either context diffs or (even better) unified diffs. You
- get these using "diff -c4" or "diff -u". If you don't have a diff that
- can generate these then please send manualy commented patches to I
- know what is being changed and where. Most patches are applied by hand
- so the info must be clear.
-
- This is a basic guideline that will assist us with assessing your
- problem more efficiently :
-
- Machine Arch: Machine OS: OS Version: Kernel:
-
- Compiler: Libc Version:
-
- Samba Version:
-
- Network Layout (description):
-
- What else is on machine (services, etc):
-
- Some extras :
-
-
- +o what you did and what happened
-
- +o relevant parts of a debugging output file with debuglevel higher.
- If you can't find the relevant parts, please ask before mailing
- huge files.
-
- +o anything else you think is useful to trace down the bug
-
-
- 22..99.. WWhhaatt iiff II hhaavvee aann UURRGGEENNTT mmeessssaaggee ffoorr tthhee ddeevveellooppeerrss??
-
-
- If you have spotted something very serious and believe that it is
- important to contact the developers quickly send a message to samba-
- urgent@samba.anu.edu.au. This will be processed more quickly than mail
- to samba-bugs. Please think carefully before using this address. An
- example of its use might be to report a security hole.
-
- Examples of things _n_o_t to send to samba-urgent include problems
- getting Samba to work at all and bugs that cannot potentially cause
- damage.
-
- 22..1100.. WWhhaatt iiff II nneeeedd ppaaiidd--ffoorr ssuuppppoorrtt??
-
-
- Samba has a large network of consultants who provide Samba support on
- a commercial basis. The list is included in the package in
- <../Support.txt>, and the latest version will always be on the main
- samba ftp site. Any company in the world can request that the samba
- team include their details in Support.txt so we can give no guarantee
- of their services.
-
-
- 22..1111.. PPiizzzzaa ssuuppppllyy ddeettaaiillss
-
-
- 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 twenty
- thousand kilometres away, but it has been done.
-
-
- 1. Ring up your local branch of an international pizza chain and see
- if they honour their vouchers internationally. Pizza Hut do, which
- is how the entire Canberra Linux Users Group got to eat pizza one
- night, courtesy of someone in the US.
-
- 2. Ring up a local pizza shop in Canberra and quote a credit card
- number for a certain amount, and tell them that Andrew will be
- collecting it (don't forget to tell him.) One kind soul from
- Germany did this.
-
- 3. Purchase a pizza voucher from your local pizza shop that has no
- international affiliations and send it to Andrew. It is completely
- useless but he can hang it on the wall next to the one he already
- has from Germany :-)
-
- 4. Air freight him a pizza with your favourite regional flavours. It
- will probably get stuck in customs or torn apart by hungry sniffer
- dogs but it will have been a noble gesture.
-
-
- 33.. AAbboouutt tthhee CCIIFFSS aanndd SSMMBB PPrroottooccoollss
-
-
-
- 33..11.. WWhhaatt iiss tthhee SSeerrvveerr MMeessssaaggee BBlloocckk ((SSMMBB)) PPrroottooccooll??
-
- SMB is a filesharing protocol that has had several maintainers and
- contributors over the years including Xerox, 3Com and most recently
- Microsoft. Names for this protocol include LAN Manager and Microsoft
- Networking. Parts of the specification has been made public at several
- versions including in an X/Open document, as listed at
- . No specification
- releases were made between 1992 and 1996, and during that period
- Microsoft became the SMB implementor with the largest market share.
- Microsoft developed the specification further for its products but for
- various reasons connected with developer's workload rather than market
- strategy did not make the changes public. This culminated with the
- "Windows NT 0.12" version released with NT 3.5 in 1995 which had
- significant improvements and bugs. Because Microsoft client systems
- are so popular, it is fair to say that what Microsoft with Windows
- affects all suppliers of SMB server products.
-
- From 1994 Andrew Tridgell began doing some serious work on his
- Smbserver (now Samba) product and with some helpers started to
- implement more and more of these protocols. Samba began to take a
- significant share of the SMB server market.
-
-
- 33..22.. WWhhaatt iiss tthhee CCoommmmoonn IInntteerrnneett FFiilleessyysstteemm ((CCIIFFSS))??
-
- The initial pressure for Microsoft to document their current SMB
- implementation came from the Samba team, who kept coming across things
- on the wire that Microsoft either didn't know about or hadn't
- documented anywhere (even in the sourcecode to Windows NT.) Then Sun
- Microsystems came out with their WebNFS initiative, designed to
- replace FTP for file transfers on the Internet. There are many
- drawbacks to WebNFS (including its scope - it aims to replace HTTP as
- well!) but the concept was attractive. FTP is not very clever, and why
- should it be harder to get files from across the world than across the
- room?
-
- Some hasty revisions were made and an Internet Draft for the Common
- Internet Filesystem (CIFS) was released. Note that CIFS is not an
- Internet standard and is a very long way from becoming one, BUT the
- protocol specification is in the public domain and ongoing discussions
- concerning the spec take place on a public mailing list according to
- the rules of the Internet Engineering Task Force. For more information
- and pointers see
-
- The following is taken from
-
-
- CIFS defines a standard remote file system access protocol for use
- over the Internet, enabling groups of users to work together and
- share documents across the Internet or within their corporate
- intranets. CIFS is an open, cross-platform technology based on the
- native file-sharing protocols built into Microsoft Windows and
- other popular PC operating systems, and supported on dozens of
- other platforms, including UNIX. With CIFS, millions of computer
- users can open and share remote files on the Internet without having
- to install new software or change the way they work."
-
-
-
- If you consider CIFS as a backwardsly-compatible refinement of SMB
- that will work reasonably efficiently over the Internet you won't be
- too far wrong.
-
- The net effect is that Microsoft is now documenting large parts of
- their Windows NT fileserver protocols. The security concepts embodied
- in Windows NT are part of the specification, which is why Samba
- documentation often talks in terms of Windows NT. However there is no
- reason why a site shouldn't conduct all its file and printer sharing
- with CIFS and yet have no Microsoft products at all.
-
-
- 33..33.. WWhhaatt iiss BBrroowwssiinngg??
-
- The term "Browsing" causes a lot of confusion. It is the part of the
- SMB/CIFS protocol which allows for resource discovery. For example, in
- the Windows NT Explorer it is possible to see a "Network
- Neighbourhood" of computers in the same SMB workgroup. Clicking on the
- name of one of these machines brings up a list of file and printer
- resources for connecting to. In this way you can cruise the network,
- seeing what things are available. How this scales to the Internet is a
- subject for debate. Look at the CIFS list archives to see what the
- experts think.
-
-
-
-
- 44.. DDeessiiggnniinngg AA SSMMBB aanndd CCIIFFSS NNeettwwoorrkk
-
-
- The big issues for installing any network of LAN or WAN file and print
- servers are
-
-
- +o How and where usernames, passwords and other security information
- is stored
-
- +o What method can be used for locating the resources that users have
- permission to use
-
- +o What protocols the clients can converse with
-
-
- If you buy Netware, Windows NT or just about any other LAN fileserver
- product you are expected to lock yourself into the product's preferred
- answers to these questions. This tendancy is restrictive and often
- very expensive for a site where there is only one kind of client or
- server, and for sites with a mixture of operating systems it often
- makes it impossible to share resources between some sets of users.
-
- The Samba philosophy is to make things as easy as possible for
- administators, which means allowing as many combinations of clients,
- servers, operating systems and protocols as possible.
-
-
- 44..11.. WWoorrkkggrroouuppss,, DDoommaaiinnss,, AAuutthheennttiiccaattiioonn aanndd BBrroowwssiinngg
-
-
- From the point of view of networking implementation, Domains and
- Workgroups are _e_x_a_c_t_l_y the same, except for the client logon sequence.
- Some kind of distributed authentication database is associated with a
- domain (there are quite a few choices) and this adds so much
- flexibility that many people think of a domain as a completely
- different entity to a workgroup. From Samba's point of view a client
- connecting to a service presents an authentication token, and it if it
- is valid they have access. Samba does not care what mechanism was used
- to generate that token in the first place.
-
- The SMB client logging on to a domain has an expectation that every
- other server in the domain should accept the same authentication
- information. However the network browsing functionality of domains
- and workgroups is identical and is explained in <../BROWSING.txt>.
-
- There are some implementation differences: Windows 95 can be a member
- of both a workgroup and a domain, but Windows NT cannot. Windows 95
- also has the concept of an "alternative workgroup". Samba can only be
- a member of a single workgroup or domain, although this is due to
- change with a future version when nmbd will be split into two daemons,
- one for WINS and the other for browsing ( <../NetBIOS.txt> explains
- what WINS is.)
-
-
- 44..11..11.. DDeeffiinniinngg tthhee TTeerrmmss
-
-
-
-
- WWoorrkkggrroouupp
- means a collection of machines that maintain a common browsing
- database containing information about their shared resources.
- They do not necessarily have any security information in common
- (if they do, it gets called a Domain.) The browsing database is
- dynamic, modified as servers come and go on the network and as
- resources are added or deleted. The term "browsing" refers to a
- user accessing the database via whatever interface the client
- provides, eg the OS/2 Workplace Shell or Windows 95 Explorer.
- SMB servers agree between themselves as to which ones will
- maintain the browsing database. Workgroups can be anywhere on a
- connected TCP/IP network, including on different subnets or even
- on the Interet. This is a very tricky part of SMB to implement.
-
-
- MMaasstteerr BBrroowwsseerrss
- are machines which holds the master browsing database for a
- workgroup or domain. There are two kinds of Master Browser:
-
-
- +o Domain Master Browser, which holds the master browsing
- information for an entire domain, which may well cross multiple
- TCP/IP subnets.
-
- +o Local Master Browser, which holds the master browsing database
- for a particular subnet and communicates with the Domain Master
- Browser to get information on other subnets.
-
- Subnets are differentiated because browsing is based on
- broadcasts, and broadcasts do not pass through routers. Subnets
- are not routed: while it is possible to have more than one
- subnet on a single network segment this is regarded as very bad
- practice.
-
- Master Browsers (both Domain and Local) are elected dynamically
- according to an algorithm which is supposed to take into account
- the machine's ability to sustain the browsing load. Samba can be
- configured to always act as a master browser, ie it always wins
- elections under all circumstances, even against systems such as
- a Windows NT Primary Domain Controller which themselves expect
- to win.
-
- There are also Backup Browsers which are promoted to Master
- Browsers in the event of a Master Browser disappearing from the
- network.
-
- Alternative terms include confusing variations such as "Browse
- Master", and "Master Browser" which we are trying to eliminate
- from the Samba documentation.
-
-
- DDoommaaiinn CCoonnttrroolllleerr
- is a term which comes from the Microsoft and IBM etc
- implementation of the LAN Manager protocols. It is tied to
- authentication. There are other ways of doing domain
- authentication, but the Windows NT method has a large market
- share. The general issues are discussed in <../DOMAIN.txt> and
- a Windows NT-specific discussion is in <../DOMAIN_CONTROL.txt>.
-
-
-
- 44..11..22.. SShhaarreelleevveell ((WWoorrkkggrroouupp)) SSeeccuurriittyy SSeerrvviicceess
-
-
- With the Samba setting "security = SHARE", all shared resources
- information about what password is associated with them but only hints
- as to what usernames might be valid (the hint can be 'all users', in
- which case any username will work. This is usually a bad idea, but
- reflects both the initial implementations of SMB in the mid-80s and
- its reincarnation with Windows for Workgroups in 1992. The idea behind
- workgroup security was that small independant groups of people could
- share information on an ad-hoc basis without there being an
- authentication infrastructure present or requiring them to do more
- than fill in a dialogue box.
-
-
- 44..11..33.. AAuutthheennttiiccaattiioonn DDoommaaiinn MMooddee SSeerrvviicceess
-
-
- With the Samba settings "security = USER" or "security = SERVER"
- accesses to all resources are checked for username/password pair
- matches in a more rigorous manner. To the client, this has the effect
- of emulating a Microsoft Domain. The client is not concerned whether
- or not Samba looks up a Windows NT SAM or does it in some other way.
-
-
- 44..22.. AAuutthheennttiiccaattiioonn SScchheemmeess
-
-
- In the simple case authentication information is stored on a single
- server and the user types a password on connecting for the first time.
- However client operating systems often require a password before they
- can be used at all, and in addition users usually want access to more
- than one server. Asking users to remember many different passwords in
- different contexts just does not work. Some kind of distributed
- authentication database is needed. It must cope with password changes
- and provide for assigning groups of users the same level of access
- permissions. This is why Samba installations often choose to implement
- a Domain model straight away.
-
- Authentication decisions are some of the biggest in designing a
- network. Are you going to use a scheme native to the client operating
- system, native to the server operating system, or newly installed on
- both? A list of options relevant to Samba (ie that make sense in the
- context of the SMB protocol) follows. Any experiences with other
- setups would be appreciated. refer to server FAQ for "passwd chat"
- passwd program password server etc etc...
-
-
- 44..22..11.. NNIISS
-
-
- For Windows 95, Windows for Workgroups and most other clients Samba
- can be a domain controller and share the password database via NIS
- transparently. Windows NT is different. Free NIS NT client
-
-
-
- 44..22..22.. KKeerrbbeerrooss
-
-
- Kerberos for US users only: Kerberos overview
- Download
- Kerberos
-
-
- 44..22..33.. FFTTPP
-
-
- Other NT w/s logon hack via NT
-
-
- 44..22..44.. DDeeffaauulltt SSeerrvveerr MMeetthhoodd
-
-
-
-
-
- 44..22..55.. CClliieenntt--ssiiddee DDaattaabbaassee OOnnllyy
-
-
-
- 44..33.. PPoosstt--AAuutthheennttiiccaattiioonn:: NNeettllooggoonn,, LLooggoonn SSccrriippttss,, PPrrooffiilleess
-
-
- See <../DOMAIN.txt>
-
-
- 55.. CCrroossss--PPrroottooccooll FFiillee SShhaarriinngg
-
-
- Samba is an important tool for...
-
- It is possible to...
-
- File protocol gateways...
-
- "Setting up a Linux File Server"
- http://vetrec.mit.edu/people/narf/linux.html
-
- Two free implementations of Appletalk for Unix are Netatalk,
- , and CAP,
- . What Samba offers MS
- Windows users, these packages offer to Macs. For more info on these
- packages, Samba, and Linux (and other UNIX-based systems) see
- 3.5) Sniffing your nework
-
-
-
- 66.. MMiisscceellllaanneeoouuss
-
-
- 66..11.. IIss SSaammbbaa YYeeaarr 22000000 ccoommpplliiaanntt??
-
-
- The CIFS protocol that Samba implements negotiates times in various
- formats, all of which are able to cope with dates beyond 2000.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/faq/sambafaq-1.html b/docs/faq/sambafaq-1.html
deleted file mode 100644
index c010e50e011..00000000000
--- a/docs/faq/sambafaq-1.html
+++ /dev/null
@@ -1,392 +0,0 @@
-
-
- Samba FAQ: General Information
-
-
-Previous
-Next
-Table of Contents
-
-
-
-
-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.
-
In practice, this means that you can redirect disks and printers to
-Unix disks and printers from Lan Manager clients, Windows for
-Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
-clients. There is also a generic Unix client program supplied as part
-of the suite which allows Unix users to use an ftp-like interface to
-access filespace and printers on any other SMB servers. This gives the
-capability for these operating systems to behave much like a LAN
-Server or Windows NT Server machine, only with added functionality and
-flexibility designed to make life easier for administrators.
-
The components of the suite are (in summary):
-
-
-
smbd, the SMB server. This handles actual connections from clients, doing all the file, permission and username work
-
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
-
smbclient, the Unix-hosted client program
-
smbrun, a little 'glue' program to help the server run external programs
-
testprns, a program to test server access to printers
-
testparms, a program to test the Samba configuration file for correctness
-
smb.conf, the Samba configuration file
-
smbprint, a sample script to allow a Unix host to use smbclient to print to an SMB server
-
Documentation! DON'T neglect to read it - you will save a great deal of time!
-
-
-
The suite is supplied with full source (of course!) and is GPLed.
-
The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer.
-
-
-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:
-
/pub/samba/
-
Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are
-available in the directory:
-
/pub/samba/alpha
-
Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Recent versions of some Linux distributions, for example,
-do contain Samba binaries for that platform.
-
-
-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
-all means take the plunge and help with the testing and development -
-but don't install it on your departmental server. Samba is typically
-very stable and safe, and this is mostly due to the policy of many
-public releases.
-
How the scheme works:
-
-
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.)
-
-
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.
-
-
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.
-
-
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.
-
-The above system means that whenever someone looks at the samba ftp
-site they will be able to grab the highest numbered release without an
-alpha in the name and be sure of getting the current recommended
-version.
-
-
-
Links to man pages and documentation, including this FAQ
-
A comprehensive survey of Samba users.
-
A searchable hypertext archive of the Samba mailing list.
-
Links to Samba source code, binaries, and mirrors of both.
-
-
-
The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at
-ftp://samba.anu.edu.au/pub/samba/docs/
-
-
-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.
-
The samba list is a digest list - every eight hours or so it
-regurgitates a single message containing all the messages that have
-been received by the list since the last time and sends a copy of this
-message to all subscribers.
-
If you stop being interested in Samba, please send another email to
-listproc@samba.anu.edu.au. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
-
-unsubscribe samba
-unsubscribe samba-announce
-
-
-
-The From: line in your message MUST be the same address you used when
-you subscribed.
-
-
-
DO NOT post messages on mailing lists or in newsgroups until you have
-carried out the first three steps given here!
-
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
-DIAGNOSIS.txt? It can save you a lot of time and effort.
-DIAGNOSIS.txt can also be found in the docs directory of the Samba distribution.
-
Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
-topics that relate to what you are trying to do.
-
Thirdly, if there is no obvious solution to hand, try to get a look at
-the log files for smbd and/or nmbd for the period during which you
-were having problems. You may need to reconfigure the servers to
-provide more extensive debugging information - usually level 2 or
-level 3 provide ample debugging info. Inspect these logs closely,
-looking particularly for the string "Error:".
-
Fourthly, if you still haven't got anywhere, ask the mailing list or
-newsgroup. In general nobody minds answering questions provided you
-have followed the preceding steps. It might be a good idea to scan the
-archives of the mailing list, which are available through the Samba
-web site described in the previous
-section.
-
If you successfully solve a problem, please mail the FAQ maintainer a
-succinct description of the symptom, the problem and the solution, so
-I can incorporate it in the next version.
-
If you make changes to the source code, _please_ submit these patches
-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
-samba-bugs@samba.anu.edu.au. Do not send patches to Andrew Tridgell or any
-other individual, they may be lost if you do.
-
-
-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
-twenty thousand kilometres away, but it has been done.
-
Method 1: Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US
-
Method 2: Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
Method 3: Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
Method 4: Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/sambafaq-2.html b/docs/faq/sambafaq-2.html
deleted file mode 100644
index b92a1e2fcd1..00000000000
--- a/docs/faq/sambafaq-2.html
+++ /dev/null
@@ -1,239 +0,0 @@
-
-
- Samba FAQ: Compiling and installing Samba on a Unix host
-
-
-Previous
-Next
-Table of Contents
-
-
-
-
-See
-BROWSING.txt
-for more information on browsing. Browsing.txt can also be found
-in the docs directory of the Samba source.
-
If your GUI client does not permit you to select non-browsable
-servers, you may need to do so on the command line. For example, under
-Lan Manager you might connect to the above service as disk drive M:
-thusly:
-
-
- net use M: \\mary\fred
-
-
-
-The details of how to do this and the specific syntax varies from
-client to client - check your client's documentation.
-
-
-
-
-
-If you check what files are not showing up, you will note that they
-are files which contain upper case letters or which are otherwise not
-DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
The Samba server can be configured either to ignore such files
-completely, or to present them to the client in "mangled" form. If you
-are not seeing the files at all, the Samba server has most likely been
-configured to ignore them. Consult the man page smb.conf(5) for
-details of how to change this - the parameter you need to set is
-"mangled names = yes".
-
-
-This indicates one of three things: You supplied an incorrect server
-name, the underlying TCP/IP layer is not working correctly, or the
-name you specified cannot be resolved.
-
After carefully checking that the name you typed is the name you
-should have typed, try doing things like pinging a host or telnetting
-to somewhere on your network to see if TCP/IP is functioning OK. If it
-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
-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
-there is something fundamental wrong with your naming and the solution
-is beyond the scope of this document.
-
If you do not have any server on your subnet supplying netbios name
-resolution, hardcoded mappings are your only option. If you DO have a
-netbios name server running (such as the Samba suite's nmbd program),
-the problem probably lies in the way it is set up. Refer to Section
-Two of this FAQ for more ideas.
-
By the way, remember to REMOVE the hardcoded mapping before further
-tests :-)
-
-
-This message indicates that your client CAN locate the specified
-server, which is a good start, but that it cannot find a service of
-the name you gave.
-
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
-to specify a service name correctly), read on:
-
-
-
Many clients cannot accept or use service names longer than eight characters.
-
Many clients cannot accept or use service names containing spaces.
-
Some servers (not Samba though) are case sensitive with service names.
-
-
-Nothing is wrong - Samba does not implement the primary domain name
-controller stuff for several reasons, including the fact that the
-whole concept of a primary domain controller and "logging in to a
-network" doesn't fit well with clients possibly running on multiuser
-machines (such as users of smbclient under Unix). Having said that,
-several developers are working hard on building it in to the next
-major version of Samba. If you can contribute, send a message to
-samba-bugs@samba.anu.edu.au !
-
Seeing this message should not affect your ability to mount redirected
-disks and printers, which is really what all this is about.
-
For many clients (including Windows for Workgroups and Lan Manager),
-setting the domain to STANDALONE at least gets rid of the message.
-
-
-Make sure that the specified print command for the service you are
-connecting to is correct and that it has a fully-qualified path (eg.,
-use "/usr/bin/lpr" rather than just "lpr").
-
Make sure that the spool directory specified for the service is
-writable by the user connected to the service. In particular the user
-"nobody" often has problems with printing, even if it worked with an
-earlier version of Samba. Try creating another guest user other than
-"nobody".
-
Make sure that the user specified in the service is permitted to use
-the printer.
-
Check the debug log produced by smbd. Search for the printer name and
-see if the log turns up any clues. Note that error messages to do with
-a service ipc$ are meaningless - they relate to the way the client
-attempts to retrieve status information when using the LANMAN1
-protocol.
-
If using WfWg then you need to set the default protocol to TCP/IP, not
-Netbeui. This is a WfWg bug.
-
If using the Lanman1 protocol (the default) then try switching to
-coreplus. Also not that print status error messages don't mean
-printing won't work. The print status is received by a different
-mechanism.
-
-
-There are numerous possible reasons for this, but one MAJOR
-possibility is that your software uses locking. Make sure you are
-using Samba 1.6.11 or later. It may also be possible to work around
-the problem by setting "locking=no" in the Samba configuration file
-for the service the software is installed on. This should be regarded
-as a strictly temporary solution.
-
In earlier Samba versions there were some difficulties with the very
-latest Microsoft products, particularly Excel 5 and Word for Windows
-6. These should have all been solved. If not then please let Andrew
-Tridgell know via email at
-samba-bugs@samba.anu.edu.au.
-
-
-Your guest account is probably invalid for some reason. Samba uses the
-guest account for browsing in smbd. Check that your guest account is
-valid.
-
-
-This can have several causes. It might be because you are using a uid
-or gid of 65535 or -1. This is a VERY bad idea, and is a big security
-hole. Check carefully in your /etc/passwd file and make sure that no
-user has uid 65535 or -1. Especially check the "nobody" user, as many
-broken systems are shipped with nobody setup with a uid of 65535.
-
It might also mean that your OS has a trapdoor uid/gid system :-)
-
This means that once a process changes effective uid from root to
-another user it can't go back to root. Unfortunately Samba relies on
-being able to change effective uid from root to non-root and back
-again to implement its security policy. If your OS has a trapdoor uid
-system this won't work, and several things in Samba may break. Less
-things will break if you use user or server level security instead of
-the default share level security, but you may still strike
-problems.
-
The problems don't give rise to any security holes, so don't panic,
-but it does mean some of Samba's capabilities will be unavailable.
-In particular you will not be able to connect to the Samba server as
-two different uids at once. This may happen if you try to print as a
-"guest" while accessing a share as a normal user. It may also affect
-your ability to list the available shares as this is normally done as
-the guest user.
-
Complain to your OS vendor and ask them to fix their system.
-
Note: the reason why 65535 is a VERY bad choice of uid and gid is that
-it casts to -1 as a uid, and the setreuid() system call ignores (with
-no error) uid changes to -1. This means any daemon attempting to run
-as uid 65535 will actually run as root. This is not good!
-
-
-Yes! Thursby now have a CIFS Client / Server called DAVE - see
-http://www.thursby.com/.
-They test it against Windows 95, Windows NT and samba for compatibility issues.
-At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available
-as a free download from the Thursby web site (the speed of finder copies has
-been greatly enhanced, and there are bug-fixes included).
-
Alternatives - There are two free implementations of AppleTalk for
-several kinds of UNIX machnes, and several more commercial ones.
-These products allow you to run file services and print services
-natively to Macintosh users, with no additional support required on
-the Macintosh. The two free omplementations are Netatalk,
-http://www.umich.edu/~rsug/netatalk/, and CAP,
-http://www.cs.mu.oz.au/appletalk/atalk.html. What Samba offers
-MS Windows users, these packages offer to Macs. For more info on
-these packages, Samba, and Linux (and other UNIX-based systems)
-see
-http://www.eats.com/linux_mac_win.html
-
-
-The following answer is provided by John E. Miller:
-
I'll assume that you're able to ping back and forth between the
-machines by IP address and name, and that you're using some security
-model where you're confident that you've got user IDs and passwords
-right. The logging options (-d3 or greater) can help a lot with that.
-DNS and WINS configuration can also impact connectivity as well.
-
Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
-configuration (I'm too much of an NT bigot to know where it's located
-in the Win95 setup, but I'll have to learn someday since I teach for a
-Microsoft Solution Provider Authorized Tech Education Center - what an
-acronym...) Note: It's under Control Panel | Network | TCP/IP | WINS
-Configuration there's a little text entry field called something like
-'Scope ID'.
-
This field essentially creates 'invisible' sub-workgroups on the same
-wire. Boxes can only see other boxes whose Scope IDs are set to the
-exact same value - it's sometimes used by OEMs to configure their
-boxes to browse only other boxes from the same vendor and, in most
-environments, this field should be left blank. If you, in fact, have
-something in this box that EXACT value (case-sensitive!) needs to be
-provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
-your Scope ID is configured as the string 'SomeStr' in Win95 then
-you'd have to use smbclient -iSomeStr otherparms in connecting to
-it.
All of the above programs are applications that sit on an NT box and
-allow multiple users to access the NT GUI applications from remote
-workstations (often over X).
-
What has this got to do with Samba? The problem comes when these users
-use filemanager to mount shares from a Samba server. The most common
-symptom is that the first user to connect get correct file permissions
-and has a nice day, but subsequent connections get logged in as the
-same user as the first person to login. They find that they cannot
-access files in their own home directory, but that they can access
-files in the first users home directory (maybe not such a nice day
-after all?)
-
Why does this happen? The above products all share a common heritage
-(and code base I believe). They all open just a single TCP based SMB
-connection to the Samba server, and requests from all users are piped
-over this connection. This is unfortunate, but not fatal.
-
It means that if you run your Samba server in share level security
-(the default) then things will definately break as described
-above. The share level SMB security model has no provision for
-multiple user IDs on the one SMB connection. See
-security_level.txt in
-the docs for more info on share/user/server level security.
-
If you run in user or server level security then you have a chance,
-but only if you have a recent version of Samba (at least 1.9.15p6). In
-older versions bugs in Samba meant you still would have had problems.
-
If you have a trapdoor uid system in your OS then it will never work
-properly. Samba needs to be able to switch uids on the connection and
-it can't if your OS has a trapdoor uid system. You'll know this
-because Samba will note it in your logs.
-
Also note that you should not use the magic "homes" share name with
-products like these, as otherwise all users will end up with the same
-home directory. Use \\server\username instead.
-
-
-This info from Stefan Hergeth
-hergeth@f7axp1.informatik.fh-muenchen.de may be useful:
-
A network-printer (with ethernetcard) is connected to the NT-Clients
-via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
-Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
-
-
If a user has choosen this printer as the default printer in his
-NT-Session and this printer is not connected to the network
-(e.g. switched off) than this user has a problem with the SAMBA-
-connection of his filesystems. It's very slow.
-
-
If the printer is connected to the network everything works fine.
-
-
When the smbd ist started with debug level 3, you can see that the
-NT spooling system try to connect to the printer many times. If the
-printer ist not connected to the network this request fails and the
-NT spooler is wasting a lot of time to connect to the printer service.
-This seems to be the reason for the slow network connection.
-
-
Maybe it's possible to change this behaviour by setting different
-printer properties in the Print-Manager-Menu of NT, but i didn't try it yet.
Most likely it's a problem with your time zone settings.
-
Internally, Samba maintains time in traditional Unix format,
-namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
-(or ``GMT''), not counting leap seconds.
-
On the server side, Samba uses the Unix TZ variable to convert
-internal timestamps to and from local time. So on the server side, there are
-two things to get right.
-
-
The Unix system clock must have the correct Universal time.
-Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
-
-
The TZ environment variable must be set on the server
-before Samba is invoked. The details of this depend on the
-server OS, but typically you must edit a file whose name is
-/etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.
-
-
TZ must have the correct value.
-
-
If possible, use geographical time zone settings
-(e.g. TZ='America/Los_Angeles' or perhaps
-TZ=':US/Pacific'). These are supported by most
-popular Unix OSes, are easier to get right, and are
-more accurate for historical timestamps. If your
-operating system has out-of-date tables, you should be
-able to update them from the public domain time zone
-tables at
-ftp://elsie.nci.nih.gov/pub/.
-
-
If your system does not support geographical timezone
-settings, you must use a Posix-style TZ strings, e.g.
-TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
-Posix TZ strings can take the following form (with optional
-items in brackets):
-
- StdOffset[Dst[Offset],Date/Time,Date/Time]
-
-
-where:
-
-
`Std' is the standard time designation (e.g. `PST').
-
-
`Offset' is the number of hours behind UTC (e.g. `8').
-Prepend a `-' if you are ahead of UTC, and
-append `:30' if you are at a half-hour offset.
-Omit all the remaining items if you do not use
-daylight-saving time.
-
-
`Dst' is the daylight-saving time designation
-(e.g. `PDT').
-
-The optional second `Offset' is the number of
-hours that daylight-saving time is behind UTC.
-The default is 1 hour ahead of standard time.
-
-
`Date/Time,Date/Time' specify when daylight-saving
-time starts and ends. The format for a date is
-`Mm.n.d', which specifies the dth day (0 is Sunday)
-of the nth week of the mth month, where week 5 means
-the last such day in the month. The format for a
-time is hh:mm[:ss], using a 24-hour clock.
-
-
-Other Posix string formats are allowed but you don't want
-to know about them.
-
-
-
-
-On the client side, you must make sure that your client's clock and
-time zone is also set appropriately. [I don't know how to do this.]
-Samba traditionally has had many problems dealing with time zones, due
-to the bizarre ways that Microsoft network protocols handle time
-zones. A common symptom is for file timestamps to be off by an hour.
-To work around the problem, try disconnecting from your Samba server
-and then reconnecting to it; or upgrade your Samba server to
-1.9.16alpha10 or later.
-
-
-
-
-
-Question:
-On NT, I opened "Printer Manager" and "Connect to Printer".
-Enter "\\ptdi270\ps1" in the box of printer. I got the
-following error message:
-
-
- You do not have sufficient access to your machine
- to connect to the selected printer, since a driver
- needs to be installed locally.
-
-
-
-Answer:
-
In the more recent versions of Samba you can now set the "printer
-driver" in smb.conf. This tells the client what driver to use. For
-example:
-
-
- printer driver = HP LaserJet 4L
-
-
-
-with this, NT knows to use the right driver. You have to get this string
-exactly right.
-
To find the exact string to use, you need to get to the dialog box in
-your client where you select which printer driver to install. The
-correct strings for all the different printers are shown in a listbox
-in that dialog box.
-
You could also try setting the driver to NULL like this:
-
-
- printer driver = NULL
-
-
-
-this is effectively what older versions of Samba did, so if that
-worked for you then give it a go. If this does work then let us know via
-samba-bugs@samba.anu.edu.au,
-and we'll make it the default. Currently the default is a 0 length
-string.
-
-
-
-
-
-As of SP3, Microsoft has decided that they will no longer default to
-passing clear text passwords over the network. To enable access to
-Samba shares from NT 4.0 SP3, you must do ONE of two things:
-
-
Set the Samba configuration option 'security = user' and implement all of the stuff detailed in
-ENCRYPTION.txt.
-
Follow Microsoft's directions for setting your NT box to allow plain text passwords. see
-Knowledge Base Article Q166730
-
-
-When installing MS Office on a Samba drive for which you have admin
-user permissions, ie. admin users = username, you will find the
-setup program unable to complete the installation.
-
To get around this problem, do the installation without admin user
-permissions The problem is that MS Office Setup checks that a file is
-rdonly by trying to open it for writing.
-
Admin users can always open a file for writing, as they run as root.
-You just have to install as a non-admin user and then use "chown -R"
-to fix the owner.
v 0.8, June '97
- This is the Frequently Asked Questions (FAQ) document for
-Samba, the free and very popular SMB server product. An SMB server
-allows file and printer connections from clients such as Windows,
-OS/2, Linux and others. Current to version 1.9.17. Please send any
-corrections to the author.
-
-
-
-
-Previous
-Next
-Table of Contents
-
-
diff --git a/docs/faq/sambafaq.sgml b/docs/faq/sambafaq.sgml
deleted file mode 100644
index d306881b56b..00000000000
--- a/docs/faq/sambafaq.sgml
+++ /dev/null
@@ -1,792 +0,0 @@
-
-
-
-
-
- Samba FAQ
-
-Paul Blackman, ictinus@samba.anu.edu.au
-
-v 0.8, June '97
-
- This is the Frequently Asked Questions (FAQ) document for
-Samba, the free and very popular SMB server product. An SMB server
-allows file and printer connections from clients such as Windows,
-OS/2, Linux and others. Current to version 1.9.17. Please send any
-corrections to the author.
-
-
-
-
- General Information
-
-All about Samba - what it is, how to get it, related sources of
-information, how to understand the version numbering scheme, pizza
-details
-
- What is Samba?
-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.
-
-In practice, this means that you can redirect disks and printers to
-Unix disks and printers from Lan Manager clients, Windows for
-Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
-clients. There is also a generic Unix client program supplied as part
-of the suite which allows Unix users to use an ftp-like interface to
-access filespace and printers on any other SMB servers. This gives the
-capability for these operating systems to behave much like a LAN
-Server or Windows NT Server machine, only with added functionality and
-flexibility designed to make life easier for administrators.
-
-The components of the suite are (in summary):
-
-
-smbd, the SMB server. This handles actual connections from clients, doing all the file, permission and username work
-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
-smbclient, the Unix-hosted client program
-smbrun, a little 'glue' program to help the server run external programs
-testprns, a program to test server access to printers
-testparms, a program to test the Samba configuration file for correctness
-smb.conf, the Samba configuration file
-smbprint, a sample script to allow a Unix host to use smbclient to print to an SMB server
-Documentation! DON'T neglect to read it - you will save a great deal of time!
-
-
-The suite is supplied with full source (of course!) and is GPLed.
-
-The primary creator of the Samba suite is Andrew Tridgell. Later
-versions incorporate much effort by many net.helpers. The man pages
-and this FAQ were originally written by Karl Auer.
-
- What is the current version of Samba?
-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.
-
-For more information see
-
- Where can I get it?
-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:
-
-/pub/samba/
-
-Development (read "alpha") versions, which are NOT necessarily stable
-and which do NOT necessarily have accurate documentation, are
-available in the directory:
-
-/pub/samba/alpha
-
-Note that binaries are NOT included in any of the above. Samba is
-distributed ONLY in source form, though binaries may be available from
-other sites. Recent versions of some Linux distributions, for example,
-do contain Samba binaries for that platform.
-
- What do the version numbers mean?
-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
-all means take the plunge and help with the testing and development -
-but don't install it on your departmental server. Samba is typically
-very stable and safe, and this is mostly due to the policy of many
-public releases.
-
-How the scheme works:
-
-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.)
-
-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.
-
-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.
-
-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.
-
-So the progression goes:
-
- 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)
-
-The above system means that whenever someone looks at the samba ftp
-site they will be able to grab the highest numbered release without an
-alpha in the name and be sure of getting the current recommended
-version.
-
- What platforms are supported?
-Many different platforms have run Samba successfully. The platforms
-most widely used and thus best tested are Linux and SunOS.
-
-At time of writing, the Makefile claimed support for:
-
- A/UX 3.0
- AIX
- Altos Series 386/1000
- Amiga
- Apollo Domain/OS sr10.3
- BSDI
- B.O.S. (Bull Operating System)
- Cray, Unicos 8.0
- Convex
- DGUX.
- DNIX.
- FreeBSD
- HP-UX
- Intergraph.
- Linux with/without shadow passwords and quota
- LYNX 2.3.0
- MachTen (a unix like system for Macintoshes)
- Motorola 88xxx/9xx range of machines
- NetBSD
- NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).
- OS/2 using EMX 0.9b
- OSF1
- QNX 4.22
- RiscIX.
- RISCOs 5.0B
- SEQUENT.
- SCO (including: 3.2v2, European dist., OpenServer 5)
- SGI.
- SMP_DC.OSx v1.1-94c079 on Pyramid S series
- SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
- SUNOS 4
- SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
- Sunsoft ISC SVR3V4
- SVR4
- System V with some berkely extensions (Motorola 88k R32V3.2).
- ULTRIX.
- UNIXWARE
- UXP/DS
-
-
- How can I find out more about Samba?
-There are a number of places to look for more information on Samba, including:
-
-Two mailing lists devoted to discussion of Samba-related matters.
-The newsgroup, comp.protocols.smb, which has a great deal of discussion on Samba.
-The WWW site 'SAMBA Web Pages' at includes:
-
- Links to man pages and documentation, including this FAQ
- A comprehensive survey of Samba users.
- A searchable hypertext archive of the Samba mailing list.
- Links to Samba source code, binaries, and mirrors of both.
-
-The long list of topic documentation. These files can be found in the 'docs' directory of the Samba source, or at
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-How do I subscribe to the Samba Mailing Lists?
-Send email to . Make sure the subject line is
-blank, and include the following two lines in the body of the message:
-
-subscribe samba Firstname Lastname
-subscribe samba-announce Firstname Lastname
-
-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.
-
-The samba list is a digest list - every eight hours or so it
-regurgitates a single message containing all the messages that have
-been received by the list since the last time and sends a copy of this
-message to all subscribers.
-
-If you stop being interested in Samba, please send another email to
-. Make sure the subject line is blank, and
-include the following two lines in the body of the message:
-
-unsubscribe samba
-unsubscribe samba-announce
-
-The From: line in your message MUST be the same address you used when
-you subscribed.
-
- Something's gone wrong - what should I do?
-[#] *** IMPORTANT! *** [#]
-
DO NOT post messages on mailing lists or in newsgroups until you have
-carried out the first three steps given here!
-
-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
-? It can save you a lot of time and effort.
-DIAGNOSIS.txt can also be found in the docs directory of the Samba distribution.
-
-Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
-topics that relate to what you are trying to do.
-
-Thirdly, if there is no obvious solution to hand, try to get a look at
-the log files for smbd and/or nmbd for the period during which you
-were having problems. You may need to reconfigure the servers to
-provide more extensive debugging information - usually level 2 or
-level 3 provide ample debugging info. Inspect these logs closely,
-looking particularly for the string "Error:".
-
-Fourthly, if you still haven't got anywhere, ask the mailing list or
-newsgroup. In general nobody minds answering questions provided you
-have followed the preceding steps. It might be a good idea to scan the
-archives of the mailing list, which are available through the Samba
-web site described in the previous
-section.
-
-If you successfully solve a problem, please mail the FAQ maintainer a
-succinct description of the symptom, the problem and the solution, so
-I can incorporate it in the next version.
-
-If you make changes to the source code, _please_ submit these patches
-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 . Do not send patches to Andrew Tridgell or any
-other individual, they may be lost if you do.
-
- Pizza supply details
-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
-twenty thousand kilometres away, but it has been done.
-
-Method 1: Ring up your local branch of an international pizza chain
-and see if they honour their vouchers internationally. Pizza Hut do,
-which is how the entire Canberra Linux Users Group got to eat pizza
-one night, courtesy of someone in the US
-
-Method 2: Ring up a local pizza shop in Canberra and quote a credit
-card number for a certain amount, and tell them that Andrew will be
-collecting it (don't forget to tell him.) One kind soul from Germany
-did this.
-
-Method 3: Purchase a pizza voucher from your local pizza shop that has
-no international affiliations and send it to Andrew. It is completely
-useless but he can hang it on the wall next to the one he already has
-from Germany :-)
-
-Method 4: Air freight him a pizza with your favourite regional
-flavours. It will probably get stuck in customs or torn apart by
-hungry sniffer dogs but it will have been a noble gesture.
-
-Compiling and installing Samba on a Unix host
-
-I can't see the Samba server in any browse lists!
- See
- for more information on browsing. Browsing.txt can also be found
- in the docs directory of the Samba source.
-
-If your GUI client does not permit you to select non-browsable
-servers, you may need to do so on the command line. For example, under
-Lan Manager you might connect to the above service as disk drive M:
-thusly:
-
- net use M: \\mary\fred
-
-The details of how to do this and the specific syntax varies from
-client to client - check your client's documentation.
-
-Some files that I KNOW are on the server doesn't show up when I view the files from my client!
-See the next question.
-Some files on the server show up with really wierd filenames when I view the files from my client!
-If you check what files are not showing up, you will note that they
-are files which contain upper case letters or which are otherwise not
-DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
-The Samba server can be configured either to ignore such files
-completely, or to present them to the client in "mangled" form. If you
-are not seeing the files at all, the Samba server has most likely been
-configured to ignore them. Consult the man page smb.conf(5) for
-details of how to change this - the parameter you need to set is
-"mangled names = yes".
-
-My client reports "cannot locate specified computer" or similar
-This indicates one of three things: You supplied an incorrect server
-name, the underlying TCP/IP layer is not working correctly, or the
-name you specified cannot be resolved.
-
-After carefully checking that the name you typed is the name you
-should have typed, try doing things like pinging a host or telnetting
-to somewhere on your network to see if TCP/IP is functioning OK. If it
-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
-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
-there is something fundamental wrong with your naming and the solution
-is beyond the scope of this document.
-
-If you do not have any server on your subnet supplying netbios name
-resolution, hardcoded mappings are your only option. If you DO have a
-netbios name server running (such as the Samba suite's nmbd program),
-the problem probably lies in the way it is set up. Refer to Section
-Two of this FAQ for more ideas.
-
-By the way, remember to REMOVE the hardcoded mapping before further
-tests :-)
-
-My client reports "cannot locate specified share name" or similar
-This message indicates that your client CAN locate the specified
-server, which is a good start, but that it cannot find a service of
-the name you gave.
-
-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
-to specify a service name correctly), read on:
-
-
- Many clients cannot accept or use service names longer than eight characters.
- Many clients cannot accept or use service names containing spaces.
- Some servers (not Samba though) are case sensitive with service names.
- Some clients force service names into upper case.
-
-
-My client reports "cannot find domain controller", "cannot log on to the network" or similar
-Nothing is wrong - Samba does not implement the primary domain name
-controller stuff for several reasons, including the fact that the
-whole concept of a primary domain controller and "logging in to a
-network" doesn't fit well with clients possibly running on multiuser
-machines (such as users of smbclient under Unix). Having said that,
-several developers are working hard on building it in to the next
-major version of Samba. If you can contribute, send a message to
- !
-
-Seeing this message should not affect your ability to mount redirected
-disks and printers, which is really what all this is about.
-
-For many clients (including Windows for Workgroups and Lan Manager),
-setting the domain to STANDALONE at least gets rid of the message.
-
-Printing doesn't work :-(
-Make sure that the specified print command for the service you are
-connecting to is correct and that it has a fully-qualified path (eg.,
-use "/usr/bin/lpr" rather than just "lpr").
-
-Make sure that the spool directory specified for the service is
-writable by the user connected to the service. In particular the user
-"nobody" often has problems with printing, even if it worked with an
-earlier version of Samba. Try creating another guest user other than
-"nobody".
-
-Make sure that the user specified in the service is permitted to use
-the printer.
-
-Check the debug log produced by smbd. Search for the printer name and
-see if the log turns up any clues. Note that error messages to do with
-a service ipc$ are meaningless - they relate to the way the client
-attempts to retrieve status information when using the LANMAN1
-protocol.
-
-If using WfWg then you need to set the default protocol to TCP/IP, not
-Netbeui. This is a WfWg bug.
-
-If using the Lanman1 protocol (the default) then try switching to
-coreplus. Also not that print status error messages don't mean
-printing won't work. The print status is received by a different
-mechanism.
-
-My programs install on the server OK, but refuse to work properly
-There are numerous possible reasons for this, but one MAJOR
-possibility is that your software uses locking. Make sure you are
-using Samba 1.6.11 or later. It may also be possible to work around
-the problem by setting "locking=no" in the Samba configuration file
-for the service the software is installed on. This should be regarded
-as a strictly temporary solution.
-
-In earlier Samba versions there were some difficulties with the very
-latest Microsoft products, particularly Excel 5 and Word for Windows
-6. These should have all been solved. If not then please let Andrew
-Tridgell know via email at .
-
-My "server string" doesn't seem to be recognised
-OR My client reports the default setting, eg. "Samba 1.9.15p4", instead
-of what I have changed it to in the smb.conf file.
-
-You need to use the -C option in nmbd. The "server string" affects
-what smbd puts out and -C affects what nmbd puts out.
-
-Current versions of Samba (1.9.16 +) have combined these options into
-the "server string" field of smb.conf, -C for nmbd is now obsolete.
-
-My client reports "This server is not configured to list shared resources"
-Your guest account is probably invalid for some reason. Samba uses the
-guest account for browsing in smbd. Check that your guest account is
-valid.
-
-See also 'guest account' in smb.conf man page.
-
-Log message "you appear to have a trapdoor uid system"
-This can have several causes. It might be because you are using a uid
-or gid of 65535 or -1. This is a VERY bad idea, and is a big security
-hole. Check carefully in your /etc/passwd file and make sure that no
-user has uid 65535 or -1. Especially check the "nobody" user, as many
-broken systems are shipped with nobody setup with a uid of 65535.
-
-It might also mean that your OS has a trapdoor uid/gid system :-)
-
-This means that once a process changes effective uid from root to
-another user it can't go back to root. Unfortunately Samba relies on
-being able to change effective uid from root to non-root and back
-again to implement its security policy. If your OS has a trapdoor uid
-system this won't work, and several things in Samba may break. Less
-things will break if you use user or server level security instead of
-the default share level security, but you may still strike
-problems.
-
-The problems don't give rise to any security holes, so don't panic,
-but it does mean some of Samba's capabilities will be unavailable.
-In particular you will not be able to connect to the Samba server as
-two different uids at once. This may happen if you try to print as a
-"guest" while accessing a share as a normal user. It may also affect
-your ability to list the available shares as this is normally done as
-the guest user.
-
-Complain to your OS vendor and ask them to fix their system.
-
-Note: the reason why 65535 is a VERY bad choice of uid and gid is that
-it casts to -1 as a uid, and the setreuid() system call ignores (with
-no error) uid changes to -1. This means any daemon attempting to run
-as uid 65535 will actually run as root. This is not good!
-
-Common client questions
-
-Are there any Macintosh clients for Samba?
-Yes! Thursby now have a CIFS Client / Server called DAVE - see .
-They test it against Windows 95, Windows NT and samba for compatibility issues.
-At the time of writing, DAVE was at version 1.0.1. The 1.0.0 to 1.0.1 update is available
-as a free download from the Thursby web site (the speed of finder copies has
-been greatly enhanced, and there are bug-fixes included).
-
-Alternatives - There are two free implementations of AppleTalk for
-several kinds of UNIX machnes, and several more commercial ones.
-These products allow you to run file services and print services
-natively to Macintosh users, with no additional support required on
-the Macintosh. The two free omplementations are Netatalk,
-, and CAP,
-. What Samba offers
-MS Windows users, these packages offer to Macs. For more info on
-these packages, Samba, and Linux (and other UNIX-based systems)
-see
-
-"Session request failed (131,130)" error
-The following answer is provided by John E. Miller:
-
-I'll assume that you're able to ping back and forth between the
-machines by IP address and name, and that you're using some security
-model where you're confident that you've got user IDs and passwords
-right. The logging options (-d3 or greater) can help a lot with that.
-DNS and WINS configuration can also impact connectivity as well.
-
-Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
-configuration (I'm too much of an NT bigot to know where it's located
-in the Win95 setup, but I'll have to learn someday since I teach for a
-Microsoft Solution Provider Authorized Tech Education Center - what an
-acronym...) [Note: It's under Control Panel | Network | TCP/IP | WINS
-Configuration] there's a little text entry field called something like
-'Scope ID'.
-
-This field essentially creates 'invisible' sub-workgroups on the same
-wire. Boxes can only see other boxes whose Scope IDs are set to the
-exact same value - it's sometimes used by OEMs to configure their
-boxes to browse only other boxes from the same vendor and, in most
-environments, this field should be left blank. If you, in fact, have
-something in this box that EXACT value (case-sensitive!) needs to be
-provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
-your Scope ID is configured as the string 'SomeStr' in Win95 then
-you'd have to use smbclient -iSomeStr [otherparms] in connecting to
-it.
-
-How do I synchronise my PC's clock with my Samba server?
-To syncronize your PC's clock with your Samba server:
-
- Copy timesync.pif to your windows directory
- timesync.pif can be found at:
-
- Add timesync.pif to your 'Start Up' group/folder
- Open the properties dialog box for the program/icon
- Make sure the 'Run Minimized' option is set in program 'Properties'
- Change the command line section that reads [\\sambahost] to reflect the name of your server.
- Close the properties dialog box by choosing 'OK'
-
-Each time you start your computer (or login for Win95) your PC will
-synchronize its clock with your Samba server.
-
-Alternativley, if you clients support Domain Logons, you can setup Domain Logons with Samba
- - see: *** for more information.
-
Then add
-
-NET TIME \\%L /SET /YES
-
-as one of the lines in the logon script.
-Problems with WinDD, NTrigue, WinCenterPro etc
-
-
-All of the above programs are applications that sit on an NT box and
-allow multiple users to access the NT GUI applications from remote
-workstations (often over X).
-
-What has this got to do with Samba? The problem comes when these users
-use filemanager to mount shares from a Samba server. The most common
-symptom is that the first user to connect get correct file permissions
-and has a nice day, but subsequent connections get logged in as the
-same user as the first person to login. They find that they cannot
-access files in their own home directory, but that they can access
-files in the first users home directory (maybe not such a nice day
-after all?)
-
-Why does this happen? The above products all share a common heritage
-(and code base I believe). They all open just a single TCP based SMB
-connection to the Samba server, and requests from all users are piped
-over this connection. This is unfortunate, but not fatal.
-
-It means that if you run your Samba server in share level security
-(the default) then things will definately break as described
-above. The share level SMB security model has no provision for
-multiple user IDs on the one SMB connection. See in
-the docs for more info on share/user/server level security.
-
-If you run in user or server level security then you have a chance,
-but only if you have a recent version of Samba (at least 1.9.15p6). In
-older versions bugs in Samba meant you still would have had problems.
-
-If you have a trapdoor uid system in your OS then it will never work
-properly. Samba needs to be able to switch uids on the connection and
-it can't if your OS has a trapdoor uid system. You'll know this
-because Samba will note it in your logs.
-
-Also note that you should not use the magic "homes" share name with
-products like these, as otherwise all users will end up with the same
-home directory. Use [\\server\username] instead.
-
-Problem with printers under NT
-This info from Stefan Hergeth
-hergeth@f7axp1.informatik.fh-muenchen.de may be useful:
-
- A network-printer (with ethernetcard) is connected to the NT-Clients
-via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
- Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
-
-If a user has choosen this printer as the default printer in his
- NT-Session and this printer is not connected to the network
- (e.g. switched off) than this user has a problem with the SAMBA-
- connection of his filesystems. It's very slow.
-
-If the printer is connected to the network everything works fine.
-
-When the smbd ist started with debug level 3, you can see that the
- NT spooling system try to connect to the printer many times. If the
- printer ist not connected to the network this request fails and the
- NT spooler is wasting a lot of time to connect to the printer service.
- This seems to be the reason for the slow network connection.
-
-Maybe it's possible to change this behaviour by setting different
- printer properties in the Print-Manager-Menu of NT, but i didn't try it yet.
-
-
-Why are my file's timestamps off by an hour, or by a few hours?
-This is from Paul Eggert eggert@twinsun.com.
-
-Most likely it's a problem with your time zone settings.
-
-Internally, Samba maintains time in traditional Unix format,
-namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
-(or ``GMT''), not counting leap seconds.
-
-On the server side, Samba uses the Unix TZ variable to convert
-internal timestamps to and from local time. So on the server side, there are
-two things to get right.
-
-The Unix system clock must have the correct Universal time.
- Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
-
-The TZ environment variable must be set on the server
- before Samba is invoked. The details of this depend on the
- server OS, but typically you must edit a file whose name is
- /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.
-
-TZ must have the correct value.
-
- If possible, use geographical time zone settings
- (e.g. TZ='America/Los_Angeles' or perhaps
- TZ=':US/Pacific'). These are supported by most
- popular Unix OSes, are easier to get right, and are
- more accurate for historical timestamps. If your
- operating system has out-of-date tables, you should be
- able to update them from the public domain time zone
- tables at .
-
- If your system does not support geographical timezone
- settings, you must use a Posix-style TZ strings, e.g.
- TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
- Posix TZ strings can take the following form (with optional
- items in brackets):
-
- StdOffset[Dst[Offset],Date/Time,Date/Time]
-
- where:
-
- `Std' is the standard time designation (e.g. `PST').
-
- `Offset' is the number of hours behind UTC (e.g. `8').
- Prepend a `-' if you are ahead of UTC, and
- append `:30' if you are at a half-hour offset.
- Omit all the remaining items if you do not use
- daylight-saving time.
-
- `Dst' is the daylight-saving time designation
- (e.g. `PDT').
-
- The optional second `Offset' is the number of
- hours that daylight-saving time is behind UTC.
- The default is 1 hour ahead of standard time.
-
- `Date/Time,Date/Time' specify when daylight-saving
- time starts and ends. The format for a date is
- `Mm.n.d', which specifies the dth day (0 is Sunday)
- of the nth week of the mth month, where week 5 means
- the last such day in the month. The format for a
- time is [h]h[:mm[:ss]], using a 24-hour clock.
-
- Other Posix string formats are allowed but you don't want
- to know about them.
-
-
-On the client side, you must make sure that your client's clock and
-time zone is also set appropriately. [[I don't know how to do this.]]
-Samba traditionally has had many problems dealing with time zones, due
-to the bizarre ways that Microsoft network protocols handle time
-zones. A common symptom is for file timestamps to be off by an hour.
-To work around the problem, try disconnecting from your Samba server
-and then reconnecting to it; or upgrade your Samba server to
-1.9.16alpha10 or later.
-
- How do I set the printer driver name correctly?
-Question:
- On NT, I opened "Printer Manager" and "Connect to Printer".
- Enter ["\\ptdi270\ps1"] in the box of printer. I got the
- following error message:
-
- You do not have sufficient access to your machine
- to connect to the selected printer, since a driver
- needs to be installed locally.
-
-Answer:
-
-In the more recent versions of Samba you can now set the "printer
-driver" in smb.conf. This tells the client what driver to use. For
-example:
-
- printer driver = HP LaserJet 4L
-
-with this, NT knows to use the right driver. You have to get this string
-exactly right.
-
-To find the exact string to use, you need to get to the dialog box in
-your client where you select which printer driver to install. The
-correct strings for all the different printers are shown in a listbox
-in that dialog box.
-
-You could also try setting the driver to NULL like this:
-
- printer driver = NULL
-
-this is effectively what older versions of Samba did, so if that
-worked for you then give it a go. If this does work then let us know via ,
-and we'll make it the default. Currently the default is a 0 length
-string.
-
-I've applied NT 4.0 SP3, and now I can't access Samba shares, Why?
-As of SP3, Microsoft has decided that they will no longer default to
-passing clear text passwords over the network. To enable access to
-Samba shares from NT 4.0 SP3, you must do ONE of two things:
-
- Set the Samba configuration option 'security = user' and implement all of the stuff detailed in .
- Follow Microsoft's directions for setting your NT box to allow plain text passwords. see
-
-
-Specific client application problems
-
-MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"
-When installing MS Office on a Samba drive for which you have admin
-user permissions, ie. admin users = username, you will find the
-setup program unable to complete the installation.
-
-To get around this problem, do the installation without admin user
-permissions The problem is that MS Office Setup checks that a file is
-rdonly by trying to open it for writing.
-
-Admin users can always open a file for writing, as they run as root.
-You just have to install as a non-admin user and then use "chown -R"
-to fix the owner.
-
-Miscellaneous
-Is Samba Year 2000 compliant?
-The CIFS protocol that Samba implements
-negotiates times in various formats, all of which
-are able to cope with dates beyond 2000.
-
-
diff --git a/docs/faq/sambafaq.txt b/docs/faq/sambafaq.txt
deleted file mode 100644
index 7108846ae67..00000000000
--- a/docs/faq/sambafaq.txt
+++ /dev/null
@@ -1,1122 +0,0 @@
- Samba FAQ
- Paul Blackman, ictinus@samba.anu.edu.au
- v 0.8, June '97
-
- This is the Frequently Asked Questions (FAQ) document for Samba, the
- free and very popular SMB server product. An SMB server allows file
- and printer connections from clients such as Windows, OS/2, Linux and
- others. Current to version 1.9.17. Please send any corrections to the
- author.
- ______________________________________________________________________
-
- Table of Contents:
-
- 1. General Information
-
- 1.1. What is Samba?
-
- 1.2. What is the current version of Samba?
-
- 1.3. Where can I get it?
-
- 1.4. What do the version numbers mean?
-
- 1.5. What platforms are supported?
-
- 1.6. How can I find out more about Samba?
-
- 1.7. How do I subscribe to the Samba Mailing Lists?
-
- 1.8. Something's gone wrong - what should I do?
-
- 1.9. Pizza supply details
-
- 2. Compiling and installing Samba on a Unix host
-
- 2.1. I can't see the Samba server in any browse lists!
-
- 2.2. Some files that I KNOW are on the server doesn't show up when
- I view the files from my client!
-
- 2.3. Some files on the server show up with really wierd filenames
- when I view the files from my client!
-
- 2.4. My client reports "cannot locate specified computer" or
- similar
-
- 2.5. My client reports "cannot locate specified share name" or
- similar
-
- 2.6. My client reports "cannot find domain controller", "cannot log
- on to the network" or similar
-
- 2.7. Printing doesn't work :-(
-
- 2.8. My programs install on the server OK, but refuse to work
- properly
-
- 2.9. My "server string" doesn't seem to be recognised
-
- 2.10. My client reports "This server is not configured to list
- shared resources"
-
- 2.11. Log message "you appear to have a trapdoor uid system"
-
- 3. Common client questions
-
- 3.1. Are there any Macintosh clients for Samba?
-
- 3.2. "Session request failed (131,130)" error
-
- 3.3. How do I synchronise my PC's clock with my Samba server?
-
- 3.4. Problems with WinDD, NTrigue, WinCenterPro etc
-
- 3.5. Problem with printers under NT
-
- 3.6. Why are my file's timestamps off by an hour, or by a few
- hours?
-
- 3.7. How do I set the printer driver name correctly?
-
- 3.8. I've applied NT 4.0 SP3, and now I can't access Samba shares,
- Why?
-
- 4. Specific client application problems
-
- 4.1. MS Office Setup reports "Cannot change properties of
- 'MSOFFICEUP.INI'"
-
- 5. Miscellaneous
-
- 5.1. Is Samba Year 2000 compliant?
- ______________________________________________________________________
-
- 11.. GGeenneerraall IInnffoorrmmaattiioonn
-
-
-
- All about Samba - what it is, how to get it, related sources of
- information, how to understand the version numbering scheme, pizza
- details
-
-
- 11..11.. WWhhaatt iiss SSaammbbaa??
-
-
- 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.
-
- In practice, this means that you can redirect disks and printers to
- Unix disks and printers from Lan Manager clients, Windows for
- Workgroups 3.11 clients, Windows NT clients, Linux clients and OS/2
- clients. There is also a generic Unix client program supplied as part
- of the suite which allows Unix users to use an ftp-like interface to
- access filespace and printers on any other SMB servers. This gives the
- capability for these operating systems to behave much like a LAN
- Server or Windows NT Server machine, only with added functionality and
- flexibility designed to make life easier for administrators.
-
- The components of the suite are (in summary):
-
-
- +o ssmmbbdd, the SMB server. This handles actual connections from clients,
- doing all the file, permission and username work
-
- +o nnmmbbdd, the Netbios name server, which helps clients locate servers,
- doing the browsing work and managing domains as this capability is
- being built into Samba
-
-
- +o ssmmbbcclliieenntt, the Unix-hosted client program
-
- +o ssmmbbrruunn, a little 'glue' program to help the server run external
- programs
-
- +o tteessttpprrnnss, a program to test server access to printers
-
- +o tteessttppaarrmmss, a program to test the Samba configuration file for
- correctness
-
- +o ssmmbb..ccoonnff, the Samba configuration file
-
- +o ssmmbbpprriinntt, a sample script to allow a Unix host to use smbclient to
- print to an SMB server
-
- +o DDooccuummeennttaattiioonn!! DON'T neglect to read it - you will save a great
- deal of time!
-
- The suite is supplied with full source (of course!) and is GPLed.
-
- The primary creator of the Samba suite is Andrew Tridgell. Later
- versions incorporate much effort by many net.helpers. The man pages
- and this FAQ were originally written by Karl Auer.
-
-
- 11..22.. WWhhaatt iiss tthhee ccuurrrreenntt vveerrssiioonn ooff SSaammbbaa??
-
-
- 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.
-
-
- For more information see ``What do the version numbers mean?''
-
-
- 11..33.. WWhheerree ccaann II ggeett iitt??
-
-
- 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:
-
- /pub/samba/
-
- Development (read "alpha") versions, which are NOT necessarily stable
- and which do NOT necessarily have accurate documentation, are
- available in the directory:
-
- /pub/samba/alpha
-
- Note that binaries are NOT included in any of the above. Samba is
- distributed ONLY in source form, though binaries may be available from
- other sites. Recent versions of some Linux distributions, for example,
- do contain Samba binaries for that platform.
-
-
- 11..44.. WWhhaatt ddoo tthhee vveerrssiioonn nnuummbbeerrss mmeeaann??
-
-
- 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
- all means take the plunge and help with the testing and development -
- but don't install it on your departmental server. Samba is typically
- very stable and safe, and this is mostly due to the policy of many
- public releases.
- How the scheme works:
-
- 1. 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.)
-
- 2. 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.
-
- 3. 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.
-
- 4. 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.
-
- So the progression goes:
-
- 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)
-
-
- The above system means that whenever someone looks at the samba ftp
- site they will be able to grab the highest numbered release without an
- alpha in the name and be sure of getting the current recommended ver-
- sion.
-
-
- 11..55.. WWhhaatt ppllaattffoorrmmss aarree ssuuppppoorrtteedd??
-
-
- Many different platforms have run Samba successfully. The platforms
- most widely used and thus best tested are Linux and SunOS.
-
- At time of writing, the Makefile claimed support for:
-
- +o A/UX 3.0
-
- +o AIX
-
- +o Altos Series 386/1000
-
- +o Amiga
-
- +o Apollo Domain/OS sr10.3
-
- +o BSDI
-
- +o B.O.S. (Bull Operating System)
-
- +o Cray, Unicos 8.0
-
- +o Convex
-
- +o DGUX.
-
- +o DNIX.
-
- +o FreeBSD
-
- +o HP-UX
-
- +o Intergraph.
-
- +o Linux with/without shadow passwords and quota
-
- +o LYNX 2.3.0
-
- +o MachTen (a unix like system for Macintoshes)
-
- +o Motorola 88xxx/9xx range of machines
-
- +o NetBSD
-
- +o NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for
- Mach).
-
- +o OS/2 using EMX 0.9b
-
- +o OSF1
-
- +o QNX 4.22
-
- +o RiscIX.
-
- +o RISCOs 5.0B
-
- +o SEQUENT.
-
- +o SCO (including: 3.2v2, European dist., OpenServer 5)
-
- +o SGI.
-
- +o SMP_DC.OSx v1.1-94c079 on Pyramid S series
-
- +o SONY NEWS, NEWS-OS (4.2.x and 6.1.x)
-
- +o SUNOS 4
-
- +o SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')
-
- +o Sunsoft ISC SVR3V4
-
- +o SVR4
-
- +o System V with some berkely extensions (Motorola 88k R32V3.2).
-
- +o ULTRIX.
-
- +o UNIXWARE
-
- +o UXP/DS
-
-
- 11..66.. HHooww ccaann II ffiinndd oouutt mmoorree aabboouutt SSaammbbaa??
-
-
- There are a number of places to look for more information on Samba,
- including:
-
- +o Two mailing lists devoted to discussion of Samba-related matters.
-
- +o The newsgroup, comp.protocols.smb, which has a great deal of
- discussion on Samba.
-
- +o The WWW site 'SAMBA Web Pages' at
- includes:
-
- +o Links to man pages and documentation, including this FAQ
-
- +o A comprehensive survey of Samba users.
-
- +o A searchable hypertext archive of the Samba mailing list.
-
- +o Links to Samba source code, binaries, and mirrors of both.
-
- +o The long list of topic documentation. These files can be found in
- the 'docs' directory of the Samba source, or at
-
-
- +o Application_Serving.txt
-
-
- +o BROWSING.txt
-
- +o BUGS.txt
-
- +o DIAGNOSIS.txt
-
- +o DNIX.txt
-
- +o DOMAIN.txt
-
- +o CONTROL.txt
-
-
- +o ENCRYPTION.txt
-
-
- +o Faxing.txt
-
- +o GOTCHAS.txt
-
- +o HINTS.txt
-
- +o INSTALL.sambatar
-
-
- +o INSTALL.txt
-
- +o MIRRORS
-
- +o NetBIOS.txt
-
- +o OS2.txt
-
- +o PROJECTS
-
- +o Passwords.txt
-
- +o Printing.txt
-
- +o README.DCEDFS
-
- +o README.OS2
-
- +o README.jis
-
- +o README.sambatar
-
-
- +o SCO.txt
-
- +o SMBTAR.notes
-
- +o Speed.txt
-
- +o Support.txt
-
- +o THANKS
-
- +o Tracing.txt
-
- +o SMB.txt
-
- +o Warp.txt
-
- +o WinNT.txt
-
- +o history
-
- +o level.txt
-
-
- +o slip.htm
-
-
- 11..77.. HHooww ddoo II ssuubbssccrriibbee ttoo tthhee SSaammbbaa MMaaiilliinngg LLiissttss??
-
-
- Send email to listproc@samba.anu.edu.au. Make sure the subject line is
- blank, and include the following two lines in the body of the message:
-
-
- subscribe samba Firstname Lastname
- subscribe samba-announce Firstname Lastname
-
-
-
-
- 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.
-
- The samba list is a digest list - every eight hours or so it
- regurgitates a single message containing all the messages that have
- been received by the list since the last time and sends a copy of this
- message to all subscribers.
-
- If you stop being interested in Samba, please send another email to
- listproc@samba.anu.edu.au. Make sure the subject line is blank, and
- include the following two lines in the body of the message:
-
-
- unsubscribe samba
- unsubscribe samba-announce
-
-
-
-
- The FFrroomm:: line in your message _M_U_S_T be the same address you used when
- you subscribed.
-
-
- 11..88.. SSoommeetthhiinngg''ss ggoonnee wwrroonngg -- wwhhaatt sshhoouulldd II ddoo??
-
-
- ## ****** IIMMPPOORRTTAANNTT!! ****** ##
-
- DO NOT post messages on mailing lists or in newsgroups until you have
- carried out the first three steps given here!
-
- 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
- DIAGNOSIS.txt ? It can
- save you a lot of time and effort. DIAGNOSIS.txt can also be found in
- the docs directory of the Samba distribution.
-
- Secondly, read the man pages for smbd, nmbd and smb.conf, looking for
- topics that relate to what you are trying to do.
-
- Thirdly, if there is no obvious solution to hand, try to get a look at
- the log files for smbd and/or nmbd for the period during which you
- were having problems. You may need to reconfigure the servers to
- provide more extensive debugging information - usually level 2 or
- level 3 provide ample debugging info. Inspect these logs closely,
- looking particularly for the string "Error:".
-
- Fourthly, if you still haven't got anywhere, ask the mailing list or
- newsgroup. In general nobody minds answering questions provided you
- have followed the preceding steps. It might be a good idea to scan the
- archives of the mailing list, which are available through the Samba
- web site described in the previous section.
-
- If you successfully solve a problem, please mail the FAQ maintainer a
- succinct description of the symptom, the problem and the solution, so
- I can incorporate it in the next version.
-
- If you make changes to the source code, _please_ submit these patches
- 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 samba-bugs@samba.anu.edu.au. Do not send patches to Andrew
- Tridgell or any other individual, they may be lost if you do.
-
-
- 11..99.. PPiizzzzaa ssuuppppllyy ddeettaaiillss
-
-
- 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 twenty
- thousand kilometres away, but it has been done.
-
- Method 1: Ring up your local branch of an international pizza chain
- and see if they honour their vouchers internationally. Pizza Hut do,
- which is how the entire Canberra Linux Users Group got to eat pizza
- one night, courtesy of someone in the US
-
- Method 2: Ring up a local pizza shop in Canberra and quote a credit
- card number for a certain amount, and tell them that Andrew will be
- collecting it (don't forget to tell him.) One kind soul from Germany
- did this.
-
- Method 3: Purchase a pizza voucher from your local pizza shop that has
- no international affiliations and send it to Andrew. It is completely
- useless but he can hang it on the wall next to the one he already has
- from Germany :-)
-
-
- Method 4: Air freight him a pizza with your favourite regional
- flavours. It will probably get stuck in customs or torn apart by
- hungry sniffer dogs but it will have been a noble gesture.
-
-
- 22.. CCoommppiilliinngg aanndd iinnssttaalllliinngg SSaammbbaa oonn aa UUnniixx hhoosstt
-
-
-
- 22..11.. II ccaann''tt sseeee tthhee SSaammbbaa sseerrvveerr iinn aannyy bbrroowwssee lliissttss!!
-
-
- See BROWSING.txt for
- more information on browsing. Browsing.txt can also be found in the
- docs directory of the Samba source.
-
- If your GUI client does not permit you to select non-browsable
- servers, you may need to do so on the command line. For example, under
- Lan Manager you might connect to the above service as disk drive M:
- thusly:
-
-
- net use M: \\mary\fred
-
-
-
-
- The details of how to do this and the specific syntax varies from
- client to client - check your client's documentation.
-
-
- 22..22.. SSoommee ffiilleess tthhaatt II KKNNOOWW aarree oonn tthhee sseerrvveerr ddooeessnn''tt sshhooww uupp wwhheenn II
- vviieeww tthhee ffiilleess ffrroomm mmyy cclliieenntt!!
-
-
- See the next question.
-
- 22..33.. SSoommee ffiilleess oonn tthhee sseerrvveerr sshhooww uupp wwiitthh rreeaallllyy wwiieerrdd ffiilleennaammeess
- wwhheenn II vviieeww tthhee ffiilleess ffrroomm mmyy cclliieenntt!!
-
-
- If you check what files are not showing up, you will note that they
- are files which contain upper case letters or which are otherwise not
- DOS-compatible (ie, they are not legal DOS filenames for some reason).
-
- The Samba server can be configured either to ignore such files
- completely, or to present them to the client in "mangled" form. If you
- are not seeing the files at all, the Samba server has most likely been
- configured to ignore them. Consult the man page smb.conf(5) for
- details of how to change this - the parameter you need to set is
- "mangled names = yes".
-
-
- 22..44.. MMyy cclliieenntt rreeppoorrttss ""ccaannnnoott llooccaattee ssppeecciiffiieedd ccoommppuutteerr"" oorr ssiimmiillaarr
-
-
- This indicates one of three things: You supplied an incorrect server
- name, the underlying TCP/IP layer is not working correctly, or the
- name you specified cannot be resolved.
-
- After carefully checking that the name you typed is the name you
- should have typed, try doing things like pinging a host or telnetting
- to somewhere on your network to see if TCP/IP is functioning OK. If it
- 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
- 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
- there is something fundamental wrong with your naming and the solution
- is beyond the scope of this document.
-
- If you do not have any server on your subnet supplying netbios name
- resolution, hardcoded mappings are your only option. If you DO have a
- netbios name server running (such as the Samba suite's nmbd program),
- the problem probably lies in the way it is set up. Refer to Section
- Two of this FAQ for more ideas.
-
- By the way, remember to REMOVE the hardcoded mapping before further
- tests :-)
-
-
- 22..55.. MMyy cclliieenntt rreeppoorrttss ""ccaannnnoott llooccaattee ssppeecciiffiieedd sshhaarree nnaammee"" oorr ssiimmii--
- llaarr
-
-
- This message indicates that your client CAN locate the specified
- server, which is a good start, but that it cannot find a service of
- the name you gave.
-
- 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
- to specify a service name correctly), read on:
-
-
- +o Many clients cannot accept or use service names longer than eight
- characters.
-
- +o Many clients cannot accept or use service names containing spaces.
-
- +o Some servers (not Samba though) are case sensitive with service
- names.
-
- +o Some clients force service names into upper case.
-
-
- 22..66.. MMyy cclliieenntt rreeppoorrttss ""ccaannnnoott ffiinndd ddoommaaiinn ccoonnttrroolllleerr"",, ""ccaannnnoott lloogg
- oonn ttoo tthhee nneettwwoorrkk"" oorr ssiimmiillaarr
-
-
- Nothing is wrong - Samba does not implement the primary domain name
- controller stuff for several reasons, including the fact that the
- whole concept of a primary domain controller and "logging in to a
- network" doesn't fit well with clients possibly running on multiuser
- machines (such as users of smbclient under Unix). Having said that,
- several developers are working hard on building it in to the next
- major version of Samba. If you can contribute, send a message to
- samba-bugs@samba.anu.edu.au !
-
- Seeing this message should not affect your ability to mount redirected
- disks and printers, which is really what all this is about.
-
- For many clients (including Windows for Workgroups and Lan Manager),
- setting the domain to STANDALONE at least gets rid of the message.
-
-
-
-
-
- 22..77.. PPrriinnttiinngg ddooeessnn''tt wwoorrkk ::--((
-
-
- Make sure that the specified print command for the service you are
- connecting to is correct and that it has a fully-qualified path (eg.,
- use "/usr/bin/lpr" rather than just "lpr").
-
- Make sure that the spool directory specified for the service is
- writable by the user connected to the service. In particular the user
- "nobody" often has problems with printing, even if it worked with an
- earlier version of Samba. Try creating another guest user other than
- "nobody".
-
- Make sure that the user specified in the service is permitted to use
- the printer.
-
- Check the debug log produced by smbd. Search for the printer name and
- see if the log turns up any clues. Note that error messages to do with
- a service ipc$ are meaningless - they relate to the way the client
- attempts to retrieve status information when using the LANMAN1
- protocol.
-
- If using WfWg then you need to set the default protocol to TCP/IP, not
- Netbeui. This is a WfWg bug.
-
- If using the Lanman1 protocol (the default) then try switching to
- coreplus. Also not that print status error messages don't mean
- printing won't work. The print status is received by a different
- mechanism.
-
-
- 22..88.. MMyy pprrooggrraammss iinnssttaallll oonn tthhee sseerrvveerr OOKK,, bbuutt rreeffuussee ttoo wwoorrkk pprroopp--
- eerrllyy
-
-
- There are numerous possible reasons for this, but one MAJOR
- possibility is that your software uses locking. Make sure you are
- using Samba 1.6.11 or later. It may also be possible to work around
- the problem by setting "locking=no" in the Samba configuration file
- for the service the software is installed on. This should be regarded
- as a strictly temporary solution.
-
- In earlier Samba versions there were some difficulties with the very
- latest Microsoft products, particularly Excel 5 and Word for Windows
- 6. These should have all been solved. If not then please let Andrew
- Tridgell know via email at samba-bugs@samba.anu.edu.au.
-
-
- 22..99.. MMyy ""sseerrvveerr ssttrriinngg"" ddooeessnn''tt sseeeemm ttoo bbee rreeccooggnniisseedd
-
-
- OR My client reports the default setting, eg. "Samba 1.9.15p4",
- instead of what I have changed it to in the smb.conf file.
-
- You need to use the -C option in nmbd. The "server string" affects
- what smbd puts out and -C affects what nmbd puts out.
-
- Current versions of Samba (1.9.16 +) have combined these options into
- the "server string" field of smb.conf, -C for nmbd is now obsolete.
-
-
- 22..1100.. MMyy cclliieenntt rreeppoorrttss ""TThhiiss sseerrvveerr iiss nnoott ccoonnffiigguurreedd ttoo lliisstt sshhaarreedd
- rreessoouurrcceess""
-
-
- Your guest account is probably invalid for some reason. Samba uses the
- guest account for browsing in smbd. Check that your guest account is
- valid.
-
- See also 'guest account' in smb.conf man page.
-
-
- 22..1111.. LLoogg mmeessssaaggee ""yyoouu aappppeeaarr ttoo hhaavvee aa ttrraappddoooorr uuiidd ssyysstteemm""
-
-
- This can have several causes. It might be because you are using a uid
- or gid of 65535 or -1. This is a VERY bad idea, and is a big security
- hole. Check carefully in your /etc/passwd file and make sure that no
- user has uid 65535 or -1. Especially check the "nobody" user, as many
- broken systems are shipped with nobody setup with a uid of 65535.
-
- It might also mean that your OS has a trapdoor uid/gid system :-)
-
- This means that once a process changes effective uid from root to
- another user it can't go back to root. Unfortunately Samba relies on
- being able to change effective uid from root to non-root and back
- again to implement its security policy. If your OS has a trapdoor uid
- system this won't work, and several things in Samba may break. Less
- things will break if you use user or server level security instead of
- the default share level security, but you may still strike problems.
-
- The problems don't give rise to any security holes, so don't panic,
- but it does mean some of Samba's capabilities will be unavailable. In
- particular you will not be able to connect to the Samba server as two
- different uids at once. This may happen if you try to print as a
- "guest" while accessing a share as a normal user. It may also affect
- your ability to list the available shares as this is normally done as
- the guest user.
-
- Complain to your OS vendor and ask them to fix their system.
-
- Note: the reason why 65535 is a VERY bad choice of uid and gid is that
- it casts to -1 as a uid, and the setreuid() system call ignores (with
- no error) uid changes to -1. This means any daemon attempting to run
- as uid 65535 will actually run as root. This is not good!
-
-
- 33.. CCoommmmoonn cclliieenntt qquueessttiioonnss
-
-
-
-
- 33..11.. AArree tthheerree aannyy MMaacciinnttoosshh cclliieennttss ffoorr SSaammbbaa??
-
-
- Yes! Thursby now have a CIFS Client / Server called DAVE - see
- . They test it against Windows 95, Windows
- NT and samba for compatibility issues. At the time of writing, DAVE
- was at version 1.0.1. The 1.0.0 to 1.0.1 update is available as a free
- download from the Thursby web site (the speed of finder copies has
- been greatly enhanced, and there are bug-fixes included).
-
- Alternatives - There are two free implementations of AppleTalk for
- several kinds of UNIX machnes, and several more commercial ones.
- These products allow you to run file services and print services
- natively to Macintosh users, with no additional support required on
- the Macintosh. The two free omplementations are Netatalk,
- , and CAP,
- . What Samba offers MS
- Windows users, these packages offer to Macs. For more info on these
- packages, Samba, and Linux (and other UNIX-based systems) see
-
- 33..22.. SSeessssiioonn rreeqquueesstt ffaaiilleedd ((113311,,113300))"" eerrrroorr
-
-
- The following answer is provided by John E. Miller:
-
- I'll assume that you're able to ping back and forth between the
- machines by IP address and name, and that you're using some security
- model where you're confident that you've got user IDs and passwords
- right. The logging options (-d3 or greater) can help a lot with that.
- DNS and WINS configuration can also impact connectivity as well.
-
- Now, on to 'scope id's. Somewhere in your Win95 TCP/IP network
- configuration (I'm too much of an NT bigot to know where it's located
- in the Win95 setup, but I'll have to learn someday since I teach for a
- Microsoft Solution Provider Authorized Tech Education Center - what an
- acronym...) Note: It's under Control Panel | Network | TCP/IP | WINS
- Configuration there's a little text entry field called something like
-
- This field essentially creates 'invisible' sub-workgroups on the same
- wire. Boxes can only see other boxes whose Scope IDs are set to the
- exact same value - it's sometimes used by OEMs to configure their
- boxes to browse only other boxes from the same vendor and, in most
- environments, this field should be left blank. If you, in fact, have
- something in this box that EXACT value (case-sensitive!) needs to be
- provided to smbclient and nmbd as the -i (lowercase) parameter. So, if
- your Scope ID is configured as the string 'SomeStr' in Win95 then
- you'd have to use smbclient -iSomeStr otherparms in connecting to it.
-
-
- 33..33.. HHooww ddoo II ssyynncchhrroonniissee mmyy PPCC''ss cclloocckk wwiitthh mmyy SSaammbbaa sseerrvveerr??
-
-
- To syncronize your PC's clock with your Samba server:
-
- +o Copy timesync.pif to your windows directory
-
- +o timesync.pif can be found at:
-
-
- +o Add timesync.pif to your 'Start Up' group/folder
-
- +o Open the properties dialog box for the program/icon
-
- +o Make sure the 'Run Minimized' option is set in program 'Properties'
-
- +o Change the command line section that reads \sambahost to reflect
- the name of your server.
-
- +o Close the properties dialog box by choosing 'OK'
-
- Each time you start your computer (or login for Win95) your PC will
- synchronize its clock with your Samba server.
-
- Alternativley, if you clients support Domain Logons, you can setup
- Domain Logons with Samba - see: BROWSING.txt
- *** for more
- information.
-
- Then add
-
-
- NET TIME \\%L /SET /YES
-
-
-
-
- as one of the lines in the logon script.
-
- 33..44.. PPrroobblleemmss wwiitthh WWiinnDDDD,, NNTTrriigguuee,, WWiinnCCeenntteerrPPrroo eettcc
-
-
- All of the above programs are applications that sit on an NT box and
- allow multiple users to access the NT GUI applications from remote
- workstations (often over X).
-
- What has this got to do with Samba? The problem comes when these users
- use filemanager to mount shares from a Samba server. The most common
- symptom is that the first user to connect get correct file permissions
- and has a nice day, but subsequent connections get logged in as the
- same user as the first person to login. They find that they cannot
- access files in their own home directory, but that they can access
- files in the first users home directory (maybe not such a nice day
- after all?)
-
- Why does this happen? The above products all share a common heritage
- (and code base I believe). They all open just a single TCP based SMB
- connection to the Samba server, and requests from all users are piped
- over this connection. This is unfortunate, but not fatal.
-
- It means that if you run your Samba server in share level security
- (the default) then things will definately break as described above.
- The share level SMB security model has no provision for multiple user
- IDs on the one SMB connection. See security_level.txt
- in the docs
- for more info on share/user/server level security.
-
- If you run in user or server level security then you have a chance,
- but only if you have a recent version of Samba (at least 1.9.15p6). In
- older versions bugs in Samba meant you still would have had problems.
-
- If you have a trapdoor uid system in your OS then it will never work
- properly. Samba needs to be able to switch uids on the connection and
- it can't if your OS has a trapdoor uid system. You'll know this
- because Samba will note it in your logs.
-
- Also note that you should not use the magic "homes" share name with
- products like these, as otherwise all users will end up with the same
- home directory. Use \serversername instead.
-
-
- 33..55.. PPrroobblleemm wwiitthh pprriinntteerrss uunnddeerr NNTT
-
-
- This info from Stefan Hergeth hergeth@f7axp1.informatik.fh-muenchen.de
- may be useful:
-
- A network-printer (with ethernetcard) is connected to the NT-Clients
- via our UNIX-Fileserver (SAMBA-Server), like the configuration told by
- Matthew Harrell harrell@leech.nrl.navy.mil (see WinNT.txt)
-
- 1. If a user has choosen this printer as the default printer in his
- NT-Session and this printer is not connected to the network (e.g.
- switched off) than this user has a problem with the SAMBA-
- connection of his filesystems. It's very slow.
-
- 2. If the printer is connected to the network everything works fine.
-
- 3. When the smbd ist started with debug level 3, you can see that the
- NT spooling system try to connect to the printer many times. If the
- printer ist not connected to the network this request fails and the
- NT spooler is wasting a lot of time to connect to the printer
- service. This seems to be the reason for the slow network
- connection.
-
- 4. Maybe it's possible to change this behaviour by setting different
- printer properties in the Print-Manager-Menu of NT, but i didn't
- try it yet.
-
-
- 33..66.. WWhhyy aarree mmyy ffiillee''ss ttiimmeessttaammppss ooffff bbyy aann hhoouurr,, oorr bbyy aa ffeeww hhoouurrss??
-
-
- This is from Paul Eggert eggert@twinsun.com.
-
- Most likely it's a problem with your time zone settings.
-
- Internally, Samba maintains time in traditional Unix format, namely,
- the number of seconds since 1970-01-01 00:00:00 Universal Time (or
- ``GMT''), not counting leap seconds.
-
- On the server side, Samba uses the Unix TZ variable to convert
- internal timestamps to and from local time. So on the server side,
- there are two things to get right.
-
- 1. The Unix system clock must have the correct Universal time. Use
- the shell command "sh -c 'TZ=UTC0 date'" to check this.
-
- 2. The TZ environment variable must be set on the server before Samba
- is invoked. The details of this depend on the server OS, but
- typically you must edit a file whose name is /etc/TIMEZONE or
- /etc/default/init, or run the command `zic -l'.
-
- 3. TZ must have the correct value.
-
- a. If possible, use geographical time zone settings (e.g.
- TZ='America/Los_Angeles' or perhaps TZ=':US/Pacific'). These
- are supported by most popular Unix OSes, are easier to get
- right, and are more accurate for historical timestamps. If your
- operating system has out-of-date tables, you should be able to
- update them from the public domain time zone tables at
- .
-
- b. If your system does not support geographical timezone settings,
- you must use a Posix-style TZ strings, e.g.
- TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time. Posix TZ
- strings can take the following form (with optional items in
- brackets):
-
- StdOffset[Dst[Offset],Date/Time,Date/Time]
-
-
- where:
-
- +o `Std' is the standard time designation (e.g. `PST').
-
- +o `Offset' is the number of hours behind UTC (e.g. `8'). Prepend
- a `-' if you are ahead of UTC, and append `:30' if you are at a
- half-hour offset. Omit all the remaining items if you do not
- use daylight-saving time.
-
- +o `Dst' is the daylight-saving time designation (e.g. `PDT').
-
- The optional second `Offset' is the number of hours that
- daylight-saving time is behind UTC. The default is 1 hour ahead
- of standard time.
-
- +o `Date/Time,Date/Time' specify when daylight-saving time starts
- and ends. The format for a date is `Mm.n.d', which specifies
- the dth day (0 is Sunday) of the nth week of the mth month,
- where week 5 means the last such day in the month. The format
- for a time is hh:mm[:ss], using a 24-hour clock.
-
- Other Posix string formats are allowed but you don't want to
- know about them.
-
- On the client side, you must make sure that your client's clock and
- time zone is also set appropriately. [I don't know how to do
- this.] Samba traditionally has had many problems dealing with time
- zones, due to the bizarre ways that Microsoft network protocols
- handle time zones. A common symptom is for file timestamps to be
- off by an hour. To work around the problem, try disconnecting from
- your Samba server and then reconnecting to it; or upgrade your
- Samba server to 1.9.16alpha10 or later.
-
-
- 33..77.. HHooww ddoo II sseett tthhee pprriinntteerr ddrriivveerr nnaammee ccoorrrreeccttllyy??
-
-
- Question: On NT, I opened "Printer Manager" and "Connect to Printer".
- Enter "\ptdi270s1"
- in the box of printer. I got the following error message:
-
-
- You do not have sufficient access to your machine
- to connect to the selected printer, since a driver
- needs to be installed locally.
-
-
-
-
- Answer:
-
- In the more recent versions of Samba you can now set the "printer
- driver" in smb.conf. This tells the client what driver to use. For
- example:
-
-
- printer driver = HP LaserJet 4L
-
-
-
-
- with this, NT knows to use the right driver. You have to get this
- string exactly right.
-
- To find the exact string to use, you need to get to the dialog box in
- your client where you select which printer driver to install. The
- correct strings for all the different printers are shown in a listbox
- in that dialog box.
-
- You could also try setting the driver to NULL like this:
-
-
- printer driver = NULL
-
-
-
-
- this is effectively what older versions of Samba did, so if that
- worked for you then give it a go. If this does work then let us know
- via samba-bugs@samba.anu.edu.au, and we'll make it the default. Cur-
- rently the default is a 0 length string.
-
-
- 33..88.. II''vvee aapppplliieedd NNTT 44..00 SSPP33,, aanndd nnooww II ccaann''tt aacccceessss SSaammbbaa sshhaarreess,,
- WWhhyy??
-
-
- As of SP3, Microsoft has decided that they will no longer default to
- passing clear text passwords over the network. To enable access to
- Samba shares from NT 4.0 SP3, you must do OONNEE of two things:
-
- 1. Set the Samba configuration option 'security = user' and implement
- all of the stuff detailed in ENCRYPTION.txt
- .
-
- 2. Follow Microsoft's directions for setting your NT box to allow
- plain text passwords. see Knowledge Base Article Q166730
-
-
-
- 44.. SSppeecciiffiicc cclliieenntt aapppplliiccaattiioonn pprroobblleemmss
-
-
-
-
- 44..11.. MMSS OOffffiiccee SSeettuupp rreeppoorrttss ""CCaannnnoott cchhaannggee pprrooppeerrttiieess ooff ''MMSSOOFF--
- FFIICCEEUUPP..IINNII''""
-
-
- When installing MS Office on a Samba drive for which you have admin
- user permissions, ie. admin users = username, you will find the setup
- program unable to complete the installation.
-
- To get around this problem, do the installation without admin user
- permissions The problem is that MS Office Setup checks that a file is
- rdonly by trying to open it for writing.
-
- Admin users can always open a file for writing, as they run as root.
- You just have to install as a non-admin user and then use "chown -R"
- to fix the owner.
-
-
- 55.. MMiisscceellllaanneeoouuss
-
-
-
- 55..11.. IIss SSaammbbaa YYeeaarr 22000000 ccoommpplliiaanntt??
-
-
- The CIFS protocol that Samba implements negotiates times in various
- formats, all of which are able to cope with dates beyond 2000.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/history b/docs/history
deleted file mode 100644
index dd9e83719ff..00000000000
--- a/docs/history
+++ /dev/null
@@ -1,196 +0,0 @@
-Contributor: Andrew Tridgell and the Samba Team
-Date: June 27, 1997
-Satus: Always out of date! (Would not be the same without it!)
-
-Subject: A bit of history and a bit of fun
-============================================================================
-
-This is a short history of this project. It's not supposed to be
-comprehensive, just enough so that new users can get a feel for where
-this project has come from and maybe where it's going to.
-
-The whole thing really started in December 1991. I was (and still am)
-a PhD student in the Computer Sciences Laboratory at the Australian
-National University, in Canberra, Australia. We had just got a
-beta copy of eXcursion from Digital, and I was testing it on my PC. At
-this stage I was a MS-DOS user, dabbling in windows.
-
-eXcursion ran (at the time) only with Dec's `Pathworks' network for
-DOS. I had up till then been using PC-NFS to connect to our local sun
-workstations, and was reasonably happy with it. In order to run
-pathworks I had to stop using PC-NFS and try using pathworks to mount
-disk space. Unfortunately pathworks was only available for digital
-workstations running VMS or Ultrix so I couldn't mount from the suns
-anymore.
-
-I had access to a a decstation 3100 running Ultrix that I used to
-administer, and I got the crazy notion that the protocol that
-pathworks used to talk to ultrix couldn't be that hard, and maybe I
-could work it out. I had never written a network program before, and
-certainly didn't know what a socket was.
-
-In a few days, after looking at some example code for sockets, I
-discovered it was pretty easy to write a program to "spy" on the file
-sharing protocol. I wrote and installed this program (the sockspy.c
-program supplied with this package) and captured everything that the
-pathworks client said to the pathworks server.
-
-I then tried writing short C programs (using Turbo C under DOS) to do
-simple file operations on the network drive (open, read, cd etc) and
-looked at the packets that the server and client exchanged. From this
-I worked out what some of the bytes in the packets meant, and started
-to write my own program to do the same thing on a sun.
-
-After a day or so more I had my first successes and actually managed
-to get a connection and to read a file. From there it was all
-downhill, and a week later I was happily (if a little unreliably)
-mounting disk space from a sun to my PC running pathworks. The server
-code had a lot of `magic' values in it, which seemed to be always
-present with the ultrix server. It was not till 2 years later that I
-found out what all these values meant.
-
-Anyway, I thought other people might be interested in what I had done,
-so I asked a few people at uni, and noone seemed much interested. I
-also spoke to a person at Digital in Canberra (the person who had
-organised a beta test of eXcursion) and asked if I could distribute
-what I'd done, or was it illegal. It was then that I first heard the
-word "netbios" when he told me that he thought it was all covered by a
-spec of some sort (the netbios spec) and thus what I'd done was not
-only legal, but silly.
-
-I found the netbios spec after asking around a bit (the RFC1001 and
-RFC1002 specs) and found they looked nothing like what I'd written, so
-I thought maybe the Digital person was mistaken. I didn't realise RFCs
-referred to the name negotiation and packet encapsulation over TCP/IP,
-and what I'd written was really a SMB implementation.
-
-Anyway, he encouraged me to release it so I put out "Server 0.1" in
-January 1992. I got quite a good response from people wanting to use
-pathworks with non-digital unix workstations, and I soon fixed a few
-bugs, and released "Server 0.5" closely followed by "Server 1.0". All
-three releases came out within about a month of each other.
-
-At this point I got an X Terminal on my desk, and I no longer needed eXcursion
-and I prompty forgot about the whole project, apart from a few people
-who e-mailed me occasionally about it.
-
-Nearly two years then passed with just occasional e-mails asking about
-new versions and bugs. I even added a note to the ftp site asking for
-a volunteer to take over the code as I no longer used it. No one
-volunteered.
-
-During this time I did hear from a couple of people who said it should
-be possible to use my code with Lanmanager, but I never got any
-definite confirmation.
-
-One e-mail I got about the code did, however, make an impression. It
-was from Dan Shearer at the university of South Australia, and he said
-this:
-
-
- I heard a hint about a free Pathworks server for Unix in the
- Net channel of the Linux list. After quite a bit of chasing
- (and lots of interested followups from other Linux people) I
- got hold of a release news article from you, posted in Jan 92,
- from someone in the UK.
-
- Can you tell me what the latest status is? I think you might
- suddenly find a whole lot of interested hackers in the Linux
- world at least, which is a place where things tend to happen
- fast (and even some reliable code gets written, BION!)
-
-I asked him what Linux was, and he told me it was a free Unix for PCs.
-This was in November 1992 and a few months later I was a Linux
-convert! I still didn't need a pathworks server though, so I didn't do
-the port, but I think Dan did.
-
-At about this time I got an e-mail from Digital, from a person working
-on the Alpha software distribution. He asked if I would mind if they
-included my server with the "contributed" cd-rom. This was a bit of a
-shock to me as I never expected Dec to ask me if they could use my
-code! I wrote back saying it was OK, but never heard from him again. I
-don't know if it went on the cd-rom.
-
-Anyway, the next big event was in December 1993, when Dan again sent
-me an e-mail saying my server had "raised its ugly head" on
-comp.protocols.tcpip.ibmpc. I had a quick look on the group, and was
-surprised to see that there were people interested in this thing.
-
-At this time a person from our computer center offered me a couple of
-cheap ethernet cards (3c505s for $15 each) and coincidentially someone
-announced on one of the Linux channels that he had written a 3c505
-driver for Linux. I bought the cards, hacked the driver a little and
-setup a home network between my wifes PC and my Linux box. I then
-needed some way to connect the two, and I didn't own PC-NFS at home,
-so I thought maybe my server could be useful. On the newsgroup among
-the discussions of my server someone had mentioned that there was a
-free client that might work with my server that Microsoft had put up
-for ftp. I downloaded it and found to my surprise that it worked first
-time with my `pathworks' server!
-
-Well, I then did a bit of hacking, asked around a bit and found (I
-think from Dan) that the spec I needed was for the "SMB" protocol, and
-that it was available via ftp. I grabbed it and started removing all
-those ugly constants from the code, now that all was explained.
-
-On December 1st 1993 I announced the start of the "Netbios for Unix"
-project, seeding the mailing list with all the people who had e-mailed
-me over the years asking about the server.
-
-About 35 versions (and two months) later I wrote a short history of
-the project, which you have just read. There are now over a hundred
-people on the mailing list, and lots of people report that they use
-the code and like it. In a few days I will be announcing the release
-of version 1.6 to some of the more popular (and relevant) newsgroups.
-
-
-Andrew Tridgell
-6th February 1994
-
----------------------
-
-It is now May 1995 and there are about 1400 people on the mailing
-list. I got downloads from the main Samba ftp site from around 5000
-unique hosts in a two month period. There are several mirror
-sites as well. The current version number is 1.9.13.
-
----------------------
-
-
----------------------
-It's now March 1996 and version 1.9.16alpha1 has just been
-released. There have been lots of changes recently with master browser
-support and the ability to do domain logons etc. Samba has also been
-ported to OS/2, the amiga and NetWare. There are now 3000 people on
-the samba mailing list.
----------------------
-
-
----------------------
-It's now June 1997 and samba-1.9.17 is due out soon. My how time passes!
-Please refer to the WHATSNEW.txt for an update on new features. Just when
-you think you understand what is happening the ground rules change - this
-is a real world after all. Since the heady days of March 1996 there has
-been a concerted effort within the SMB protocol using community to document
-and standardize the protocols. The CIFS initiative has helped a long way
-towards creating a better understood and more interoperable environment.
-The Samba Team has grown in number and have been very active in the standards
-formation and documentation process.
-
-The net effect has been that we have had to do a lot of work to bring Samba
-into line with new features and capabilities in the SMB protocols.
-
-The past year has been a productive one with the following releases:
- 1.9.16, 1.9.16p2, 1.9.16p6, 1.9.16p9, 1.9.16p10, 1.9.16p11
-
-There are some who believe that 1.9.15p8 was the best release and others
-who would not want to be without the latest. Whatever your perception we
-hope that 1.9.17 will close the gap and convince you all that the long
-wait and the rolling changes really were worth it. Here is functionality
-and a level of code maturity that ..., well - you can be the judge!
-
-Happy SMB networking!
-Samba Team
-
-ps: The bugs are ours, so please report any you find.
----------------------
diff --git a/docs/htmldocs/wfw_slip.htm b/docs/htmldocs/wfw_slip.htm
deleted file mode 100644
index 5b4a0a5e539..00000000000
--- a/docs/htmldocs/wfw_slip.htm
+++ /dev/null
@@ -1,175 +0,0 @@
-
-
-Peter Karrer Announces SLIP for WFW
-
-
-
Winserve
-
-
Peter Karrer Announces SLIP for WFW
-[NEW 03-22-95)
-
-Hello,
-
-I've discovered a way to run WfW's TCP/IP-32 over a SLIP packet driver. This
-allows WfW users to do Windows networking over dialup lines just like it is
-possible with NT and the Windows 95 beta!
-
-For instance, you can mount Microsoft's FTP server as a network drive in File
-Manager or connect to an MS Mail post office over the Internet. Of course,
-the usual Internet stuff works as well. Another interesting site is
-WINSERVE.001; check out www.winserve.com.
-
-This method should work with any class 1 (Ethernet II) packet driver. However,
-I'm not in a position to try anything else than SLIPPER/CSLIPPER.
-
-
- Don Provan's ODI-over-Packet Driver shim. This *must* be version 1.05 (or
- above).
-
-LSL.COM:
-
- Novell's LAN Support Layer. If you're an owner of Windows 3.10, you'll
- have it on one of your install disks. Use "expand a:lsl.co_ lsl.com" to
- expand it. Microsoft has stopped bundling LSL.COM with WfW 3.11, though.
- The newest version of LSL.COM can be downloaded as part of
- ftp://ftp.novell.com/pub/netware/nwos/dosclnt12/vlms/vlmup2.exe.
- However, it's not clear if this one may be legally used outside Netware
- environments.
-
-NET.CFG:
-
- A configuration file for LSL and PDETHER. It should contain the following
- text:
-
- A little hack of mine to disable the COM port used by the SLIP packet driver.
- Usage is e.g. "discomx 2" to disable COM2. This should be run before
- starting WfW, otherwise you'll get "device conflict" messages. Here it is:
-
- (Save this text to disk as filename, then run "uudecode filename".
- uudecode can be found, for instance, at
- ftp://ftp.switch.ch/mirror/simtel/msdos/starter/uudecode.com )
-
-LMHOSTS:
-
- An optional file which should be stored in your Windows subdirectory. It is
- used to map NetBIOS computer names to IP addresses. Example:
-
Put the files mentioned above into a directory, e.g. C:\SLIP.
-
-
Put the following lines into AUTOEXEC.BAT:
-
- cd \slip
- slipper com1 vec=60 baud=57600 ether (may vary with your modem setup)
- lsl
- pdether
- discomx 1 (must correspond to SLIPPER's COM port)
-
- (If you use another vec= setting, you must update that in NET.CFG as well.)
- Use CSLIPPER instead of SLIPPER if your SLIP provider supports VJC.
-
-
Start WfW.
-
-
Under Windows Setup, choose "Change Network Settings".
-
Select "Install Microsoft Windows Network".
-
In "Drivers...", choose "Add Adapter"
- and install the "IPXODI Support driver (Ethernet) [ODI/NDIS3]".
-
In "Add Protocols...", select "Unlisted or Updated Protocol". When asked for a
- driver disk, enter the directory where you expanded WFWT32.EXE.
-
Configure TCP/IP (IP address, enable LMHOSTS lookup, try 204.118.34.11 as primary
- WINS server). Remove all other protocols (NetBEUI, IPX/SPX).
-
-
-
Windows will probably update the first lines of AUTOEXEC.BAT with
-
-
- c:\windows\net start
- c:\windows\odihlp.exe.
-
- The "odihlp" line must be moved behind the "pdether" line.
-
-
Windows will also update NET.CFG with some "Frame" lines. These must
- be removed (except "Frame Ethernet_II").
-
-
Somehow, you will have to dial in to your SLIP provider. I do it manually
- before slipper (or cslipper) gets loaded, using a DOS-based terminal program.
- But there are some automatic dialers around. I've seen recommendations for
- ftp://mvmpc9.ciw.uni-karlsruhe.de/x-slip/slip_it.exe.
-
-
To connect to Microsoft's FTP server (or Winserve) go into File Manager,
- choose "Connect Network drive" and enter "\\ftp" or "\\winserve.001" into
- the "Path:" field.
-
-
-
How it works:
-
-Microsoft's TCP/IP-32 requires an NDIS3 interface. NDIS is Microsoft's way
-to interface with a network.
-
-WfW also contains an NDIS3-over-ODI "shim", whose real mode component is
-ODIHLP.EXE. ODI is Novell's way to interface with a network.
-
-SLIPPER is a Packet Driver (PD) for use over serial lines. PDs are everybody
-else's way to interface with a network. SLIPPER's "ether" option makes it
-look like an Ethernet PD to applications using it.
-
-A "shim" is a program which simulates a network application programming
-interface on top of another.
-
-There is no NDIS SLIP driver which would work with WfW.
-
-There is no NDIS-over-PD shim.
-
-However, there's an ODI-over-PD shim (PDETHER) and an NDIS-over-ODI shim
-(ODIHLP etc.)
-
-OK, so let's do NDIS-over-ODI-over-PD!
-
-This should have worked all the time; however, a non-feature in PDETHER
-versions < 1.05 has prevented the method from functioning until now.
-
-
-Copyright 1995, Silicon Graphics, Inc. -- ALL RIGHTS RESERVED
-
-You may copy, modify, use and distribute this software, (i)
-provided that you include the entirety of this reservation of
-rights notice in all such copies, and (ii) you comply with any
-additional or different obligations and/or use restrictions
-specified by any third party owner or supplier of the software
-in other notices that may be included with the software.
-
-
-SGI DISCLAIMS ALL WARRANTIES WITH RESPECT TO THIS SOFTWARE,
-EXPRESS, IMPLIED, OR OTHERWISE, INCLUDING WITHOUT LIMITATION,
-ALL WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
-PURPOSE OR NONINFRINGEMENT. SGI SHALL NOT BE LIABLE FOR ANY
-SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING,
-WITHOUT LIMITATION, LOST REVENUES, LOST PROFITS, OR LOSS OF
-PROSPECTIVE ECONOMIC ADVANTAGE, RESULTING FROM THE USE OR MISUSE
-OF THIS SOFTWARE.
-
-
-U.S. GOVERNMENT RESTRICTED RIGHTS LEGEND:
-
-
-
-Use, duplication or disclosure by the Government is subject to
-restrictions as set forth in FAR 52.227.19(c)(2) or subparagraph
-(c)(1)(ii) of the Rights in Technical Data and Computer Software
-clause at DFARS 252.227-7013 and/or in similar or successor
-clauses in the FAR, or the DOD or NASA FAR Supplement.
-Unpublished - rights reserved under the Copyright Laws of United
-States. Contractor/manufacturer is Silicon Graphics, Inc., 2011
-N. Shoreline Blvd. Mountain View, CA 94039-7311.
-
-
-Freeware products are not supported by Silicon Graphics or any
-of its support providers. The software contained in this package
-is made available through the generous efforts of their authors.
-Although they are interested in your feedback, they are under no
-obligation to address bugs, enhancements, or answer questions.
-
-
-
diff --git a/packaging/SGI/mkman b/packaging/SGI/mkman
deleted file mode 100755
index fedeb4d7196..00000000000
--- a/packaging/SGI/mkman
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/bin/sh
-
-if [ ! -d catman ]; then
- mkdir catman
-fi
-
-# if you wish to make html versions of the man pages then uncomment
-# the following section and the "rman" command below
-#
-# if [ ! -d html ]; then
-# mkdir html
-# fi
-
-FILES="*.?"
-
-cd ../../docs
-for FILE in $FILES ; do
- neqn $FILE | tbl | nroff -man > ../packaging/SGI/catman/`basename $FILE`
- compress -f ../packaging/SGI/catman/`basename $FILE`
-# rman -f html -r "%s.%s.html" $FILE > ../packaging/SGI/html/$FILE.html
-done
-cd ../packaging/SGI
diff --git a/packaging/SGI/mkprintcap.sh b/packaging/SGI/mkprintcap.sh
deleted file mode 100755
index f610e757f06..00000000000
--- a/packaging/SGI/mkprintcap.sh
+++ /dev/null
@@ -1,15 +0,0 @@
-#! /bin/sh
-#
-# create printcap file
-#
-if [ -r /usr/samba/printcap ]
-then
- cp /usr/samba/printcap /usr/samba/printcap.O
-fi
-
-echo "#" > /usr/samba/printcap
-echo "# Samba printcap file" >> /usr/samba/printcap
-echo "# Alias names are separated by |, any name with spaces is taken as a comment" >> /usr/samba/printcap
-echo "#" >> /usr/samba/printcap
-lpstat -a | sed -e "s/ .*//" >> /usr/samba/printcap
-
diff --git a/packaging/SGI/mkrelease.sh b/packaging/SGI/mkrelease.sh
deleted file mode 100755
index 03644b2f7c0..00000000000
--- a/packaging/SGI/mkrelease.sh
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/sh
-
-# create the catman versions of the manual pages
-#
-echo Making manual pages
-./mkman
-
-# build the sources
-#
-echo Making binaries
-cd ../../source
-# make -f ../packaging/SGI/Makefile clean
-make -f ../packaging/SGI/Makefile all
-cd ../packaging/SGI
-
-# generate the packages
-#
-echo Generating Inst Packages
-
-if [ ! -d bins ]; then
- mkdir bins
-fi
-
-/usr/sbin/gendist -rbase / -sbase ../.. -idb samba.idb -spec samba.spec -dist ./bins -all
-
diff --git a/packaging/SGI/printcap b/packaging/SGI/printcap
deleted file mode 100644
index b67b9cb167c..00000000000
--- a/packaging/SGI/printcap
+++ /dev/null
@@ -1,5 +0,0 @@
-#
-# Sample printcap file
-# Alias names are separated by |, any name with spaces is taken as a comment
-#
-lp4js|lp12|LaserJet on the third floor by the coffee machine
diff --git a/packaging/SGI/psfixes.sed b/packaging/SGI/psfixes.sed
deleted file mode 100644
index cf5ce889145..00000000000
--- a/packaging/SGI/psfixes.sed
+++ /dev/null
@@ -1,4 +0,0 @@
-/^%/,/
/d
-/^%%Title:/s/.
$/
/
-/^\/VM?/,/ VM?/c\
-/VM? { pop } def
diff --git a/packaging/SGI/relnotes.html b/packaging/SGI/relnotes.html
deleted file mode 100644
index 71140420fe0..00000000000
--- a/packaging/SGI/relnotes.html
+++ /dev/null
@@ -1,234 +0,0 @@
-
-
-
- Samba 1.9.17 Release Notes
-
-
-
-
-
Samba 1.9.17 Release Notes
-
-
-
-
-
Table of Contents
-
-
-
-
-
-
-
What is Samba?
-
-
Samba is an SMB client and server for Unix. It makes it possible for
-client machines running Windows 95 and Windows for Workgroups to access
-files and/or print services on a Unix system. Samba includes an SMB server
-to provide LanManager-style file and print services to PCs, a Netbios (RFC10001/1002)
-name server, and an FTP-like client application for accessing PC resources
-from Unix.
-
-
To make Samba work you'll need to configure your server host to run
-smbd and nmbd whenever you connect to a certain Internet
-port from the client machine. Smbd and nmbd can be started
-either as daemons or from inetd.
-
-
By default smbd and nmbd are started as daemons by the
-file /etc/init.d/samba in conjunction with the chkconfig variable
-samba being set to on. If you set chkconfig samba off then the deamons
-will not be automatically started on reboot. In this case you must type
-the following at a shell prompt to start samba after a reboot:
-
-
chkconfig samba on
- /etc/init.d/samba start
-
-
-
If you make changes to your configuration files, smbd and nmbd
-may be restarted by typing the following at a shell prompt:
-
-
/etc/init.d/samba start
-
-
-
smbd and nmbd may be killed by typing the following at
-a shell prompt:
-
-
/etc/init.d/samba stop
-
-
-
To have smbd and nmbd started by inetd you can execute
-the shell script /usr/samba/inetd.sh to automatically configure
-the various files and start the processes. This shell script first kills
-any running smbd and nmbd processes. It then removes any
-existing entries for "netbios*" from /etc/inetd.conf and
-adds the following lines
The software in this package is considered unsupported by Silicon Graphics.
-Neither the authors or Silicon Graphics are compelled to help resolve problems
-you may encounter in the installation, setup, or execution of this software.
-To be more to the point, if you call us with an issue regarding products
-in the Freeware package, we'll have to gracefully terminate the call. The
-
-Samba Web Page has a listing of companies and individuals that offer
-commercial support for a fee.
-
Samba documentation: hints on installation and configuration, an FAQ
-(Frequently Asked Questions), help in diagnosing problems, etc..
-
-
-
-
samba.man.relnotes (default)
-
-
Samba online release notes.
-
-
-
-
samba.src.samba
-
-
The Samba 1.9.17 software distribution from which this product was
-built (including the packaging/SGI directory which will allow this distribution
-to be rebuilt).
-
-
-
-
Installation Method
-
-
All of the subsystems for Samba can be installed using IRIX. You do
-not need to use the miniroot. Refer to the Software Installation Administrator's
-Guide for complete installation instructions.
-
-
Prerequisites
-
-
Your workstation must be running IRIX 5.3 or later in order to use this
-product.
-
-
Configuration Files
-
-
Because configuration files often contain modifications, inst treats
-them specially during the installation process. If they have not been modified,
-inst removes the old file and installs the new version during software
-updates. For configuration files that have been modified, the new version
-is installed and the old version is renamed by adding the suffix .O (for
-older) to the name. The no-suffix version contains changes that are required
-for compatibility with the rest of the newly installed software, that increase
-functionality, or that fix bugs. You should use diff(1) or gdiff(1) to
-compare the two versions of the files and transfer information that you
-recognize as machine or site-specific from the .O version to the no-suffix
-version.
-
-
-
/usr/samba/lib/smb.conf
-
-
Configuration definitions for the smbd program; the SMB server
-process. The default configuration sets up password-based access to home
-directories on a machine as well as open access to to all printers and
-/tmp. The workgroup is set by default to "workgroup". It is highly
-recommended that administrators review the content of this file when installing
-Samba for the first time.
-
-
/usr/samba/printcap
-
-
A file that specifies the available printers on a system. It is included
-as an example; administrators may want to replace it or override the reference
-to it in the smb.conf file. The script /usr/samba/mkprintcap.sh
-was used by inst to create a printcap file that contains all printers on
-your system. You may wish to remove some printers or add a comment to each
-printer name to describe its location.
-
-
-
Documentation Information
-
-
Preformatted manual pages are installed by default as are the contents
-of the docs directory from the Samba distribution; consult samba(7)
-for an introduction.
-
-
There is a mailing list for discussion of Samba. To subscribe send mail
-to listproc@samba.anu.edu.au
-with a body of "subscribe samba Your Name"
There is also an announcement mailing list where new versions are announced.
-To subscribe send mail to listproc@samba.anu.edu.au
-with a body of "subscribe samba-announce Your Name". All announcements
-also go to the samba list.
-
-
You might also like to look at the Usenet news group comp.protocols.smb
-as it often contains lots of useful info and is frequented by lots of Samba
-users. The newsgroup was initially setup by people on the Samba mailing
-list. It is not, however, exclusive to Samba, it is a forum for discussing
-the SMB protocol (which Samba implements).
-
-
-
diff --git a/packaging/SGI/samba.config b/packaging/SGI/samba.config
deleted file mode 100644
index b3d86404ab5..00000000000
--- a/packaging/SGI/samba.config
+++ /dev/null
@@ -1 +0,0 @@
-on
diff --git a/packaging/SGI/samba.idb b/packaging/SGI/samba.idb
deleted file mode 100644
index dbf9f3b10ff..00000000000
--- a/packaging/SGI/samba.idb
+++ /dev/null
@@ -1,394 +0,0 @@
-f 0644 root sys etc/config/samba packaging/SGI/samba.config samba.sw.base config(update)
-f 0755 root sys etc/init.d/samba packaging/SGI/samba.rc samba.sw.base
-l 0000 root sys etc/rc0.d/K39samba packaging/SGI samba.sw.base symval(../init.d/samba)
-l 0000 root sys etc/rc2.d/S81samba packaging/SGI samba.sw.base symval(../init.d/samba)
-d 0755 root sys usr/relnotes/samba packaging/SGI samba.man.relnotes
-f 0644 root sys usr/relnotes/samba/GNU_COPYING.txt COPYING samba.man.relnotes
-f 0644 root sys usr/relnotes/samba/legal_notice.html packaging/SGI/legal_notice.html samba.man.relnotes
-f 0644 root sys usr/relnotes/samba/samba-relnotes.html packaging/SGI/relnotes.html samba.man.relnotes
-d 0755 root sys usr/samba packaging/SGI samba.sw.base
-f 0444 root sys usr/samba/README packaging/SGI/README samba.sw.base
-d 0755 root sys usr/samba/bin packaging/SGI samba.sw.base
-f 0755 root sys usr/samba/bin/addtosmbpass source/addtosmbpass samba.sw.base
-f 0775 root sys usr/samba/bin/nmbd source/nmbd samba.sw.base
-f 0755 root sys usr/samba/bin/nmblookup source/nmblookup samba.sw.base
-f 0644 root sys usr/samba/bin/psfixes.sed packaging/SGI/psfixes.sed samba.sw.base
-f 0755 root sys usr/samba/bin/sambalp packaging/SGI/sambalp samba.sw.base
-f 0755 root sys usr/samba/bin/smbclient source/smbclient samba.sw.base
-f 0775 root sys usr/samba/bin/smbd source/smbd samba.sw.base
-f 4555 root sys usr/samba/bin/smbpasswd source/smbpasswd samba.sw.base
-f 0755 root sys usr/samba/bin/smbprint packaging/SGI/smbprint samba.sw.base
-f 0755 root sys usr/samba/bin/smbrun source/smbrun samba.sw.base
-f 0755 root sys usr/samba/bin/smbstatus source/smbstatus samba.sw.base
-f 0755 root sys usr/samba/bin/smbtar source/smbtar samba.sw.base
-f 0775 root sys usr/samba/bin/testparm source/testparm samba.sw.base
-f 0775 root sys usr/samba/bin/testprns source/testprns samba.sw.base
-d 0755 root sys usr/samba/docs docs samba.man.doc
-f 0644 root sys usr/samba/docs/Application_Serving.txt docs/Application_Serving.txt samba.man.doc
-f 0644 root sys usr/samba/docs/BROWSING.txt docs/BROWSING.txt samba.man.doc
-f 0644 root sys usr/samba/docs/BUGS.txt docs/BUGS.txt samba.man.doc
-f 0644 root sys usr/samba/docs/DIAGNOSIS.txt docs/DIAGNOSIS.txt samba.man.doc
-f 0644 root sys usr/samba/docs/DNIX.txt docs/DNIX.txt samba.man.doc
-f 0644 root sys usr/samba/docs/DOMAIN.txt docs/DOMAIN.txt samba.man.doc
-f 0644 root sys usr/samba/docs/DOMAIN_CONTROL.txt docs/DOMAIN_CONTROL.txt samba.man.doc
-f 0644 root sys usr/samba/docs/ENCRYPTION.txt docs/ENCRYPTION.txt samba.man.doc
-f 0644 root sys usr/samba/docs/Faxing.txt docs/Faxing.txt samba.man.doc
-f 0644 root sys usr/samba/docs/GOTCHAS.txt docs/GOTCHAS.txt samba.man.doc
-f 0644 root sys usr/samba/docs/HINTS.txt docs/HINTS.txt samba.man.doc
-f 0644 root sys usr/samba/docs/INSTALL.sambatar docs/INSTALL.sambatar samba.man.doc
-f 0644 root sys usr/samba/docs/MIRRORS docs/MIRRORS samba.man.doc
-f 0644 root sys usr/samba/docs/NT4_PlainPassword.reg docs/NT4_PlainPassword.reg samba.man.doc
-f 0644 root sys usr/samba/docs/NetBIOS.txt docs/NetBIOS.txt samba.man.doc
-f 0644 root sys usr/samba/docs/OS2-Client-HOWTO.txt docs/OS2-Client-HOWTO.txt samba.man.doc
-f 0644 root sys usr/samba/docs/PROJECTS docs/PROJECTS samba.man.doc
-f 0644 root sys usr/samba/docs/Passwords.txt docs/Passwords.txt samba.man.doc
-f 0644 root sys usr/samba/docs/Printing.txt docs/Printing.txt samba.man.doc
-f 0644 root sys usr/samba/docs/README.DCEDFS docs/README.DCEDFS samba.man.doc
-f 0644 root sys usr/samba/docs/README.jis docs/README.jis samba.man.doc
-f 0644 root sys usr/samba/docs/README.sambatar docs/README.sambatar samba.man.doc
-f 0644 root sys usr/samba/docs/SCO.txt docs/SCO.txt samba.man.doc
-f 0644 root sys usr/samba/docs/SMBTAR.notes docs/SMBTAR.notes samba.man.doc
-f 0644 root sys usr/samba/docs/Speed.txt docs/Speed.txt samba.man.doc
-f 0644 root sys usr/samba/docs/Support.txt docs/Support.txt samba.man.doc
-f 0644 root sys usr/samba/docs/THANKS docs/THANKS samba.man.doc
-f 0644 root sys usr/samba/docs/Tracing.txt docs/Tracing.txt samba.man.doc
-f 0644 root sys usr/samba/docs/UNIX-SMB.txt docs/UNIX-SMB.txt samba.man.doc
-f 0644 root sys usr/samba/docs/UNIX_INSTALL.txt docs/UNIX_INSTALL.txt samba.man.doc
-f 0644 root sys usr/samba/docs/Win95.txt docs/Win95.txt samba.man.doc
-f 0644 root sys usr/samba/docs/Win95_PlainPassword.reg docs/Win95_PlainPassword.reg samba.man.doc
-f 0644 root sys usr/samba/docs/WinNT.txt docs/WinNT.txt samba.man.doc
-f 0644 root sys usr/samba/docs/announce docs/announce samba.man.doc
-d 0755 root sys usr/samba/docs/faq docs/faq samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-Server-FAQ-1.html docs/faq/Samba-Server-FAQ-1.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-Server-FAQ-2.html docs/faq/Samba-Server-FAQ-2.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-Server-FAQ.html docs/faq/Samba-Server-FAQ.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-Server-FAQ.sgml docs/faq/Samba-Server-FAQ.sgml samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-1.html docs/faq/Samba-meta-FAQ-1.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-2.html docs/faq/Samba-meta-FAQ-2.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-3.html docs/faq/Samba-meta-FAQ-3.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-4.html docs/faq/Samba-meta-FAQ-4.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-5.html docs/faq/Samba-meta-FAQ-5.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ-6.html docs/faq/Samba-meta-FAQ-6.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ.html docs/faq/Samba-meta-FAQ.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ.sgml docs/faq/Samba-meta-FAQ.sgml samba.man.doc
-f 0644 root sys usr/samba/docs/faq/Samba-meta-FAQ.txt docs/faq/Samba-meta-FAQ.txt samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq-1.html docs/faq/sambafaq-1.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq-2.html docs/faq/sambafaq-2.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq-3.html docs/faq/sambafaq-3.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq-4.html docs/faq/sambafaq-4.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq-5.html docs/faq/sambafaq-5.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq.html docs/faq/sambafaq.html samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq.sgml docs/faq/sambafaq.sgml samba.man.doc
-f 0644 root sys usr/samba/docs/faq/sambafaq.txt docs/faq/sambafaq.txt samba.man.doc
-f 0644 root sys usr/samba/docs/history docs/history samba.man.doc
-f 0644 root sys usr/samba/docs/internals.doc source/internals.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameannounce.doc source/nameannounce.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namebrowse.doc source/namebrowse.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namedbname.doc source/namedbname.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namedbresp.doc source/namedbresp.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameelect.doc source/nameelect.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namelogon.doc source/namelogon.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namepacket.doc source/namepacket.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namequery.doc source/namequery.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameresp.doc source/nameresp.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameserv.doc source/nameserv.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameservreply.doc source/nameservreply.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nameservresp.doc source/nameservresp.doc samba.man.doc
-f 0644 root sys usr/samba/docs/namework.doc source/namework.doc samba.man.doc
-f 0644 root sys usr/samba/docs/nmbd.8 docs/nmbd.8 samba.man.doc
-f 0644 root sys usr/samba/docs/samba.7 docs/samba.7 samba.man.doc
-f 0644 root sys usr/samba/docs/samba.faq docs/samba.faq samba.man.doc
-f 0644 root sys usr/samba/docs/samba.lsm docs/samba.lsm samba.man.doc
-f 0644 root sys usr/samba/docs/security_level.txt docs/security_level.txt samba.man.doc
-f 0644 root sys usr/samba/docs/smb.conf.5 docs/smb.conf.5 samba.man.doc
-f 0644 root sys usr/samba/docs/smbclient.1 docs/smbclient.1 samba.man.doc
-f 0644 root sys usr/samba/docs/smbd.8 docs/smbd.8 samba.man.doc
-f 0644 root sys usr/samba/docs/smbpasswd.8 docs/smbpasswd.8 samba.man.doc
-f 0644 root sys usr/samba/docs/smbrun.1 docs/smbrun.1 samba.man.doc
-f 0644 root sys usr/samba/docs/smbstatus.1 docs/smbstatus.1 samba.man.doc
-f 0644 root sys usr/samba/docs/smbtar.1 docs/smbtar.1 samba.man.doc
-f 0644 root sys usr/samba/docs/testparm.1 docs/testparm.1 samba.man.doc
-f 0644 root sys usr/samba/docs/testprns.1 docs/testprns.1 samba.man.doc
-f 0644 root sys usr/samba/docs/wfw_slip.htm docs/wfw_slip.htm samba.man.doc
-f 0755 root sys usr/samba/inetd.sh packaging/SGI/inetd.sh samba.sw.base
-d 0755 root sys usr/samba/lib packaging/SGI samba.sw.base
-f 0644 root sys usr/samba/lib/smb.conf packaging/SGI/smb.conf samba.sw.base config(update)
-f 0775 root sys usr/samba/mkprintcap.sh packaging/SGI/mkprintcap.sh samba.sw.base exitop(/usr/samba/mkprintcap.sh) removeop(rm /usr/samba/printcap)
-d 0755 root sys usr/samba/src source samba.src.samba
-f 0644 root sys usr/samba/src/COPYING COPYING samba.src.samba
-f 0644 root sys usr/samba/src/Manifest Manifest samba.src.samba
-f 0644 root sys usr/samba/src/README README samba.src.samba
-f 0644 root sys usr/samba/src/Read-Manifest-Now Read-Manifest-Now samba.src.samba
-f 0644 root sys usr/samba/src/Roadmap Roadmap samba.src.samba
-f 0644 root sys usr/samba/src/WHATSNEW.txt WHATSNEW.txt samba.src.samba
-d 0755 root sys usr/samba/src/docs docs samba.src.samba
-f 0644 root sys usr/samba/src/docs/Application_Serving.txt docs/Application_Serving.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/BROWSING.txt docs/BROWSING.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/BUGS.txt docs/BUGS.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/DIAGNOSIS.txt docs/DIAGNOSIS.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/DNIX.txt docs/DNIX.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/DOMAIN.txt docs/DOMAIN.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/DOMAIN_CONTROL.txt docs/DOMAIN_CONTROL.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/ENCRYPTION.txt docs/ENCRYPTION.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/Faxing.txt docs/Faxing.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/GOTCHAS.txt docs/GOTCHAS.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/HINTS.txt docs/HINTS.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/INSTALL.sambatar docs/INSTALL.sambatar samba.src.samba
-f 0644 root sys usr/samba/src/docs/MIRRORS docs/MIRRORS samba.src.samba
-f 0644 root sys usr/samba/src/docs/NT4_PlainPassword.reg docs/NT4_PlainPassword.reg samba.src.samba
-f 0644 root sys usr/samba/src/docs/NetBIOS.txt docs/NetBIOS.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/OS2-Client-HOWTO.txt docs/OS2-Client-HOWTO.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/PROJECTS docs/PROJECTS samba.src.samba
-f 0644 root sys usr/samba/src/docs/Passwords.txt docs/Passwords.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/Printing.txt docs/Printing.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/README.DCEDFS docs/README.DCEDFS samba.src.samba
-f 0644 root sys usr/samba/src/docs/README.jis docs/README.jis samba.src.samba
-f 0644 root sys usr/samba/src/docs/README.sambatar docs/README.sambatar samba.src.samba
-f 0644 root sys usr/samba/src/docs/SCO.txt docs/SCO.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/SMBTAR.notes docs/SMBTAR.notes samba.src.samba
-f 0644 root sys usr/samba/src/docs/Speed.txt docs/Speed.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/Support.txt docs/Support.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/THANKS docs/THANKS samba.src.samba
-f 0644 root sys usr/samba/src/docs/Tracing.txt docs/Tracing.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/UNIX-SMB.txt docs/UNIX-SMB.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/UNIX_INSTALL.txt docs/UNIX_INSTALL.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/Win95.txt docs/Win95.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/Win95_PlainPassword.reg docs/Win95_PlainPassword.reg samba.src.samba
-f 0644 root sys usr/samba/src/docs/WinNT.txt docs/WinNT.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/announce docs/announce samba.src.samba
-d 0755 root sys usr/samba/src/docs/faq docs/faq samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-Server-FAQ-1.html docs/faq/Samba-Server-FAQ-1.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-Server-FAQ-2.html docs/faq/Samba-Server-FAQ-2.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-Server-FAQ.html docs/faq/Samba-Server-FAQ.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-Server-FAQ.sgml docs/faq/Samba-Server-FAQ.sgml samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-1.html docs/faq/Samba-meta-FAQ-1.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-2.html docs/faq/Samba-meta-FAQ-2.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-3.html docs/faq/Samba-meta-FAQ-3.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-4.html docs/faq/Samba-meta-FAQ-4.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-5.html docs/faq/Samba-meta-FAQ-5.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ-6.html docs/faq/Samba-meta-FAQ-6.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ.html docs/faq/Samba-meta-FAQ.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ.sgml docs/faq/Samba-meta-FAQ.sgml samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/Samba-meta-FAQ.txt docs/faq/Samba-meta-FAQ.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq-1.html docs/faq/sambafaq-1.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq-2.html docs/faq/sambafaq-2.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq-3.html docs/faq/sambafaq-3.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq-4.html docs/faq/sambafaq-4.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq-5.html docs/faq/sambafaq-5.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq.html docs/faq/sambafaq.html samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq.sgml docs/faq/sambafaq.sgml samba.src.samba
-f 0644 root sys usr/samba/src/docs/faq/sambafaq.txt docs/faq/sambafaq.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/history docs/history samba.src.samba
-f 0644 root sys usr/samba/src/docs/nmbd.8 docs/nmbd.8 samba.src.samba
-f 0644 root sys usr/samba/src/docs/samba.7 docs/samba.7 samba.src.samba
-f 0644 root sys usr/samba/src/docs/samba.faq docs/samba.faq samba.src.samba
-f 0644 root sys usr/samba/src/docs/samba.lsm docs/samba.lsm samba.src.samba
-f 0644 root sys usr/samba/src/docs/security_level.txt docs/security_level.txt samba.src.samba
-f 0644 root sys usr/samba/src/docs/smb.conf.5 docs/smb.conf.5 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbclient.1 docs/smbclient.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbd.8 docs/smbd.8 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbpasswd.8 docs/smbpasswd.8 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbrun.1 docs/smbrun.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbstatus.1 docs/smbstatus.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/smbtar.1 docs/smbtar.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/testparm.1 docs/testparm.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/testprns.1 docs/testprns.1 samba.src.samba
-f 0644 root sys usr/samba/src/docs/wfw_slip.htm docs/wfw_slip.htm samba.src.samba
-d 0755 root sys usr/samba/src/examples examples samba.src.samba
-f 0664 root sys usr/samba/src/examples/README examples/README samba.src.samba
-d 0755 root sys usr/samba/src/examples/dce-dfs examples/dce-dfs samba.src.samba
-f 0644 root sys usr/samba/src/examples/dce-dfs/README examples/dce-dfs/README samba.src.samba
-f 0644 root sys usr/samba/src/examples/dce-dfs/smb.conf examples/dce-dfs/smb.conf samba.src.samba
-d 0755 root sys usr/samba/src/examples/misc examples/misc samba.src.samba
-f 0644 root sys usr/samba/src/examples/misc/extra_smbstatus examples/misc/extra_smbstatus samba.src.samba
-f 0644 root sys usr/samba/src/examples/misc/wall.perl examples/misc/wall.perl samba.src.samba
-d 0775 root sys usr/samba/src/examples/printer-accounting examples/printer-accounting samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/README examples/printer-accounting/README samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/acct-all examples/printer-accounting/acct-all samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/acct-sum examples/printer-accounting/acct-sum samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/hp5-redir examples/printer-accounting/hp5-redir samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/lp-acct examples/printer-accounting/lp-acct samba.src.samba
-f 0664 root sys usr/samba/src/examples/printer-accounting/printcap examples/printer-accounting/printcap samba.src.samba
-d 0755 root sys usr/samba/src/examples/printing examples/printing samba.src.samba
-f 0755 root sys usr/samba/src/examples/printing/smbprint examples/printing/smbprint samba.src.samba
-f 0644 root sys usr/samba/src/examples/printing/smbprint.sysv examples/printing/smbprint.sysv samba.src.samba
-d 0755 root sys usr/samba/src/examples/simple examples/simple samba.src.samba
-f 0644 root sys usr/samba/src/examples/simple/README examples/simple/README samba.src.samba
-f 0644 root sys usr/samba/src/examples/simple/smb.conf examples/simple/smb.conf samba.src.samba
-d 0775 root sys usr/samba/src/examples/svr4-startup examples/svr4-startup samba.src.samba
-f 0664 root sys usr/samba/src/examples/svr4-startup/README examples/svr4-startup/README samba.src.samba
-f 0775 root sys usr/samba/src/examples/svr4-startup/samba.server examples/svr4-startup/samba.server samba.src.samba
-d 0755 root sys usr/samba/src/examples/thoralf examples/thoralf samba.src.samba
-f 0644 root sys usr/samba/src/examples/thoralf/smb.conf examples/thoralf/smb.conf samba.src.samba
-d 0755 root sys usr/samba/src/examples/tridge examples/tridge samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/README examples/tridge/README samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/smb.conf examples/tridge/smb.conf samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/smb.conf.WinNT examples/tridge/smb.conf.WinNT samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/smb.conf.fjall examples/tridge/smb.conf.fjall samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/smb.conf.lapland examples/tridge/smb.conf.lapland samba.src.samba
-f 0644 root sys usr/samba/src/examples/tridge/smb.conf.vittjokk examples/tridge/smb.conf.vittjokk samba.src.samba
-d 0775 root sys usr/samba/src/examples/validchars examples/validchars samba.src.samba
-f 0664 root sys usr/samba/src/examples/validchars/msdos70.out examples/validchars/msdos70.out samba.src.samba
-f 0664 root sys usr/samba/src/examples/validchars/nwdos70.out examples/validchars/nwdos70.out samba.src.samba
-f 0664 root sys usr/samba/src/examples/validchars/readme examples/validchars/readme samba.src.samba
-f 0664 root sys usr/samba/src/examples/validchars/validchr.c examples/validchars/validchr.c samba.src.samba
-f 0664 root sys usr/samba/src/examples/validchars/validchr.com examples/validchars/validchr.com samba.src.samba
-d 0755 root sys usr/samba/src/packaging packaging samba.src.samba
-f 0644 root sys usr/samba/src/packaging/README packaging/README samba.src.samba
-d 0755 root sys usr/samba/src/packaging/SGI packaging/SGI samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/Makefile packaging/SGI/Makefile samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/README packaging/SGI/README samba.src.samba
-f 0755 root sys usr/samba/src/packaging/SGI/inetd.sh packaging/SGI/inetd.sh samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/legal_notice.html packaging/SGI/legal_notice.html samba.src.samba
-f 0755 root sys usr/samba/src/packaging/SGI/mkman packaging/SGI/mkman samba.src.samba
-f 0755 root sys usr/samba/src/packaging/SGI/mkprintcap.sh packaging/SGI/mkprintcap.sh samba.src.samba
-f 0755 root sys usr/samba/src/packaging/SGI/mkrelease.sh packaging/SGI/mkrelease.sh samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/printcap packaging/SGI/printcap samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/psfixes.sed packaging/SGI/psfixes.sed samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/relnotes.html packaging/SGI/relnotes.html samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/samba.config packaging/SGI/samba.config samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/samba.idb packaging/SGI/samba.idb samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/samba.rc packaging/SGI/samba.rc samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/samba.spec packaging/SGI/samba.spec samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/sambalp packaging/SGI/sambalp samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/smb.conf packaging/SGI/smb.conf samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/smbpasswd packaging/SGI/smbpasswd samba.src.samba
-f 0644 root sys usr/samba/src/packaging/SGI/smbprint packaging/SGI/smbprint samba.src.samba
-d 0755 root sys usr/samba/src/packaging/redhat packaging/redhat samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/Instructions packaging/redhat/Instructions samba.src.samba
-f 0755 root sys usr/samba/src/packaging/redhat/makeldirp.sh packaging/redhat/makeldirs.sh samba.src.samba
-f 0755 root sys usr/samba/src/packaging/redhat/makerpms.sh packaging/redhat/makerpms.sh samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/samba-axp.patch packaging/redhat/samba-axp.patch samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/samba-make.patch packaging/redhat/samba-make.patch samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/samba.log packaging/redhat/samba.log samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/samba.pamd packaging/redhat/samba.pamd samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/samba.spec packaging/redhat/samba.spec samba.src.samba
-f 0644 root sys usr/samba/src/packaging/redhat/smb.conf packaging/redhat/smb.conf samba.src.samba
-f 0755 root sys usr/samba/src/packaging/redhat/smb.init packaging/redhat/smb.init samba.src.samba
-f 0755 root sys usr/samba/src/packaging/redhat/smbprint packaging/redhat/smbprint samba.src.samba
-d 0755 root sys usr/samba/src/source source samba.src.samba
-f 0644 root sys usr/samba/src/source/Makefile source/Makefile samba.src.samba
-f 0644 root sys usr/samba/src/source/Makefile.OS2 source/Makefile.OS2 samba.src.samba
-f 0644 root sys usr/samba/src/source/access.c source/access.c samba.src.samba
-f 0644 root sys usr/samba/src/source/addtosmbpass source/addtosmbpass samba.src.samba
-f 0644 root sys usr/samba/src/source/byteorder.h source/byteorder.h samba.src.samba
-f 0644 root sys usr/samba/src/source/change-log source/change-log samba.src.samba
-f 0644 root sys usr/samba/src/source/charcnv.c source/charcnv.c samba.src.samba
-f 0644 root sys usr/samba/src/source/charset.c source/charset.c samba.src.samba
-f 0644 root sys usr/samba/src/source/charset.h source/charset.h samba.src.samba
-f 0644 root sys usr/samba/src/source/checkos.sh source/checkos.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/chgpasswd.c source/chgpasswd.c samba.src.samba
-f 0644 root sys usr/samba/src/source/client.c source/client.c samba.src.samba
-f 0644 root sys usr/samba/src/source/clientutil.c source/clientutil.c samba.src.samba
-f 0644 root sys usr/samba/src/source/clitar.c source/clitar.c samba.src.samba
-f 0644 root sys usr/samba/src/source/clitar.h source/clitar.h samba.src.samba
-f 0644 root sys usr/samba/src/source/dir.c source/dir.c samba.src.samba
-f 0644 root sys usr/samba/src/source/fault.c source/fault.c samba.src.samba
-f 0644 root sys usr/samba/src/source/getsmbpass.c source/getsmbpass.c samba.src.samba
-f 0644 root sys usr/samba/src/source/includes.h source/includes.h samba.src.samba
-f 0644 root sys usr/samba/src/source/installbin.sh source/installbin.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/installman.sh source/installman.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/installscripts.sh source/installscripts.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/interface.c source/interface.c samba.src.samba
-f 0644 root sys usr/samba/src/source/internals.doc source/internals.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/ipc.c source/ipc.c samba.src.samba
-f 0644 root sys usr/samba/src/source/kanji.c source/kanji.c samba.src.samba
-f 0644 root sys usr/samba/src/source/kanji.h source/kanji.h samba.src.samba
-f 0644 root sys usr/samba/src/source/loadparm.c source/loadparm.c samba.src.samba
-f 0644 root sys usr/samba/src/source/local.h source/local.h samba.src.samba
-f 0644 root sys usr/samba/src/source/locking.c source/locking.c samba.src.samba
-f 0644 root sys usr/samba/src/source/mangle.c source/mangle.c samba.src.samba
-f 0644 root sys usr/samba/src/source/md4.c source/md4.c samba.src.samba
-f 0644 root sys usr/samba/src/source/md4.h source/md4.h samba.src.samba
-f 0644 root sys usr/samba/src/source/message.c source/message.c samba.src.samba
-f 0644 root sys usr/samba/src/source/mkproto.awk source/mkproto.awk samba.src.samba
-f 0644 root sys usr/samba/src/source/mksmbpasswd.sh source/mksmbpasswd.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/nameannounce.c source/nameannounce.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameannounce.doc source/nameannounce.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namebrowse.c source/namebrowse.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namebrowse.doc source/namebrowse.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nameconf.c source/nameconf.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbname.c source/namedbname.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbname.doc source/namedbname.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbresp.c source/namedbresp.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbresp.doc source/namedbresp.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbserver.c source/namedbserver.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbsubnet.c source/namedbsubnet.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namedbwork.c source/namedbwork.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameelect.c source/nameelect.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameelect.doc source/nameelect.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namelogon.c source/namelogon.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namelogon.doc source/namelogon.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namepacket.c source/namepacket.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namepacket.doc source/namepacket.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namequery.c source/namequery.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namequery.doc source/namequery.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nameresp.c source/nameresp.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameresp.doc source/nameresp.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nameserv.c source/nameserv.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameserv.doc source/nameserv.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nameserv.h source/nameserv.h samba.src.samba
-f 0644 root sys usr/samba/src/source/nameservreply.c source/nameservreply.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameservreply.doc source/nameservreply.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nameservresp.c source/nameservresp.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nameservresp.doc source/nameservresp.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/namework.c source/namework.c samba.src.samba
-f 0644 root sys usr/samba/src/source/namework.doc source/namework.doc samba.src.samba
-f 0644 root sys usr/samba/src/source/nmbd.c source/nmbd.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nmblib.c source/nmblib.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nmblookup.c source/nmblookup.c samba.src.samba
-f 0644 root sys usr/samba/src/source/nmbsync.c source/nmbsync.c samba.src.samba
-f 0644 root sys usr/samba/src/source/params.c source/params.c samba.src.samba
-f 0644 root sys usr/samba/src/source/password.c source/password.c samba.src.samba
-f 0644 root sys usr/samba/src/source/pcap.c source/pcap.c samba.src.samba
-f 0644 root sys usr/samba/src/source/pipes.c source/pipes.c samba.src.samba
-f 0644 root sys usr/samba/src/source/predict.c source/predict.c samba.src.samba
-f 0644 root sys usr/samba/src/source/printing.c source/printing.c samba.src.samba
-f 0644 root sys usr/samba/src/source/proto.h source/proto.h samba.src.samba
-f 0644 root sys usr/samba/src/source/quotas.c source/quotas.c samba.src.samba
-f 0644 root sys usr/samba/src/source/replace.c source/replace.c samba.src.samba
-f 0644 root sys usr/samba/src/source/reply.c source/reply.c samba.src.samba
-f 0644 root sys usr/samba/src/source/revert.sh source/revert.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/server.c source/server.c samba.src.samba
-f 0644 root sys usr/samba/src/source/shmem.c source/shmem.c samba.src.samba
-f 0644 root sys usr/samba/src/source/smb.h source/smb.h samba.src.samba
-f 0644 root sys usr/samba/src/source/smbencrypt.c source/smbencrypt.c samba.src.samba
-f 0644 root sys usr/samba/src/source/smbpass.c source/smbpass.c samba.src.samba
-f 0644 root sys usr/samba/src/source/smbpasswd.c source/smbpasswd.c samba.src.samba
-f 0644 root sys usr/samba/src/source/smbrun.c source/smbrun.c samba.src.samba
-f 0644 root sys usr/samba/src/source/smbtar source/smbtar samba.src.samba
-f 0644 root sys usr/samba/src/source/status.c source/status.c samba.src.samba
-f 0644 root sys usr/samba/src/source/system.c source/system.c samba.src.samba
-f 0644 root sys usr/samba/src/source/testparm.c source/testparm.c samba.src.samba
-f 0644 root sys usr/samba/src/source/testprns.c source/testprns.c samba.src.samba
-f 0644 root sys usr/samba/src/source/time.c source/time.c samba.src.samba
-f 0644 root sys usr/samba/src/source/trans2.c source/trans2.c samba.src.samba
-f 0644 root sys usr/samba/src/source/trans2.h source/trans2.h samba.src.samba
-f 0644 root sys usr/samba/src/source/ufc.c source/ufc.c samba.src.samba
-f 0644 root sys usr/samba/src/source/uid.c source/uid.c samba.src.samba
-f 0644 root sys usr/samba/src/source/uninstallbin.sh source/uninstallbin.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/uninstallman.sh source/uninstallman.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/uninstallscripts.sh source/uninstallscripts.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/updatesmbpasswd.sh source/updatesmbpasswd.sh samba.src.samba
-f 0644 root sys usr/samba/src/source/username.c source/username.c samba.src.samba
-f 0644 root sys usr/samba/src/source/util.c source/util.c samba.src.samba
-f 0644 root sys usr/samba/src/source/version.h source/version.h samba.src.samba
-f 0644 root sys usr/samba/src/source/vt_mode.c source/vt_mode.c samba.src.samba
-f 0644 root sys usr/samba/src/source/vt_mode.h source/vt_mode.h samba.src.samba
-d 0775 root sys usr/samba/var/locks packaging/SGI samba.sw.base
-d 0755 root sys usr/share/catman/u_man packaging/SGI/catman samba.man.manpages
-d 0755 root sys usr/share/catman/u_man/cat1 packaging/SGI/catman samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/smbclient.1.Z packaging/SGI/catman/smbclient.1.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/smbrun.1.Z packaging/SGI/catman/smbrun.1.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/smbstatus.1.Z packaging/SGI/catman/smbstatus.1.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/smbtar.1.Z packaging/SGI/catman/smbtar.1.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/testparm.1.Z packaging/SGI/catman/testparm.1.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat1/testprns.1.Z packaging/SGI/catman/testprns.1.Z samba.man.manpages
-d 0755 root sys usr/share/catman/u_man/cat5 packaging/SGI/catman samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat5/smb.conf.5.Z packaging/SGI/catman/smb.conf.5.Z samba.man.manpages
-d 0755 root sys usr/share/catman/u_man/cat7 packaging/SGI/catman samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat7/samba.7.Z packaging/SGI/catman/samba.7.Z samba.man.manpages
-d 0755 root sys usr/share/catman/u_man/cat8 packaging/SGI/catman samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat8/nmbd.8.Z packaging/SGI/catman/nmbd.8.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat8/smbd.8.Z packaging/SGI/catman/smbd.8.Z samba.man.manpages
-f 0664 root sys usr/share/catman/u_man/cat8/smbpasswd.8.Z packaging/SGI/catman/smbpasswd.8.Z samba.man.manpages
diff --git a/packaging/SGI/samba.rc b/packaging/SGI/samba.rc
deleted file mode 100644
index 121b3400a38..00000000000
--- a/packaging/SGI/samba.rc
+++ /dev/null
@@ -1,42 +0,0 @@
-#! /bin/sh
-
-#
-# Samba server control
-#
-
-IS_ON=/etc/chkconfig
-KILLALL=/sbin/killall
-
-SAMBAD=/usr/samba/bin/smbd
-#SAMBA_OPTS=-d2
-NMBD=/usr/samba/bin/nmbd
-#NMBD_OPTS=-d1
-
-if test ! -x $IS_ON ; then
- IS_ON=true
-fi
-
-if $IS_ON verbose ; then
- ECHO=echo
-else # For a quiet startup and shutdown
- ECHO=:
-fi
-
-case $1 in
-'start')
- if $IS_ON samba && test -x $SAMBAD; then
- $KILLALL -15 smbd nmbd
- $ECHO "Samba:\c"
- $SAMBAD $SAMBA_OPTS -D; $ECHO " smbd\c"
- $NMBD $NMBD_OPTS -D; $ECHO " nmbd\c"
- $ECHO "."
- fi
- ;;
-'stop')
- $ECHO "Stopping Samba Servers."
- $KILLALL -15 smbd nmbd
- ;;
-*)
- echo "usage: /etc/init.d/samba {start|stop}"
- ;;
-esac
diff --git a/packaging/SGI/samba.spec b/packaging/SGI/samba.spec
deleted file mode 100644
index 1940e93e935..00000000000
--- a/packaging/SGI/samba.spec
+++ /dev/null
@@ -1,45 +0,0 @@
-product samba
- id "Samba version 1.9.17"
- image sw
- id "Samba Execution Environment"
- version 0109170006
- order 0
- subsys base default
- id "Samba Execution Environment"
- replaces fw_samba.sw.base 0 9999999999
- replaces fw_samba.sw.samba 0 9999999999
- exp samba.sw.base
- endsubsys
- endimage
- image man
- id "Samba Online Documentation"
- version 0109170006
- order 1
- subsys manpages default
- id "Samba Man Page"
- replaces fw_samba.man.manpages 0 9999999999
- replaces fw_samba.man.samba 0 9999999999
- exp samba.man.manpages
- endsubsys
- subsys doc default
- id "Samba Documentation"
- replaces fw_samba.man.doc 0 9999999999
- exp samba.man.doc
- endsubsys
- subsys relnotes default
- id "Samba Release Notes"
- replaces fw_samba.man.relnotes 0 9999999999
- exp samba.man.relnotes
- endsubsys
- endimage
- image src
- id "Samba Source Code"
- version 0109170006
- order 2
- subsys samba
- id "Samba Source Code"
- replaces fw_samba.src.samba 0 9999999999
- exp samba.src.samba
- endsubsys
- endimage
-endproduct
diff --git a/packaging/SGI/sambalp b/packaging/SGI/sambalp
deleted file mode 100644
index d7c6be2a2d4..00000000000
--- a/packaging/SGI/sambalp
+++ /dev/null
@@ -1,21 +0,0 @@
-#! /bin/sh
-#
-# Workaround Win95 printer driver/Impressario bug by removing
-# the PS check for available virtual memory. Note that this
-# bug appears to be in all Win95 print drivers that generate
-# PostScript; but is for certain there with a QMS-PS 810 (the
-# printer type I configure on the Win95-side for printing with
-# Samba).
-#
-# the sed script fixes 3 different bugs. The first line removes
-# the JCL statements added by some HP printer drivers to the
-# beginning of the postscript output. The second line fixes a
-# bug in output from word files with long filenames. A non-printing
-# character added to the end of the title comment by word is
-# removed. The third and fourth lines are the VM fix described
-# above.
-#
-TITLE="$3 on $4"
-
-sed -f /usr/samba/bin/psfixes.sed $2 | /usr/bin/lp -c -d$1 -t"$TITLE"
-rm $2
diff --git a/packaging/SGI/smb.conf b/packaging/SGI/smb.conf
deleted file mode 100644
index 178231d2cd1..00000000000
--- a/packaging/SGI/smb.conf
+++ /dev/null
@@ -1,84 +0,0 @@
-; Configuration file for smbd.
-; ============================================================================
-; For the format of this file and comprehensive descriptions of all the
-; configuration option, please refer to the man page for smb.conf(5).
-
-; This is a sample configuration for IRIX 6.x systems
-;
-; The following configuration should suit most systems for basic usage and
-; initial testing. It gives all clients access to their home directories and
-; allows access to all printers specified in /etc/printcap as well as /usr/tmp.
-;
-[global]
- comment = Samba %v
- workgroup = workgroup
- printing = sysv
-;
-; A printcap file is created during installation that contains the names
-; of all printers attached to your system. Names longer than 8 characters
-; will not be visible to clients.
-;
- printcap name = /usr/samba/printcap
-;
-; If you are using Impressario then you'll want to use the
-; sambalp script provided with this package. It works around
-; a problem in the PostScript generated by the standard Windows
-; drivers--there is a check to verify sufficient virtual memory
-; is available in the printer to print the job, but this fails
-; under Impressario because of a bug in Impressario. The sambalp
-; script strips out the vmstatus check. BTW, when using this
-; setup to print be sure to configure a Windows printer driver
-; that generates PostScript--QMS-PS 810 is one that should work
-; with the sambalp script.
-;
- print command = /usr/samba/bin/sambalp %p %s %U %m
- load printers = yes
- guest account = nobody
- browseable = yes
-
-; Set a max size for log files in Kb
- log file = /usr/samba/var
- max log size = 50
-
-; You will need a world readable lock directory and "share modes=yes"
-; if you want to support the file sharing modes for multiple users
-; of the same files
- locking = yes
- lock directory = /usr/samba/var/locks
- share modes = yes
-
-; security = user
-
-; You need to test to see if this makes a difference on your system
- socket options = TCP_NODELAY
-
-; Set the os level to > 32 if there is no NT server for your workgroup
- os level = 0
- preferred master = no
- domain master = no
- local master = no
- wins support = no
- wins server =
-
- preserve case = yes
- short preserve case = yes
-
-[homes]
- comment = Home Directories
- browseable = no
- writable = yes
-
-[printers]
- comment = All Printers
- path = /usr/tmp
- browseable = no
- printable = yes
- public = yes
- writable = no
- create mask = 0700
-
-[tmp]
- comment = Temporary file space
- path = /usr/tmp
- read only = no
- public = yes
diff --git a/packaging/SGI/smbpasswd b/packaging/SGI/smbpasswd
deleted file mode 100644
index 79c834dc354..00000000000
--- a/packaging/SGI/smbpasswd
+++ /dev/null
@@ -1 +0,0 @@
-username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:Long name:user home dir:user shell
diff --git a/packaging/SGI/smbprint b/packaging/SGI/smbprint
deleted file mode 100644
index 935f98bf923..00000000000
--- a/packaging/SGI/smbprint
+++ /dev/null
@@ -1,52 +0,0 @@
-#!/bin/sh
-#
-# @(#) smbprint.sysv version 1.0 Ross Wakelin
-#
-# Version 1.0 13 January 1995
-# modified from the original smbprint (bsd) script
-#
-# this script is a System 5 printer interface script. It
-# uses the smbclient program to print the file to the specified smb-based
-# server and service.
-#
-# To add this to your lp system, copy this file into your samba directory
-# (the example here is /opt/samba), modify the server and service variables
-# and then execute the following command (as root)
-#
-# lpadmin -punixprintername -v/dev/null -i/opt/samba/smbprint
-#
-# where unixprintername is the name that the printer will be known as
-# on your unix box.
-#
-# the script smbprint will be copied into your printer administration
-# directory (/usr/lib/lp or /etc/lp) as a new interface
-# (interface/unixprintername)
-# Then you have to enable unixprintername and accept unixprintername
-#
-# This script will then be called by the lp service to print the files
-# This script will have 6 or more parameters passed to it by the lp service.
-# The first five will contain details of the print job, who queued it etc,
-# while parameters 6 onwards are a list of files to print. We just
-# cat these at the samba client.
-#
-# Set these to the server and service you wish to print to
-# In this example I have a WfWg PC called "lapland" that has a printer
-# exported called "printer" with no password.
-#
-# clear out the unwanted parameters
-shift;shift;shift;shift;shift
-# now the argument list is just the files to print
-
-server=admin
-service=hplj2
-password=""
-
-(
-# NOTE You may wish to add the line `echo translate' if you want automatic
-# CR/LF translation when printing.
- echo translate
- echo "print -"
- cat $*
-) | /usr/samba/bin/smbclient "\\\\$server\\$service" $password -N -P > /dev/null
-exit $?
-
diff --git a/packaging/Solaris/pkg-specs/Packaging.script b/packaging/Solaris/pkg-specs/Packaging.script
deleted file mode 100644
index 6f182c33e52..00000000000
--- a/packaging/Solaris/pkg-specs/Packaging.script
+++ /dev/null
@@ -1,5 +0,0 @@
-#!/bin/sh
-./mkprototype
-pkgmk -o -d /tmp -b `pwd` -f ./prototype
-cd /tmp
-pkgtrans . samba.pkg samba
diff --git a/packaging/Solaris/pkg-specs/mkprototype b/packaging/Solaris/pkg-specs/mkprototype
deleted file mode 100644
index 5ca0746beea..00000000000
--- a/packaging/Solaris/pkg-specs/mkprototype
+++ /dev/null
@@ -1,31 +0,0 @@
-#!/bin/sh
-# this creates prototype files
-pkgproto * > prototype
-nawk 'BEGIN { print "# d directory"
- print "# e a file to be edited upon installation or removal"
- print "# f a standard executable or data file"
- print "# i installation script or information file"
- print "# l linked file"
- print "# s symbolic link"
- print "# v volatile file (one whose contents are expected to
-change)"
- print "#" }
-/ pkginfo / { print "i pkginfo" ; next }
-/ postinstall / { print "i postinstall" ; next }
-/ postremove / { print "i postremove" ; next }
-/d none usr / { print "d none usr ? ? ?" ; next }
-/d none usr\/local / { print "d none usr/local ? ? ?" ; next }
-/d none etc / { print "d none etc ? ? ?" ; next }
-/f none etc\// { $1 = "v" }
-/d none opt / { print "d none opt ? ? ?" ; next }
-/d none var / { print "d none var ? ? ?" ; next }
-/none prototype / { next }
-/none mkprototype / { next }
-/ src[ \/]/ { next }
-/^[dfv]/ { $5 = "bin"
- $6 = "bin"
- print
- next }
-{ print }' prototype >/tmp/prototype.$$
-mv /tmp/prototype.$$ prototype
-
diff --git a/packaging/Solaris/pkg-specs/pkginfo b/packaging/Solaris/pkg-specs/pkginfo
deleted file mode 100644
index ab06b3fffab..00000000000
--- a/packaging/Solaris/pkg-specs/pkginfo
+++ /dev/null
@@ -1,12 +0,0 @@
-PSTAMP=Mon Sep 29 17:26:14 BST 1997
-PKG=samba
-NAME=SMB based file/printer sharing
-VERSION=1.9.17p2,REV=1
-ARCH=sparc
-CATEGORY=system
-VENDOR=samba group
-DESC=File and printer sharing for NT workstations
-CLASSES=none
-INTONLY=1
-HOTLINE=Please contact your local UNIX support group
-BASEDIR=/
diff --git a/packaging/Solaris/pkg-specs/postinstall b/packaging/Solaris/pkg-specs/postinstall
deleted file mode 100644
index 0fbe9da10b5..00000000000
--- a/packaging/Solaris/pkg-specs/postinstall
+++ /dev/null
@@ -1,37 +0,0 @@
-#!/bin/sh
-# install samba
-
-nawk '/^netbios-[ns]*[ ]/ {next}
-{print}
-END { print "netbios-ssn 139/tcp"
- print "netbios-ns 137/udp # samba service" }' \
- ${PKG_INSTALL_ROOT}/etc/inet/services > /tmp/services.$$ && \
- mv -f /tmp/services.$$ ${PKG_INSTALL_ROOT}/etc/inet/services &&
-\
- chmod 644 ${PKG_INSTALL_ROOT}/etc/inet/services && \
- echo "Updated ${PKG_INSTALL_ROOT}/etc/inet/services"
-
-nawk '/samba.*mbd[ ]/ { next }
-{print}
-END { print "# samba connections are handled by smbd and nmbd"
- print "netbios-ssn stream tcp nowait root /opt/samba/bin/smbd
-smbd"
- print "netbios-ns dgram udp wait root /opt/samba/bin/nmbd nmbd" }'
-\
- ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf > /tmp/inetd.conf.$$ &&
-\
- mv -f /tmp/inetd.conf.$$ ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf
-&& \
- chmod 644 ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf && \
- echo "Updated ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf"
-
-echo "Installed samba service into ${PKG_INSTALL_ROOT:-/}"
-
-inetpid=`/bin/ps -ef | awk '/ \/usr\/sbin\/inetd / { print $2 } '`
-if [ "X$inetpid" = "X" ]; then
- echo "inetd not running"
-else
- echo "Restarting inetd($inetpid)"
- kill -HUP $inetpid
-fi
-
diff --git a/packaging/Solaris/pkg-specs/postremove b/packaging/Solaris/pkg-specs/postremove
deleted file mode 100644
index 7f7a5c1f8e4..00000000000
--- a/packaging/Solaris/pkg-specs/postremove
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/bin/sh
-# remove samba
-
-nawk '/^netbios-[ns]*[ ]/ {next}
-{print} ' \
- ${PKG_INSTALL_ROOT}/etc/inet/services > /tmp/services.$$ && \
- mv -f /tmp/services.$$ ${PKG_INSTALL_ROOT}/etc/inet/services &&
-\
- chmod 644 ${PKG_INSTALL_ROOT}/etc/inet/services && \
- echo "Updated ${PKG_INSTALL_ROOT}/etc/inet/services"
-
-nawk '/samba.*mbd[ ]/ { next }
-{print} ' \
- ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf > /tmp/inetd.conf.$$ &&
-\
- mv -f /tmp/inetd.conf.$$ ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf
-&& \
- chmod 644 ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf && \
- echo "Updated ${PKG_INSTALL_ROOT}/etc/inet/inetd.conf"
-
-echo "Removed samba service from ${PKG_INSTALL_ROOT:-/}"
-
-inetpid=`/bin/ps -ef | awk '/ \/usr\/sbin\/inetd / { print $2 } '`
-if [ "X$inetpid" = "X" ]; then
- echo "inetd not running"
-else
- echo "Restarting inetd($inetpid)"
- kill -HUP $inetpid
-fi
-
diff --git a/source/.cvsignore b/source/.cvsignore
deleted file mode 100644
index 9b7ea034be9..00000000000
--- a/source/.cvsignore
+++ /dev/null
@@ -1,12 +0,0 @@
-Makefile.RPM
-makefile
-makefile.sunos5
-nmbd
-nmblookup
-smbclient
-smbd
-smbpasswd
-smbrun
-smbstatus
-testparm
-testprns
diff --git a/source/arcfour.c b/source/arcfour.c
deleted file mode 100644
index a28d702a861..00000000000
--- a/source/arcfour.c
+++ /dev/null
@@ -1,91 +0,0 @@
-/*
- Unix SMB/Netbios implementation.
- Version 1.9.
-
- a implementation of arcfour designed for use in the
- SMB password change protocol based on the description
- in 'Applied Cryptography', 2nd Edition.
-
- Copyright (C) Jeremy Allison 1997
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-*/
-
-#include "arcfour.h"
-
-void set_arc4_key(unsigned char *data, int key_length, arc4_key *arckey)
-{
- unsigned int i;
- unsigned char j;
- unsigned char tc;
- unsigned char *s_box = &arckey->s_box[0];
-
- arckey->index_i = 0;
- arckey->index_j = 0;
- for(i = 0; i < 256; i++)
- s_box[i] = (unsigned char)i;
-
- j = 0;
- for( i = 0; i < 256; i++)
- {
- j += (s_box[i] + data[i%key_length]);
- tc = s_box[i];
- s_box[i] = s_box[j];
- s_box[j] = tc;
- }
-}
-
-void arc4(arc4_key *arckey, unsigned char *data_in, unsigned char *data_out,
- int length)
-{
- unsigned char tc;
- int ind;
- unsigned char i, j;
- unsigned char t;
- unsigned char *s_box = &arckey->s_box[0];
-
- for( ind = 0; ind < length; ind++)
- {
- i = ++arckey->index_i;
- j = arckey->index_j += s_box[i];
- tc = s_box[i];
- s_box[i] = s_box[j];
- s_box[j] = tc;
- t = s_box[i] + s_box[j];
- *data_out++ = *data_in++ ^ s_box[t];
- }
-}
-
-#if 0
-/* Test vector */
-unsigned char key_data[] = { 0x61, 0x8a, 0x63, 0xd2, 0xfb };
-unsigned char plaintext[] = { 0xdc, 0xee, 0x4c, 0xf9, 0x2c };
-unsigned char ciphertext[] = { 0xf1, 0x38, 0x29, 0xc9, 0xde };
-
-int main(int argc, char *argv[])
-{
- unsigned char out[5];
- arc4_key key;
-
- set_arc4_key(key_data, 5, &key);
- arc4(&key, plaintext, out, 5);
-
- if(memcmp(out, ciphertext, 5) ==0)
- printf("Test ok !\n");
- else
- printf("Test fail !\n");
- return 0;
-}
-#endif
diff --git a/source/arcfour.h b/source/arcfour.h
deleted file mode 100644
index 34a4e8f91be..00000000000
--- a/source/arcfour.h
+++ /dev/null
@@ -1,39 +0,0 @@
-#ifndef _ARC4_H_
-#define _ARC4_H_
-
-/*
- Unix SMB/Netbios implementation.
- Version 1.9.
-
- a implementation of arcfour designed for use in the
- SMB password change protocol based on the description
- in 'Applied Cryptography', 2nd Edition.
-
- Copyright (C) Jeremy Allison 1997
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-*/
-
-typedef struct {
- unsigned char s_box[256];
- unsigned char index_i;
- unsigned char index_j;
-} arc4_key;
-
-extern void set_arc4_key(unsigned char *data, int key_length, arc4_key *arckey);
-extern void arc4(arc4_key *arckey, unsigned char *data_in,
- unsigned char *data_out, int length);
-
-#endif /* _ARC4_H_ */
diff --git a/source/cgi.c b/source/cgi.c
deleted file mode 100644
index 56c293985d6..00000000000
--- a/source/cgi.c
+++ /dev/null
@@ -1,163 +0,0 @@
-/*
- Unix SMB/Netbios implementation.
- Version 1.9.
- some simple CGI helper routines
- Copyright (C) Andrew Tridgell 1997
-
- This program is free software; you can redistribute it and/or modify
- it under the terms of the GNU General Public License as published by
- the Free Software Foundation; either version 2 of the License, or
- (at your option) any later version.
-
- This program is distributed in the hope that it will be useful,
- but WITHOUT ANY WARRANTY; without even the implied warranty of
- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
- GNU General Public License for more details.
-
- You should have received a copy of the GNU General Public License
- along with this program; if not, write to the Free Software
- Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
-*/
-
-
-#include "includes.h"
-
-#define MAX_VARIABLES 512
-
-struct var {
- char *name;
- char *value;
-};
-
-static struct var variables[MAX_VARIABLES];
-static int num_variables;
-
-
-static int grab_line(int *cl, char *line, int maxsize)
-{
- int i = 0;
-
- while ((*cl)) {
- int c = fgetc(stdin);
- (*cl)--;
-
- if (c == EOF) {
- (*cl) = 0;
- break;
- }
-
- if (c == '+') {
- c = ' ';
- }
-
- if (c == '\r') continue;
-
- if (strchr("\n&", c)) break;
-
- if (c == '%' && (*cl) >= 2) {
- int c1, c2;
- c1 = fgetc(stdin);
- c2 = fgetc(stdin);
- (*cl) -= 2;
- if (c1 == EOF || c2 == EOF) break;
- if (c1 >= '0' && c1 <= '9')
- c1 = c1 - '0';
- else if (c1 >= 'A' && c1 <= 'F')
- c1 = 10 + c1 - 'A';
- else if (c1 >= 'a' && c1 <= 'f')
- c1 = 10 + c1 - 'a';
- else break;
-
- if (c2 >= '0' && c2 <= '9')
- c2 = c2 - '0';
- else if (c2 >= 'A' && c2 <= 'F')
- c2 = 10 + c2 - 'A';
- else if (c2 >= 'a' && c2 <= 'f')
- c2 = 10 + c2 - 'a';
- else break;
-
- c = (c1<<4) | c2;
- }
-
- line[i++] = c;
-
- if (i == maxsize) break;
- }
-
- /* now unescape the line */
-
-
- line[i] = 0;
- return 1;
-}
-
-
-/***************************************************************************
- load all the variables passed to the CGI program
- ***************************************************************************/
-void cgi_load_variables(void)
-{
- static pstring line;
- char *p;
- int len;
-
- if (!(p=getenv("CONTENT_LENGTH"))) return;
-
- len = atoi(p);
-
- if (len <= 0) return;
-
-
-
- while (len && grab_line(&len, line, sizeof(line)-1)) {
- p = strchr(line,'=');
- if (!p) continue;
-
- *p = 0;
-
- variables[num_variables].name = strdup(line);
- variables[num_variables].value = strdup(p+1);
-
- if (!variables[num_variables].name ||
- !variables[num_variables].value)
- continue;
-
-#if 0
- printf("%s=%s \n",
- variables[num_variables].name,
- variables[num_variables].value);
-#endif
-
- num_variables++;
- if (num_variables == MAX_VARIABLES) break;
- }
-
- fclose(stdin);
-}
-
-
-/***************************************************************************
- find a variable passed via CGI
- ***************************************************************************/
-char *cgi_variable(char *name)
-{
- int i;
-
- for (i=0;i= LANMAN1
- - fixed TimeDiff() for machines without TIMEZONE or TIMELOCAL
- (thanks to Vesa S{rkel{ )
- - added SYSV defs to AIX and HPUX to fix "memory" problem
- (actually a signal problem).
- - added version to client banner in log file
- - Ultrix patches from Vesa S{rkel{
- - added ! command to client for executing shell commands
- - fixed ERRnofids bug in server
- - fixed name_equal bug
- (thanks to cjkiick@flinx.b11.ingr.com (Chris Kiick))
- - wrapped gethostbyname() with Get_Hostbyname() to prevent
- case sensitive problems on name lookups
- - limit printer tmp filename to 14 chars
- (from Paul Thomas Mahoney )
- - added ability to understand 64 bit file times
- (thanks to davidb@ndl.co.uk (David Boreham))
- - added Gwt_Pwnam() wrapper to cover server case-sensitivity
- problems (suggestion from J.M.OConnor@massey.ac.nz (John O'Connor))
- - changed the setuid() calls to try and work for more systems
- without breaking the ones it currently works for
- - added version number to usage()
- (suggestion from peter@prospect.anprod.csiro.au)
- - added "security=" option for share or user level security
- - allowed multiple usernames in "user=" field
- - changed display method for recursive dorectory listings
- - switched client to use long filenames where supported
- - added speed reporting to client transfers
- - several NT fixes to server from jra@vantive.com (Jeremy Allison)
- - ISC fixes from ptm@xact.demon.co.uk (Paul Mahoney)
- - fix to README from grif@cs.ucr.edu (Michael A. Griffith)
- - default netmask and broadcast from Ian A Young
- - changed default of is_locked() on fcntl() error.
- - fixed bug in read_with_timeout() that could cause a runaway
- smbd process.
- - fixed findnext bug for long filenames in client
- - changed default protocol level to LANMAN1
- - change default reported security level to SHARE.
- - changed password_ok() so that if pwdauth() fails it tries
- with standard crypt.
- - added "translate" command to the client to do CR/LF translation
- for printing, and add a form feed at the end.
- (thanks to mh2620@sarek.sbc.com (Mark A. Horstman ) )
- - added "locking=yes/no" toggle for each service
- - SCO unix patches from Heinz Mauelshagen (mauelsha@ez.da.telekom.de)
-
-1.6.10: 7/5/94
- - fixed important bug in readbraw/writebraw
- - added -A option to client
- - fixed delete bug on long filenames (untested). Thanks to
- Stefan Wessels
- - neatened up the byte swapping code
-
-1.6.11: 3/6/94
- - fixed bug in client in receive_trans2_response() that caused
- some strange behaviour with LANMAN2.
- - fixed some offset/alignment problems with lockingX (thanks to
- Jeremy Allison)
- - allow locking on O_RDONLY files. Thanks to Martin N Dey
- - fixed del bug in client thanks to paulzn@olivetti.nl (Paul van der Zwan)
- - fixed multiple user= bug thanks to MDGrosen@spectron.COM (Mark Grosen)
- - added translate ability for all files. Thanks to mh2620@sarek.sbc.com (Mark A. Horstman )
- - mask out negative lock offsets. Thanks to bgm@atml.co.uk (Barry G Merrick)
- - more attempts to get the structure alignment better for some machines
- - cleaned up the machine dependencies a little
- - ISC fixes from Paul Thomas Mahoney
- - enabled printing with a SMBclose and SMBwrite for NT
- thanks to jkf@frisky.Franz.COM (Sean Foderaro)
- - SGI changes from Michael Chua
- - CLIX patches from cjkiick@ingr.com
- - NEXT2 and NEXT3_0 patches from Brad Greer (brad@cac.washington.edu)
- - BSDI changes from tomh@metrics.com (Tom Haapanen)
- - SCO patches from John Owens (john@micros.com)
- - fix psz bug in pcap.c (thanks to Karl Auer)
- - added widelinks option (global and per service). Suggestion from
- Karl Auer. Defaults to True.
- - made locking able to be global or local (default is give by global)
- - added check_name() to dir listings
- - added "packet size" option to globals. default to 32767. This
- "fixes" a WfWg bug (thanks to Karl Auer)
- - fixes for getattrE and setattrE and minor fix in util.c from Jeremy Allison.
- - Karl updated the man pages o be current
- - disabled writebraw and readbraw until a possible bug can be investigated further
-
-1.7.00: 14/7/94
- - added session_users list, to overcome problem of missing usernames in SMBTconX.
- - added term support to the client
- - added "default service"
- - fork for print so user is not root
- - added name mangling to 8.3 (rudimentary)
- - fixed bug in in_group()
- - changed to use gid in place of egid
- - fixed client connection to OS/2 (1.3 + lanman2.2) and long filenames
- - added patches from mcochran@wellfeet.com (Marc Cochran)
- these implement scope ids and fix some udp bugs. It means
- the -L option to nmbd now works.
- - made nmbd respond to incoming port rather than only 137
- - made wide links refuse .. components
- - fixed "dir foo." bug to stop it showing "foo.???"
- - improved name mangling (added stack)
- - added valid FNUM check to most calls
- - fixed important do_put bug in the client
- - added magic scripts to the server
- - re-enabled getwd_cache code
- - added optional agressive password checking
- - removed dptr_closepath from SMBsearch to try and stop "dos for loop"
- bug
- - DGUX patches from ross@augie.insci.com (ross andrus)
- - updated the README and THANKS file.
- - added node status request to -L option of nmbd
- - stripped trailing spaces in mask_match() (thanks to mike hench hench@cae.uwm.edu)
- - added COREPLUS style print queue reporting and "lpq command"
- in globals.
- - cleaned up date handling and fixed byte order dependancy on dates
- in SMBgetattrE.
- - cleaned up the password handling and added "password level" with
- the possability of checking all case combinations up to N upper
- case chars.
- - changed to use recvfrom only on udp ports (fixed read raw!)
- - added TCB password support for SCO (thanks to lance@fox.com)
- - updated README, THANKS and announce files.
- - fixed timezone reporting to be signed (thanks to noses@oink.rhein.de)
- - disabled max packet as it could cause problems with WfWg (no longer
- needed now readraw is "fixed")
- - changed from creat() to open() in mktemp and mknew.
- - changed umask handling
- - sped up nmbd by making it cache names
- - changed idle timeout on nmbd to 2 mins
- - Netbsd changes from noses@oink.rhein.de
- - released alpha2
- - added name timeout to nmbd
- - changed bind port retry in nmbd
- - added Limitations sections to README
- - fixed two . in is_83()
- - fixed compilations warnings in util.c (thanks to njw@cpsg.com.au)
- - made [homes] honour multiple user list
- - fixed mask match bug introduced in alpha1
- - added "mangled stack" option for stack size
- - added mangled stack promotion
- - released alpha3
- - netbsd-1.0 fix for statfs().
- - added null_string to util.c to reduce memory usage
- - changed the way directory structures are put together
- - added smbrun for system() requests
- - changed maxmux to 0 in hope of avoiding mpx commands problem
- - fixed zero response length for session keepalives
- - removed called name from session users list
- - added F_RDLCK support to try and handle locks on readonly files
- - made directory creation honour the lowercase flag in client (thanks
- to charlie@edina.demon.co.uk)
- - made checksum for mangling independant of extension if extension is
- lowercase
- - added ability to rename files with different extension, preserving
- root name
- - released alpha4
- - better command line error checking in client
- - changed all debug statements to new format
- - fixed delete error code reporting
- - released alpha5
- - added mangled name support to wildcard delete in server
- - fixed mask bug in SMBsearch
- - cleaned up prototypes
- - released alpha6
- - fixed important bug in session_setup which made WfWg freeze
- (maxmux was 0 - this bug was introduced in alpha4)
- - released alpha7
- - two printing bug fixes thanks to bgm@atml.co.uk (Barry G Merrick)
- - uid fix to smbrun (thanks to larry@witch.mitra.com)
- - man page updates from Karl Auer
- - FAQ file from Karl Auer
- - released alpha8
- - fixed read-only flag in dos_mode() for non writeable services
- - fixed error code reporting in open() and openX().
- - minor secureware fix from (thanks to lance@fox.com)
- - released alpha9
- - casting cleanups for memcpy().
- - cleaned up error code names to be more consistant
-
-1.7.01: 17/7/94
- - minor man page fix from baeder@cadence.com (Scott Baeder)
- - changed usage() error message in client
- - made nmbd not exit if can't register own name
- - made nmbd only register if running as a daemon
- - fixed stdout problem in smbrun by closing stdin/stdout/stderr
- - minor fix to lmhosts parsing
-
-
-1.7.02: 20/7/94
- - made nmbd not call get_broadcast if both -B and -N are used (thanks
- to Chris Woodrow )
- - disabled GETWD_CACHE again
- - fixed INCLUDES list in Makefile to add version.h (thanks to
- jimw@PE-Nelson.COM (Jim Watt))
- - made checkname do a become user if it hasn't already done so.
- - added consistancy check to become_user().
- - removed mask extension expansion from SMBsearch
- - small change to chkpth
- - fix to snum select for lpq status (thanks to Rafi Sadowsky
- rafi@tavor.openu.ac.il)
- - changed daemon to is_daemon for NetBSD (thanks to noses@oink.rhein.de)
- - removed STAFS3 stuff for NETBSD_1_0
-
-
-1.7.03: 29/7/94
- - updated docs for new distribution structure
- - made getatr return 0 size for directories (thanks to Bernd Esser
- esser@pib1.physik.uni-bonn.de)
- - added valid dos filename checks from Stefan Wessels
- (swessels@cs.up.ac.za)
- - added trimming of . in hostnames to -S mode of nmbd
- - removed become_user() and OPEN_CNUM calls. Now make them
- in switch_message instead which simplifies a lot of code.
- - added GETFNUM macro to make chain_fnum more consistant and
- reliable.
- - added flags to protocol structures to simplify CAN_WRITE and AS_USER
- checking
- - added getwd cache boolean option to globals
- - added fclose() to lpq status routine thanks to
- dgb900@durras.anu.edu.au (David Baldwin)
- - added "only user" option, to limit connection usernames to those
- in the user= line
- - changed to badpath from badfile in chkpath despite specs (following
- what WfWg does). This fixes "file not found" error in copy command.
- Thanks to rwa@aber.ac.uk for pointing out the bug
- - changes for apollo from Stephen C. Steel
- - more changes for Apollo from jmi@csd.cri.dk (John Mills)
- - released alpha release
- - added FTRUNCATE_CAN_EXTEND=0 as default to fix problem with word6.
- Possibly not needed on many OSes? Thanks to Charlie Hussey
- charlie@edina.demon.co.uk
- - started adding max connections code
- - much improved group handling contributed by
- Ian Heath (ih@ecs.soton.ac.uk)
-
-1.7.04: 29/7/94
- - fixed one line bug in SMBopenX that got error code wrong.
-
-1.7.05: 2/8/94
- - added UNIXERROR() macro to get error code from unix errno.
- - fixed lpq status for MSTCPB3
- - added @ option for user= line to lookup groups in group file
- - added become_user optimisation and process timeout (thanks to
- Jeanette Pauline Middelink (middelin@calvin.iaf.nl)
- - added malloc optimisation in readbraw
- - released alpha
- - patches for OSF1 enhanced security from Udo Linauer
- - made level 2 a more useful debug level (less guff)
- - added "max connections" and "lock dir" options to allow
- limiting of the number of connections to a service at one time.
- - released alpha2
- - updated man pages
- - released alpha3
- - added read prediction code for better read performance
- - released alpha4
- - minor tuning to receive_smb()
- - changed the order of mangled stack checking
- - bug fix in read_predict().
- - released alpha5
- - minor search optimisation
- - fixed keep alive bug in writebraw and in readbraw in the client
- - released alpha6
- - disabled writeraw by default pending a bug fix
- - added profiling code (off by default)
- - minor delete tuning
-
-
-1.7.06: 4/8/94
- - OSF1 crypt fix thanks to Udo Linauer
- - ifdef'd EDQUOT in case you don't have it (thanks to Paul Blackman )
- - tidied up UNIXERROR stuff to work on more systems.
- - made Makefile more sophisticated and added "make revert"
-
-1.7.07: 4/8/94
- - fixed one line fatal bug in receive_smb. Thanks to bruce@pixar.com
-
-1.7.08: 2/9/94
- - initgroups call for SCO from lance@fox.com
- - code cleanups from cap@isac.hces.com (Simon Casady)
- - use full pathname in print command construction
- - ISC includes fix from Martin Tomes
- - added GID_TYPE define to cope with ultrix. Thanks to
- brad@cac.washington.edu
- - added umask call to main in server
- - fixed several minor problems with the max connections
- code. Thanks to lehmann@klizix.mpi-stuttgart.mpg.de (Arno Lehmann).
- - fixed filetime in writeclose. Thanks to Andreas Bahrdt
- <100321.2431@compuserve.com>
- - df fix for large disks from Andreas Bahrdt
- - getpwanam support from horn@mickey.jsc.nasa.gov
- - clean name change from Bernd Esser
-
- - released alpha1
- - more locking changes to fix Excel problem
- - released alpha3
- - another minor locking change
- - smarter masking in the locking code. Excel now apparently works.
- - minor FAQ updates
- - changed max connections refusal error to access denied.
- - added queue command to client to show the print queue
- - changed some print queue reporting stuff
-
-1.8.0: 14/10/94
- - added international chars to valid_dos_char(). Thanks
- to Daniel.Grandjean@dgr.epfl.ch
- - volume label fix
- - released alpha1
- - important off by 4 fix in the server
- - readbraw size adaption in the client
- - released alpha2
- - wait3 cast for NeXt fixed. Thanks to dbrandon@politics.tamu.edu.
- - man page fix for max xmit. Thanks to mmoore@wexford (Mike Moore)
- - is_8_3() fixes from Jochen Roderburg
- - list_match() fix from jkf@soton.ac.uk
- - statfs3 fix for BSDI from dan@supra.com
- - changed file open/close/read in server in preparation for mmap()
- based IO.
- - added mmap() support for reading files in the server. Optional
- at compile time. Thanks to suggestion from Roger Binns
- - mmap bug fixes
- - added __SAMBA__ name in nmbd
- - major changes for support of lanman2 and long filenames from
- Jeremy Allison (jeremy@netcom.com)
- - lseek optimisation. Thanks to Linus Torvalds.
- - released alpha4
- - date patches for lanman2 from Jeremy Allison
- - added protocol aliases to handle WfWg (untested)
- - allow for zero params or data in reply_trans2
- - small lanman2 patches from jeremy
- - more prototype additions for clean compilation
- - postscript patches from tim@fsg.com
- - more lanman2 patches from Jeremy
- - added null ioctl support
- - kanji patches from fujita@ainix.isac.co.jp
- - released alpha6
- - disallowed null password access (thanks to Birger Kraegelin krg@iitb.fhg.de)
- - Makefile fix for ultrix from andrew@d2bsys.demon.co.uk (Andrew Stirling)
- - added per-service mangled names
- - totally re-vamped loadparm.c
- - added "mangling char" parameter
- - released alpha7
- - added "default case = lower|upper" service option
- - change mangling char to a service parameter
- - ultrix enhanced security patch from steven@gopher.dosli.govt.nz
- - more changes to loadparm.c
- - printer name always set in [printers]
- - string_free() fix thanks to jef_iwaniw@pts.mot.com
- - changed group handling to be faster and work for large numbers
- of groups
- - added dynamic gid_t type determination
- - released alpha8
- - fixed become_user() problem for services with invalid
- directories
- - added "invalid users" list on per service basis
- - fixed pointer problems in alpha8 (thanks to murnaghant@a1uproar.yuppy.rdgmts.MTS.dec.com)
- - fixed some date setting problems
- - trans2 fixes from jeremy to stop infinite directory listings of
- long filenames
- - "standard input" lpq patch from root@tlspu.demon.co.uk (Adrian Hungate)
- - changed password checking to check session list and validated ids
- before user list
- - split off password functions into password.c
- - added hosts equiv and rhosts code (thanks to Tim Murnaghan )
- - released alpha11
- - added "newer" command to the client
- - attempt at aix trapdoor uid workaround
- - released alpha12
- - minor trans2 bugfix
- - added ufc crypt (fast crypt) support. Thanks to suggestion from
- forrest d whitcher
- - socket() fix for getting bcast and netmask thanks to
- Brian.Onn@Canada.Sun.COM
- - added beginnings of IPC and named pipe support in the server
- - changed file structure a bit, creating reply.c
- - finished print queue support for lanman1
- - changed default protocol to LANMAN2
- - released alpha13
- - logged IPC connects at a higher debug level
- - added netgroup support to hosts equiv search
- - disallowed root access though hosts.equiv (thanks to Colin.Dean@Smallworld.co.uk)
- - kanji and password handling fixes from fujita@ainix.isac.co.jp
- - several bug fixes for lanman and other things from
- esser@pib1.physik.uni-bonn.de (Bernd Esser)
- - updated man pages, README and announce files.
- - released 1.8.00alpha1
- - reply_close() time change fix from Andreas Bahrdt <100321.2431@compuserve.com>
- - added valid users list to compliment invalid users list.
- - aix fixes from tomc@osi.curtin.edu.au (Tom Crawley)
- - changed testparm output format
- - support for getting time from the server (nearly untested)
- - fixed device type error for wild device ????
- - fixed groups problem when in 0 groups
- - more IPC fixups
- - added support for "net view \\server" command to list
- available services (like browsing)
- - released 1.8.00alpha2
- - changed port choice for nmbd -L
- - added -L option to client to view share list on a host
- - bug fixes for NetShareEnum code
- - added "server string" option
- - changed default print file name to include remote machine name.
- - added hooks for browsing in nmbd
- - added browsing to nmbd
- - freebsd fixed from Steve Sims SimsS@Infi.Net
- - got rid of tell()
- - added subnet browsing with the S option in lmhosts
- - made smbd prime nmbd with a 1 byte dgram
- - added REUSADDR to open_socket_in() thanks to peter@ifm.liu.se
-
-
-1.8.01: 18/10/94
-
- - auto add group "LANGROUP" if no group specified in nmbd
- - made nmbd more responsive at startup
- - lots of cleanups and consistancy checks
- - added -C option to nmbd to set "machine comment".
- - fixed postscript option
- - force print_file in print_open()
- - restructured the browsing a little
- - casesignames fix for lanman-dos
- - auto-load home directory from session setup
- - changed to StrnCpy() for safety
- - fixed "out of file descriptors" bug in the client (a WfWg bug?)
-
-
-1.8.02: 22/10/94
- - fixed uppercase username problem
- - added "hide dot files" option
- - changed auto debug log in nmbd
- - added LMHOSTS to Makefile
- - added M flag in lmhosts to specify own netbios name
- - added "load printers" option to auto-load all printers
- - substitution of %p in lpq command
- - substitution of %h and %v in server string and -C option of
- nmbd
- - string substitions substitute all occurances of a pattern
- - added casesignames global option
- - fix for man pages thanks to David Gardiner
- - changed debug options a bit
- - added default for lpq command and lpr command
- - changed default shell path to /bin/sh
- - forced lpq under api to run as root - should speed things up
- - added "group" option to force group of a connection
- - added "read list" and "write list" options
- - added max mux option - seems to fix NT browsing?
- - added "mangled map" option thanks to
- Martin.Tomes@uk.co.eurotherm.controls
- - separated mangling functions into mangle.c
- - allowed all dos chars in mangled names
- - apollo changes from Helmut Buchsbaum
- - password changing code from Bob Nance
- it doesn't quite work yet, but it's a start (disabled by default)
-
-
-1.8.03: 25/10/94
- - made auto loaded services browsable as per default service
- so you can hide homes but keep home directories.
- - changed check_name() to handle "direct to network" printing
- - auto 3 minute deadtime if all connections are closed. This
- prevents restart when polling the print queue.
- - fix for newer command in client from Rich-Hoesly@uai.com
- - changed connection recording method
- - added the program smbstatus
- - changed timeout mechanism
- - "null passwords" option from Pim Zandbergen
- - made new files with casesignames=False set their case to the default
- case.
- - fixed problem of uppercasing first letter of printers in printcap
- - debug level fixes in trans2 from jimw@PE-Nelson.COM (Jim Watt)
- - made null printer default to lp
-
-1.8.04: 27/10/94
- - added OS2.txt from riiber@oslonett.no
- - another "auto services" fix. A silly strtok() bug :-(
- - fixed the status locking and max connections (broken in 1.8.03)
- - released alpha1
- - added gets_slash so lines can be continued in smb.conf and
- lmhosts
- - browse list bugfix
- - default to "load printers=yes"
- - rewrote pcap.c
- - intergraph bugfix from tarjeij@ulrik.uio.no
- - changed properties flags in nmbd (to fix NT print browsing)
- - allowed very long lines in printcap parsing.
-
-1.8.05: 28/10/94
- - lanman2 fix from Jeremy
-
-1.9.00: 22/1/95
- - only add home if not already there.
- - added ulogoffX support
- - PTR_DIFF() cleanups
- - fixed a bug that caused STATUS..LCK to grow very large
- - changed mangling to handle names ending in . a little better
- - added "strip dot" option
- - SGI and setgroups() fix from bill@sg25.npt.nuwc.navy.mil
- - fixed password preservation in password_ok() (again?)
- - unink fix from emer@vssad.enet.dec.com (Joel S. Emer)
- - changed username part of spool filename to max 10 chars (from 6)
- - magic script fix from beverly@datacube.com (Beverly Brown)
- - reply_special() fix from Peter Brouwer
- - stopped nmbd from listening on 138. It didn't seem to help much.
- - clix fixes from ttj@sknsws61.sjo.statkart.no
- - fixed select behaviour under Linux
- - man page fix from Robin Cutshaw
- - ISC block size fix from ralf@rbsoft.sdata.de (Ralf Beck)
- - ISC fixes from Martin.Tomes@controls.eurotherm.co.uk
- - attrib bit fix in smbclient (pointed out by Rich-Hoesly@uai.com)
- - japanese extensions from fujita@ainix.isac.co.jp (Takashi
- Fujita) and ouki@gssm.otuska.tsukuba.ac.jp.
- - SCO patches from Stephen.Rothwell@pd.necisa.oz.au
- - changed the system commands to redirect stderr
- - changed default printername to service name for all print ops
- - added ability to delete print queue entries
- - added warning if you try to print without -P in smbclient
- - INTERACTIVE patches from cardinal@settimo.italtel.it
- - patch to handle spaces in group names from GJC@vax1.village.com
- (GEORGE J. CARRETTE)
- - lockingX fix from stefank@esi.COM.AU (Stefan Kjellberg)
- - some fairly radical changes to filename handling. We can now
- handle mixed case filenames properly
- - released alpha2
- - added sysv printing support and improved bsd support
- - changed the user that does print queues and lprm jobs
- - return code support in the client from doylen@nbslib.isc-br.com (Doyle Nickless)
- - added "strict locking" option. Defaults to no.
-
- - added -I switch to nmbd
- - fixed DEV bug thanks to Dirk.DeWachter@rug.ac.be
- - use pw_encrypt() for shadow passords in Linux (from begemot@begemot.iko.kharkov.ua (Dmitry Gorodchanin))
- - disabled read prediction by default
- - added varient handling code to ipc.c for printQ and printDel.
- - released alpha5
- - AUX patches from root@dolphin.csudh.edu
- - struct timeval fix from gkb1@york.ac.uk
- - patches to merge ISC and INTERACTIVE from pim@cti-software.nl
- - changed to "printing ="
- - fixed problem with long print queues.
- - fixed node status request in nmbd to go to non bcast
- - made default path in services /tmp if not specified
- - added %u in passwd program
- - fixed up the password changing code for Linux
- - no guest sess setup when user level security
- - changed timeouts to kill dirptrs so cdroms can be unmounted
- - added auto-reload of smb.conf if changed
- - added SIGHUP to reload the config files
- - added -M option to nmbd to search for a master browser
- - added support for continue bit in trans2findnext
- - changed to dynamic strings in some more structures
- - changed default deadtime to 30 minutes
- - cleaned up the memory swapping code a bit
- - updated the man pages somewhat
- - added %m and %u in the "path=" of services
- - released alpha6
- - simple testing and fixups for solaris, sunos, aix, ultrix and
- osf/1 (this is all I have access to).
- - fixed chdir bug
- - added hashing to cnum selection
- - released alpha7
- - fixed printing bug
- - reduced chance of "hung" smbd with dead client
- - fixed do_match() bug (recently introduced)
- - released alpha8
- - nameserver fix from W.J.M.vGeest@et.tudelft.nl (W.J.M. van Geest)
- - rewrote readbraw to try and overlap reads with writes
- - client optimisations
- - rewrote getwd cache and enabled it by default
- - added partial smb packet reads (hopefully faster writes)
- - added log file and log level options (with subs)
- - added "read size" option
- - tried setting some more socket options
- - can use subs in "config file=" and will auto-reload
- - added "include" options, with some subs
- - finally got print manager working with NT
- - auto-respond in nmbd to non-broadcast (auto WINS server, no -A
- needed)
- - released alpha10
- - auto-delet unused services when reloading
- - fixed auto-deletion
- - fixed long names in printing
- - fixed double loading of services file
- - added printer file name support
- - reformatted man pages for better www conversion
- - renamed to 1.9.00.
- - added support for RNetServerGetInfo and NetWkstaGetInfo API's
- - updated the docs a bit
- - released alpha1
- - added -M -
- - changed nmbd announce interval to 10 mins in outgoing packets
- - hopefully fixed idle timeout reconnects
- - strupper all command lines in nmbd
- - added %a substitution for "remote architecture"
- - added "Samba" protocol (same as lanman2)
- - added "security = SERVER"
- - released alpha2
- - lowercase password fix
- - fixed connect path length bug (thanks to JOHN YTSENG
- )
- - added subs on "password server".
- - fixed printing filename bug from smbclient
- - disk quotas and hpux printing support from Dirk.DeWachter@rug.ac.be
- - Makefile patches from pappinm@ayr_srv2.nth.dpi.qld.gov.au
- - AFS patches from Mike Allard (mgrmja@nextwork.rose-hulman.edu)
- - fixed grp name = server name problem
- - man page updates from Charlie Brady (charlieb@budge.apana.org.au)
- - fixed file search bug by adding "finished" flag
- - added "max log size". Suggestion from Mark Hastings
- - released alpha3
- - changed the read/write routines to handle partial read/writes
- - released alpha4
- - changed "guest account" to per-service
- - changed so "guest ok" allows access to the guest account,
- not the "user=" line
- - changed default readsize to 2048
- - try bind to 137 in nmbd if possible
- - added server lookup to -L option in smbclient (gets list of servers)
- - added -M switch to smbclient for sending winpopup messages
- - released alpha5
- - FAQ updates from Paul Blackman ictinus@lake.canberra.edu.au
-
-1.9.01: 23/1/95
- - changed comment in print Q info to service rather than server comment
- - fixed smbclient -L to NT when in user level security mode
- - hopefully finally fixed NT print manager problems
- - added informative messages during smbclient -M
- - added node status replies to nmbd
- - changed the lock offset fixup calculation to be more friendly
- to dumb lockd daemons.
- - added sigbus and sigsegv handlers to catch any silly errors and
- print a message
- - added message receipt to smbd and "message command =" option
-
-1.9.02: 25/1/95
- - added argv/argc mangling for people who start the server the
- wrong way.
- - some man page updates
- - added "revalidate" option
- - added hosts allow/deny access check to messaging access
- - added timeouts in the client
- - added check for existance of smbrun binary
- - man page updates from Colin.Dean@Smallworld.co.uk
- - freebsd patches from dfr@render.com
- - added mask sanity check in SMBsearch
- - added more useful substitutions (%S, %P, %I and %T)
- - added "exec =" option to execute commands on each connection
-
-1.9.03: 13/3/95
- - added "socket options" option
- - close base fd's (0,1 and 2)
- - use dup(0) for inetd operation
- - better detection of is_daemon
- - hopefully finally fixed silly put bug that gave the wrong
- date on files.
- - fixed segv in readbraw bug
- - added improved checing for invalid (or null) print file name
- - several patches from ad@papyrus.hamburg.com (Andreas Degert)
- - fixed slow logout bug in smbclient
- - fixed automounter problems
- - added subs on lock dir
- - BSDI patch from John.Terpstra@Aquasoft.com.au
- - added separate nmb and smb logfile entries in the Makefile
- - fixed return code error in open calls
- - added simple status display of printer in lpq parsing
- - rewrote the directory handling to avoid seekdir (added dir.c)
- - added uid=65535 check (thanks to grant@gear.torque.net)
- - enhanced transfer_file() to add header (used in readbraw)
- - reply_special bugfix from ferret@pc8871.seqeb.gov.au
- - added HAVE_PATHCONF
- - RiscIX patches from Jim Barry and
- Charles Gay-Jones
- - CLIX patches from ttj@sknsws61.sjo.statkart.no
- - fixed aix lpq parser from kvintus@acd.com
- - added substitutions to "include="
- - M88K_S3 patches from tonyb@plaza.ds.adp.com (Tony D. Birnseth)
- - fixed mangled stack problem
- - added code to handle broken readdir() setups on solaris
- - initgroups() fix from jarit@to.icl.fi
- - dgux dfree fix from listwork@cloud9.net
- - dnix support from Peter Olsson
- - getgrgid() patch from tpg@bailey.com (Tom Gall)
- - Makefile patch from obrien@Sea.Legent.com (David O'Brien)
- - password changing fixes from Dirk.DeWachter@rug.ac.be
- - minor man page updates
- - tried to enhance the read prediction code a little bit
-
-1.9.04: 16/3/95
- - a bit better handling of global include lists
- - fixed GSTRING bug in loadparm.c (affected "socket options =")
- - fixed broken lpq parsing code (recent bug).
- Thanks to Dirk.DeWachter@rug.ac.be
-
-1.9.05: 20/3/95
- - improved mget in client to take multiple arguments and default
- to *.*
- - socket option fixes for both nmbd and smbd
- - changed the byteorder handling scheme to be more portable (and
- faster)
- - lint cleanups from kast@kcs.planet.net (Robert Kast)
- - added crude segv, sigbus and sighup recovery to nmbd
- - rewrote lanman2_match to be closer to NT and WfWg behaviour
- - Cray support from velo@sesun3.epfl.ch (Martin Ouwehand)
- - "admin users" patch from Tim Leamy
- - released alpha1
- - added samba.7 man page
- - no chdir when doing non AS_USER protocols
- - become_guest() returns true in trapdoor uid system
- - added more sophisticated segv/sigbus reporting (Linux only)
- - released alpha2
- - minor code cleanups (output of -Wall)
- - smbprint fix from James Dryfoos
- - improved testparm a little
- - updated INSTALL.txt a little
-
-
-1.9.06: 21/3/95
- - added %S substitution to users, valid users and invalid
- users. This is useful for [homes].
- - split off printing routines into printing.c and more dir
- commands into dir.c
- - postexec patch from jpm@gin.Mens.DE (Jan-Piet Mens)
- - smbstatus updates from jpm@gin.Mens.DE (Jan-Piet Mens)
- - reload sighup after use
- - fixed name ptr offset bug
- - added %f in print commands
- - fixed byte ordering in nmbd which caused browsing to fail in
- 1.9.05
-
-1.9.07: 22/3/95
- - important directory listing fix
- - allowed path= in [homes] section
- - printer status patches from Dirk.DeWachter@rug.ac.be
-
-1.9.08: 24/3/95
- - fixed . and .. in root dir for lanman2
- - better default comment in [homes]
- - added time stamping to directory entries
- - check directory access at connection time
- - rlimit code from loebach@homer.atria.com (Thomas M. Loebach)
- - fixed home dir default comment
- - totally rewrote dptr handling to overcome a persistant bug
- - added [globals] as well as [global]
-
-1.9.09: 30/3/95
- - fixed static string bug in nmbd
- - better null password handling
- - split CFLAGS in Makefile
- - fixed typo in smbclient messaging
- - made home dir not inherit path from [global]
- - standard input printing patch from xiao@ic.ac.uk
- - added O_CREAT to all print opens (bug in Win95)
- - use /proc for process_exists under Linux and solaris
- - fixed another segv problem in readbraw
- - fixed volume label problem
- - lots of changes to try and support the NT1 protocol
- - released alpha1
- - fixed session setup bug with NT in NT1 protocol
- - released alpha2
- - fixed "get" bug in smbclient that affected NT3.5
- - added SO_KEEPALIVE as a default socket option in smbd
- - changed some error codes to match those that NT 3.5 produces
- - updated trans2 with some new calls for Win95 and WinNT (better
- long file support)
- - released alpha3
- - fixed "nmbd -D -b" timeouts
- - added IS_LONG_NAME flag to getattr in NT1
- - added the NT qfileinfo trans2 commands
- - merged qpathinfo with qfileinfo
- - changed idling technique to try and be more friendly to
- clients
- - merged setfileinfo with setpathinfo and updated them with the NT fns
- - improved read prediction a lot
- - added read prediction to readbraw
- - improved fault reporting (last packet dump)
-
-1.9.10: 30/3/95
- - fixed read prediction+readbraw bug for read/write files
-
-1.9.11: 9/4/95
- - fixed trans2 qpathinfo bug
- - fixed bug with % in service name when doing print queue requests
- - default readsize now 16K
- - minor read prediction changes
- - fixed status initialisation in print queue reporting
- - fixed const compile problem for hpux
- - minor SMBread fix from Volker Lendecke
- - removed space after -P in print commands (for fussy systems)
- - disabled level2 of setfilepathinfo
- - changed to a single read dir model, saving all dir names in
- the Dir structure
- - disabled NT protocols in the client due to reported problems
- - fixed QUERY_FS_VOLUME_INFO which caused Win95 to hang on drive
- properties
- - minor lseek bug fix
- - fixed up keepalives
- - new timezone handling code (hopefully better!)
- from steve@qv3pluto.LeidenUniv.nl
- - BSDI interface patch from jrb@csi.compuserve.com
- - gettimeofday changes from Roger Binns
- - added smbrun option
- - added "root preexec" and "root postexec" options
-
-1.9.12: 12/4/95
- - hopefully fixed some recently introduced NT problems
- - fixed a unlink error code problem
- - minor testparm fix
- - fixed silly error messages about comments in config files
- - added "valid chars" option for other languages
-
-1.9.13: 28/4/95
- - patches from David O'Brien (obrien@Sea.Legent.com) improving the
- netgroup suport, and adding the "map archive" option, as well as
- other minor cleanups.
- - tried to add info level 3 and 4 support for OS/2
- - default deadtime set to 0 as in docs
- - cleaned up the trans2 code a little
- - cleaned up the Makefile a little
- - added charset.c and charset.h
- - expanded "valid chars" option to handle case mapping
- - lots of changes to try and get timezones right
- - released alpha1
- - win95 fixups
- - released alpha2
- - added %H substitution (gives home directory)
- - nameserv.c cleanups and minor bug fixes
- - redid the browse hook logic
- - fixed daylight saving time offset for logfile messages
- - added name cacheing to nmbd
- - added send counts to node status in nmbd
- - added STRICT_TIMEZONES compile time option (very computationally
- expensive)
- - removed the partial read code
- - cleaned up the permission checking a lot
- - added share modes (DENY_READ, DENY_WRITE, DENY_ALL, DENY_NONE,
- DENY_FCB and DENY_DOS)
- - added "share modes" option
- - cleaned up the file open calls
- - released alpha4
- - fixed important one line bug in open_file()
- - trans2 client fix from lendecke@namu01.gwdg.de
- - netgroup patche from David O'Brien (obrien@Sea.Legent.com)
- - case sensitive fix from lenneis@statrix2.wu-wien.ac.at (Joerg Lenneis)
- - got long filenames working from Win95 dos prompt
- - added "workgroup=" option
- - added "username map" option including multiple maps, group maps etc
- - fixed password server for NT1 protocol and made it more robust
- - changed unix_mode() to add IWUSR to read-only directories. This
- is much closer to what clients expect.
- - added preservation of unused permission bits when a chmod() is
- called from a client.
- - made static those fns that could be
- - fixed typo in access.c (thanks to Andrew J Cole
- )
- - added %d substitution for process id
- (thanks to lenneis@statrix2.wu-wien.ac.at (Joerg Lenneis))
- - changed share error code to ERRbadshare
- - added locked files list to smbstatus if share modes is enabled
- - changed DENY_DOS to allow read by other tasks
- - added shared_pending checks to server
- - preserverd all possible permission bits during a chmod, and
- fixed a trans2 chmod bug
- - open /dev/null to use up first 3 fds, in an attempt to stop rogue
- library routines from causing havoc
- - fixed NT username problem when in server security
- - added "force user" and "force group" options
- - cleaned up some of the IPC calls a bit
- - added writeraw to the client and cleaned up write raw in the server
- - osf1 big-crypt bugfix from Udo Linauer
- - hopefully better disk-full checking
- - next uid bugfix from patrick@graphics.cornell.edu
- - changed share modes so lock directory doesn't need to be world
- writeable
- - enabled write-raw by default
- - added server_info() in client
- - added level checks in some ipc calls
- - added defines for the important timeouts in local.h
- - added print queue deletion to smbclient (untested)
- - removed the sysconf() calls
- - optimised writebraw a bit
- - fixed some file deletion problems
- - added total_data check for extended attribs in trans2 (for OS/2)
- - fixed broadcast reply bug in nmbd
- - added careful core dumping code
- - added faster password level searches (suggestion
- by lydick@cvpsun104.csc.ti.com (Dan Lydick))
-
-
-1.9.14: 22/9/95
- - fixed up level 3 and 4 trans2 requests for OS/2
- - minor optimisations in a few places
- - cleaned up the closing of low fds a bit
- - added SO_REUSEADDR to socket as a daemon
- - override aDIR bit for directories in dos_chmod()
- - SGI5 fixes from ymd@biosym.com (Yuri Diomin)
- - bsize sanity check and removed sunos force to 1k
- - force the create mode to be at least 0700
- - SCO and freebsd include changes from Peter Olsson
-
- - check with FQDN in access.c (thanks to Arne Ansper )
- - default broadcast for dnix from Peter Olsson
- - solaris patches from Ronald Guilmette
- - added EXDEV handling
- - small AFS Makefile patch from mgrlhc@nextwork.rose-hulman.edu
- - hopefully fixed the Win95 dates to work in other than my
- timezone
- - attempted alignment fixups (to speed up memcpy)
- - added some DCE/DFS support (thanks to Jim Doyle )
- - added fix so that root doesn't have special privilages to open
- readonly files for writing (but admin users do). This fixes the MS
- office install problem.
- - fixed trans2 response bug in client
- - got dual names working for NT
- - enabled lock_and_read in NT protocol
- - added %L macro for "local machine"
- - changed dfree reporting to use "sectors per unit"
- - fixed "not enough memory" bug in MS print manger by limiting
- share name length in share enum.
- - "short preserve case" option from Rabin Ezra (rabin@acm.org)
- - added archive option to client
- - changed openX in client to be able to open hidden and system files
- - added "sync always" option
- - rewrote writebmpx and readbmpx
- - added auto string_sub_basic to all loadparm strings
- - lots of nmbd fixups (add registration, refresh etc)
- - released alpha1
- - added smbtar patches from Ricky Poulten (poultenr@logica.co.uk)
- - added a lpq cache and the "lpq cache time" option
- - released alpha 2
- - sun includes fix from Kimmo Suominen
- - change nmbd -L lookup type to workstation from server
- - added min print space option
- - added user and group names to smbstatus (thanks to
- davide.migliavacca@inferentia.it)
- - fixed %f in print command bug (thanks to huver@amgraf.com)
- - added wildcard support to SMBmv
- - misc patches from David Elm (delm@hookup.net)
- - changed default of "share modes" to yes
- - changed default of "status" to yes
- - aix qconfig parsing from Jean-Pierre.Boulard@univ-rennes1.fr
- - more long_date fixups
- - added wildcards to nmbd
- - extensive changes to ipc.c and miscellaneous other changes
- from ad@papyrus.hamburg.com (Andreas Degert). Should especially
- help OS/2 users
- - added name release to nmbd
- - relesed alpha4
- - fixed "SOLARIS" to SUNOS5 in Makefile
- - several minor fixups to get it to compile on aix, osf1, ultrix,
- solaris and sunos
- - released alpha5
- - minor bug fixes and cleanups in ipc.c
- - fixed "only user" bug
- - changed lpq to report guest queue entries as sesssetup_user to
- allow for deletion by windows
- - released alpha6
- - added __SAMBA__ as type 0 in nmbd (was type 20)
- - fixed null print job bug
- - added 8 char warnings to testparm and smbclient
- - changed to 8 char limit for names in pcap.c
- - added linked list of config files to detect all date changes
- that require a reload
- - simplified pcap guessing heuristics
- - added space trimming to the name mapping
- - updated Get_Pwnam to add allow_change field for username mapping
- - fixed MemMove bug (thanks to mass@tanner.com (Massimo
- Sivilotti))
- - released alpha7
- - rewrote MemMove to be a little more efficient
- - ipc va_arg bug fix from djg@tas.com (Dave Gesswein)
- - added check for illegal chars in long filenames
- - fixed name cache init bug in nmbd
- - Convex patches from Victor Balashov
- - timestring() bugfix from staale@spacetec.no
- - changed %H to give path of forced user if one is set
- - added quoting to smbclient to allow spaces in filenames
- - convex and other patches from Ulrich Hahn
-
- - released alpha8
- - fixed rename directory bug
- - nmbd wins fix from Maximilian Errath
- - client and AFS changes + password.c reorganisation + "more" and
- "pwd" commands in client from Todd j. Derr (tjd@smi.med.pitt.edu)
- - fixed several nmbd bugs
- - released alpha9
- - fixed another "cd" bug in smbclient
- - password encryption from Jeremy Allison
- - added "passwd chat" option and chat interpretation code
- - added "smb passwd file" option
- - released alpha10
- - cleaned up chgpasswd.c a little
- - portability changes to the encryption handling code
- - added password encryption to smbclient
- - fixed a share level security encryption bug
- - added "ENCRYPTION.txt" document
- - released alpha11
- - added code to detect a password server loop
- - fixed typo in chkpath in client.c that broken cd (again)
- - LINUX_BIGCRYPT from marsj@ida.liu.se
- - AFS password fixup from jbushey@primenet.com (Jeffrey G. Bushey)
- - iso/8859-1 charcnv patches from Dan.Oscarsson@malmo.trab.se
- - strtok/user_in_list fix from roderich@nodebonn.muc.bmw.de
- - NETGROUP patches from J.W.Schilperoort@research.ptt.nl
- - trim_string patch from J.W.Schilperoort@research.ptt.nl
- - fixed problem with files with no extension getting mixed up
- - ipc bugfix for print job deletion from Rainer Leberle
- - released alpha12
- - pwlen fix in NETGROUP from Andrew J Cole
- - lots of uid and encryption changes from Jeremy Allison. WinDD
- should now work.
- - released alpha13
- - fixed max_xmit bug in client
- - select fix in server (fixed critical drive errors under ISC)
- - released alpha14
- - wildcard fix from Jeremy
- - changes to make IPC code more robust
- - small select loop change to reduce cleaning of share files
- - vtp, altos and mktime patches from Christian A. Lademann
-
- - EEXIST bugfix in server.c
- - changed mangled map to apply in all cases
- - released alpha15
- - fixed fcb open permissions (should mean apps know when a file is
- read only)
- - released alpha16
- - client help formatting fix and docs fix from Peter Jones
-
- - added a directory cache
- - use /proc whenever possible for pid detection
- - TCSANOW fix in getsmbpasswd from roderich@nodebonn.muc.bmw.de
- - fixed default printing mode for sysv systems
- - make client always expand mask
- - more minor IPC fixups
- - pyramid makefile entry from jeffrey@itm.org
- - client fixups for passlen, maxvcs and session redirect from
- Charles Hoch
- - finally fixed important IPC bug (varargs bug with int16)
- - quota patches from Dirk.DeWachter@rug.ac.be
- - print queue cache changes (per service) and print queue priority
- additions from Dirk.DeWachter@rug.ac.be
- - new japanese patches (incomplete) from
- fujita@ainix.isac.co.jp (Takashi Fujita)
- - moved a lot more functions into system.c via wrappers
- - changed a lot of the connection refused error codes to be more
- informative (or at least different)
- - released alpha17
- - changed error return code from cannor chdir() in make_connection
- - fixed realloc() bug in printing.c
- - fixed invalid username bug in sesssetupX
- - released alpha18
- - made default service change name to asked for service (idea
- from Ian McEwan )
- - fixed "guest only" bug
- - sambatar patches from Ricky
- - printing.c patches from Dirk.DeWachter@rug.ac.be
- - rewrote become_user()
- - sunos5 patch from Niels.Baggesen@uni-c.dk
- - more japanese extensions patches from fujita@ainix.isac.co.jp
- - released alpha20
- - added force_user to conn struct
-
-
-1.9.15: 14/11/95
- - removed bcast override from workgroup announce in nmbd
- - aix patch, added NO_SYSMOUNTH, from
- lionel leston <102624.346@compuserve.com>
- - quick fix in lp_string() to try and stop some core dumps
- - added uid cache in connections structure
- to make user level security faster
- - changed dos_mode() to show read-only on read-only shares only if
- user w bit not set
- - added check to stop exit_server() looping
- - core dump fix in string_sub()
- - fix client bug for long dirs in NT1 mode.
- Thanks to Erwin Authried (erwin@ws1.atv.tuwien.ac.at)
- - switched to a safer (but probably slower) readbraw implementation
- - released p1
- - readbraw fix from Stefaan.Eeckels@eunet.lu
- - fixed groups bug when user is in 1 group
- - fixed NT1 dir bug
- - changed default protocol in client to NT1
- - changed trans2 to not return both names in long listing if long
- name is 8.3
- - made stat of "" return RONLY if not writeable drive
- - wrapped strcpy() to stop nulls propogating (hack)
- - made rename and unlink look at share locks on file
- - clitar memory leak fix from jjm@jjm.com
- - added -p option to smbstatus to list smbd processes
- - added rename to the client
- - released p2
- - fixed SMBmv for case where the destination exists
- - man page patch from michal@ellpspace.math.ualberta.ca (Michal Jaegermann)
- - once again redid the time handling, but finally explained what
- is going on, this is written up in TIME.txt. The "kludge-GMT" used
- by NT is a bastard and led to a lot of the confusion
- - kanji patch from fujita@ainix.isac.co.jp (Takashi Fujita)
- - is08859-1 patches from eauth@mail.cso.co.at
- - starting rewriting nmbd, new nmbd is nmbd2, old one still around
- for time being
- - released p3
- - rewrote more of nmbd2 to use new structures
- - CLIX patches from Jason.J.Faultless@bechtel.btx400.co.uk
- - DirCacheFlush() bugfix from Michael Joosten
- . This bug explains a lot of the crashes.
- - fixed a bug in ChDir() that caused reversion to / in some
- situations
- - ipc fix from Magnus Hyllander
- - released p4
- - smbpasswd fix from Jeremy
- - compilation fixes from Magnus Hyllander
- - added NetServerEnum to ipc.c (needed for master browser stuff)
- - Makefile fix from Gunther Mayer
- - cleanups for clean compile on several OSes
- - added browse mastering code
- - started integration with smb.conf for nmbd2
- - released p5
- - fixed death_time (should be t+ttl*3)
- - fixed non-removal of dead servers
- - added smbstatus -u patch from oskarh@spornet.is (Oskar Hannesson)
- - NETGROUP fix from J.W.Schilperoort@research.kpn.com
- - select and NO_SETGROUPS patches from lennylim@netcom.com (Lenny
- Lim)
- - added LINKS_READ_ONLY define in dos_mode() for LM/X
- compatability
- - "dir a.c" bug fixed thanks to roderich@nodebonn.muc.bmw.de
- (Roderich Schupp)
- - job cancel fix in client from peo@mtek.chalmers.se
- - changed nmbd2 to nmbd
- - fixed "dir a*" under trans2 lookups
- - added StrnCaseCmp()
- - updated docs a bit for new browsing stuff
- - updated INSTALL.txt
- - hopefully fixed server level security with WfWg
-
-1.9.15 (patches):
- - major/minor fix for solaris from Jeroen Schipper
-
- - fixed critical bug in directory listings
- - released p1
- - fixed one of the causes of "out of memory" while browsing
- - fixed manpage install script (Paul Blackman)
- - added DNS failures to name cache
- - fixed writebmpx bug (affects OS/2)
- - misc OS/2 fixes, mostly for EA handling
- - added SMBcopy
- - added "max ttl" option
- - arch detection patch from Bas Laarhoven
- - released p2
- - another OS/2 fix - the level 4 getpathinfo for EAs
- - added "alternate permissions" option
- - changed client to parse destination names into name + domain
- - fixed problem with PrimaryGroup and lmhosts loading
- - added domain master ability to nmbd
- - added "domain master" option
- - added "domain controller" option and code
- - pwd fix to client from Erik Devriendt (de@te6.siemens.be)
- - fixed problem in smbmv that led to ar not working in mks
- - added transs2
- - released p3
- - updated email addresses
- - fix for innetgr from Olaf Seibert (rhialto@polder.ubc.kun.nl)
- - client translate fix from bandc@dircon.co.uk
- - netbsd bcast fix from from Olaf Seibert (rhialto@polder.ubc.kun.nl)
- - syslog code from Alex Nash
- - strip dot fix from Arne Ansper
- - added addtosmbpass + man page from
- michal@ellpspace.math.ualberta.ca (Michal Jaegermann)
- - pcap fix for AIX from Jon Christiansen
- - fixed servertype bug in remote announcements
- - fixed up illegal name checks (should also be faster)
- - kanji patches from fujita@ainix.isac.co.jp (Takashi Fujita)
- - fixed bug handling non-encrypted passwords
- - released p4
- - fixed makefile for addtosmbpass
- - DCE/DFS fixes from John Brezak (brezak@ch.hp.com)
- - client patch for partial command matching from Andrew Wiseman
-
- - made is_8_3() handle full paths
- - rewrote open_file_shared() with help from Charles Hoch
-
- - changed syslog to handle interactive programs
- - fixed syslog problem with full path in argv[0]
- - illegal name fixup for kanji from fujita@ainix.isac.co.jp
- - fixed server level security to allow fallback to encryption
- - changed reply_read() and reply_lockread() to ignore clients
- smb_bufsize in order to handle broken lanman clients
- - fixed NT wildcard problem with old style programs
- - man page patches from "John M. Sellens"
-
- - partially documented the "character set" option
- - changed default for MAXDIR to 64
- - changed default DPTR idle time to 120
- - released p5
- - QNX patches from eldo@invisa.satlink.net (Eldo Loguzzo)
- - made nmbd use the "max log size" option and changed log handling
- code a bit
- - sunos patches, remote protocol (%R) addition and arch detection
- changes to stop compiler warning from Timothy Hunt
- - fixed become_user() bug that led to incorrect permissions in
- some situations.
- - released p6
- - is_8_3() fix from Charles Hoch
- - nmblib bugfix from gmk@mhcnet.att.com (George Kull)
- - aix pcap fix from Jon Christiansen
- - added explicit sig_pipe() in server.c
- - added domain logins option (not fully implemented)
- - added HAVE_GMTOFF code
- - got rid of PM_MAXLINE
- - minor client fix from goggi@eflir (Garðar Georg Nielsen)
- - added SIGCLD_IGNORE for HPUX (from Tor Lillqvist
- )
- - OSF/1 lpq patch from scooter@GENE.COM (Scooter Morris)
- - NeXT patches from pmarcos@next.com (Paul Marcos)
- - dstdiff patch to stop infinite loop from Erwin Authried (eauth@cso.co.at)
- - password server option can now take a list of password servers
- - patches to let samba run on OS/2 from Jason Rumney