On 2022-06-21 12:09:00 -0600, D. R. Evans wrote:
> DdB wrote on 6/20/22 10:07:
> > Since i am running dozens of VM's, i can say:
> > Me2 am running into this regularly, when i am trying to purge old
> > kernels. I am seeing this so frequently, that i even wrote a script
> > (meant to be run inside
DdB wrote on 6/20/22 10:07:
Since i am running dozens of VM's, i can say:
Me2 am running into this regularly, when i am trying to purge old
kernels. I am seeing this so frequently, that i even wrote a script
(meant to be run inside the VM's) to clean up the mess, some apt-scripts
happen to leave
Since i am running dozens of VM's, i can say:
Me2 am running into this regularly, when i am trying to purge old
kernels. I am seeing this so frequently, that i even wrote a script
(meant to be run inside the VM's) to clean up the mess, some apt-scripts
happen to leave behind.
But in this special ca
On Mon, 20 Jun 2022 08:58:55 -0600
"D. R. Evans" wrote:
Hello D.,
>But it failed, with the error message:
Actually; .exited, with the warning.
That is to say, it's doing what it's supposed to do.
--
Regards _
/ ) "The blindingly obvious is never immediately apparent"
On Mon, 20 Jun 2022 08:58:55 -0600
"D. R. Evans" wrote:
> So it seems reasonable to remove /lib/modules/5.10.0-11-amd64/misc/
> manually and re-execute the purge command.
Yes, go ahead and do so.
>
> But before I try that, I'm puzzled as to how this situation could
> have arisen. Has anyone el
Normally to remove an old kernel from my debian stable systems, I issue the
following command:
apt purge linux-headers--amd64
linux-headers--common linux-image--amd64
Following this recipe, which has always worked in the past, I issued:
apt purge linux-headers-5.10.0-11-amd
6 matches
Mail list logo