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 13:23:56 -0800 [thread overview]
Message-ID: <20020606132356.B9152@plato.local.lan> (raw)
In-Reply-To: <20020606052443.A21838@pants.nu>; from flar@pants.nu on Thu, Jun 06, 2002 at 05:24:43AM -0700
On Thu, Jun 06, 2002 at 05:24:43AM -0700, Brad Boyer wrote:
> but it can handle most standard UNIX features other than
> hard links, which will show up as empty files. (Don't ask...)
in case anyone is curious the reason for this is because HFS+ has no
support whatsoever for hard links. Apple kludged around this by
making OSX create a MacOS alias pointing to an inode number (or
similar) this macos alias has a special magic id to it so OSX knows to
pretend its a hard link instead of a regular file like it really is.
MacOS aliases are of course stored entirly in the resource fork, which
this implementation has no support for, thus hard link -> empty file.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
WARNING: multiple messages have this Message-ID (diff)
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 13:23:56 -0800 [thread overview]
Message-ID: <20020606132356.B9152@plato.local.lan> (raw)
In-Reply-To: <20020606052443.A21838@pants.nu>; from flar@pants.nu on Thu, Jun 06, 2002 at 05:24:43AM -0700
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
On Thu, Jun 06, 2002 at 05:24:43AM -0700, Brad Boyer wrote:
> but it can handle most standard UNIX features other than
> hard links, which will show up as empty files. (Don't ask...)
in case anyone is curious the reason for this is because HFS+ has no
support whatsoever for hard links. Apple kludged around this by
making OSX create a MacOS alias pointing to an inode number (or
similar) this macos alias has a special magic id to it so OSX knows to
pretend its a hard link instead of a regular file like it really is.
MacOS aliases are of course stored entirly in the resource fork, which
this implementation has no support for, thus hard link -> empty file.
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2002-06-06 21:23 UTC|newest]
Thread overview: 10+ 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 [this message]
2002-06-06 21:23 ` Ethan Benson
2002-06-06 22:50 ` Timothy A. Seufert
2002-06-06 22:50 ` Timothy A. Seufert
2002-06-07 7:25 ` Ethan Benson
2002-06-07 7:25 ` Ethan Benson
2002-06-07 19:16 ` Timothy A. Seufert
2002-06-07 19:16 ` Timothy A. Seufert
-- strict thread matches above, loose matches on Subject: below --
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=20020606132356.B9152@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 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.