Date: 04 Feb 2001 09:52:41 +0900 From: Makoto MATSUSHITA <matusita@ics.es.osaka-u.ac.jp> To: jhb@FreeBSD.ORG Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: doFS.sh should obey MDDEVICE if available Message-ID: <20010204095241U.matusita@ics.es.osaka-u.ac.jp> In-Reply-To: <XFMail.010203154437.jhb@FreeBSD.org> References: <20010204082409C.matusita@jp.FreeBSD.org> <XFMail.010203154437.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
jhb> The current method always finds an unused device to use, so the
jhb> old VNDEVICE-style hack is no longer needed. There's no point to
jhb> setting an explicit device to use.
But I want to ensure that all used md(4) devices is unconfigured after
it is used.
Imagine you run 'make release' for your own release. If something is
trouble in doFS.sh ('kernel size exceeds 1.44MB floppy size' is a
typical example), make will exit without umounting /mnt and
unconfigureing /dev/mdX, where X is dynamically allocated (and no way
to know what X is outside of doFS.sh). If I can say 'doFS.sh, your md
device number is X', it's obviously easy to umount /mnt and
unconfigure md devices after the script runs.
My mother tolds me that I should put away my toys after I play with
them, so I want to do a sure way to unconfigure md device.
BTW, how many md devices can we configure at the same time? What's
happen if a file of md's backing store is removed?
-- -
Makoto MATSUSHITA
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010204095241U.matusita>