On Thu, Aug 07, 2014 at 08:21:14PM +0200, Pascal Hambourg wrote:
> > Kernel modules that are needed for the boot process itself reside in the
> > initrd, and he copies that.
>
> For the *early* boot process. I.e. mounting the root filesystem and not
> much else.
Indeed. So, considering worst case
Reco a écrit :
> Hi.
>
> On Wed, Aug 06, 2014 at 10:06:46AM +0200, Pascal Hambourg wrote:
>> Marc Auslander a écrit :
>>>
>>> I just manually copy the four files in /boot associated with the
>>> working kernel. I append -knowngood to get new names. update grup
>>> happily makes boot entries for
ph> Don't confuse installing a new kernel (3.2 and 3.12 are different
ph> kernels, different packages names) and upgrading an installed
ph> kernel with a new release (same version, same package name,
ph> different package release versions). Upgrading an installed kernel
ph> package replac
Hi.
On Wed, Aug 06, 2014 at 10:06:46AM +0200, Pascal Hambourg wrote:
> Marc Auslander a écrit :
> > Andrei POPESCU writes:
> >
> >> On Sb, 02 aug 14, 12:11:43, Kenneth Jacker wrote:
> >>> [ Wheezy; 3.2.0-4-amd64 ]
> >>>
> >>> I've noticed that when I upgrade a kernel image, the prior one appea
Marc Auslander a écrit :
> Andrei POPESCU writes:
>
>> On Sb, 02 aug 14, 12:11:43, Kenneth Jacker wrote:
>>> [ Wheezy; 3.2.0-4-amd64 ]
>>>
>>> I've noticed that when I upgrade a kernel image, the prior one appears
>>> to be removed. So, at any time there is only one kernel image in /boot.
>
>
Andrei POPESCU writes:
> On Sb, 02 aug 14, 12:11:43, Kenneth Jacker wrote:
>> [ Wheezy; 3.2.0-4-amd64 ]
>>
>> I've noticed that when I upgrade a kernel image, the prior one appears
>> to be removed. So, at any time there is only one kernel image in /boot.
>
I just manually copy the four files
On Sb, 02 aug 14, 12:11:43, Kenneth Jacker wrote:
> [ Wheezy; 3.2.0-4-amd64 ]
>
> I've noticed that when I upgrade a kernel image, the prior one appears
> to be removed. So, at any time there is only one kernel image in /boot.
Let's distinguish between package names and versions.
Currently the
Le 03/08/2014 20:32, Lisi Reisz a écrit :
On Sunday 03 August 2014 17:10:33 Pascal Hambourg wrote:
Don't confuse installing a new kernel (3.2 and 3.12 are different
kernels, different packages names) and upgrading an installed kernel
with a new release (same version, same package name, differen
On Sun, 3 Aug 2014 19:32:09 +0100
Lisi Reisz wrote:
Hello Lisi,
>I have the impression, however, that when other packages are
>"upgraded" (moved on to a higher version) the previous package *is*
>removed.
For the most part, that's true. With kernels though, removing a
previous one is considere
On Sunday 03 August 2014 17:10:33 Pascal Hambourg wrote:
> Le 03/08/2014 11:58, Lisi Reisz a écrit :
> > And on my Debian Wheezy system. I have four kernels, including three
> > from Backports: 3.2, 3.12, 3.13, 3.14. I have removed 3.10 and 3.11. I
> > originally installed 3.10 from Backports.
>
Le 03/08/2014 11:58, Lisi Reisz a écrit :
And on my Debian Wheezy system. I have four kernels, including three from
Backports: 3.2, 3.12, 3.13, 3.14. I have removed 3.10 and 3.11. I
originally installed 3.10 from Backports.
Upgrading never seems to remove a kernel and never has.
Don't conf
On Sun, Aug 03, 2014 at 10:58:10AM +0100, Lisi Reisz wrote:
> On Sunday 03 August 2014 01:38:56 Chris Bannister wrote:
> > Weird. So on these systems there are old packages which haven't been
> > removed by the package manager?
>
> And on my Debian Wheezy system. I have four kernels, including th
On Sunday 03 August 2014 01:38:56 Chris Bannister wrote:
> Weird. So on these systems there are old packages which haven't been
> removed by the package manager?
And on my Debian Wheezy system. I have four kernels, including three from
Backports: 3.2, 3.12, 3.13, 3.14. I have removed 3.10 and 3
>I've noticed that when I upgrade a kernel image, the prior one appears
>to be removed. So, at any time there is only one kernel image in /boot.
As stated by others; certainly old kernel is not removed after upgrade, you
might be doing something
tricky..
On Sat, Aug 2, 2014 at 9:41 PM, Kenneth
On Sat, Aug 02, 2014 at 12:11:43PM -0400, Kenneth Jacker wrote:
> [ Wheezy; 3.2.0-4-amd64 ]
>
> I've noticed that when I upgrade a kernel image, the prior one appears
> to be removed. So, at any time there is only one kernel image in /boot.
Updates are different to a new package install. On a n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 08/02/2014 12:11 PM, Kenneth Jacker wrote:
> [ Wheezy; 3.2.0-4-amd64 ]
>
> I've noticed that when I upgrade a kernel image, the prior one
> appears to be removed. So, at any time there is only one kernel
> image in /boot.
That doesn't happen
Ahoj,
Dňa Sat, 02 Aug 2014 12:11:43 -0400 Kenneth Jacker
napísal:
> [ Wheezy; 3.2.0-4-amd64 ]
>
> I've noticed that when I upgrade a kernel image, the prior one appears
> to be removed. So, at any time there is only one kernel image
> in /boot.
>
> Just in case (unlikely I know) a new kernel
[ Wheezy; 3.2.0-4-amd64 ]
I've noticed that when I upgrade a kernel image, the prior one appears
to be removed. So, at any time there is only one kernel image in /boot.
Just in case (unlikely I know) a new kernel has "problems", I'd like to
retain, say, the last three prior images in /boot. Ot
18 matches
Mail list logo
