Re: [Devil-linux-develop] Boot bug on latest 1.1.

[Heiko Z. <he...@zu...>]

Emmanuel ESCARABAJAL wrote:

> hi,
>
> Heiko Zuerker a écrit:
>
>> Tim Tait wrote:
>>
>>> Bruce Smith wrote:
>>>
>>>> I just downloaded devil-linux-1.1.1-2003-12-21-i586-SMP.tar.bz2 
>>>> (since I
>>>> didn't have a recent compile of my own at work), and installed it on a
>>>> new box.
>>>>
>>>> It booted up, ask me to copy a blank config to media (I said "y"), it
>>>> booted, I setup the box, ran save-config, and rebooted.  It came back
>>>> up, and I noticed that I didn't have a root password, which was set. I
>>>> also noticed my network wasn't setup, and NONE of my changes were 
>>>> there.
>>>> After repeating the process a couple times, I finally figured out that
>>>> the boot process was creating and reading my config on a local hard
>>>> drive (ext3 /dev/hda2), and save-config was saving to my USB stick on
>>>> /dev/sda1.
>>>>
>>>> - BS
>>>>  
>>>>
>>> I confused, why doesn't it write back to the same place it found it 
>>> on boot? AIR, the location is saved into a environment variable. 
>>> Can't that be preserved somehow and used in save-config?
>>
>>
>>
>> The reason is easy: initrd is already updated to use devfs and 
>> save-config is old (out-dated).
>> I still have to copy the specific part over to the save-config script.
>>
>> We could store the config location somewhere in the system and re-use 
>> it for save-config, but we would loose the flexibility of switching 
>> config devices while the system is up.
>> Any more thoughts/opinions about this ?
>
>
> Yes, add a parameter in /etc/sysconfig/config for the save-config 
> device to use ... 

I was more thinking about saving which devices we found in the initrd 
and re-using this.

But I like you idea almost better.
We could make the parameter in /etc/sysconfig/config optional:
  not defined: our script searches for the device
  defined: our script uses this device and fails if not present

Heiko