public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: Valdis.Kletnieks@vt.edu, Michael Witten <mfwitten@gmail.com>,
	Mike Galbraith <efault@gmx.de>, Richard Yao <ryao@ic.sunysb.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: UNIX Compatibility
Date: Thu, 26 May 2011 09:35:18 -0400	[thread overview]
Message-ID: <20110526133518.GI9520@thunk.org> (raw)
In-Reply-To: <1306412699.28597.90.camel@thorin>

On Thu, May 26, 2011 at 02:24:59PM +0200, Bernd Petrovitsch wrote:
> > RATIONALE
> > 
> > Unlinking a directory is restricted to the superuser in many historical
> > implementations for reasons given in link() (see also rename()).
> > 
> > http://pubs.opengroup.org/onlinepubs/009695399/functions/unlink.html
> 
> So someone changes the semantics of the unlink() sys-call (obviously in
> some compatible, standards-compliant way) as it no longer unlinks
> directories but it is not possible to define the returned errno for
> the new error case to something sane?

Yes, it was those horrible hackers at BSD that implemented mkdir() and
rmdir() as atomic operations that could be executed by any process,
instead of only allowing root to create subdirectories.

It was the righteous AT&T marketing managers that created the first
standard, the AT&T SVID, which enshrined the Unix V7 error return, and
forbade it from ever being changed lest you "not be compatible with
Unix".  And thus was a design decision made over 40 years became cast
in concrete, never to change, until the Linux hackers said, "to hell
with the standard".

						- Ted

  reply	other threads:[~2011-05-26 13:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 11:49 UNIX Compatibility Richard Yao
2011-05-24 13:06 ` Theodore Tso
2011-05-24 13:54   ` Michael Witten
2011-05-24 14:49   ` Richard Yao
2011-05-24 18:16     ` Ted Ts'o
2011-05-24 18:31       ` Michael Witten
2011-05-25  4:18         ` Mike Galbraith
2011-05-25 14:20           ` Michael Witten
2011-05-25 14:36             ` Ted Ts'o
2011-05-25 15:17               ` Michael Witten
2011-05-25 17:38                 ` Ted Ts'o
2011-05-25 20:33                   ` Casey Schaufler
2011-05-26 11:30                   ` Bernd Petrovitsch
2011-05-26 11:30                 ` Bernd Petrovitsch
2011-05-26 12:07                   ` Valdis.Kletnieks
2011-05-26 12:24                     ` Bernd Petrovitsch
2011-05-26 13:35                       ` Ted Ts'o [this message]
2011-05-25 21:06               ` Valdis.Kletnieks
2011-05-25 14:38             ` Ted Ts'o
2011-05-25 15:17             ` Mike Galbraith
2011-05-25 15:21               ` Michael Witten
2011-05-24 18:23     ` david

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=20110526133518.GI9520@thunk.org \
    --to=tytso@mit.edu \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=bernd@petrovitsch.priv.at \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfwitten@gmail.com \
    --cc=ryao@ic.sunysb.edu \
    /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