![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
> On Mon, 23 Jun 2008 19:06:51 -0400 > "David Hummel" <[hidden email]> wrote: > >> AFAIK there's no reliable >> mechanism to inform the apt system that a given kernel is really no >> longer needed. I'm guessing this is one reason you don't see a tool >> for this purpose, at least in Debian derivatives. Fedora's way of handling this is pretty sane I think: there's a yum plugin that implements a policy that at most 2 kernels will be installed at any given time. When updating, always leave the running kernel installed (since it's obviously able to at least boot and provide some functionality), and if necessary remove the other one. Kernels with special names (ie from the CCRMA repository or somesuch) don't fall under this policy (since they need to be manually installed anyway). The "only 2" rule only applies to distro-supplied kernel packages. Since distro-supplied kernel releases are typically bug-fixes, there's usually not any good reason to have more than two of them installed. Matt -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss