[it seems my original post didn't make it]
Upgraded a 9.1 system with the 9.2B2 CD's yesterday and ran into a bug -
that stopped installation dead.
The system in question has always used grub as its bootloader (why would
you use anything else?). I've built many a custom kernel on this box,
and deleted old ones to make space.
9.2B2 wants to use lilo - so it grabs my old /etc/lilo.conf file and
adds the new stuff to it. Trouble is, /etc/lilo.conf is full of garbage
- all the old experimental kernels, for example.
Result - it fails. Solution - create appropriate symlinks to make it
think those kernels and initrd's are there. This got the installation
to complete.
I think we need to do a bit better than this, if the user is using lilo,
it'll work as is mostly. Unless they've deleted something from /boot;
in which case they have the same problem I had.
How about the perl script sanity checks things? Or we go with just the
new stuff and have a post install migration script for lilo?
Or just use grub :-)
/Kevin
--
Kevin J. Maciunas Net: [EMAIL PROTECTED]
Dept. of Computer Science Ph : +61 8 8303 5845
University of Adelaide Fax: +61 8 8303 4366
Adelaide 5005 SOUTH AUSTRALIA Web: http://www.cs.adelaide.edu.au/~kevin
Fingerprint = 7E5A A0C2 22BC 5993 17F2 93CE B1FD DEC6 D0C0 50CD