Matthew Denson said:
>Do I just change /etc/lilo.conf? Or, do I change it and then run lilo? Is
>lilo automatically run because the /etc/lilo.conf file is modified?
Nope, there's no process watching lilo.conf and running lilo whenever it gets
changed. Any time you edit lilo.conf, you _always_ hav
Hi,
Sorry to butt in here, but I'm a little unclear on this, and I'm having
similar problems myself.
>To install Lilo in the MBR of the primary/master drive (/dev/hda), you
>need this line in your /etc/lilo.conf:
>
>boot=/dev/hda
>
>A minimum lilo.conf in your case (with no menu or boot prompt) m
To install Lilo in the MBR of the primary/master drive (/dev/hda), you
need this line in your /etc/lilo.conf:
boot=/dev/hda
A minimum lilo.conf in your case (with no menu or boot prompt) might be:
boot=/dev/hda
root=/dev/hdb1
install=/boot/boot.b
map=/boot/map
read-only
image=/path/to/your/kerne
A quick follow-up to my own query, with a bit more info. I wrote:
> I have two HD's, /dev/hda is the master, but Linux is installed on
> /dev/hdb. ... I can't seem to figure out how to get LILO to put the
> boot stuff on /dev/hda and then start up Linux on /dev/hdb.
The partition info for my d
I have two HD's, /dev/hda is the master, but Linux is installed on
/dev/hdb. Originally, the master drive was DOS, and I used loadlin to
start Linux on the second HD. Something fatal happened to my original
DOS HD, so now I've put a new HD in its place, made it ext2, and mounted
it as extra spac
5 matches
Mail list logo
