From owner-cvs-all Mon Jan 29 1:29:16 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 526BC37B69E; Mon, 29 Jan 2001 01:28:56 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA04645; Mon, 29 Jan 2001 01:28:34 -0800 Date: Mon, 29 Jan 2001 01:28:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Matt Dillon , John Baldwin , cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Mikhail Teterin Subject: Re: workaround for broken mfs using vn. (was Re: cvs commit: src/sys/i386/conf GENERIC ) In-Reply-To: <19503.980759275@critter> 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 Yeah, err, but mdconfig panics for me.... On Mon, 29 Jan 2001, Poul-Henning Kamp wrote: > In message <200101290903.f0T93ms62313@earth.backplane.com>, Matt Dillon writes: > > > > It's sad to see mfs not work, but I'm sure Poul will fixup whatever > > problems md has replacing it real quick. > > > > In the mean time, you can use 'vn' to workaround the MFS issue. It's > > a little messy, but it works: > > > > vnconfig -c -s labels,reserve -S 256m /dev/vn0 > > disklabel -r -w vn0c auto > > newfs /dev/vn0c > > tunefs -n enable /dev/vn0c > > mount /dev/vn0 /usr/src/sys/compile (or whatever) > > Actually you can get in trouble because vn(4) is not fully DEVFS savy. > That is one of the reasons why the vn(4) functionality has been > integrated into md(4). > > Please see mdconfig(8) for how to do this right. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message