--- Ron Stodden <[EMAIL PROTECTED]> wrote:
...
> Probably a better way is to make a one-time global change, not stanza
> changes, thus avoiding the need for a disk on IDE0 to bring up lilo
> from and to hold the secondary boot loader. To do this insert the
> lilo 'lock' global command into lilo.conf, run lilo and reboot. At
> the prompt enter:
>
> linux ide0=0xfff0,0xffe6 ide1=0xffa8,0xffe2
>
> From now on, every boot will skip any delay, timeout and message
> commands and come up with the IDEs remapped as you requested and now
> 'locked in'. To go back, all you probably have to do is remove the
> lock command, run lilo and reboot, but I have not tried this yet.
> There is probably no way of discovering what was 'locked in', so you
> must keep meticulous manual records.
I don't really understand what you are trying to achieve here.
I don't have any drive at the mobo controller (what would normally be ide0
without the append string). The whole concept of ide0, ide1, ide2, and ide3 is
a *linux* concept, not really pertaining to lilo or the bios. The append string
is saved in the master boot record of the drive specified in the lilo.conf when
you run lilo, so there is no need to have a drive or a file system from where
to read the append string; so why use the lock command?
Now, from what drive does the machine boots (or read lilo for that matter), is
a whole other matter, but that's controlled by the bios, and has nothing to do
with lilo or linux. I guess that an intelligent bios will search all drives on
all ide channels until it finds one with a bootable master record, and then
boots from there.
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
