Hi David,
Skipping to quote most of the mail you wrote, I read it a few more times. :-)
[]
> In the listing above, you have removed versions 7 through 16, and then purged
> 7, as quoted above. The remaining 8 through 16 contain no modules, and the
> evidence is shown in your listing
>
On 5/2/23, Greg Wooledge wrote:
> On Tue, May 02, 2023 at 10:18:10AM +0100, Tixy wrote:
>> On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
>> > man apt
>>
>> Which doesn't say what 'apt purge' does without a package name. It says
>> 'Performs the requested action on one or more packages
On Mon 08 May 2023 at 08:27:52 (+), Bonno Bloksma wrote:
> > "apt autoremove" will remove (not purge) packages
> []
> Thanks for the better explanation, that is what I understood as well.
I doubt that.
> > One imagines that if you simply purged all of the kernel packages that had
> >
Hi,
As we have seen some modules directories are larger than others. I was just
cleaning up some old stuff and this is what I noticed.
---
xxx:/usr/lib/modules# du * -sh
4.7M5.10.0-16-amd64
309M5.10.0-18-amd64
309M5.10.0-19-amd64
309M5.10.0-20-amd64
Hi Greg,
>> Just created a snapshot of my servers and then did:
>> apt autoremove
>> apt purge
>> apt clean
>> and I still have a working system so it will not just get rid of all
>> installed packages. :-) But... I still also have all those folders in
>> /usr/lib/modules
> It seems like
On Fri 05 May 2023 at 14:35:08 (+), Bonno Bloksma wrote:
> As I was trying to find out what would work and if I was doing something
> wrong getting rid of old kernels
>
> After upgrading a new kernel for a week I will do apt autoremove to get rid
> of the old kernel(s).
And this will
On Fri, May 05, 2023 at 02:35:08PM +, Bonno Bloksma wrote:
> Just created a snapshot of my servers and then did:
> apt autoremove
> apt purge
> apt clean
> and I still have a working system so it will not just get rid of all
> installed packages. :-)
> But... I still also have all those
On 03 May 2023 18:22, Curt wrote:
You really don't have to tread dangerous waters (or rather wade into
them, unless your Jesus) because you can simulate without root privileges.
curty@einstein:~$ apt -s purge
NOTE: This is only a simulation!
Quick nitpicking.
Even if "-s" is easily remembered
Hi,
>> I expect that, by context, running
>> apt purge
>> without the restriction specifying particular package, will apply apt
>> purge to all installed packages, according to what purge does, in
>> relation to packages.
>
> But as "apt purge " remove this package and remove configuration for
On Wed, May 03, 2023 at 04:22:55PM -, Curt wrote:
[...]
> You really don't have to tread dangerous waters (or rather wade into
> them, unless your Jesus) because you can simulate without root privileges.
Yes, +1 for -s :-)
> curty@einstein:~$ apt -s purge
> NOTE: This is only a simulation!
Le 3 mai 2023 Curt a écrit :
> You really don't have to tread dangerous waters (or rather wade into
> them, unless your Jesus) because you can simulate without root privileges.
>
> curty@einstein:~$ apt -s purge
> NOTE: This is only a simulation!
Nice parameter, thanks !
On 2023-05-02, Greg Wooledge wrote:
>
> unicorn:~$ apt purge
> E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13:
> Permission denied)
> E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend),
> are you root?
>
> Rats! No luck here. Either "apt purge" is
On Tue 02 May 2023 at 13:03:48 (-0400), songbird wrote:
> David Wright wrote:
> ...
> > It seems a bluff was called. Anyway, I got
> > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> > as it seems bookworm's libfreetype6 was upgraded overnight.
>
> that was the only upgrade i
On Tue, 02 May 2023 18:10:01 +0200 David Wright
wrote:
> On Tue 02 May 2023 at 11:39:09 (-0400), The Wanderer wrote:
>
>> It's a pointless thing to discuss, in any case, since I have been
>> unable to think of essentially any reason why anyone would ever want
>> to do any such thing.
>
> It
David Wright wrote:
...
> It seems a bluff was called. Anyway, I got
> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
> as it seems bookworm's libfreetype6 was upgraded overnight.
that was the only upgrade i saw this morning for my
testing partition.
> And I'm not brave; the
On Tue 02 May 2023 at 11:39:09 (-0400), The Wanderer wrote:
> It's a pointless thing to discuss, in any case, since I have been unable
> to think of essentially any reason why anyone would ever want to do any
> such thing.
It makes me think of that gruesome cartoon where a meat mincer's
handle is
Bret Busby wrote:
> On 2/5/23 20:23, Michel Verdier wrote:
> > Le 2 mai 2023 Bret Busby a écrit :
> >
> >> I expect that, by context, running
> >> apt purge
> >> without the restriction specifying particular package, will apply
> >> apt purge
> >> to all installed packages, according to what
On 2023-05-02 at 10:28, Bret Busby wrote:
> On 2/5/23 20:23, Michel Verdier wrote:
>
>> Le 2 mai 2023 Bret Busby a écrit :
>>
>>> I expect that, by context, running
>>> apt purge
>>> without the restriction specifying particular package, will apply
>>> apt purge
>>> to all installed packages,
On Tue, 2023-05-02 at 22:28 +0800, Bret Busby wrote:
> I think that, to remove all installed packages, a system administrator,
> from the superuser level, needs to run something like
> rm -r /
Or
apt remove '*'
Man page for apt says it accepts regex and globs for package
specifiers. Other
On Tue 02 May 2023 at 22:28:11 (+0800), Bret Busby wrote:
> On 2/5/23 20:23, Michel Verdier wrote:
> > Le 2 mai 2023 Bret Busby a écrit :
> >
> > > I expect that, by context, running
> > > apt purge
> > > without the restriction specifying particular package, will apply
> > > apt purge
> > > to
On Tue 02 May 2023 at 08:09:57 (-0400), Greg Wooledge wrote:
> On Tue, May 02, 2023 at 10:18:10AM +0100, Tixy wrote:
> > On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
> > > man apt
> >
> > Which doesn't say what 'apt purge' does without a package name. It says
> > 'Performs the requested
Le 2 mai 2023 Bret Busby a écrit :
> and, so, where a particular package is specified as an argument to the
> command, all obsolete configuration files associated with the package, will be
> removed, and, where no package is specified as an argument to the command, all
> obsolete configuration
On 2/5/23 20:23, Michel Verdier wrote:
Le 2 mai 2023 Bret Busby a écrit :
I expect that, by context, running
apt purge
without the restriction specifying particular package, will apply
apt purge
to all installed packages, according to what purge does, in relation to
packages.
But as "apt
On 2/5/23 18:18, Bret Busby wrote:
On 2/5/23 17:18, Tixy wrote:
On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
On 2/5/23 16:58, Bret Busby wrote:
On 2/5/23 11:42, David Wright wrote:
Have you tried running also
apt autoclean
I thought that just cleared /var/cache/apt/archives/.
Le 2 mai 2023 Bret Busby a écrit :
> I expect that, by context, running
> apt purge
> without the restriction specifying particular package, will apply
> apt purge
> to all installed packages, according to what purge does, in relation to
> packages.
But as "apt purge " remove this package and
On Tue, May 02, 2023 at 10:18:10AM +0100, Tixy wrote:
> On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
> > man apt
>
> Which doesn't say what 'apt purge' does without a package name. It says
> 'Performs the requested action on one or more packages specified via
> regex(7), glob(7) or exact
On 2/5/23 18:20, Bret Busby wrote:
On 2/5/23 18:18, Bret Busby wrote:
On 2/5/23 17:18, Tixy wrote:
On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
On 2/5/23 16:58, Bret Busby wrote:
On 2/5/23 11:42, David Wright wrote:
Have you tried running also
apt autoclean
I thought that
On 2/5/23 17:18, Tixy wrote:
On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
On 2/5/23 16:58, Bret Busby wrote:
On 2/5/23 11:42, David Wright wrote:
Have you tried running also
apt autoclean
I thought that just cleared /var/cache/apt/archives/.
and
apt purge
I've never tried
On Tue, 2023-05-02 at 17:03 +0800, Bret Busby wrote:
> On 2/5/23 16:58, Bret Busby wrote:
> > On 2/5/23 11:42, David Wright wrote:
>
>
>
> > >
> > > > > > Have you tried running also
> > > > > > apt autoclean
> > >
> > > I thought that just cleared /var/cache/apt/archives/.
> > >
> > > > > >
On 2/5/23 16:58, Bret Busby wrote:
On 2/5/23 11:42, David Wright wrote:
Have you tried running also
apt autoclean
I thought that just cleared /var/cache/apt/archives/.
and
apt purge
I've never tried that without a package name. What does it do?
RTFM ?
man apt
...
..
Bret
On 2/5/23 11:42, David Wright wrote:
On Mon 01 May 2023 at 23:24:56 (-0400), Timothy M Butterworth wrote:
On Mon, May 1, 2023 at 10:45 PM Rick Thomas wrote:
On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
On 2/5/23 02:06, David Christensen wrote:
On 5/1/23 06:51, Bonno Bloksma wrote:
On Mon 01 May 2023 at 23:24:56 (-0400), Timothy M Butterworth wrote:
> On Mon, May 1, 2023 at 10:45 PM Rick Thomas wrote:
> > On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> > > On 2/5/23 02:06, David Christensen wrote:
> > >> On 5/1/23 06:51, Bonno Bloksma wrote:
> > >>> The cause seems to
On Mon, May 1, 2023 at 10:45 PM Rick Thomas wrote:
> On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> > On 2/5/23 02:06, David Christensen wrote:
> >> On 5/1/23 06:51, Bonno Bloksma wrote:
> >>> Hi,
> >>>
> >>> On my "new" Bullseye machines the root volume starts to fill up. The
> >>> cause
On Mon, May 1, 2023, at 11:14 AM, Bret Busby wrote:
> On 2/5/23 02:06, David Christensen wrote:
>> On 5/1/23 06:51, Bonno Bloksma wrote:
>>> Hi,
>>>
>>> On my "new" Bullseye machines the root volume starts to fill up. The
>>> cause seems to be the /usr/lib folder.
>>> On my older Buster (10.13)
On Mon, 1 May 2023 12:10:08 -0600
Charles Curley wrote:
Hello Charles,
>Ah. I don't recall that I've ever tried that. Maybe one should
>experiment on a throw-away VM. :-)
Go ahead: What's life without a little jeopardy? :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
On Mon, 01 May 2023 14:09:56 -0400
Stefan Monnier wrote:
Hello Stefan,
>The main downside is usually that you won't be able to access
Or reboot, into a working system, if it's the *only* kernel. But
hey... :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/
On 5/1/23 11:14, Bret Busby wrote:
On 5/1/23 06:51, Bonno Bloksma wrote:
Hi,
On my "new" Bullseye machines the root volume starts to fill up.
Have you tried running also
apt autoclean
and
apt purge
?
I updated and cleaned my daily driver recently:
2023-04-29 11:54:03 root@taz ~
#
On Mon 01 May 2023 at 11:06:25 (-0600), Charles Curley wrote:
> On Mon, 1 May 2023 13:51:06 + > Bonno Bloksma wrote:
>
> > Guessing on what I see these are libraries for older kernel versions.
> > I usually clean up older kernel versions by using # apt autoremove"
> > All 3 servers have 1
On 2/5/23 02:06, David Christensen wrote:
On 5/1/23 06:51, Bonno Bloksma wrote:
Hi,
On my "new" Bullseye machines the root volume starts to fill up. The
cause seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M,
the /usr/lib folder is 260M
In
On Mon, 1 May 2023 18:52:09 +0100
Brad Rogers wrote:
> If memory serves, should one try to do that, warnings are issued.
>
> Not quite HAL in "2001, A Space Odyssey", but near enough. :-)
Ah. I don't recall that I've ever tried that. Maybe one should
experiment on a throw-away VM. :-)
>>to not purge the two most recent kernel packages, and especially not
>>the kernel you are currently running on.
> If memory serves, should one try to do that, warnings are issued.
> Not quite HAL in "2001, A Space Odyssey", but near enough. :-)
Also, purging the current kernel is not nearly
On 5/1/23 06:51, Bonno Bloksma wrote:
Hi,
On my "new" Bullseye machines the root volume starts to fill up. The cause
seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M, the
/usr/lib folder is 260M
In my /usr/lib folder on Buster is NO
On Mon, 1 May 2023 11:06:25 -0600
Charles Curley wrote:
Hello Charles,
>to not purge the two most recent kernel packages, and especially not
>the kernel you are currently running on.
If memory serves, should one try to do that, warnings are issued.
Not quite HAL in "2001, A Space Odyssey",
On Mon, 1 May 2023 13:51:06 +
Bonno Bloksma wrote:
> Guessing on what I see these are libraries for older kernel versions.
> I usually clean up older kernel versions by using # apt autoremove"
> All 3 servers have 1 older kernel version installed according to apt
> autoremove.
Autoremove
On Mon 01 May 2023 at 13:51:06 (+), Bonno Bloksma wrote:
Hmm, that took a long time to get posted.
> On my "new" Bullseye machines the root volume starts to fill up. The cause
> seems to be the /usr/lib folder.
> On my older Buster (10.13) machine the total /usr directory is 701M, the
>
On Mon, 2023-05-01 at 13:51 +, Bonno Bloksma wrote:
[...]
> On my Bullseye machines the /usr/lib folder is 2+GB on the machines that have
> been operating for a while and 1+G on a machine that has been operating for a
> shorter while.
>
> The cause seems to be the folder /usr/lib/modules#
Hi,
On my "new" Bullseye machines the root volume starts to fill up. The cause
seems to be the /usr/lib folder.
On my older Buster (10.13) machine the total /usr directory is 701M, the
/usr/lib folder is 260M
In my /usr/lib folder on Buster is NO /usr/lib/modules folder
On my Bullseye machines
47 matches
Mail list logo
