On Mon, May 12, 2008 at 01:29:32PM -0700, Darrian Hale wrote:
> Thanks for your help,
>
> See additional comments below.
>
> -Darrian
> >
> > Just edit your disklabel, using the 'm' command.
>
> Thanks, this worked. After booting from 4.2 ramdisk kernel, i ran
> disklabel -E wd0
> I then modified the a partition and the default offset was a very large
> number,
> i changed this to 63 and kept the size the same. For the remainder of the
> partitions i just added the previous size and offset for the new offset.
>
> My real upgrade however needs to be remote, so I cannot boot the ramdisk
> kernel
> and perform these steps. For completeness, I did the following to make a
> remote
> upgrade work.
>
> 1. login to 4.1 system
> 2. copy 4.2 kernels and disklabel from 4.2 to system.
> 3. run 4.2 disklabel while still running 4.1 kernel and fix disklabel
> as described above.
> 4. reboot, it works and i can still remotely login to system which is
> now running a 4.2
> kernel with 4.1 userland.
> ** unexpectedly at this point, I can now boot either the 4.1 kernel or
> 4.2 kernel with the
> same 4.1 userland. It seems that after modifying the disk label with
> the 4.2 version of
> disklabel, that the 4.1 version still reads it properly. **
> 5. finish upgrade as described in openbsd upgrade FAQ.
I repeat, if your 4.1 disklabel is OK an never touched by a 4.2
kernel, a regular upgrade should work. You upgrade procedure above is
non-standard, and I have no idea if it will work in all cases.
-Otto
