linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org, linux-fsdevel@vger.kernel.org
Subject: Re: HFS+ support (read-only)
Date: Thu, 6 Jun 2002 23:25:43 -0800	[thread overview]
Message-ID: <20020606232543.C9152@plato.local.lan> (raw)
In-Reply-To: <a05111b00b92592a276c0@[10.0.0.42]>; from tas@mindspring.com on Thu, Jun 06, 2002 at 03:50:31PM -0700


On Thu, Jun 06, 2002 at 03:50:31PM -0700, Timothy A. Seufert wrote:
> I thought there was also a special file (completely hidden from
> userland in X) which tracks all the hard links in the FS.  I'm pretty
> sure something like that is necessary to truly implement hard link
> semantics.  Consider what happens when a file with hardlinks gets
> unlink()ed -- then all its hardlinks point at nothing.  The OS needs
> a database of all files that are hardlinked, with full reverse
> mappings, so that whenever a file with hardlinks is unlinked it has
> enough information to replace one of the hardlinks with the real file.

i don't know about that, maybe.  to be honest it would not surprise me
if apple just let that break.

> (For efficiency I'd want a flag bit in the metadata of each file to
> indicate that it has been hardlinked, to avoid searching the table
> when deleting files that have no hardlinks.  For even more
> efficiency, a direct pointer to the table entry.)

you cannot use the word efficient to describe this puke inducing
kludge.  the efficient way is to design the filesystem properly to
begin with, which apple did not do with HFS+.

--
Ethan Benson
http://www.alaska.net/~erbenson/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-07  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 12:24 HFS+ support (read-only) Brad Boyer
2002-06-06 21:23 ` Ethan Benson
2002-06-06 22:50   ` Timothy A. Seufert
2002-06-07  7:25     ` Ethan Benson [this message]
2002-06-07 19:16       ` Timothy A. Seufert

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=20020606232543.C9152@plato.local.lan \
    --to=erbenson@alaska.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).