On Sun, 2002-03-24 at 18:58, Ethan Benson wrote:
> bad plan, the bootloader will be overwritten as soon as swap is
> activated, and you will probably end up crashing your system when you
> scribble part of the active swap with lilo.
> his only options are put lilo in the MBR, or create a small ext2
> partition to hold lilo (such as /boot). i recommend MBR it will not
> cause problems with dual booting, just read the lilo.conf man page.
> lilo should really have a check added to see if the partition its
> going to install on has an XFS superblock, as far as linux filesystems
> go XFS is unique in that it doesn't have 1K of space left alone at the
> start of the partition for bootblocks. should be a trivial 2 or 3
> line change to lilo which would save a few people a lousy day i imagine.
That's what i thought about using swap...that the loader would get
wiped, not that my swap is used a lot these days (1gig of ram helps).
I grabbed latest LILO and put it on MBR (they way i intended to do it
long time ago).It works all fine now for both XFS on / and win2k.
But teh thing is that it all worked till now,LILO was happy and so was
XFS...unless i had done it all wrong.Now i wonder wheater to report this
to LILO maintainer and hope it will get fixed/changed?
( http://www.linuxdiscussions.org )
Description: This is a digitally signed message part