From owner-freebsd-current Sun Oct 18 14:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11246 for freebsd-current-outgoing; Sun, 18 Oct 1998 14:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11233 for ; Sun, 18 Oct 1998 14:26:02 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id RAA16222; Sun, 18 Oct 1998 17:25:14 -0400 (EDT) Date: Sun, 18 Oct 1998 17:25:14 -0400 (EDT) From: Chuck Robey To: Nik Clayton cc: Andy Farkas , freebsd-current@FreeBSD.ORG Subject: Re: mount flags In-Reply-To: <19981018200901.53009@nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Oct 1998, 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. I asked him several hours ago. Don't know the clock over there, but he's got to sleep *sometime*, and I've probably hit it. I understand from David O'Brien that this is part and parcel of BSD4.4Lite2 changes ... which seem to make a user's job of identifying what kind of filesystem he's dealing with (as opposed to mounting one from scratch) terribly kludgy. I think it's most likely a missing doc problem, or maybe I just haven't found it yet. Likely... > > N > -- > C.R.F. Consulting -- we're run to make me richer. . . > > ----------------------------+----------------------------------------------- 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