From owner-cvs-all Sat Jan 27 18: 3: 1 2001 Delivered-To: cvs-all@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F0C0137B402; Sat, 27 Jan 2001 18:02:36 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA32521; Sat, 27 Jan 2001 18:02:37 -0800 Date: Sat, 27 Jan 2001 18:02:38 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/conf GENERIC In-Reply-To: <200101280149.f0S1nLi00816@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 27 Jan 2001, Mike Smith wrote: > > > One should use md(4) and mdconfig(8) rather than MFS nowadays anyways, which > > > does work with DEVFS. > > > > Uh, I don't think so. MFS should be fixed. With MFS you should be able to take > > advantage of VM. I don't think the same applies to md. > > If by "take advantage of VM" you mean "can be backed by swap", then md(4) > can do this too. I'll have to re-examine this. What I want and what people can/should use MFS or md for is like solaris tmpfs. Even with softupdates it's preferrable to have a volatile filesystem. I would think a VFS would be better at doing this than a 'device driver', but I really don't care. If MFS is really currently broken by DEVFS and md really does replace it, then it should be nuked from GENERIC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message