X-Debbugs-CC: cl...@debian.org, adcon...@0c3.net El ds 27 de 01 de 2018 a les 17:06 +0100, Samuel Thibault va escriure: > > > Putting the interpreter meaning in the kernel means putting it where it > > > is not expected to be found. > > > > Do you know that the kernel is the component that loads the ELF > > interpreter? > > So what?
I expect to find this functionality in the ELF loader. Where do you expect it to be found? > People expect to be able to interpret these string as path names in the > filesystem. Making it mean something else means hiding. That is your point of view. To me, implementation details are hidden from the interface. To know the implementation details, you must know the specific implementation, which is available to the user. "Invoke this interpreter" and "load this dependency" may not be the same as "read this file" or "test this file's existence"; it is a user decision. The latter operations will act as you expect, unless the user chooses otherwise, because of interoperability or whatever reason. > Period, no point answering me again. Why? We are exchanging interesting ideas. I learn about Debian's shortcomings and my own ones.
smime.p7s
Description: S/MIME cryptographic signature
