Bernd Schoeller wrote:
> On Fri, 22 Sep 2006 08:44:30 +0200, Christopher Vance <[EMAIL PROTECTED]>
> wrote:
>
>> It might not be the 'right' way to do things, but I've had no trouble
>> upgrading machines remotely. YMMV, depending on how busy the thing is.
>>
>> What I would do is:
>
> Please, that is not the recommended way of doing it. The recommended way
> of doing it is to follow the instructions in the ugrade guide ("without
> install media") from 3.6>3.7, then from 3.7>3.8, then from 3.8>3.9 - each
> one with a reboot in between. This is the tested process and should be the
> safe way. Doing it all in one step may get you there, but nobody really
> knows.
>
> http://www.openbsd.org/faq/upgrade37.html
> http://www.openbsd.org/faq/upgrade38.html
> http://www.openbsd.org/faq/upgrade39.html
>
> Bernd
yes...
And pay really close attention to the first paragraphs, which people
usually think is unimportant for unknown reasons.
Especially if you haven't been doing upgrades properly, you need to
practice the process locally. Build out a machine as similar to your
remote machine as you can (and I don't just mean just the OpenBSD
version[*]), back it up. Now, put it in another room, and upgrade it.
If it works, restore, try it again. If it doesn't, walk over, figure
out what went wrong, fix, and try again.
Repeat until you got a long string of successful upgrades. :)
Can you jump a bunch of releases? With extreme care and deep
understanding of the process. i.e., if you have to ask, probably no.
For 3.6 to 3.9 (and soon 4.0), it just isn't that big a deal to do it
"right".
Nick.
[*] SOME of the things you should make sure are "identical" to your
production machine:
disk layout
available disk space on each partition (pad out partitions as needed)
same versions of same applications
Same disk interface and network adapters
(I'm sure I'm forgetting some important things here...)
