From owner-freebsd-current Mon Mar 9 17:58:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03488 for freebsd-current-outgoing; Mon, 9 Mar 1998 17:58:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03385 for ; Mon, 9 Mar 1998 17:57:59 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA28398; Tue, 10 Mar 1998 01:56:55 GMT Date: Tue, 10 Mar 1998 10:56:55 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Dmitrij Tejblum , nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: vnode_pager: *** WARNING *** stale FS code in system In-Reply-To: <199803091958.MAA23552@usr05.primenet.com> 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 Mon, 9 Mar 1998, Terry Lambert wrote: > The FFS/UFS inheritance is both more and less problematic. More, > because it is so fundamental to the system. Less, because it's > *almost* sufficiently abstract. Kirk's stated intent in the > seperation was to provide a flat inode namespace. Some of this has > been recently broken (via default vops and other changes), and some The flat-namespace filestore vop's were just taken out. They didn't really fit earlier since they didn't have vnodes associated with them. They were hand coded and bypass mechanisms were special cased to ignore them. This policy has changed recently so there's no reason not to bring them back, but a little work will need to be done to update them to include a vnode arg. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message