Re: How to ensure that old kernel does not get removed

2019-01-07 Thread David Wright
On Mon 07 Jan 2019 at 09:18:40 (-0500), songbird wrote: > Greg Wooledge wrote: > > On Sat, Jan 05, 2019 at 08:45:37AM -0500, songbird wrote: > >> APT::Clean-Installed "false"; > >> APT::NeverAutoRemove { "linux-image.*"; }; // packages that should never > >>

Re: How to ensure that old kernel does not get removed

2019-01-07 Thread songbird
Greg Wooledge wrote: > On Sat, Jan 05, 2019 at 08:45:37AM -0500, songbird wrote: >> APT::Clean-Installed "false"; >> APT::NeverAutoRemove { "linux-image.*"; }; // packages that should never >> // considered for autoRemove > > Yeah, personally I'm all

Re: How to ensure that old kernel does not get removed

2019-01-07 Thread Greg Wooledge
On Sat, Jan 05, 2019 at 08:45:37AM -0500, songbird wrote: > APT::Clean-Installed "false"; > APT::NeverAutoRemove { "linux-image.*"; }; // packages that should never > // considered for autoRemove Yeah, personally I'm all about that Never Auto Remove.

Re: How to ensure that old kernel does not get removed

2019-01-05 Thread hdv@gmail
On 05/01/2019 14.45, songbird wrote: > hdv@gmail wrote: > ... >> So how do I make sure that 4.18.0-2 does not get removed from the boot menu >> after the next kernel upgrade? I'd like to keep it until I have verified >> that an >> upgrade does work. However, as far as I can tell only the last 3

Re: How to ensure that old kernel does not get removed

2019-01-05 Thread songbird
hdv@gmail wrote: ... > So how do I make sure that 4.18.0-2 does not get removed from the boot menu > after the next kernel upgrade? I'd like to keep it until I have verified that > an > upgrade does work. However, as far as I can tell only the last 3 kernels are > kept. Thus now I run the risk of

Re: How to ensure that old kernel does not get removed

2019-01-05 Thread hdv@gmail
On 05/01/2019 11.19, Reco wrote: > On Sat, Jan 05, 2019 at 11:16:23AM +0100, hdv@gmail wrote: >> On 05/01/2019 08.52, Reco wrote: >>> Hi. >>> >>> On Sat, Jan 05, 2019 at 03:41:05AM +0100, hdv@gmail wrote: So how do I make sure that 4.18.0-2 does not get removed from the boot menu

Re: How to ensure that old kernel does not get removed

2019-01-05 Thread Reco
On Sat, Jan 05, 2019 at 11:16:23AM +0100, hdv@gmail wrote: > On 05/01/2019 08.52, Reco wrote: > > Hi. > > > > On Sat, Jan 05, 2019 at 03:41:05AM +0100, hdv@gmail wrote: > >> So how do I make sure that 4.18.0-2 does not get removed from the boot menu > >> after the next kernel upgrade? > > >

Re: How to ensure that old kernel does not get removed

2019-01-05 Thread hdv@gmail
On 05/01/2019 08.52, Reco wrote: > Hi. > > On Sat, Jan 05, 2019 at 03:41:05AM +0100, hdv@gmail wrote: >> So how do I make sure that 4.18.0-2 does not get removed from the boot menu >> after the next kernel upgrade? > > Do not uninstall this version of kernel, simple as that. > Invoke this

Re: How to ensure that old kernel does not get removed

2019-01-04 Thread Reco
Hi. On Sat, Jan 05, 2019 at 03:41:05AM +0100, hdv@gmail wrote: > So how do I make sure that 4.18.0-2 does not get removed from the boot menu > after the next kernel upgrade? Do not uninstall this version of kernel, simple as that. Invoke this to be sure: apt-mark hold

How to ensure that old kernel does not get removed

2019-01-04 Thread hdv@gmail
Hi list, After a recent upgrade I noticed that my system could not reboot into the new 4.19 kernel. So I rebooted into the kernel before that (4.18.0-3), which did not work either. Booting into the version before that (4.18.-02) did work just fine. It seems I hadn't rebooted after the previous