Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #204197
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: How to ensure that old kernel does not get removed |
| Date | 2019-01-07 21:30 +0100 |
| Message-ID | <xdJH4-3Z9-7@gated-at.bofh.it> (permalink) |
| References | <xcKca-8aP-15@gated-at.bofh.it> <xcVqW-6Bw-19@gated-at.bofh.it> <xdDih-8o6-9@gated-at.bofh.it> <xdEem-xK-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
> >> // considered for autoRemove
> >
> > Yeah, personally I'm all about that Never Auto Remove.
> >
> > wooledg:~$ cat /etc/apt/apt.conf.d/99local
> > APT::NeverAutoRemove ".";
> >
> > This completely disables that "feature" and leaves my system alone, just
> > how I want it.
>
> i've never gone to that extreme, i just want
> the previous kernel-images to not go away until
> i explicitly say to do so. this means that i do
> have to go clean them out manually.
>
>
> as an aside unfortunately for a default install
> the initial packages installed and used in the apt
> cache are cleared unless you figure out how to
> prevent that (via preseeding or some other method).
>
> when you are trying to audit a system to know
> exactly what has been installed (and then replaced
> by what) it is rather annoying. there are logs
> kept during install so the information is available
> but i also liked before that the cache was left
> intact until i explicitly requested it be cleared
> or adjusted in any way.
The very earliest package .deb files might never be downloaded to
/var/cache/apt/archives because they're already in
firmware-9.5.0-amd64-netinst.iso/iso9660://pool/ for example
but I haven't checked this out recently because of the
caching I do.
For example, the first package set up according to installer/syslog,
base-passwd (3.5.43) is here:
pool/main/b/base-passwd/base-passwd_3.5.43_amd64.deb 57656 Jan 16 2017
For those that are downloaded later in the installation, I rely on
apt-cacher-ng through which the installation takes place.
If you're not running a cacher, then the simplest way to grab these
packages is by running a shell on VC2 and
# mkdir /target/home/<first user>/somewhere
# cp -ip /target/var/cache/apt/archives/*deb /target/home/<first user>/somewhere/
Do this after configuring grub and before "Finish the installation"
Cheers,
David.
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
How to ensure that old kernel does not get removed "hdv@gmail" <hdv.jadev@gmail.com> - 2019-01-05 03:50 +0100
Re: How to ensure that old kernel does not get removed Reco <recoverym4n@enotuniq.net> - 2019-01-05 09:00 +0100
Re: How to ensure that old kernel does not get removed "hdv@gmail" <hdv.jadev@gmail.com> - 2019-01-05 11:20 +0100
Re: How to ensure that old kernel does not get removed Reco <recoverym4n@enotuniq.net> - 2019-01-05 11:20 +0100
Re: How to ensure that old kernel does not get removed "hdv@gmail" <hdv.jadev@gmail.com> - 2019-01-05 11:40 +0100
Re: How to ensure that old kernel does not get removed songbird <songbird@anthive.com> - 2019-01-05 15:50 +0100
Re: How to ensure that old kernel does not get removed "hdv@gmail" <hdv.jadev@gmail.com> - 2019-01-05 17:00 +0100
Re: How to ensure that old kernel does not get removed Greg Wooledge <wooledg@eeg.ccf.org> - 2019-01-07 14:40 +0100
Re: How to ensure that old kernel does not get removed songbird <songbird@anthive.com> - 2019-01-07 15:40 +0100
Re: How to ensure that old kernel does not get removed David Wright <deblis@lionunicorn.co.uk> - 2019-01-07 21:30 +0100
csiph-web