Re: [expert] LILO doesn't recognize default label
Right--if you have your IDE drives set up to use LBA mode then the 1024 "limit" is not an issue for LILO (older version). It is only if you are not using LBA that you need to worry about this. Norm Ron Stodden wrote: > Mark Weaver wrote: > > > This is just a basic partition map for large drives, but the MOST > > essential partition, and the one that is a MUST is the /boot partition. > > Not a MUST at all these days. For people with large physical drives > set up LBA, and who keep bootable partitions on low logical numbers > or who use the latest LILO (which has no 1024 cylinder limit) the > best move is to put all of Linux in the one partition (the Mandrake > installer supports this), and so totally avoid the constant problem > of partition resize rejuggling. > > There is NO need or value in having a separate /boot partition these > days. > > -- > Regards, > > Ron. [AU] - sent by Mandrake Linux. > To write a poem in 17 syllables is very diffic >
Re: [expert] LILO doesn't recognize default label
That's wonderful if you happen to be running the new version of LILO, however the new version of LILO isn't shipping with any of the latest distros of either RedHat, or Mandrake. Instead it looks as if they're offering Grub instead. I personally prefer LILO. That's just what I'm used to and if it ain't broken I can't see any reason to fix it. Actually it isn't all that big a deal to carve out a small chunk for /boot. In fact, it seems to help the system boot faster. At least that's been my experience with doing it that way. And I've done it both ways. ACtually I'm surprised that they have'nt offered the updated version of LILO on the Mandrake "update" utility listing with the rest of the system updates. That might be worth adding to the list for people to take a look at. Mark John Aldrich wrote: > > On Mon, 31 Jul 2000, you wrote: > > it sounds like you have the > 1024 syndrome. If you haven't done a lot to > > your system yet as far as moving in and settling down you may want to > > re-install Linux. LILO doesn't work well on Large HDD's unless you use a > > 10-15MB /boot partition. LILO will work perfectly then. You would > > partition your drive in a manner something like this. > > > This is incorrect. The new version of LILO doesn't care WHERE the > kernel is located. > John
Re: [expert] LILO doesn't recognize default label
On Mon, 31 Jul 2000, you wrote: > it sounds like you have the > 1024 syndrome. If you haven't done a lot to > your system yet as far as moving in and settling down you may want to > re-install Linux. LILO doesn't work well on Large HDD's unless you use a > 10-15MB /boot partition. LILO will work perfectly then. You would > partition your drive in a manner something like this. > This is incorrect. The new version of LILO doesn't care WHERE the kernel is located. John
Re: [expert] LILO doesn't recognize default label
Mark Weaver wrote: > This is just a basic partition map for large drives, but the MOST > essential partition, and the one that is a MUST is the /boot partition. Not a MUST at all these days. For people with large physical drives set up LBA, and who keep bootable partitions on low logical numbers or who use the latest LILO (which has no 1024 cylinder limit) the best move is to put all of Linux in the one partition (the Mandrake installer supports this), and so totally avoid the constant problem of partition resize rejuggling. There is NO need or value in having a separate /boot partition these days. -- Regards, Ron. [AU] - sent by Mandrake Linux. To write a poem in 17 syllables is very diffic
Re: [expert] LILO doesn't recognize default label
On Mon, Jul 31, 2000 at 08:19:26PM -0400, Mark Weaver wrote: Or you can try the lilo from cooker which, I believe, doesn't have problems with >1024 anymore. > it sounds like you have the > 1024 syndrome. If you haven't done a lot to > your system yet as far as moving in and settling down you may want to > re-install Linux. LILO doesn't work well on Large HDD's unless you use a > 10-15MB /boot partition. LILO will work perfectly then. You would > partition your drive in a manner something like this. > > /boot = 15MB > > /home = at least 300MB or more if you have multiple users > > / = no less than 1GB or the remainder of your drive or however > much space you intend to allow your Linux system if you're dual > booting. > > By using a small /boot partition (which should be the first partition that > you define) you're staying within the 1024 cyclinder requirment of > LILO. LILO can't see beyond that distance. > > This is just a basic partition map for large drives, but the MOST > essential partition, and the one that is a MUST is the /boot partition. > > -- > Mark > > ** Registered Linux user # 182496 ** > > > > On Mon, 31 Jul 2000, Marco Fioretti wrote: > > > Hello, > > I just installed Mandrake 7.1, and it looks great, except one or two issues. > > > > The most important is with LILO. When I power up, LILO starts, greets me, > > telling that it will boot the default image in 5 seconds, but nothing happens. > > If *I* type linux, LILO boots fine, and the system works great. I have an 8.4 > > GBYTE HD, partitioned as follows > > > > swaphda5240 MB cyl 0-30 > > / hda6300 MB cyl 31-68 > > /usrhda73 GIG following > > /home/ hda84.5 GIG following > > > > It was done this way by the installation software. /etc/lilo.conf follows. > > > > Any help is appreciated. > > > > Thank you, > > Marco > > > > boot=/dev/hda > > map=/boot/map > > install=/boot/boot.b > > vga=normal > > default=linux > > keytable=/boot/us.klt > > lba32 > > prompt > > timeout=50 > > message=/boot/message > > image=/boot/vmlinuz-secure > > label=linux > > root=/dev/hda6 > > initrd=/boot/initrd-secure.img > > read-only > > image=/boot/vmlinuz > > label=linux-up > > root=/dev/hda6 > > initrd=/boot/initrd.img > > read-only > > image=/boot/vmlinuz > > label=failsafe > > root=/dev/hda6 > > initrd=/boot/initrd.img > > append=" failsafe" > > read-only > > > > > -- [EMAIL PROTECTED], OpenPGP key available on www.keyserver.net Freezer Burn BBS: telnet://bbs.freezer-burn.org . ICQ: 54924721 Webmaster for the Linux Portal Site Freezer Burn: http://www.freezer-burn.org Current Linux uptime: 2 days 2 hours 58 minutes.
Re: [expert] LILO doesn't recognize default label
it sounds like you have the > 1024 syndrome. If you haven't done a lot to your system yet as far as moving in and settling down you may want to re-install Linux. LILO doesn't work well on Large HDD's unless you use a 10-15MB /boot partition. LILO will work perfectly then. You would partition your drive in a manner something like this. /boot = 15MB /home = at least 300MB or more if you have multiple users / = no less than 1GB or the remainder of your drive or however much space you intend to allow your Linux system if you're dual booting. By using a small /boot partition (which should be the first partition that you define) you're staying within the 1024 cyclinder requirment of LILO. LILO can't see beyond that distance. This is just a basic partition map for large drives, but the MOST essential partition, and the one that is a MUST is the /boot partition. -- Mark ** Registered Linux user # 182496 ** On Mon, 31 Jul 2000, Marco Fioretti wrote: > Hello, > I just installed Mandrake 7.1, and it looks great, except one or two issues. > > The most important is with LILO. When I power up, LILO starts, greets me, > telling that it will boot the default image in 5 seconds, but nothing happens. > If *I* type linux, LILO boots fine, and the system works great. I have an 8.4 > GBYTE HD, partitioned as follows > > swap hda5240 MB cyl 0-30 > / hda6300 MB cyl 31-68 > /usr hda73 GIG following > /home/hda84.5 GIG following > > It was done this way by the installation software. /etc/lilo.conf follows. > > Any help is appreciated. > > Thank you, > Marco > > boot=/dev/hda > map=/boot/map > install=/boot/boot.b > vga=normal > default=linux > keytable=/boot/us.klt > lba32 > prompt > timeout=50 > message=/boot/message > image=/boot/vmlinuz-secure > label=linux > root=/dev/hda6 > initrd=/boot/initrd-secure.img > read-only > image=/boot/vmlinuz > label=linux-up > root=/dev/hda6 > initrd=/boot/initrd.img > read-only > image=/boot/vmlinuz > label=failsafe > root=/dev/hda6 > initrd=/boot/initrd.img > append=" failsafe" > read-only > >
