On Sat, Apr 14, 2007 at 01:23:13PM +0100, John Pilkington wrote: > A new FC5 kernel has just appeared in the system. Smart 'upgrade all' > installs it and sets it as default. A default boot then spells trouble > before the appropriate kmdls have arrived, so after installation I > revert to the old version using system-config-boot. > > There's no real problem, and I have no doubt that this is an old > question, but is it really best to update the default boot as soon as a > new kernel is installed?
Since there is no real heads-up for 3rd party repos, there will always be a delay. I learn about the new kernel the same way everybody else does. There is an updates-testing repo that is supposed to carry new packages before they make it into the proper updates, but the kernels have shown to have last minute fixed that make any pre-built kmdls based on the updates-testing repo rather useless. Although that was not the case with today's kernels, they were in updates-testing a day earlier than in updates-released. So, what can you do, you can o either wait for 3rd parties to prepare their kmdls o use an self-rebuilding system like dkms o rpmbuild --rebuild yourself from the src.rpm It usually takes only a couple of hours after the new kernel updates make it to the public until 3rd party repos offer new modules. So, if you go for waiting, then I'd say wait a day and you'll be fine. -- Axel.Thimm at ATrpms.net
pgptau0FawkS7.pgp
Description: PGP signature
_______________________________________________ atrpms-users mailing list [EMAIL PROTECTED] http://lists.atrpms.net/mailman/listinfo/atrpms-users
