On Monday, 18 January 1999 at 15:19:34 +0900, Makoto MATSUSHITA wrote: > > grog> I'll think out another way and test more thoroughly. How does this > grog> look? > > g...@itga.com.au already pointed out that "vinum read" command in such > an early stage of /etc/rc causes much much warnings about /dev/ is > read-only filesystem.
We can get rid of the warnings. And they'll go away by themselves when we have devfs. > And, a typo around reading from /etc/vinumslices > (I don't want to type every time :-). > > Anyway, I do try with this: > > if [ -f /etc/vinumslices ]; then > read vinum_slices < /etc/vinumslices > if [ -r /modules/vinum.ko ]; then # jkh paranoia > kldload vinum > vinum read $vinum_slices >/dev/null 2>&1 > else > echo "Can't find /modules/vinum.ko" > fi > fi > > It works fine, however, sorry I have only ONE volume so how it goes if > two or more volumes are defined (note that 'vinum read' takes only one > argument). The syntax for `vinum read' is changing. It now *must* specify all drives (not volumes). You can lie and specify others, too, if you want: it will silently ignore any drives which don't contain Vinum data. We need to do it like this in order to read in the config in the correct order after a crash. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
