Date: Sun, 18 Oct 1998 22:17:30 -0400 (EDT) From: Chuck Robey <chuckr@mat.net> To: Peter Wemm <peter@netplex.com.au> Cc: Nik Clayton <nik@nothing-going-on.demon.co.uk>, Andy Farkas <andyf@speednet.com.au>, freebsd-current@FreeBSD.ORG Subject: Re: mount flags Message-ID: <Pine.BSF.4.05.9810182207500.348-100000@picnic.mat.net> In-Reply-To: <199810190150.JAA03392@spinner.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 Oct 1998, Peter Wemm wrote: > > Bruce can presumably shed some more light. > > > > N > > The FS type numbers are essentially random numbers, so it's no good > trying to match them to a MOUNT_* constant. I was hoping you wouldn't say that. Murphy was telling me you would. Mike commented that both the old and new methods should be working ... I agree, at least until the new method doesn't resemble keystone kops so well. Bruce hasn't replied yet, let's be patient. I at least don't know enough about it to undo anything he's done. I *could* do that, but not with safety. > > NetBSD had them #defined to strings, ie: #define MOUNT_NFS "nfs" so that > you had some idea what you could expect from the kernel on a known > filesystem. There can be no such thing as a canonical list since of > fstypenames because new ones can be loaded on the fly. OK. Can the field in struct statfs, f_fsid, be mapped to something, like say the struct vfsconf that comes back from a getvfsbyname(), the vfc_typenum field? Geeze, that nfs code is impenetrable. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9810182207500.348-100000>