kernel module fixes

[r0dzilla]

The other problem is not everyone uses lilo.

Maybe one piece of the puzzle would be a boot manager script that would
write the correct boot mgr config script.

This would probably require another lunar variable.
BOOTMGR=lilo
or
BOOTMGR=grub


I also imagine that we would need a kernel mgmt script that would change
the symlink to the new linux kernel and then call the bootmgr script to
update desired boot manager ( add an entry for the just-replaced kernel
and alter the default boot entry)

I would be willing to work on the boot manager part.

On Wed, 2003-10-01 at 20:10, Chuck Mead wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I am begging here and I admit it but... so be it!
> 
> For several months now I have been saying we need to do something about
> our kernel modules and now I am to the point of utter and total
> frustration with this.
> 
> So... here's what needs to happen... effective immediately no updates
> are to happen to anything at all until the kernel modules are fixed...
> this is our priority until it is done. If it means we have to adjust
> some things in the core to support it then so be it as a part of the
> priority it must be done.
> 
> Here is the desired end state...
> 
> When any kernel is built if there is a pre-existing kernel on the box in
> question that kernel, along with it's modules must be preserved on the
> file system *AND* in the lilo.conf or menu.lst. This is an absolute must
> and not something that is any longer negotiable. It is absolutely
> incomprehensible to me that we can even consider dumping an old kernel
> before the new one has been tested... we're running remote hosts guys...
> and in some cases they are a long ways off... we have *GOT* to "safe"
> this process ASAP.
> 
> So... if nobody has any ideas about how to go about this lets discuss it
> via email or in lunar-dev and come up with a plan we can execute.
> Honestly, at this point if we simply preserved them somehow with
> scripting even outside installwatch that would be better than the risk
> we take now!
> 
> - --
> csm
> Lunar Project Lead
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE/e2zgq3bny/5+GAcRAk4FAJ9zULI6kplwIgncw31m93PCLstI1wCffLQ1
> SfYq9WHfXGqpU/b9OyAY+Xk=
> =D2Jv
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> lunar-dev mailing list
> lunar-dev at lunar-linux.org
> http://dbguin.lunar-linux.org/mailman/listinfo/lunar-dev