[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: reinstall lilo after windows

On Mon, Sep 12, 2005 at 02:26:22PM -0700, Alvin Oga wrote:
> On Mon, 12 Sep 2005, Hendrik Boom wrote:
> > > vi lilo.conf
> > > 	boot = /dev/fd0
> > > 
> > > 	root = /dev/hda1
> > 
> > Won't that make it boot from /dev/hda1?
> no... it boots from floppy ( the MBR )

Poor choice of language.  Yes.  It boots the MBR on the floppy,
then tries to read the kernel, the initrd, and such from /dev/hda1.
But if the drive has been physically moved to /dev/hdc1, 
this won't do much good.

> it's told that /, /dev, /etc, /bin etc ( rootfs ) is on /dev/hda1
> >  How will it know to look on  /dev/hdc1 
> you tell it ...
> 	a) change lilo.conf  and rerun lilo

This one won't work, because when the drive is still /dev/hda1
I can't run lilo with the line root=/dev/hdc1 because there is
nothing to read there.  And After I've moved the drive, I can't
boot from /dev/hda1 to run lilo.  Until after I've run lilo there,
of course :-)

> 	or 
>  	b) at lilo prompt:  root=/dev/hdc1

I forgot about this one.  But doesn't lilo record the actual
device and block addresses of the kernel and initrd it is to load?
Wouldn't it expect them to be in their appointed places
on /dev/hda1 whether it is told root=/dev/hdc1 or not?
Can it actually do *anything* with /dev/hdc1 before it's
read the kernel form the appointed place -- the kernel that
will understand teh file system on /dev/hdc1?

> 	or
> 	gazillion other ways
> (where it will be after the hardware change?)
> wherever you want it to be including never never land
> if you want it to be a known state, you must know
> the state too .... every file, every option, every character
> in the file and the "characters" of the system that makes it boot
> into your "known/expected state"
> 	- if you dont know, .. it will do EXACTLY what
> 	"you" told it to do  or the system defaults per
> 	the gpl developers
> c ya
> alvin

Reply to: