Fri, 26 Jan 2024 12:15:03 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-01-25 22:55, Ben T. Fender wrote:
Thu, 25 Jan 2024 21:35:27 +0100 "Carlos E. R." <> :
On 2024-01-25 15:05, Ben T. Fender wrote:
Thu, 25 Jan 2024 08:53:39 +0100 "Carlos E. R." <> :
On 2024-01-25 03:53, Ben T. Fender wrote:
...
You have not shown that you can mount by another method.
Not sure I understand what more I can do
If I do
# mount UUID=4960ac17-a377-4007-84fd-45ee43713a57 /0/sa07
then it gets mounted there but tha's NOT what I want (not interested in copy-pasting uuids!)
DMESG:
[ 1072.223450] EXT4-fs (dm-7): mounted filesystem 4960ac17-a377-4007-84fd-45ee43713a57 r/w with ordered data mode. Quota mode: none. [ 1072.229397] audit: type=1400 audit(1706219199.152:130): apparmor="DENIED" operation="open" class="file" profile="nscd" name="/0/adat/u3/0DirectLink/hosts-nosnoop" pid=1341 comm="nscd" requested_mask="r" denied_mask="r" fsuid=473 ouid=1003
Notice that the log says it mounted dm-7! That's a device mapper name.
Yes, I've noticed the dozen dm lines in the fdisk output: /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part7 645924864 855640063 209715200 100G Linux filesystem But the thing is this: /dev/sda7 is another linux OS in this case and no-one told the freakin' system to *mount* it ANYWHERE! So why is it being mounted at all? Knowing where something is is one thing, sticking your dick into it without being told to is something else. What kind of confusion can this lead to if I have 10 back-level copies of my OS all with the same uuid there, just to look at one of many possible examples? If some app wants to know what partitions exist let it run "fdisk-l" EACH TIME. I gotta keep device-mapper and multipath packages for vBox to work (from what I see) so that's probably how they got onto my hard-drives in the first place. And I need vBox because it's the only way I can run the microcancer bundleware of my Boss-gx-100 effects board. # umount /dev/mapper/Samsung_SSD_860_EVO_1TB_S59VNJ0N419951T-part8 umount: /: target is busy. A partition that is totally off-limits unless I say otherwise is being mounted without my knowlege, permission, or directive AND I can't even unmount it? I don't get this, and like it even less. So what does a user have to do, delete the partition from the table before each boot and edit it back in on shutdown?