From: Dan Bethe <dan_bethe@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: HFS+ feature request
Date: Fri, 3 Mar 2000 12:32:25 -0800 (PST) [thread overview]
Message-ID: <20000303203225.3481.qmail@web1001.mail.yahoo.com> (raw)
> 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.
I understand that. My request was basically just that we have an
option for that. Basically, to have something like this:
# mount -t hfsplus -o rw,casesensitive /dev/sda1 /mnt/local/sda1
And the default can be case insensitive-but-preserving, like MacOS and
the official specs state. I just want the chance to be able to use it
as a "real" filesystem, sharing the maximum amount of space while I
still have to deal with the silliness of MacOS :) If I could format
/usr with HFS+, I'd give that a shot.
If any of you have access to a MacOS 10 which installs its root with
HFS+, let's see how it behaves. I have MacOS 10 "Server" 1.0 on my
powerbook, and its root fs is UFS BSD 4.4.
> 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.
Good idea. Let's keep cooking on this! It would be funny if
eventually HFS+ was the most compatible unix-based filesystem on all
Linux architectures :)
=====
"Don't expect your own messiah; this neverworld which you desire is
only in your mind." -- http://www.dreamtheater.net/songb4.htm#IV5
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-03 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-03 20:32 Dan Bethe [this message]
2000-03-06 0:32 ` HFS+ feature request Brad Boyer
[not found] <200002251949.NAA09042@wolfram.com>
2000-02-28 21:47 ` 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=20000303203225.3481.qmail@web1001.mail.yahoo.com \
--to=dan_bethe@yahoo.com \
--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).