On Thu, Mar 27, 2008 at 11:37:33AM +0000, you wrote:
https://bugs.edge.launchpad.net/ubuntu/+source/coreutils/+bug/192239
and saw that the debugging was done in the Debian bug report.
You appear to have a handle on what the problem is now, and you
mention a few possible fixes, have you thought any more about
the issue?
I'm mainly leaning toward ignoring it, since it isn't applicable to a
supported configuration. (That is, it requires an unsupported kernel to
trigger the problem, as well as not having /proc mounted, which is also
non-standard.) One alternative is to look for a "function not supported"
return code from the *at functions, and fall back to the functions which
coreutils would have used if there were no *at functions in the first
place. The patch to do that would be fairly invasive, though, because
those functions are intended as replacements and aren't compiled if the
libc function exists. (The patch would basically have to rename the
functions and compile them unconditionally.) Another approach would be
to get libc to use the same sort of fallback that the coreutils internal
functions do, but I can understand why they might not want to do that.
(The *at functions are intended to be more secure than the existing
alternatives, and emulating them through insecure code would weaken the
security assumptions.) If someone wants to propose a patch to implement
the above I would consider it.
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
