From owner-freebsd-current Sun Oct 18 14:51:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12828 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:51:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12812 for ; Sun, 18 Oct 1998 14:51:00 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id OAA24329; Sun, 18 Oct 1998 14:50:31 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd024321; Sun Oct 18 14:50:30 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id OAA12751; Sun, 18 Oct 1998 14:50:29 -0700 (MST) From: Terry Lambert Message-Id: <199810182150.OAA12751@usr07.primenet.com> Subject: Re: mount flags To: andyf@speednet.com.au (Andy Farkas) Date: Sun, 18 Oct 1998 21:50:28 +0000 (GMT) Cc: chuckr@mat.net, freebsd-current@FreeBSD.ORG In-Reply-To: <362A307E.8C676700@speednet.com.au> from "Andy Farkas" at Oct 19, 98 04:16:30 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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 , 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. > > Me too! 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