All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Roland McGrath <roland@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linasvepstas@gmail.com, Chris Metcalf <cmetcalf@tilera.com>,
	GLIBC Devel <libc-alpha@sourceware.org>,
	linux-kernel@vger.kernel.org, libc-ports@sourceware.org,
	linux-api@vger.kernel.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [BUG] Generic syscalls -- chmod vs. fchmodat
Date: Thu, 10 Feb 2011 19:12:21 +0100	[thread overview]
Message-ID: <20110210181221.GA19413@win.tue.nl> (raw)
In-Reply-To: <20110125174515.C1DC2183C19@magilla.sf.frob.com>

On Tue, Jan 25, 2011 at 09:45:15AM -0800, Roland McGrath wrote:

> the empty string has never been a valid relative pathname.

Hmm. I definitely recall otherwise.

The old Unix definition is that the empty string stands for "."
so that 'ls ""' means the same as 'ls .'
and 'ls /tmp/""' the same as 'ls /tmp/.'.

Let me try.

On a recent Linux system:

% ls -l ""
ls: cannot access : No such file or directory

On an old Unix system:

# ls -l ""
drwxr-xr-x  2 bin      1040 Jan  1  1970 bin
drwxr-xr-x  2 bin       352 Jan  1  1970 dev
drwxr-xr-x  2 bin       304 Aug 20 12:39 etc
...

Andries

  parent reply	other threads:[~2011-02-10 18:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 19:57 [BUG] Generic syscalls -- chmod vs. fchmodat Linas Vepstas
2011-01-24 21:05 ` Roland McGrath
2011-01-24 21:32   ` Mike Frysinger
2011-01-25 14:29 ` Arnd Bergmann
2011-01-25 14:29   ` Arnd Bergmann
2011-01-25 17:45   ` Roland McGrath
2011-01-25 17:45     ` Roland McGrath
2011-01-25 18:21     ` Arnd Bergmann
2011-01-25 18:21       ` Arnd Bergmann
2011-01-25 18:34       ` Roland McGrath
2011-01-25 18:34         ` Roland McGrath
2011-01-25 20:04         ` Arnd Bergmann
2011-01-25 20:04           ` Arnd Bergmann
2011-01-25 18:52       ` Mike Frysinger
2011-01-25 18:52         ` Mike Frysinger
2011-01-25 19:56         ` Eric Blake
2011-01-25 19:56           ` Eric Blake
2011-01-25 20:31           ` Eric Blake
2011-01-25 20:31             ` Eric Blake
2011-01-25 21:32             ` Eric Blake
2011-01-25 21:32               ` Eric Blake
2011-01-25 22:10               ` Linas Vepstas
2011-02-10 18:12     ` Andries Brouwer [this message]
2011-02-10 18:17       ` Roland McGrath
2011-02-10 18:17         ` Roland McGrath
2011-02-11  9:11       ` Andreas Schwab

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=20110210181221.GA19413@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=arnd@arndb.de \
    --cc=cmetcalf@tilera.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-ports@sourceware.org \
    --cc=linasvepstas@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=vapier@gentoo.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.