| |||||||||||||
Fixing broken userspace is NOT the kernel's jobFixing broken userspace is NOT the kernel's jobPosted May 1, 2012 23:59 UTC (Tue) by mezcalero (subscriber, #45103)In reply to: Fixing broken userspace is NOT the kernel's job by pr1268 Parent article: Fixing the unfixable autofs ABI
Sorry, but systemd is not the place to put workarounds for broken APIs. Fix the stuff where it is broken, don't litter systemd code with it, thank you very much.
(Log in to post comments)
Fixing broken userspace is NOT the kernel's job Posted May 2, 2012 5:02 UTC (Wed) by dlang (✭ supporter ✭, #313) [Link]
I have seen a very good companies product basically destroyed over many years of fixing things in the wrong place.
In opensource software there is almost never a reason to do this, and never without discussing the problem first.
That said, I have no problem with the sanity check that systemd is doing. They are not working around anything, they are just checking that what they are getting has a chance of being what they expect to get. They know the size of the object that they are getting, and so they only get that much data. fetching more would potentially cause other grief.
|
|||||||||||||