Date: Mon, 29 Jan 2001 01:28:35 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Matt Dillon <dillon@earth.backplane.com>, John Baldwin <jhb@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Mikhail Teterin <mi@aldan.algebra.com> Subject: Re: workaround for broken mfs using vn. (was Re: cvs commit: src/sys/i386/conf GENERIC ) Message-ID: <Pine.BSF.4.21.0101290128250.21912-100000@beppo.feral.com> In-Reply-To: <19503.980759275@critter>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101290128250.21912-100000>