Re: LI for LILO or loading from a second harddrive
Subject: Re: LI for LILO or loading from a second harddrive Date: Mon, Jan 10, 2000 at 04:42:29PM +0100 In reply to:[EMAIL PROTECTED] Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]): | LILO can only boot Opertive Systems located in primary partitions | (max 4) and located in the first hard drive that usually is /dev/hda . | | Bye bye. This fact has been uttered before. The problem is, is isn't correct. My potato dist is in a 1 gug partion on hdb10. That is an extended partition and LILO boot it just fine. While I'm at it. lorenzo, please cease sending me your auto answer message about having received messages I post to the list. I really don't need the spam. -- Who's General Failure and why's he reading my disk? ___
Re: LI for LILO or loading from a second harddrive
On 08-Jan-2000, Bryan Scaringe [EMAIL PROTECTED] wrote: Lilo must be installed in the MBR of /dev/hda. That is where your BIOS looks to boot your system. change your boot line to look like: boot=/dev/hda This will install LILO in the MBR of /dev/hda. LILO can *boot* things pretty much anywhere in your system (like /dev/hdc1) but it must be located where the BIOS looks (generally the boot sector of your first floopy drive, or the MBR of your first Hard disk. I am not sure about that, here is my setup for lilo at home, where the NT bootmanager is in charge, and all it needs to now is how to boot from the start of the partition. boot=/dev/hda5 root=/dev/hda5 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 append=mem=20M image=/vmlinuz label=linux read-only image=/vmlinuz.new label=new read-only image=/vmlinuz.old label=old read-only Pete
Re: LI for LILO or loading from a second harddrive
LILO can only boot Opertive Systems located in primary partitions (max 4) and located in the first hard drive that usually is /dev/hda . Bye bye. -- Memo - Header --- To: Bryan Scaringe [EMAIL PROTECTED] cc: Arcady Genkin [EMAIL PROTECTED] debian-user@lists.debian.org From: Peter Ross [EMAIL PROTECTED] Date: 10/01/2000 12.35.04 GMT 10/01/2000 15.49.36 Subject: Re: LI for LILO or loading from a second harddrive - Memo - Message -- On 08-Jan-2000, Bryan Scaringe [EMAIL PROTECTED] wrote: Lilo must be installed in the MBR of /dev/hda. That is where your BIOS looks to boot your system. change your boot line to look like: boot=/dev/hda This will install LILO in the MBR of /dev/hda. LILO can *boot* things pretty much anywhere in your system (like /dev/hdc1) but it must be located where the BIOS looks (generally the boot sector of your first floopy drive, or the MBR of your first Hard disk. I am not sure about that, here is my setup for lilo at home, where the NT bootmanager is in charge, and all it needs to now is how to boot from the start of the partition. boot=/dev/hda5 root=/dev/hda5 compact install=/boot/boot.b map=/boot/map vga=normal delay=20 append=mem=20M image=/vmlinuz label=linux read-only image=/vmlinuz.new label=new read-only image=/vmlinuz.old label=old read-only Pete -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: LI for LILO or loading from a second harddrive
[EMAIL PROTECTED] wrote: LILO can only boot Opertive Systems located in primary partitions (max 4) and located in the first hard drive that usually is /dev/hda . Bye bye. This is not correct as stated. Here is an informative item : http://www.heise.de/ct/english/99/12/166/ I quote a relevant section : If the MBR was created by a boot manager which can start operating systems from an extended partition (a partition which has been divided into logical drives) or from a logical drive, it may make sense to install Lilo in the boot sector of an extended partition or a logical drive. Lilo itself is such a boot manager - an MBR Lilo has no problems with starting another Lilo in the boot sector of a logical drive. Cheers, -- Howard Mann Online Troubleshooting Resources: HOWTO http://www.newbielinux.comhttp://www.xmission.com/~howardm/t1.html
RE: LI for LILO or loading from a second harddrive
Lilo must be installed in the MBR of /dev/hda. That is where your BIOS looks to boot your system. change your boot line to look like: boot=/dev/hda This will install LILO in the MBR of /dev/hda. LILO can *boot* things pretty much anywhere in your system (like /dev/hdc1) but it must be located where the BIOS looks (generally the boot sector of your first floopy drive, or the MBR of your first Hard disk. Bryan On 08-Jan-2000 Arcady Genkin wrote: I've installed potato on the second harddrive. Lilo won't boot from the HD (hangs at LI prompt). I can boot from the boot floppy just fine. My lilo.conf and the disk layout are quoted below. I tried adding linear and compact (interchangeably) to lilo.conf, as well as changing line boot=/dev/hdc for boot=/dev/hdc1, but the problem is still the same. FWIW, I'm using a third-party multybooter (BootMagic), but it picks out Linux installation on the second drive just fine. Also, since LILO does get started, I assume that the problem is with my LILO configuration, rather than with the mutlibooter's. I belive that during installation I chose to install lilo into MBR on /dev/hdc. The drive is an IBM's 13G, connected as an only drive on secondary IDE controller. Root is a primary partition in the very beginning of the drive, and is only 100M big. I'm stuck not being able to use custom kernel. :^( Any input greately appreciated! ,[ mount output ] | /dev/hdc1 on / type ext2 (rw,errors=remount-ro,errors=remount-ro) | /dev/hdc5 on /tmp type ext2 (rw) | /dev/hdc6 on /var type ext2 (rw) | /dev/hdc4 on /usr type ext2 (rw) | /dev/hda5 on /mnt/slink_local type ext2 (rw) | /dev/hda4 on /mnt/slink_root type ext2 (rw) | proc on /proc type proc (rw) ` ,[ lilo.conf ] | boot=/dev/hdc | root=/dev/hdc1 | install=/boot/boot.b | map=/boot/map | delay=200 | vga=normal | | image=/vmlinuz |label=default |read-only | | image = /zImage | label = linux | read-only ` -- Arcady Genkin http://www.thpoon.com -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
LI for LILO or loading from a second harddrive
I've installed potato on the second harddrive. Lilo won't boot from the HD (hangs at LI prompt). I can boot from the boot floppy just fine. My lilo.conf and the disk layout are quoted below. I tried adding linear and compact (interchangeably) to lilo.conf, as well as changing line boot=/dev/hdc for boot=/dev/hdc1, but the problem is still the same. FWIW, I'm using a third-party multybooter (BootMagic), but it picks out Linux installation on the second drive just fine. Also, since LILO does get started, I assume that the problem is with my LILO configuration, rather than with the mutlibooter's. I belive that during installation I chose to install lilo into MBR on /dev/hdc. The drive is an IBM's 13G, connected as an only drive on secondary IDE controller. Root is a primary partition in the very beginning of the drive, and is only 100M big. I'm stuck not being able to use custom kernel. :^( Any input greately appreciated! ,[ mount output ] | /dev/hdc1 on / type ext2 (rw,errors=remount-ro,errors=remount-ro) | /dev/hdc5 on /tmp type ext2 (rw) | /dev/hdc6 on /var type ext2 (rw) | /dev/hdc4 on /usr type ext2 (rw) | /dev/hda5 on /mnt/slink_local type ext2 (rw) | /dev/hda4 on /mnt/slink_root type ext2 (rw) | proc on /proc type proc (rw) ` ,[ lilo.conf ] | boot=/dev/hdc | root=/dev/hdc1 | install=/boot/boot.b | map=/boot/map | delay=200 | vga=normal | | image=/vmlinuz | label=default | read-only | | image = /zImage | label = linux | read-only ` -- Arcady Genkin http://www.thpoon.com
