What happened to this patch/this discussion?
To remind everyone, the issue was to print specific file-system
specific mount options as in
dima@spike% /sbin/mount -vt nfs
pid295@spike:/host on /host (nfs, v2, udp, hard, intr)
pid295@spike:/st on /st (nfs, v2, udp, hard, intr)
instead of
On Sun, Mar 25, 2001, Boris Popov wrote:
On Sun, 25 Mar 2001, Peter Pentchev wrote:
bikeshed type=question value="mostly stupid"
Or could mount(8) invoke a couple of sysctl's to get a string representation
of each mountpoint's mount options?
/bikeshed
This is not a bikeshed,
On Sun, Mar 25, 2001 at 02:18:43PM +1000, Bruce Evans wrote:
On Sat, 24 Mar 2001, Dima Dorfman wrote:
I tried to export this stuff in struct statfs, but ran into a problem:
I'd need the complete definitions of fs_args in sys/mount.h, but I
can't include, e.g., nfs/nfs.h because the
* Peter Pentchev [EMAIL PROTECTED] [010325 00:38] wrote:
bikeshed type=question value="mostly stupid"
Or could mount(8) invoke a couple of sysctl's to get a string representation
of each mountpoint's mount options?
/bikeshed
That seems like abuse of an interface.
--
-Alfred Perlstein -
On Sun, 25 Mar 2001, Peter Pentchev wrote:
Only mount_foofs can reasonably know about the options for foofs.
perhaps mount(8) could fork-exec mount_foofs(8) to print options for
foofs.
bikeshed type=question value="mostly stupid"
Or could mount(8) invoke a couple of sysctl's to get a
In message [EMAIL PROTECTED], Bruce Ev
ans writes:
On Sun, 25 Mar 2001, Peter Pentchev wrote:
Only mount_foofs can reasonably know about the options for foofs.
perhaps mount(8) could fork-exec mount_foofs(8) to print options for
foofs.
bikeshed type=question value="mostly stupid"
Or
On Sun, 25 Mar 2001, Peter Pentchev wrote:
bikeshed type=question value="mostly stupid"
Or could mount(8) invoke a couple of sysctl's to get a string representation
of each mountpoint's mount options?
/bikeshed
This is not a bikeshed, but sysctl is the wrong interface to do
this.
Boris Popov [EMAIL PROTECTED] writes:
This is not a bikeshed, but sysctl is the wrong interface to do
this. Use VFSs/VOPs instead. This isn't a big problem with passing string
from kernel to userland.
I like your idea of using the extattr interface. It isn't a perfect
match, since
Gerald Pfeifer [EMAIL PROTECTED] writes:
What I'd like to see is `mount -v' printing
vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs: v3, udp)
instead of
vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs)
On Sat, 24 Mar 2001, Dima Dorfman wrote:
Implementing the above functionality in mount(8) isn't actually that
hard. We would need to export the filesystem-specific fs_args
structures (e.g., nfs_args, ffs_args) to the userland. If we do that,
mount(8) will be able to display all kinds of
On Sat, 24 Mar 2001, Dima Dorfman wrote:
I tried to export this stuff in struct statfs, but ran into a problem:
I'd need the complete definitions of fs_args in sys/mount.h, but I
can't include, e.g., nfs/nfs.h because the latter includes the
former (sys/mount.h)!
mount.h used to know too
I tried to get some responses to this on -questions a couple of months
ago, but failed:
What I'd like to see is `mount -v' printing
mail:/var/mail on /var/mail (nfs: v3, udp)
vexpert:/files7 on /system (nfs: v3, tcp)
vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs: v3, udp)
12 matches
Mail list logo
