From owner-freebsd-current Sun Oct 18 18:55:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01020 for freebsd-current-outgoing; Sun, 18 Oct 1998 18:55:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01002 for ; Sun, 18 Oct 1998 18:55:12 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id JAA03392; Mon, 19 Oct 1998 09:50:35 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810190150.JAA03392@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Nik Clayton cc: Andy Farkas , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-reply-to: Your message of "Sun, 18 Oct 1998 20:09:01 +0100." <19981018200901.53009@nothing-going-on.org> Date: Mon, 19 Oct 1998 09:50:35 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nik Clayton wrote: > On Mon, Oct 19, 1998 at 04:16:30AM +1000, Andy Farkas wrote: > > 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. > > From the logs for src/sys/sys/mount.h; > > ---------------------------- > revision 1.67 > date: 1998/09/07 13:17:05; author: bde; state: Exp; lines: +5 -54 > Removed statically configured mount type numbers (MOUNT_*) and all > references to them. > > The change a couple of days ago to ignore these numbers in statically > configured vfsconf structs was slightly premature because the cd9660, > cfs, devfs, ext2fs, nfs vfs's still used MOUNT_* instead of the number > in their vfsconf struct. > ---------------------------- > > 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. 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. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message