public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: davecb@sun.com
Cc: Ray Lee <ray-lk@madrabbit.org>,
	Oliver.Soltys@rsel.renesas.com, linux-kernel@vger.kernel.org
Subject: Re: directory sort order no longer beginning with "." and ".."?
Date: Tue, 29 Jul 2008 10:24:12 -0700	[thread overview]
Message-ID: <488F523C.7090201@goop.org> (raw)
In-Reply-To: <488F4F30.1070903@sun.com>

David Collier-Brown wrote:
> Alas, this implementation side-effect dates back to v6[1], and is so
> depended upon that even  CD filesystems, which are by no means Unix-like,
> contain dummy "." and ".." entries[2].

Er, no, I wouldn't call '.' and '..' implementation side-effects in 
themselves.  They're one of the particularly clever parts of the 
filesystem/namespace design.  I would agree that the specific 
implementation using "link" and "unlink" was a bit of a hack, and adding 
proper "mkdir" and "rmdir" made the world a better place.

>  I'd recommend either reproducing it or starting a project
> to hunt down and kill all the programs which assume it (;-))

Well, '.' and '..' are guaranteed to be somewhere in a (linked) 
directory, so all filesystems are required to make sure they exist 
somewhere, and programs which expect them to exist are perfectly within 
their rights.  But not necessarily the first two entries.

    J

  reply	other threads:[~2008-07-29 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  9:49 directory sort order no longer beginning with "." and ".."? Oliver Soltys
2008-07-29 14:53 ` Jeremy Fitzhardinge
2008-07-29 16:35   ` Ray Lee
2008-07-29 17:11     ` David Collier-Brown
2008-07-29 17:24       ` Jeremy Fitzhardinge [this message]
2008-07-29 17:28     ` Jeremy Fitzhardinge

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=488F523C.7090201@goop.org \
    --to=jeremy@goop.org \
    --cc=Oliver.Soltys@rsel.renesas.com \
    --cc=davecb@sun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox