Michael Lake wrote:
> John Clarke wrote:
>
>>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).
Someone else mentioned that rpms are expected to install
completely non-interactively. I think thats a good thing.
Anyway I think that rpm already has the option you want; it's
something like
rpm --install --noconfig ....
>>
>>
>>>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.
>
> I can understand some want an auto upgrade and change the config files s
> they don't want want to edit them themselves or even wish to; others
> have their own customisations. One solution ;-)
>
> /etc/expertise/
> touch [ newbie | experienced | guru | wizard ]
>
> The upgrade process looks at the experience level directory. If newbie
> overwrite config; else if experienced ask etc etc.... :-)
>
I had thought the same thing myself, but I'm pretty much
convinced that too many choices like this reduce usability.
http://www.joelonsoftware.com/news/20020427.html
There usually IS a RIGHT way to do it.
It's nice to know that debian does the right thing.
Experts won't install kernel rpms anyway, they'll
pull down the tar ball or a kernel source rpm.
-Matt
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
