Very Computer

by **John in S** » Tue, 27 Mar 2001 09:32:41

Why not use LILO as your boot manager?

suggested lilo.conf: (lilo 21.2 or later REQUIRED)

===================================
boot=/dev/hda
prompt
timeout=50
lba32 <-- you WILL need this line; you have big disks
default=Win98 <-- use whichever default you like
disk=/dev/hdc <-- these two lines may, or may not, be needed
bios=0x81 <-- "

image=/boot/vmlinuz
label=linux
root=/dev/hdc1
read-only

other=/dev/hda1
label=Win98
===================================

I assume that your BIOS makes drive /dev/hdc1 available as 0x81.

--John

>#the questions are marked with '***' (three asterisks)
>#the other stuff is here only to make the message longer ;)

>My computer was/is running W98SE (oem), and I installed RH7 on top of it,
>conf. as follows:

>/dev/hda1 -- W98 -- fat32 -- 10GB
>/dev/hdb -- CDROM -- iso*
>/dev/hdc1 -- Linux -- ext2fs -- 20GB
>/dev/hdd5 -- file archive -- fat32 -- 2GB
>+swap

>When I started the install, I switched drives for BIOS to boot to Linux (on
>/dev/hda - the only option available - referred to as drive C: in BIOS) ,
>where I planned to install LILO(for more information look at the table
>below) and everything worked fine, until I tried LILO to boot W98, then it
>hanged, saying booting windows...

>The trouble seemed to be, that W98 would only boot as /dev/hda (primary
>master), so I switched the drives back. Now, not wanting to install LILO in
>/dev/hda (it being a windoze drive and all), I set up W98 to display boot
>menu with choices, which OS to boot - using loadlin.exe to boot Linux.
>Command to invoke Linux is as follows: "shell=c:\loadlin\loadlin.exe
>c:\loadlin\vmlinuz2 mem=128M root=/dev/hdc1 ro"

>*** The questions are: "If I installed LILO on /dev/hdc1 (currently on
>/dev/hdc (MBR) as installed since the drive was /dev/hda), booted to Linux
>using loadlin.exe, would it first run LILO (for kernel testing etc.) and use
>the kernel image defined there, or would it still use the kernel image on
>/dev/hda1 (W98 drive - for loadlin.exe to find it)? Would it be worth the
>hassle, or should I just copy a new compiled kernel image to the appropriate
>directory on /dev/hda1 and rewrite the startup menu?"

>TABLE1:
>"which drives were where" aka 'changelog'
>===
>at first i had only w98
>---
>/dev/hda1 -- W98 -- fat32 -- 10GB
>/dev/hdd -- CDROM -- iso*
>/dev/hdc5 -- file archive -- fat32 -- 2GB
>===
>bought a hd and installed rh7
>---
>/dev/hda1 -- Linux -- ext2fs -- 20GB
>/dev/hdb5 -- file archive -- fat32 -- 2GB
>/dev/hdc1 -- W98 -- fat32 -- 10GB
>/dev/hdd -- CDROM -- iso*
>+swap
>===
>switched the drives back
>---
>/dev/hda1 -- W98 -- fat32 -- 10GB
>/dev/hdb -- CDROM -- iso*
>/dev/hdc1 -- Linux -- ext2fs -- 20GB
>/dev/hdd5 -- file archive -- fat32 -- 2GB
>+swap

LILO version 21.7 (24-Feb-2001) source at
http://www.ibiblio.org/pub/Linux/system/boot/lilo
patches to -2 at ftp://brun.dyndns.org/pub/linux/lilo

by **Chie** » Wed, 28 Mar 2001 03:26:01

24 Mar 2001 21:45 UTC, Taavi Hein did say to the dudes:
[snip]

Quote:> *** The questions are: "If I installed LILO on /dev/hdc1 (currently on
> /dev/hdc (MBR) as installed since the drive was /dev/hda), booted to Linux
> using loadlin.exe, would it first run LILO (for kernel testing etc.) and use
> the kernel image defined there, or would it still use the kernel image on
> /dev/hda1 (W98 drive - for loadlin.exe to find it)? Would it be worth the
> hassle, or should I just copy a new compiled kernel image to the appropriate
> directory on /dev/hda1 and rewrite the startup menu?"

Just wondering if the best thing to do (with loadlin), would be to copy
your kernel to /dev/hda1 and fire up Loadlin with something like;

c:\path\to\kernel compact root=/dev/hdc1 ro

--

by **Chie** » Thu, 29 Mar 2001 02:16:48

26 Mar 2001 18:26 UTC, Chiefy did say to the dudes:

Quote:> Just wondering if the best thing to do (with loadlin), would be to copy
> your kernel to /dev/hda1 and fire up Loadlin with something like;

> c:\path\to\kernel compact root=/dev/hdc1 ro

Just noticed the error. Missed loadlin off the front !!!

c:\path\to\loadlin c:\path\to\kernel compact root=/dev/hdc1 ro

--

Corduroy pillows - They're making headlines!

by **Bloody Viki** » Thu, 05 Apr 2001 13:47:36

: Why not use LILO as your boot manager?

Maybe becuse he couldn't get it to work? I use Loadlin as my standard Linux
booter too. LILO is problematical becuse of hard drive geometry and many
computers have flaky BIOSes.

--
FOOD FOR THOUGHT: 100 calories are used up in the course of a mile run.
The USDA guidelines for dietary fibre is equal to one ounce of sawdust.
The liver makes the vast majority of the cholesterol in your *stream.

by **Bloody Viki** » Thu, 05 Apr 2001 13:51:46

: Just wondering if the best thing to do (with loadlin), would be to copy
: your kernel to /dev/hda1 and fire up Loadlin with something like;

: c:\path\to\kernel compact root=/dev/hdc1 ro

You can put the line into a one-liner batch script. On my box on the C:\HOME\
dir is a file named UNIX.BAT that starts Loadlin.

--
FOOD FOR THOUGHT: 100 calories are used up in the course of a mile run.
The USDA guidelines for dietary fibre is equal to one ounce of sawdust.
The liver makes the vast majority of the cholesterol in your *stream.

Very Computer

LILO vs. loadlin

LILO vs. loadlin

LILO vs. loadlin

LILO vs. loadlin

LILO vs. loadlin

LILO vs. loadlin