Date: Sun, 18 Oct 1998 20:09:01 +0100 From: Nik Clayton <nik@nothing-going-on.demon.co.uk> To: Andy Farkas <andyf@speednet.com.au>, Chuck Robey <chuckr@mat.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: mount flags Message-ID: <19981018200901.53009@nothing-going-on.org> In-Reply-To: <362A307E.8C676700@speednet.com.au>; from Andy Farkas on Mon, Oct 19, 1998 at 04:16:30AM %2B1000 References: <Pine.BSF.4.05.9810181240390.348-100000@picnic.mat.net> <362A307E.8C676700@speednet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <sys/mount.h>, 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 -- C.R.F. Consulting -- we're run to make me richer. . . 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?19981018200901.53009>