public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@phunq.net>
To: linux-ext4@vger.kernel.org
Cc: Theodore Tso <tytso@mit.edu>
Subject: Dot and dotdot need to be physically present?
Date: Wed, 13 Aug 2008 16:36:59 -0700	[thread overview]
Message-ID: <200808131636.59436.phillips@phunq.net> (raw)

Hi Ted,

Many years ago we had a discussion about whether or not the . and ..
directory entries had to be physically present in htree, and I remember
the conclusion was that they had to be, but I forget the argument and
lost track of the email thread.  I think the VFS will happily supply
the . and .. entries to getdents on its own.  So what was the issue?
Something about telldir?

This is in relation to implementing a cleaner successor to htree that
could end up being useful to Ext4 and Lustre as well as Tux3.  See
"phtree" here:

   http://tux3.org/design.html

Regards,

Daniel

p.s. Wow, you still have your MIT email.  There must be a war story.

             reply	other threads:[~2008-08-13 23:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13 23:36 Daniel Phillips [this message]
2008-08-14  3:47 ` Dot and dotdot need to be physically present? Theodore Tso
2008-08-20 23:52   ` Daniel Phillips

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=200808131636.59436.phillips@phunq.net \
    --to=phillips@phunq.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.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