On Fri, 25 May 2007, Matej Vela wrote:
Mirsad Todorovac <[EMAIL PROTECTED]> writes:
During the upgrade to new kernel package it happened that I noted the
following:
1. package kernel-new was downloaded
2. kernel-old was removed
3. kernel-new was unpacked
4. kernel-new was setup
[...]
Actua
* Steve Langasek [Fri, 25 May 2007 11:36:25 -0700]:
> With current aptitude, this is not the case. There is a specific aptitude
> rule to exclude linux-image packages from "auto" handling.
Oh, cool. I didn't know about this.
Thanks,
--
Adeodato Simó dato at
On Fri, May 25, 2007 at 08:30:14PM +0200, Adeodato Simó wrote:
> * Matej Vela [Fri, 25 May 2007 20:16:44 +0200]:
> > Actually, Debian's kernel packages never remove old versions, they
> > simply pull in new ones.
> This is not the case in one particular scenario: one installs one of the
> kernel
* Matej Vela [Fri, 25 May 2007 20:16:44 +0200]:
> Actually, Debian's kernel packages never remove old versions, they
> simply pull in new ones.
This is not the case in one particular scenario: one installs one of the
kernel metapackages, eg. linux-image-686, with aptitude. The image that
gets ins
Mirsad Todorovac <[EMAIL PROTECTED]> writes:
> During the upgrade to new kernel package it happened that I noted the
> following:
>
> 1. package kernel-new was downloaded
> 2. kernel-old was removed
> 3. kernel-new was unpacked
> 4. kernel-new was setup
[...]
Actually, Debian's kernel packages ne
5 matches
Mail list logo