[Format recovered--see http://www.lemis.com/email/email-format.html]
On Saturday, 18 March 2000 at 3:34:38 +0100, Palle Girgensohn wrote:
> Hi!
Please don't send messages one line per paragraph. It's a pain to
reformat.
> I'm having troubles updating a FreeBSD 3-stable system to current,
> since it has /usr as a vinum volume. I've just updated about a dozen
> machines without any problems, but none of them uses vinum.
>
> Following the instructions in UPDATING, when rebooting to single
> user mode, vinum wouldn't work since the kernel module was out of
> date - no surprise.
Hmm. After updating, you should have had new klds as well. But
that's probably not your fault. Could you enter a PR about it,
please?
> So, I copied a fresh vinum.ko in there and tried again. This time,
> vinum loaded fine, but complained that it couldn't get the list from
> disk (or similiar).
How similar? That statement doesn't really help very much. Vinum
produces error messages to help pinpoint problems.
> A 'vinum list' command would show nothing. So, I tried rebooting
> with the old 3-stable kernel. When makeing installworld running the
> 3-stable kernel, make first installed the make binary itself, and
> then could not do anything more, since the new libc was not in
> place, and the just installed make needed the new libc... odd? shall
> it really start by installing make? dunno how this happened?
It looks like you shot yourself in the foot.
> Anyway, what is a good strategy for upgrading a system where /usr is
> a vinum volume? Any tips, tricks or ideas (apart from moving /usr to
> a non-vinum volume and install onto that one).
I'd have to find out what went wrong first. It looks as if it should
have worked modulo the problems installing the klds.
Greg
--
When replying to this message, please take care not to mutilate the
original text.
For more information, see http://www.lemis.com/email.html
Finger [EMAIL PROTECTED] for PGP public key
See complete headers for address and phone numbers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
