Hi !

If we have a script for installing a new kernel, the goal is to have a
'standard' way for this, a method that everyone use, a real STANDARD.
If you choose to not use this way and do your method, it's your system and your
choice.
The goal of a standard is to provide to everyone a commom configuration to help
future actions. I think we could not cope with hundred of 'personal' way to name
 the kernel or install a new one, or renaming an old one.
With such a 'standard', your friend will never erased an old kernel, or
something like this (because this will be automatic, and we can implement an
archive system).
But don't miss understand me, your method is good, and it could be choosen to be
 the standard script ;-))
We just need ONE simple method.
I hope that I'm not too agressive ;-))

Thanks.

----- Original Message -----
From: "Bill Studenmund" <wrstuden@nas.nasa.gov>
> Well, we'd have to agree on how to do the install. :-)
>
> My standard approach is to install the kernel as netbsd.NAME# (i.e.
> netbsd.EVERMEET14) and link that to netbsd.new. Then I boot the new
> kernel. If I'm happy, I link netbsd.new to netbsd. :-)
>
> It would be nice to be able to customize the install methods easily - like
> a site specific way. One of my co workers messed up some of the old
> kernels because he used a different approach. With a site-specific install
> hook, he'd have done the same thing I did, and all would be well. ;-)


___________________________________________________________________________

L'integrite de ce message n'etant pas assuree sur Internet, la societe 
ne peut etre tenue responsable de son contenu.
Si vous n'etes pas destinataire de ce message, merci de le detruire et 
d'avertir l'expediteur.

The integrity of this message cannot be guaranteed on the Internet. 
The society cannot therefore be considered responsible for the contents.
If you are not the intended recipient of this message, then please delete 
it and notify the sender.