Ken Moffat wrote:
I was missing that you swapped the cable. So, you have installed lilo
onto the disk while it is at /dev/sdb.
>
>
>>Question 3: My lilo.conf file looks like this:
>>root:/# cat /etc/lilo.conf
>># Begin /etc/lilo.conf
>># lilo.conf
>>#
>># global options
>>boot=/dev/sda
>>
>>
>
> To me, this is telling lilo to write the bootblock to the
>disk at sda - I don't understand how you managed to put this onto
>the correct disk from within chroot. I would expect that lilo would
>overwrite the mbr on the disk conected at sda (the FC5 drive) I
>would also expect that when you boot FC5 is uses grub ?
>
> Because you swap the disk from sdb to sda, this sounds like the
>situation I referred to yesterday where disk= and bios= were used,
>but I note that the current manpage says that the bios= option is
>now largely obsolete.
>
> I'm hesitant to advise how to procede, because your results are
>not what I expect, and I don't want to do anything that will
>overwrite the FC5 bootloader. You say you "swap" the cables - have
>you tried booting with ONLY the clfs drive connected ?
>
>
Hi Ken,
I can't remember for sure at the moment but I think the first time I
wrote the MBR the lilo.conf file said that boot=/dev/sdb. It may
actually have said /dev/sdb1. I have written the MBR quite a few times
since then and it's all running together now. I tried last night to use
the books command "lilo -v" and that with the current lilo.conf file did
in fact write the MBR to sda and over wrote the GRUB MBR. I did the
hexdump of the MBR before I wrote the MBR and again after and it was
then LILO not GRUB. I then replaced the LILO with the saved MBR in
/boot/boot.0080. I can still boot FC5 so I guess I recovered from what
could have been a very bad move. In later attempts to write the MBR I
have used command line switches to tell lilo to write the MBR to sdb. As
I'm typing this I'm thinking I might try to change the lilo.conf to make
boot=/dev/sdb then do the default "lilo -v" and see what that does. As
to your last paragraph I want yo hear what you would do next. I am
grasping at straws here and anything you say to do I will think about
and take full responsibility for. If I end up executing a command and
blowing everything away it's my fault not yours. I want to get this
system up and it can't be booted right now. If I do something to screw
it up I'll just start over. If that in fact does happen I would like
your input as to how to configure my system to do the build. So, if you
found yourself in the spot I'm in what would you do next? BTW, the
article I saw on the web said the last two bytes in the MBR were the
"signature" LILO was looking for. Do you agree with that? Does the lilo
source have the code for the MBR? Can I tell what it looks for? I don't
know x86 machine language instructions. Is there source for that or is
it just delivered in a binary that they load? Has anyone out there ever
disassembled it?
Arnie
_______________________________________________
Clfs-support mailing list
[email protected]
http://ninja.linux-phreak.biz/mailman/listinfo/clfs-support
