[prev in list] [next in list] [prev in thread] [next in thread] 

List:       samba
Subject:    SAMBA digest 302
From:       samba () anu ! edu ! au
Date:       1995-01-18 7:09:38
[Download RAW message or body]

			    SAMBA Digest 302

Topics covered in this issue include:

  1) File dates
	by pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
  2) Installation directories (patch)
	by pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
  3) You _broke_ it, Ren^H^H^HAndrew! (alpha10)
	by pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
  4) 1.9.00alpha1
	by "Andrew.Tridgell" <tridge@cs.anu.edu.au>
  5) Re:  Lanmanager Clients for UNIX
	by terry@cs.weber.edu (Terry Lambert)
  6) Master browsers and subnetting
	by acs@kwi.com (Tony Sumrall)

----------------------------------------------------------------------

Date: Tue, 17 Jan 95 19:35:47 +1000
From: pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
To: Andrew.Tridgell@anu.edu.au
Cc: samba@anu.edu.au
Subject: File dates
Message-ID: <9501170935.AA10711@ayr_srv2.nth.dpi.qld.gov.au>

Andrew, is there some special reason why the modification times on
_all_ files in the distribution are updated in each tarfile?  For
example, between alphas 7 and 8, the only files which changed were

% awk '$1 ~ /^diff$/ {print $3}' 7-8.diff  
alpha7/change-log
alpha7/server.c
alpha7/util.c
alpha7/version.h

and from 8 to 10:

% awk '$1 ~ /^diff$/ {print $3}' 8-10.diff 
alpha8/HINTS.txt
alpha8/change-log
alpha8/client.c
alpha8/includes.h
alpha8/ipc.c
alpha8/loadparm.c
alpha8/loadparm.h
alpha8/local.h
alpha8/nameserv.c
alpha8/nmbd.8
alpha8/params.c
alpha8/reply.c
alpha8/server.c
alpha8/smb.h
alpha8/trans2.c
alpha8/util.c
alpha8/version.h

yet every file has a date of Jan 16 23:22 except [Sep 25 23:24
tstuid.c] and [Mar 17 1994 COPYING].  It kinda makes it hard to see
which files one should browse to find out what's new, without doing a
`diff -r' (like I did :-).

-- 
Mark Pappin ph:61/77/830555 fax:61/77/834188 pappinm@dpi.qld.gov.au
Computer Support, Ayr (Giddy Road) DPI, North Queensland, Australia

------------------------------

Date: Tue, 17 Jan 95 19:37:17 +1000
From: pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
To: Andrew.Tridgell@anu.edu.au
Cc: samba@anu.edu.au
Subject: Installation directories (patch)
Message-ID: <9501170937.AA10716@ayr_srv2.nth.dpi.qld.gov.au>

The supplied Makefile wants to install everything into the same
directory -- binaries, scripts, setup files and logfiles.

I've made a small change, to differentiate between binaries, setup and
logs, although maybe scripts could be separated out too (since the
same script may be shared across multiple architectures, but binaries
probably can't be):

diff -uw oldsamba/Makefile samba-1.8.06/Makefile
--- oldsamba/Makefile		Fri Jan 13 13:04:56 1995
+++ samba-1.8.06/Makefile	Mon Jan 16 23:22:30 1995
@@ -8,7 +8,9 @@
 MANDIR = /usr/local/man
 
 # The directory to put the executables in
-INSTALLDIR = /usr/local/samba
+BINDIR = /usr/local/bin
+LIBDIR = /usr/local/lib/samba
+VARDIR = /var/samba
 
 # The permissions to give the executables
 INSTALLPERMS = 0755
@@ -28,10 +30,10 @@
 # set these to where to find various files
 # These can be overridden by command line switches (see smbd(8))
 # or in smb.conf (see smb.conf(5))
-DEBUGFILE = $(INSTALLDIR)/log
-SERVICES = $(INSTALLDIR)/smb.conf
-LMHOSTS = $(INSTALLDIR)/lmhosts
-LOCKDIR = $(INSTALLDIR)/locks
+DEBUGFILE = $(VARDIR)/log
+SERVICES = $(LIBDIR)/smb.conf
+LMHOSTS = $(LIBDIR)/lmhosts
+LOCKDIR = $(VARDIR)/locks
 
 # set this to the default group you want your machine to appear in
 # for browsing. This can also be set in nmbd (see nmbd(8))
@@ -48,7 +50,7 @@
 # where you are going to have the smbrun binary. This defaults to the 
 # install directory. This binary is needed for correct printing
 # and magic script execution. This should be an absolute path!
-SMBRUN = $(INSTALLDIR)/smbrun
+SMBRUN = $(BINDIR)/smbrun
 
 #####################################
 # WHICH OPERATING SYSTEM?
@@ -310,18 +312,19 @@
 installbin: all
 	@echo
 	@echo "IGNORE ANY \"File exists\" MESSAGES FROM THIS COMMAND"
-	-mkdir $(INSTALLDIR)
+	-mkdir $(BINDIR)
+	-mkdir $(LIBDIR)
+	-mkdir $(VARDIR)
 	@echo
 	@echo "IGNORE ANY \"No such file\" MESSAGES FROM THESE COMMANDS"
 	-for i in $(PROGS); do \
-		mv $(INSTALLDIR)/$$i $(INSTALLDIR)/$$i.old ; \
+		mv $(BINDIR)/$$i $(BINDIR)/$$i.old ; \
 	done
 	@echo
-	@echo "INSTALLING IN "$(INSTALLDIR)
+	@echo "INSTALLING IN "$(BINDIR)
 	for i in $(PROGS); do \
-		cp $$i $(INSTALLDIR)/$$i ; \
-		chmod $(INSTALLPERMS) $(INSTALLDIR)/$$i ; \
-		strip $(INSTALLDIR)/$$i ; \
+		cp $$i $(BINDIR)/$$i ; \
+		chmod $(INSTALLPERMS) $(BINDIR)/$$i ; \
 	done
 	@echo
 	@echo "INSTALLATION COMPLETE. TO REVERT TO THE PREVIOUS VERSION"



-- 
Mark Pappin ph:61/77/830555 fax:61/77/834188 pappinm@dpi.qld.gov.au
Computer Support, Ayr (Giddy Road) DPI, North Queensland, Australia

------------------------------

Date: Tue, 17 Jan 95 19:54:08 +1000
From: pappinm@ayr_srv2.nth.dpi.qld.gov.au (Mark Pappin)
To: Andrew.Tridgell@anu.edu.au
Cc: samba@anu.edu.au
Subject: You _broke_ it, Ren^H^H^HAndrew! (alpha10)
Message-ID: <9501170954.AA10760@ayr_srv2.nth.dpi.qld.gov.au>

Me again.

I just installed 1.8.06alpha10, and when I tried to `Connect Network
Drive' in File Mangler, and entered `\\ayr_srv2' in the `Path:' box,
as has worked in the past to browse the Samba server, I get a dialog
box saying 

``<Stop> The requested API isn't supported on the remote server.''

However, in a DOG-window, `net view \\ayr_srv2' worked fine.

Andrew, if you want log-files, I have them for successful and
unsuccessful browses, at levels 4 and 6.  Mail me if you want them, or
any other cases.

-- 
Mark Pappin ph:61/77/830555 fax:61/77/834188 pappinm@dpi.qld.gov.au
Computer Support, Ayr (Giddy Road) DPI, North Queensland, Australia

------------------------------

Date: Tue, 17 Jan 1995 23:03:55 +1100
From: "Andrew.Tridgell" <tridge@cs.anu.edu.au>
To: samba@cscgpo.anu.edu.au
Subject: 1.9.00alpha1
Message-ID: <199501171203.XAA02883@arvidsjaur.anu.edu.au>

With all the recent changes I decided that the next version should be
1.9.00.

I have just released 1.9.00alpha1. Hopefully we won't have too many
alphas before a final release.

Also, as of this release, I will provide patch files for every release
(alpha or not). This should help other developers. Look in the patches
directory on nimbus.

Some of the recent changes include:

- fixed \\SERVER browse problem (introduced in alpha10)

- added support for the client setting the print file name. This only
works for bsd style lpq commands, but if it does work then you'll see
print queue entries like Paintbrush-FRED.BMP rather than the rather
messy TRIDGE.a00987.

If you try it, please report any bugs in this release.

Andrew

PS: Yes I know that Win95 gets mangled names. 

------------------------------

Date: Tue, 17 Jan 95 9:01:47 MST
From: terry@cs.weber.edu (Terry Lambert)
To: samba@anu.edu.au
Cc: terry@cs.weber.edu (Terry Lambert)
Subject: Re:  Lanmanager Clients for UNIX
Message-ID: <9501171601.AA26520@cs.weber.edu>


Beverly Brown writes:
> 
> John Stewart:
> >>From SAMBA Digest 282
> >
> >> It doesn't work very well, although I think the basic idea is OK,
> >> maybe somebody with more time wants to adopt the code?
> >
> >I am very interested in making this code work with LINUX. 
> >
> >I'll adopt it, but do not have an FTP site in which to place it. If 
> >someone can suggest a place for it (like Nimbus :-), I'll volunteer to
> >be keeper of the revisions. Although I'll state from the outset that
> >I can not put the effort into it that Andrew has done with Samba.
> >
> >I have the code from Tor, and have started investigating what is needed
> >to convert it to work for LINUX.
> >
> >Any comments/questions/concerns?
> >
> 
> Since there is already a solution for Linux (i.e. smbfs) I would like to see
> contiued support for the code under SunOS 4.1.3. I'm sure folks with other
> flavors of Unix would like it to run under their favorite platform as well.
> If I had time, I'd assist with this effort, but between work that I'm being 
> paid for, school, and trying to maintain some kind of a home life, it's just 
> not possible. Can anyone out there make this code actually work under SunOS?
> (Or other Unix variants?) 

Supporting smbfs as a file system type under a previous version of SunOS
(one that did not support parallel processing) would be trivial, I think,
as would FreeBSD, Linux, and UnixWare 1.0 or below (UnixWare 2.0 is SMP).

Supporting it under AIX would be less trivial, but possible, since IBM
provides source code to a GFS module (the big problem there would be
kernel use of the network calls).  The source code is in one of the
supplementary manuals you can order for the thing.

The problem with SMP SunOS, all versions of Solaris, and UnixWare 2.0 is
that the OS vendors do not provide interface specifications which will
allow you to produce a kernel preemption safe file system.  This is
mostly because they've done their locking below the vncalls layer instead
of at the vncalls layer (where it would be transparent to the file system
provider).  The net effect is that without a source license, you are SOL.

The one SMP exception is Unisys, which (correctly, IMO) put their locking
at the vncalls layer.  You could do the work for a 6000/50 or so, but
there's little point in that, considering how the machine has not taken
any significant market share.


Short of causing Sun or someone to expose their internals, I believe
support will remain limited to user space loopback via NFS, like hlfsd.



					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.

------------------------------

Date: Tue, 17 Jan 1995 11:16:15 +0800
From: acs@kwi.com (Tony Sumrall)
To: samba@cscgpo.anu.edu.au
Subject: Master browsers and subnetting
Message-ID: <9501171916.AA15852@yeehaw.smux.kwi.com>

We have about a dozen class C networks here internally.  The PCs (running
Windows NT and WfWg) are on a different class C net from the Unix
machines.  The PC network is the one on which the browse masters reside
and all of the PCs are in the same netBIOS group.  My problem is that I
can't seem to get SAMBA to register in that group.  From log.nmb.debug I
can see nmbd generating the name queries to port 137 for all of the
subnets I list in lmhosts but a 'snoop port 137' (I'm running Solaris 2.3)
doesn't show any outbound packets for any subnets other than the local
one.

I guess I have 2 questions:

1.  Why won't my Unix machine register?
2.  Why don't I see outbound packets?  Could this be the cause of problem
    1?

I'm running samba 1.8.06 alpha 8.
-- 
Tony Sumrall	acs@kwi.com

[Views expressed herein are the author's and do not necessarily reflect those
 of Sterling Software, Inc.]


------------------------------

End of SAMBA Digest 302
***********************

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic