10-02-2007, 03:00 PM
|
| Junior Member | | Join Date: Sep 2009
Posts: 0
| |
 Re: NFS Exporting a samba share
"Mike Eisler" wrote in message
news:36f0f19f.0407070450.511d1f0c@posting.google.c om...
> > > Try exporting the samba mounts. This assumes the samba file system
> > > will allow NFS exporting.
> >
> > Try the reverse. You can SMB export almost anything, including other SMB
> ^^^^^^^^^^^^^^^^^^
> That only works if the NFS client also has an SMB client, which was
> not
> specified in the original post. If this were so, then there's be no
> point in original question.
>
> > mounts and including NFS mounts. Alternatively, set up the SMB mount to
be
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> So to quote you: "allowing machine C to inherit permissions from
> machine B to access things on machine A just breaks a lot of security
> and file locking paradigms. Transitive directory mounting is just a
> big, big, big problem."
>
> Why is it, if NFS does it, it's a problem, but if an SMB server does
> it, it
> is not?
That's a very good question. It's a potential problem with security and
file-locking craziness, which NFS handles by saying "You can't do that you
silly goose". But the file ownership, file permissions, and file locking of
SMB is far more handled, at least for Samba servers and ASU servers, by
programs in userspace, not by kernel fun and joy. You described some of the
kernel-level fun and joy for NFS in your bits that I snipped. So while the
security and file-locking issues exist, SMB servers like Samba just go ahead
and provide them anyway. Also, SMB is nowhere near so vulnerable to the
sorts of failures NFS experiences when either a client *or* a server loses
track of its partner, such as during an extended network interruption or
power failures, and refuses to let go of the old mount and require rebooting
of *both* machines, especially with having to go in by hand and remove
entries from the "rmtab" file. Add in a middle NFS server doing transitive
file mounting and you're asking for your head on a platter, carved up fine
and scatterd with onion rings.
But in places like the Windows world, you can't mount one directory inside
another, so you do avoid some of the potential delights.
> > mounted somewhere else on machine B and C and use symbolic links inside
/a
> > pointing to the other SMB mount point, which is a quite common way to do
> > things.
 |