On Monday, 18 January 1999 at 13:51:57 +0900, Makoto MATSUSHITA wrote:
>
> grog> Because it doesn't work like that. The config is stored in the
> grog> disk labels, not in a static (and not necessarily correct)
> grog> config file. The config file is only for the first-time create.
>
> O.K. I understand (not 'vinum create' but 'vinum read'). Would you
> please ('cause I don't know :-) how to set the "vinum_slice" variable?
> We don't include /etc/rc.conf in such an early stage of /etc/rc...
Oops. This was a thoroughly successful commit, wasn't it? At least
it didn't break `make world'.
I'll think out another way and test more thoroughly. How does this
look?
if [ -f /etc/vinumslices ]; then
read /etc/vinumslices
if [ -r /modules/vinum.ko ]; then # jkh paranoia
kldload vinum
vinum read $vinum_slices
else
echo "Can't find /modules/vinum.ko"
fi
fi
> grog> Currently, yes. Peter put in hooks to statically configure
> grog> Vinum, but THEY ARE NOT TESTED. Not at all. Please don't use
> grog> them, or if you do, tell me only about the fixes you make.
>
> Hmm, I've used vinum without module (built-in the kernel). It works
> for a week... Anyway, I'll stop it and switch to kldloading... thank you.
OK, I take that back. You can also tell me about your successes :-)
There's still one way you can shoot yourself in the foot with
statically configured Vinum: unless you specify VINUMDEBUG, you can
find yourself out of sync with Vinum(8): they pass structures via
ioctl, and some of the structures include debugging information.
Greg
--
See complete headers for address, home page and phone numbers
finger [email protected] for PGP public key
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
