On Wed, May 01, 2002 at 04:53:42PM +1000, Matthew Hannigan wrote: > John Clarke wrote: > > > I don't agree. If installing a kernel package overwrites my lilo config > > I'd call *that* a bug. I never use the stock kernel; I always rebuild > > with my own config and then install, so the last thing I'd want is for > > the upgrade to force something other than my custom kernel to boot. > > Turn that around; imagine you are a newbie and installing > a kernel rpm did nothing at all. What use is that?! What > deity ordained that you must know about grub/lilo/milo blah blah > just because you want to upgrade your kernel so that you can > use your nice new video camera?
OK, fair point. I still don't want it to touch *my* lilo.conf. How about a compromise: rather than automatically upgrade lilo.conf, prompt the user (I wouldn't complain if the default was `yes', as long as I could say `no'). It could even provide the option of rebooting into the new kernel immediately (but only if the update to lilo.conf could be done and lilo ran OK). > It's been said before; the experienced can look after themselves; > let the computer do whatever it can do for you that can make your > life easier. Try to have the computer do too much to try to make life easier and you'll end with something like Windows. Change that to: have the computer do what it reasonably can to make life easier for the inexperienced user without making it impossible for the experienced user, and I'll agree with you. Cheers, John -- whois [EMAIL PROTECTED] GPG key id: 0xD59C360F http://kirriwa.net/john/ -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
