X-Debbugs-CC: cl...@debian.org, adcon...@0c3.net El ds 27 de 01 de 2018 a les 03:17 +0100, Samuel Thibault va escriure: > So you are hiding some things.
I do not understand. What do you think I am hiding? There are no hidden symlinks. The file /lib64/ld-linux-x86-64.so.2 does not exist, unless you create it. > > The way I see the ABIs, /lib64/ld-linux-x86-64.so.2, /lib/ld.so.1, > > /libexec/ld-elf.so.1, etc. are magic strings, not requirements for the > > filesystem. > > That's hiding the actual ABI meaning. I do not think so. The ABI is just an interface, it says: "My executable will ask for this interpreter". I say: "Okay, let me handle the implementation details". I will not hide this fact. Tools like gdb and valgrind fail with /lib64 programs, which is not a problem since I usually recompile to fix a bug or a leak. In the unusual case that I must audit /lib64 programs, I grab a read-write environment and add a symlink. If there were complaints, I would adapt those tools.
smime.p7s
Description: S/MIME cryptographic signature
