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 case of yours, there is no harm done by just removing this empty dir (which is left behind quite a lot in my machines too). But ... as this is not the only place, where debian does not comply with my sense of an orderly regime in the filesystem, i prefer to resort to living with the feeling of "a somewhat dirty" system. Just as my body gets polluted over a lifetime, so does any operating system and the effort, to clean it up only to save a few bytes, gets increasingly ridiculous, as those bytes wont crash the system. Hopefully, the microplastic and active chemicals, that pollute our bodies, wont crash it either, but i am not so certain about the latter.
DdB Am 20.06.2022 um 16:58 schrieb D. R. Evans: > So it seems reasonable to remove /lib/modules/5.10.0-11-amd64/misc/ > manually and re-execute the purge command. > > But before I try that, I'm puzzled as to how this situation could have > arisen. Has anyone else seen this happen, and does anyone have a > reasonable suggestion as to how it could have occurred? > > Doc -- Liebe ist ... Datakanja
