samba.2.0.4b.1.README May 28, 1999 This is an initial (and long awaited) port of Samba 2.0.x for NEXTSTEP and OpenStep for Mach. Samba is a free SMB and CIFS client and server for unix and other operating systems. FILES file: samba.2.0.4b.1.NIS.b.tar.gz desc: binaries (NS 3.2+ & OSM 4.x) sum: 58198 6233 md5sum: a0a63fdcc89bba14f377c2345c8da3da file: samba.2.0.4b.1.m.NIS.b.tar.gz desc: binaries (OSM 4.x only) sum: 34914 5934 md5sum: 4fcb1813b6e0088ee7e387630be0fdd9 file: samba.2.0.4b.1.s.tar.gz desc: Slightly modified samba 2.0.4b source (unpack and make) sum: 00841 2129 md5sum: e6725942bb7ffa79e09e990a1bf23917 (** (to be) found at: http://www.peak.org/next/apps/utils/networks/ and/or http://www.peak.org/openstep/mach/apps/utils/networks/ **) INSTALLATION 1. Unpack archive > gnutar xzf /path_to/Archive/samba.2.0.4b.1.NIS.bd.tar.gz 2. Install samba.pkg with /NextAdmin/Installer.app 3. Launch samba daemons You can do this by hand, or use the provided install_samba script (in the installed samba/ directory) to automate this. 4. Edit lib/smb.conf to your liking. There is ample documentation in samba/docs and samba/swat/help CHANGELOG/RELEASE NOTES May 28, 1999 (2.0.4b port #1) * nmbd and smbd seem to work fairly reliably now (finally!), provided you use share modes = no in the smb.conf file. (under investigation). * swat still has serious problems. - Cannot be used for editing smb.conf (results in corrupted conf file) - Cannot be used to start/stop/restart nmbd and smbd daemons (a restart or stop will sometimes kill your entire system!) - MAY be used for viewing status information and documentation (but this is not recommended) not released (2.0.3 beta ) * (990521) Tweak fcntl.c locking a bit. Samba doesn't seem to like/use locks owned by process 0, so I'll use an arbitrary 666. I'm seeing periodic locking problems that I think are related to this. * (990521) Adding smb pipe support = no and nt smb support = no to smb.conf seems to help wrt browsing difficulties (see below). * (990419) Comment out some more signal blocking code so that nmbd dies reliably on SIGTERM. No bad side effects witnessed... yet. * (990419) Undo some swat changes that weren't helping anyway. This will require a lot of work, it seems, to address/fix. Until then, swat is hopelessly broke. Mar 16, 1999 (2.0.3 beta 990316) * I've been testing samba2 primarily in security=domain mode. I'm having periodic difficulties browsing samba shares, especially just \\samba_host, which doesn't seem to show anything (on NT4SP4 clients, at least). * Found out samba2 actually REQUIRES fcntl locking to even come close to working. So I wrote a wrapper to translate fnctl lock calls to use flock instead. samba/src/samba-2.0.3/source/fcntl.c * swat seems hopelessly broke for some reason: - Editing parameters are oftentimes trunctated in smb.conf - Any attempt to kill a swat-started smbd will bring your system down ('cause it kills inetd, window server, and probably a few others???) * nmbd has some signal handling bugs which had caused it to be unkillable, short of 'kill -KILL `cat nmbd.pid` '. I removed some signal blocking code so that it now (sometimes, at least) shuts down on a regular kill, but I'm not sure if my hacks have any other bad consequences. Feb 15, 1999 (2.0.2 beta 990215) * First attempt at a Samba2 port. CREDITS Samba home page http://www.samba.org/ Package Creation Rex Dieter Computer System Manager Universtity of Nebraska-Lincoln Department of Mathematics and Statistics http://www.math.unl.edu/~rdieter/ Rex's Samba users message board: http://www.math.unl.edu/~rdieter/Projects/msgBoard/msgBoard/Samba Rex's Samba Survey entry http://samba.anu.edu.au/cgi-bin/ssurvey.cgi?mode=ViewOrg&theRecNo=2511