On Sun, Nov 11, 2018 at 07:55:30AM +0100, Michael Kerrisk (man-pages) wrote: > [1] https://sourceware.org/bugzilla/show_bug.cgi?id=6399 is a > longstanding example. This one was a sad read and shows that applications will continue to suffer from glibc's prehistorical view on operating systems and will continue to have to define their own syscall wrappers to exploit the full potential of the modern operating systems they execute on. This reminds me when one had to write their own spinlocks and atomics many years ago. Seeing comments suggesting an application should open /proc/$PID makes me really wonder if people actually want to use slow and insecure applications designed this way. Bah, after all, this wipes quite a bit of the shame I feel every time I do something to bypass it :-/ The sad thing is that the energy wasted arguing in the bug above could have been better spent designing and implementing a generic solution to expose syscalls without depending on glibc's politics anymore. Willy
