From: "Timothy A. Seufert" <tas@mindspring.com>
To: Ethan Benson <erbenson@alaska.net>,
linuxppc-dev@lists.linuxppc.org, linux-fsdevel@vger.kernel.org
Subject: Re: HFS+ support (read-only)
Date: Fri, 7 Jun 2002 12:16:31 -0700 [thread overview]
Message-ID: <adr110$sca$2@main.gmane.org> (raw)
In-Reply-To: <20020606232543.C9152@plato.local.lan>
At 11:25 PM -0800 6/6/02, Ethan Benson wrote:
>On Thu, Jun 06, 2002 at 03:50:31PM -0700, Timothy A. Seufert wrote:
>> 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.
Oh, come on. :) I just tested it, they didn't let it 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+.
The kludge part is trying to retrofit features like hardlinks into a
FS which wasn't designed to naturally support them (as classic UNIX
inode FS designs do). Aside from that I see nothing wrong with the
basic design of HFS+.
--
Tim Seufert
next prev parent reply other threads:[~2002-06-07 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020606052443.A21838@pants.nu>
2002-06-06 21:23 ` HFS+ support (read-only) Ethan Benson
2002-06-06 22:50 ` Timothy A. Seufert
2002-06-07 7:25 ` Ethan Benson
2002-06-07 19:16 ` Timothy A. Seufert [this message]
2002-06-06 12:24 Brad Boyer
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='adr110$sca$2@main.gmane.org' \
--to=tas@mindspring.com \
--cc=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