Subject: Re: MNT_NOSHARE for non-exportable fs [was: Removing tmpfs'
To: None <mjf@NetBSD.org>
From: YAMAMOTO Takashi <email@example.com>
Date: 10/25/2006 11:23:06
> There is a patch in another mail that implements a "noshare" option for
> This allows filesystems to declare that they do not want to be exported.
> The code in kern/vfs_syscalls.c:sys_mount() is there for compatability reasons.
> arkanian# mount -o noshare /dev/wd0e /mnt/1
> Oct 24 17:10:04 arkanian mountd: "/mnt/1 -network 192.168.0.0 -mask
> +255.255.255.0", line 2: Can't change attributes for /mnt/1 to 192.168.0.0:
> +Operation not permitted
> arkanian# mount | grep wd0e
> /dev/wd0e on /mnt/1 type ntfs (noshare, local)
- why "share" rather than "export"?
- what's the point to expose it as a mount option?
sys_mount is not an appropriate interface to control nfs exportability
these days. to specify filesystem characteristics,
IMNT_ is more appropriate.
- you are committing too fast.