From owner-cvs-all Mon Jan 29 1: 8:17 2001 Delivered-To: cvs-all@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 100A937B402; Mon, 29 Jan 2001 01:07:55 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0T97tK19505; Mon, 29 Jan 2001 10:07:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Matthew Jacob , 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: Your message of "Mon, 29 Jan 2001 01:03:48 PST." <200101290903.f0T93ms62313@earth.backplane.com> Date: Mon, 29 Jan 2001 10:07:55 +0100 Message-ID: <19503.980759275@critter> From: Poul-Henning Kamp Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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