Samba and NetInfo and NIS and LDAP and ... (fwd)

[Luke Kenneth Casson Leighton]

On Wed, 8 Apr 1998, Gerald W. Carter wrote:

> Luke Kenneth Casson Leighton wrote:
> > 
> > > And finally, I though it might be a good idea to parse not only the
> > > printcap (or the equivalent in SYSV) but also /etc/exports or
> > > /etc/dfs/dfstab to 'automagically' set up the same 'shares' as the
> > > server provides as nfs!
> > 
> > you haven't actually _done_ this already, have you?  if so, totally
> > wicked!
> > 
> 
> IMHO I would prefer to be able to turn the mechanism off.  One or the
> reasons that we wanted to switch from NFS to SMB was the finer
> granularity of control that smb server ( such as samba offers ). 

that's no problem: you put it under an option like:

nfs mount table = /etc/exports


> Normally with NFS you export a top level directory and then clients
> mounts various subdirectories.  You can do this with SMB.  Of course you
> can do things like "dir \\server\share\directory" but not things like
> "net use x: \\server\share\directory".  Think of it like this.  Here's
> an entry from a standard Solaris type /etc/dfs/dfstab
> 
> 	share -F nfs -o rw=clients -d "Home dirs" /export/home
> 
> Then this is placed in the automount maps so athat things like 
> "cd ~username" work correctly.  If you automatically make a share out
> the NFS export, users can then go "net use x: \\server\homedir" and get
> a top level listing of all the home directories.
> 
> By now you are probably thinking "Yeah but the standard unix permissions
> still apply" and I agree, but why give user's access to this type of
> thing if they don't need it?

how about \\server\profiles, which _is_ needed.  i'm trying to encourage
people to move away from \\server\homes\profile and to move to
\\server\profiles\%U because of the substitution problems that occur with
the [homes] share: the stupid microsoft clients maintain the connection to
[homes] in a background process...

luke