From: Brad Boyer <flar@pants.nu>
To: bdowning@wolfram.com (Brian Downing)
Cc: tas@mindspring.com (Timothy A. Seufert),
geert@linux-m68k.org (Geert Uytterhoeven),
linuxppc-dev@lists.linuxppc.org
Subject: Re: HFS+ feature request
Date: Mon, 28 Feb 2000 13:47:46 -0800 (PST) [thread overview]
Message-ID: <200002282147.QAA05378@marcus.pants.nu> (raw)
In-Reply-To: <200002251949.NAA09042@wolfram.com> from "Brian Downing" at Feb 25, 2000 01:49:44 PM
Brian Downing wrote:
> The filesystem isn't case-sensitive. This doesn't bug me _that_ much, I
> suppose, but some system calls feel a little broken:
>
> % touch README
> % touch test
> % mv test readme
> mv: rename test to readme: file exists
> % mv test README
> % ls
> README
>
> The mv error is from the rename(2) system call returning -1. Fine,
> except that in the documentation it states that if the "to" argument
> exists, it is removed first. In a case-insensitive filesystem, I expect
> "README" to be replaced with "readme".
The official format of HFS+ does specify that the strings are compared
in a case insensitive way. In fact, it goes further and specifies a
bunch of details about actual Unicode sequences and I really don't want
to break all of that.
> Symlinks show up as a file in MacOS. I was hoping they would be able
> to do them as aliases, but I suppose they can't.
>
> Aliases show up a zero-length files in Unix, because all of the alias'
> stuff is in the resource fork, which I haven't been able to find a way
> to get at with Unix calls.
>
> Hard links (this is scary) make _all_ linked files show up as aliases
> to diskname:FileNodeDataXXXXX in the MacOS, where XXXXX is a number
> (inode number, or the HFS+ equivalent?). The aliases are unresolvable,
> and the FileNodeData file does not exist.
If you can give me an image of an HFS+ filesystem with some of this UNIX style
stuff, I can enable that stuff in the linux driver as well. The official
spec doesn't say much about the permissions, ownership, devices, etc. It
just says that they will be supported, and reserves a block for UNIX style
info like device numbers and uid/gid. I figured I'd ignore that stuff until
I could get more info about the way OSX would handle it.
Just in case anyone is wondering, I have some preliminary code that a few
other people are helping me with, but I'm swamped at work and haven't had
much time. Volunteers are much appreciated.
Brad Boyer
flar@pants.nu
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-02-28 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200002251949.NAA09042@wolfram.com>
2000-02-28 21:47 ` Brad Boyer [this message]
2000-03-03 20:32 HFS+ feature request Dan Bethe
2000-03-06 0:32 ` Brad Boyer
[not found] <20000225113608.001404@mailhost.mipsys.com>
2000-02-25 17:16 ` Kevin Kubarych
[not found] <20000225013416.6567.qmail@web1001.mail.yahoo.com>
2000-02-25 9:42 ` Geert Uytterhoeven
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=200002282147.QAA05378@marcus.pants.nu \
--to=flar@pants.nu \
--cc=bdowning@wolfram.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tas@mindspring.com \
/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).