On Sun, 1 Aug 1999, Kevin Day wrote:
> >
> > :Yeah, I know about -alldirs... The problem was that we had customers who
> > :wanted us to export their home directories, and unless I gave them their own
> > :filesystem, I couldn't restrict it in the manner i wanted. :)
> > :
> > :Just checking to
Matthew Dillon scribbled this message on Aug 1:
> :Yeah, I know about -alldirs... The problem was that we had customers who
> :wanted us to export their home directories, and unless I gave them their own
> :filesystem, I couldn't restrict it in the manner i wanted. :)
> :
> :Just checking to see t
On Sun, 1 Aug 1999, Matthew Dillon wrote:
> Well, theoretically there is nothing wrong going on since you can mount
> things on top of an NFS directory. Mount only complains about
> duplicate normal partition mounts because it can't open the buffered
> block device the second t
>
> :Yeah, I know about -alldirs... The problem was that we had customers who
> :wanted us to export their home directories, and unless I gave them their own
> :filesystem, I couldn't restrict it in the manner i wanted. :)
> :
> :Just checking to see that I wasn't missing a way to do this. :)
> :
> IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc)
> are set per filesystem. Given a filesystem structure like this:
>
> > df
> Filesystem 1K-blocks UsedAvail Capacity Mounted on
> /dev/da0s1a127023271518971123%/
> /dev/ccd0c8321099 23
:Yeah, I know about -alldirs... The problem was that we had customers who
:wanted us to export their home directories, and unless I gave them their own
:filesystem, I couldn't restrict it in the manner i wanted. :)
:
:Just checking to see that I wasn't missing a way to do this. :)
:
:Kevin
I'
>
> You misunderstood me. The problem you have is the fact that NFS exports
> are usually limited to the physical mount point of the filesystem being
> exported. Thus it thinks that /var above is the same as /, or that
> /var/tmp is the same as /var if both happen to be in the
IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc)
are set per filesystem. Given a filesystem structure like this:
> df
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/da0s1a127023271518971123%/
/dev/ccd0c8321099 2391764 526364
:You sure about you can export a directory multiple times? I can't even
:export two directories under the same filesystem.
:
:su-2.03# mount
:/dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3945 async
:1317317)
:procfs on /proc (local)
:su-2.03# cat /etc/exports
:
:/var
>
> To export a single filesystem multiple times, *all* of the attributes must
> be the same. If they aren't the only person you are fooling is yourself,
> since once a filesystem is NFS exported, it is open to the world.
>
> anyway the syntax for what you want is:
>
> /var /var/mails
To export a single filesystem multiple times, *all* of the attributes must
be the same. If they aren't the only person you are fooling is yourself,
since once a filesystem is NFS exported, it is open to the world.
anyway the syntax for what you want is:
/var /var/mail some.machine
--
David C
> Well, theoretically there is nothing wrong going on since you can mount
> things on top of an NFS directory. Mount only complains about
> duplicate normal partition mounts because it can't open the buffered
> block device the second time. NFS doesn't care how many times a
>
:I'm a little bit astonished that's now possible to mount via nfs
:several times at the same mountpoint with freebsd nfs clients:
:
:normal behaviour (Linux 2.2, Solaris):
:--
:
:magma:/ # mount magma:/cdrom /mnt
:magma:/ # mount magma:/cdrom /mnt
:mount: magma:
13 matches
Mail list logo
