On Wednesday 12 October 2005 10:00, [EMAIL PROTECTED] wrote: > On 11 Oct, Terry Collins wrote: > > I think the original comparison was that lilo squarks when it can not > > understand something, so you have a chance of fixing minor problems > > before you end up with an non-bootable machine. > > Thanks, Terry. Yes, that was precisely my point. > > I confess I didn't understand James' comment: > > EG you've screwed up your grub config, end of world ? No just edit it and > > make it right and then try to boot again. > > > > All you need to do is install it correctly once ever!
Sorry to not be clear: I was trying to say if you've created an wrong grub.conf menu.lst etc then you can edit your command line and fix (but you can in lilo too) the try to boot again. In grub (correctly installed) you can always edit and boot (if you could boot) but with lilo if you omit to run lilo then you cannot boot from that disk Again assuming no backup/recover options ie 1 entry and a new kernel. [snip] > I think the bios is old (AMIBIOS (C) 2000), so probably doesn't have the > extensions. Yet other sluggers and the grub doco, says that doesn't > matter. E.g.: > http://www.redat.com/docs/manuals/linux/RHL-7.3-Manual/ref-guide/ch-grub.ht >ml > > GRUB supports Logical Block Addressing (LBA) mode. LBA places the > addressing conversion used to find files on the drive in the drive's > firmware, and it is used on many IDE and all SCSI hard disks. Before > LBA, hard drives could encounter a 1024-cylinder limit, where the BIOS > could not find a file after that point, such as a boot loader or kernel > files. LBA support allows GRUB to boot operating systems from > partitions beyond the 1024-cylinder limit, so long as the system BIOS > supports LBA mode (most do). > > So now I'm a bit confused, even though the evidence seems to be in your > favour. :-):-) I'm very confused too ... RH9 builds a default /boot under 1024, warns you that the bios may not support booting when you overide, uses grub. I've had a motherboad and disk that wont boot (using /boot < 1024 does work), same disk new motherboard does boot. I don't understand! I appologise if my experiences are contary to known science, and confused the issue. James -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
