From: Andries.Brouwer@cwi.nl
To: linux-kernel@vger.kernel.org, vii@users.sourceforge.net
Cc: torvalds@transmeta.com
Subject: Re: [PATCH] setuid(2) buggy or bad docs
Date: Wed, 20 Jun 2001 11:17:24 +0200 (MET DST) [thread overview]
Message-ID: <UTC200106200917.LAA326522.aeb@vlet.cwi.nl> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
> setuid(2) differs from the OpenBSD setuid(2)
> Either I am non compos or the thing is very wrong.
> The docs (man-pages-1.35) say ...
Yes, setuid() has a behaviour that varies a bit from system to system.
Moreover, it has varied in the history of Linux. The manpage may have
been correct when it was written, but it is not today, and I just
fixed it.
ERRORS
EPERM The user is not the super-user, and uid does not
match the real or saved user ID of the calling pro
cess.
Our norm is the coming POSIX standard, roughly the Austin 7 draft,
which again is based on the SUSv2. According to this, the current
kernel code is correct here.
Andries
next reply other threads:[~2001-06-20 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 9:17 Andries.Brouwer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-20 0:37 [PATCH] setuid(2) buggy or bad docs John Fremlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=UTC200106200917.LAA326522.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=vii@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox