Date: Sun, 18 Oct 1998 21:50:28 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: andyf@speednet.com.au (Andy Farkas) Cc: chuckr@mat.net, freebsd-current@FreeBSD.ORG Subject: Re: mount flags Message-ID: <199810182150.OAA12751@usr07.primenet.com> In-Reply-To: <362A307E.8C676700@speednet.com.au> from "Andy Farkas" at Oct 19, 98 04:16:30 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > I have a very recently broke thing that was happily using a call to > > statfs, to tell if it was an NFS filesystem or not. Last time I had > > occasion to take a look at this, there were flags of the sort MOUNT_XXX, > > where the XXX could have been UFS, MFS, NFS, etc. The application is > > specifically looking for MOUNT_NFS, and it's just not around anymore, > > that I can find. > > Yeah, something fishy is going on here with statfs(2). According to the > man page on a 2.2.7 system, and in <sys/mount.h>, there are definitions > for struct statfs->f_type, but on a 3.0-current, they have strangely > disappeared. The use of this field in order to determine FS type presupposes the definition of a manifest value in the mount.h file each time someone adds a new FS type. This is basically an utterly bogus thing to presuppose, since it means that you have to recompile the kernel and modify mount.h to add support for a new FS type. > > Anyhow, anyone got a recommendation on how to change this thing so that > > it works under current? > > You're not trying to compile Midnight Commander are you? If so, add > "#define NO_INFOMOUNT 1" to config.h as a workaround .... > > > A real short history on what's changed in > > regards to this would be a nice thing to stick in the mail archives. > > <AOL>Me too!</AOL> I'd like to see a history, as well. IMO, the correct thing to do is to go by string, but this still leaves the mount flags and data in a position where they are rather bogusly externalized for string parsing within the kernel. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. 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?199810182150.OAA12751>