Le 2014-03-07 11:21, Stuart Henderson a écrit :
On 2014/03/07 11:04, Jean-Philippe Luiggi wrote:
Hi everybody,

I follow "-current" for several years but recently a thing puzzles me.

My "x200" is a dual-boot system ("Seven"/OpenBSD "-current") and since (I 
think) the
"amd64/i386 installboot" change, each time I upgrade via "bsd.rd", I have to generate a new 
"openbsd.pbr" and  copy it to "Seven".

If I miss that, I get an "ERR M" and can't go further.

First I was thinking about changes but I checked code and last modification on 
boot(8) was made 2 weeks ago (I did 2 updates since it).

I used that setup for several years without any need to do that, what do I
miss here, is it now normal ?

Regards,

Jean-Philippe.



--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
For all your IT requirements visit: http://www.transtec.co.uk

The location of /boot (second-stage boot loader) is recorded in the
pbr so the 1st-stage can find it.

With the old method of cp + /usr/mdec/installboot, though it wasn't
guaranteed, /boot tended to stay in the same place on disk most of the
time:

# cp boot /; ./installboot -v /boot ./biosboot sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2344
# cp boot /; ./installboot -v /boot ./biosboot sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2344
# cp boot /; ./installboot -v /boot ./biosboot sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2344
# cp boot /; ./installboot -v /boot ./biosboot sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2344

Whereas new installboot tends to shift it around:

# installboot -v sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2344
# installboot -v sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 48, offset 16168
# installboot -v sd1 2>&1 | grep shift
fs block shift 2; part offset 64; inode block 56, offset 2472

Meaning that the pbr must be updated with the new location.



Hi Stuart,

This is pretty clear,  thanks a lot for explaining that. :)

Regards,

Jean-Philippe

--
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
For all your IT requirements visit: http://www.transtec.co.uk

Reply via email to