Can LILO do this too?
- From: no.top.post@xxxxxxxxx
- Date: Sat, 19 May 2012 14:23:38 +0000 (UTC)
Having grub setup to boot from a CompactFlash,
and then plugging eg. a USB disk before you boot,
means that the CF may change from being /dev/sdb,
to being /dev/sdc,
because the USB disk gets 'allocated in front of'
the CF -- apparently.
With grub, you can just 'live edit' the immediately
visible menu, from sdb to sdc.
Besides grub can access a device via its LABEL;
so it doesn't matter <where the device is located>.
What do you do if you've got LILO instead?!
How is it possible that a 'knl2.4 grub' can see
a knl2.4 originated ext2, but can't see a
knl2.6 originated ext2 ?
Since grub has got the various FS-drivers: ext2, ext3, js*,
one can understand that it couldn't read an ext3 if the
driver was missing; but aren't ALL ext2 equal, independant
of the kernel-version that created them?
What about different inode sizes, can grub handle all?
Of course, it's nice with grub: it shows you what IT can see,
because even before the OS has booted, grub can effectively
do a <fdisk -l>. But with LILO, you are in the dark.
The <old>-grub has some quirks.
Is it worth getting grub-2 -- for distributions designed for LILO?
I've got a little-known-slak-based distribution CD, which allows
<editing of the knl, initrd, vga ..etc> before booting, which seems
nice; but I'm confused, because I thought this distribution used LILO.
What does the <syslinux> system do?
- Prev by Date: Re: PPTP and NAT, IPSec and vpnc to Draytek Vigor
- Next by Date: Re: Can LILO do this too?
- Previous by thread: heads up on ASUS motherboards
- Next by thread: Re: Can LILO do this too?