From: flar@allandria.com
To: khalfmann@libra.de (Halfmann, Klaus)
Cc: viro@math.psu.edu ('viro@math.psu.edu '),
dgatwood@deepspace.mklinux.org ('dgatwood@deepspace.mklinux.org
'), ak@suse.de ('ak@suse.de '), lord@sgi.com ('lord@sgi.com '),
matthew@wil.cx ('matthew@wil.cx '),
khalfmann@libra.de (Halfmann Klaus),
roman@augan.com ('roman@augan.com '),
linuxppc-dev@lists.linuxppc.org
('linuxppc-dev@lists.linuxppc.org '),
linux-fsdevel@vger.kernel.org ('linux-fsdevel@vger.kernel.org ')
Subject: Re: Btree directories (Re: Status of HFS+ support)
Date: Fri, 1 Sep 2000 10:40:07 -0700 (PDT) [thread overview]
Message-ID: <200009011740.KAA01445@marcus.allandria.com> (raw)
In-Reply-To: <F14441D40E5AD3118886005004607AD10BDD90@MAIL1> from "Halfmann, Klaus" at Sep 01, 2000 07:05:50 PM
Halfmann, Klaus wrote:
> Brad, Im sure you are wrong on this one, try the following in MacOS:
> create an alias to a folder and then renam it, the alias will stiil work
> So Im sure the CNIDs will not change ..
Alias files in the MacOS aren't that simple. The MacOS stores quite a bit
of info in an alias record, and tries to find the file even if a bunch of
stuff has changed. Take a look at
http://developer.apple.com/techpubs/mac/Files/Files-340.html
Note that it mentions that even files restored from backups can be easily
found by alias.
I went searching, and found a description of the funcions FSpExchangeFiles
and PBExchangeFiles in
http://developer.apple.com/technotes/tn/tn1041.html
which specifically states that when files are moved, the CNID is what is
changed effectively, because the disk block allocation data is what is
really moved around, not the filename. This allows them to not have to
do any major changes to a catalog record. All they have to do is change
a few particular fields in the entry. (Note this info is for HFS...)
Brad Boyer
flar@pants.nu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-01 17:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 17:05 Btree directories (Re: Status of HFS+ support) Halfmann, Klaus
2000-09-01 17:40 ` flar [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-30 12:06 Steve Lord
2000-08-30 15:07 ` Andi Kleen
2000-08-30 16:07 ` flar
2000-08-30 20:49 ` David A. Gatwood
2000-08-30 20:45 ` Steve Lord
2000-08-30 21:05 ` Alexander Viro
2000-08-30 21:51 ` David A. Gatwood
2000-08-30 21:49 ` Alexander Viro
2000-08-30 22:13 ` David A. Gatwood
2000-08-30 22:17 ` Alexander Viro
2000-08-30 23:11 ` David A. Gatwood
2000-08-31 0:10 ` Alexander Viro
2000-08-31 5:49 ` flar
2000-08-31 10:33 ` Alexander Viro
2000-08-31 17:48 ` flar
2000-08-31 19:54 ` Alexander Viro
2000-08-31 22:09 ` flar
2000-09-01 2:40 ` Alexander Viro
2000-09-01 3:52 ` flar
2000-09-02 4:04 ` Tony Mantler
2000-08-29 16:40 Status of HFS+ support (was hfs support for blocksize != 512) Halfmann, Klaus
2000-08-29 17:18 ` Btree directories (Re: Status of HFS+ support) Matthew Wilcox
2000-08-29 18:45 ` Steve Lord
2000-08-29 21:25 ` Matthew Wilcox
2000-08-30 2:22 ` flar
2000-08-30 8:35 ` Andi Kleen
2000-08-30 14:25 ` Chris Mason
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=200009011740.KAA01445@marcus.allandria.com \
--to=flar@allandria.com \
--cc=ak@suse.de \
--cc=dgatwood@deepspace.mklinux.org \
--cc=khalfmann@libra.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=lord@sgi.com \
--cc=matthew@wil.cx \
--cc=roman@augan.com \
--cc=viro@math.psu.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;
as well as URLs for NNTP newsgroup(s).