> Yes, and my impression/guess is that because 'apt' docs describe it
> as being basically a front end with more convenient defaults for
> interactive use, what happens when 'apt' is given these (or other
> similar) options that it does not recognise as its own as documented
> in the 'apt' man page
On Thu, 8 Apr 2021 at 23:33, Marco Ippolito wrote:
> Gotcha. I like the long option names there, almost all of which are
> immediately
> suggestive of what the change of behaviour might be:
>
> --simulate, --just-print, --dry-run, --recon, --no-act
Yes, and my impression/guess is that becau
> > Where would I put the -s please?
>
> Explanation of how to find the answer:
> He was talking about 'apt' commands.
> If you read 'man apt' it hints that it is a front-end to
> various 'apt-*' commands like 'apt-get'.
> The hints look like "apt-get(8)" which is a reference
> to the 'apt-get' ma
On Thu, 8 Apr 2021 at 22:23, Marco Ippolito wrote:
> > And I'm a big fan of -s with commands like these, so that
> > you know what's going to be changed. Then recall the command
> > and remove the -s.
> Where would I put the -s please?
Explanation of how to find the answer:
He was talking about
> And I'm a big fan of -s with commands like these, so that
> you know what's going to be changed. Then recall the command
> and remove the -s.
Where would I put the -s please?
> I decided to let MY initramfs images go on diet
> and added a little script which removes a few drivers that I certainly
> don't need (checked with lsmod) and which contained lots of firmwares
> and similar stuff.
Creative. I liked it. Indeed the ``most'' strategy produces large files.
Hallo,
* Marco Ippolito [Wed, Apr 07 2021, 09:20:46AM]:
> dpkg: error processing package initramfs-tools (--configure):
> installed initramfs-tools package post-installation script subprocess
> returned
> error exit status 1
> Errors were encountered while processing:
> initramfs-tools
>
> #
On Wed 07 Apr 2021 at 14:02:58 (-0400), Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> > While I'm a big fan of aptitude's patterns it's also not installed by
> > default. For basic uses 'apt' is fine as well and supports globs:
> >
> > apt list --ins
Am Mittwoch, 7. April 2021, 19:40:58 CEST schrieb Andrei POPESCU:
Hi Andrei,
yes, you casn do this also with using apt. However, I forgot how to do this,
it was a litttle bit more complicated.
The syntax was something like "apt-get --purge remove `somestring` " or
similar. Apt was then using re
On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> While I'm a big fan of aptitude's patterns it's also not installed by
> default. For basic uses 'apt' is fine as well and supports globs:
>
> apt list --installed linux-image-4*
>
> apt purge linux-image-4.9.10-?-amd64
Re
On Mi, 07 apr 21, 11:11:55, Marco Ippolito wrote:
> > Hi Marco,
>
> Hi Hans :)
>
> > aptitude purge ~n4.9.10-amd64-*
>
> Hadn't thought of matching a pattern, thanks.
While I'm a big fan of aptitude's patterns it's also not installed by
default. For basic uses 'apt' is fine as well and suppo
>> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
>> me (more or less shrunk the initrd images by a factor 3-4).
> Thank you.
> Why did you choose lzma Vs xz or zstd, by the way? Measured diff?
`lzma` and `xz` should be pretty much identical, it was a toss-up (I
have a pref
> Hi Marco,
Hi Hans :)
> aptitude purge ~n4.9.10-amd64-*
Hadn't thought of matching a pattern, thanks.
> Recently that was fixed at unstable [1]
I thought I had noticed a warning about this clean-up, but it does not happen
during the upgrade so I run out of space.
> I found a interesting manpage for this issue [2]
Good catch. Functionality now in apt and purge-old-kernels got deprecated.
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).
Thank you.
Why did you choose lzma Vs xz or zstd, by the way? Measured diff?
> > Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
> >
Le 07/04/2021 à 14:58, Stefan Monnier a écrit :
What do you recommend I do?
Other than purging old kernels, I also recommend you check
/etc/initramfs-tools/initramfs.conf
where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
me (more or less shrunk the initrd images by a
El mié., 7 abr. 2021 14:58, Stefan Monnier
escribió:
> > What do you recommend I do?
>
> Other than purging old kernels, I also recommend you check
>
> /etc/initramfs-tools/initramfs.conf
>
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the
Am Mittwoch, 7. April 2021, 14:20:46 CEST schrieb Marco Ippolito:
Hi Marco,
just get rid of older kernels.
This is may way:
1st, check your running actual kernel:
uname -a
Then check all installed kernel versions:
ls /boot
You will see several kernels. I suppose, apt-get autoremove will no
> What do you recommend I do?
Other than purging old kernels, I also recommend you check
/etc/initramfs-tools/initramfs.conf
where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
me (more or less shrunk the initrd images by a factor 3-4).
> Doubt: after this, by default old
>
>
> # df -h /boot
> Filesystem Size Used Avail Use% Mounted on
> /dev/nvme0n1p1 236M 233M 0 100% /boot
>
> What do you recommend I do?
>
1. Autoremove old automatically installed stuff
$ apt purge --autoremove
2. Check packages:
$ dpkg-query --show -f='${Installed-Size}\t${Package
On Wed, Apr 07, 2021 at 09:20:46AM -0300, Marco Ippolito wrote:
> # df -h /boot
> Filesystem Size Used Avail Use% Mounted on
> /dev/nvme0n1p1 236M 233M 0 100% /boot
>
> What do you recommend I do?
Purge one or more of your kernel images.
Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted in
recovery mode and cleaned up space. Restarted and run:
# dpkg --configure -a
Setting up initramfs-tools (0.139) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.139)
22 matches
Mail list logo
