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 just
dima@spike% /sbin/mount -vt nfs
pid295@spike:/host on /host (nfs)
pid295@spike:/st on /st (nfs)
Gerald
On Sun, 25 Mar 2001, Dima Dorfman wrote:
>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 ideally this would be a VFS operation, but it works quite
> well. The only modifications required are to mount(8) to try to get
> this attribute, and then to any filesystem which wishes to support it.
>
> Below is a patch which makes the necessary changes to mount(8), and
> adds support for this to NFS. It's amazingly simple, and doesn't
> interfere with anything else (i.e., you don't have to rebuild half the
> world to use it). The only thing I don't like is that the "mountopts"
> and "mountopts_verbose" constants aren't macroized, but that can be
> easily solved (I just didn't know where to put them). With it,
> mount(8) outputs stuff like this:
>
> 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)
> bazooka:/a on /.amd/bazooka/host/a (nfs, nodev, nosuid, v3, tcp, hard, intr)
> bazooka:/b on /.amd/bazooka/host/b (nfs, nodev, nosuid, v3, tcp, hard, intr)
>
> Comments? Suggestions?
>
> Thanks in advance
>
> Dima Dorfman
> [EMAIL PROTECTED]
>
> P.S. Would anyone have a fit if I wrote man pages for
> extattr_get_file, extattr_set_file, and extattr_delete_file?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
