"Brian J. Murrell" <[EMAIL PROTECTED]> writes:
> Damn! I liked this! What is/was the problem with it? OK, how about a
> compromise? How about having %post look for a script, maybe in
do problems with DrakX. Ask pixel :).
> /usr/local/bin called "activate_kernel". If it's there, run it,
> passing the kernel version being installed. If people want the
> kernel install to activate their new kernel automagically, they can
> put the code in /usr/local/bin/activate_kernel. Those who don't
> want it done, don't have to use it.
i don't think it's too much ''distribution'' to do this. Well we have
better to do a script to do this :
parse the /etc/lilo.conf script :
get on which device lilo want to install .
check if lilo was installed on the device (if not do anything).
get the default entry.
backup the default entry and point to a old kernel
point the new entry to the new installed kernel.
regenerate lilo.
anyway we can hope with grub to solve this sort of problems.
--Chmouel
