On 11/15/2011 10:09 AM, Eric Blake wrote:
> Still debatable. POSIX explicitly states that the condition of errno
> after a successful call to a standardized function is unspecified; that
> is, a successful geteuid() may pollute errno, but it's okay, because the
> user shouldn't be inspecting errno
Hi,
For those following email in near real time: let's try to meet as usual
at 19:00 UTC, in channel #hurd on irc.freenode.net, and discuss some
Hurd stuff.
-antrik-
Hi,
On Tue, Nov 15, 2011 at 12:02:58AM +0100, Samuel Thibault wrote:
> Considering the target of user-level drivers, I've come to a few
> biting points:
>
> - we should have a PCI arbitrer in the end. - that arbitrer should
> permit to confine drivers to resources of only one PCI device, no more
Here are proposed patches for the other coreutils applications
that invoke getuid et al.
port to GNU hosts, where getuid and friends can fail
* src/groups.c (main):
* src/install.c (need_copy):
* src/su.c (log_su):
* src/test.c (unary_operator):
* src/whoami.c (main):
Don't assume that getuid and
