|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Alexander Hall (alexander
beard.se)
Date: Fri Feb 08 2008 - 03:39:57 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jean-Yves Boisiaud wrote:
> Alexander Hall wrote:
>> Jean-Yves Boisiaud wrote:
>>> Hello,
>>>
>>> I'm using OpenBSD with a Soekris NET4801.
>>> To make my job easy and more secure to upgrade software,
> If think that boot do not read /etc/boot.conf :
You might have missed the end of my last reply. Shortening this message
a bit to make it clear again in case you missed it.
>> The boot loader won't find your /etc/boot.conf at wd0b (searches at
>> wd0a, if I read boot.c, ..., dev_i386.c correctly).
>>
>> I guess you could patch it, but I'd say you are creating a monster.
>>
>> I still do not get the point of this exercise, but could not wd0a be
>> the default boot device and wd0b the alternative?
I now get the idea, but I think you need to always use the
/etc/boot.conf from wd0a, regardless of which partition is active.
One possible solution might be to use wd0a for /etc/boot.conf _only_,
and then use wd0d and wd0e for the alternating boot partitions. So,
after a successful update, you mount wd0a (which is otherwise unmounted)
and modify the "set device X" to the newly updated root partition.
BTW, how is the root partition handled in /etc/fstab? Or is the entire
system residing in the root partition?
/Alexander
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]