From: "J.A. Magallon" <jamagallon@able.es>
To: Brad Boyer <flar@pants.nu>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Roman Zippel <zippel@linux-m68k.org>,
linux-hfsplus-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] HFS+ driver
Date: Fri, 9 May 2003 00:12:02 +0200 [thread overview]
Message-ID: <20030508221202.GE3458@werewolf.able.es> (raw)
In-Reply-To: <20030508214746.GB19450@pants.nu>; from flar@pants.nu on Thu, May 08, 2003 at 23:47:46 +0200
On 05.08, Brad Boyer wrote:
> On Thu, May 08, 2003 at 11:34:01PM +0200, J.A. Magallon wrote:
> > How about this ?
>
> Yes, this is a good patch. I originally started on 2.2.x, which
> doesn't have strsep, and I didn't trust strtok (with good reason).
> I'll get rid of my little hacked up function and use strsep instead.
> Thanks for taking a look at the code.
>
Just by chance... I was looking for options...
BTW, i could look for it but perhaps you know the answer. I use a zip
to move files between osx at the uni and my home linux. I have always been
hit bit the short name length in hfs. Does hfs+ increase it ? If not, have
you been able to read UFS filesystems created on osx with Linux UFS ?
And finally, while we are at it, I also did some other changes, some aesthetic
and some needed to patch on top of 2.4.21-rc1:
- Changed a bit the description strings in Config.in and Configure.help to
uniformize HFS and HFS+.
- Moved HFS+ next to HFS in Configure.in
- Killed your new_inode() macro, that function is already in -rc1 (yup, if
you want to maintain backwards compat, it would be better to wrap it
with a LINUX_VERSION_CODE < KERNEL_VERSION(2,4,???), since when is
new_inode() in ?)
Modified version, including the hfsplus dir and the 64 bit changes, is at
http://giga.cps.unizar.es/~magallon/linux/hfsplus-20030507-2.bz2
Can you check it ?
TIA
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-rc1-jam2 (gcc 3.2.2 (Mandrake Linux 9.2 3.2.2-5mdk))
next prev parent reply other threads:[~2003-05-08 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 15:06 [ANNOUNCE] HFS+ driver Roman Zippel
2003-05-07 15:06 ` Roman Zippel
2003-05-07 15:40 ` David S. Miller
2003-05-07 15:40 ` David S. Miller
2003-05-07 16:14 ` Daniele Pala
2003-05-07 19:39 ` Brad Boyer
2003-05-07 19:39 ` Brad Boyer
2003-05-07 23:53 ` Roman Zippel
2003-05-07 23:53 ` Roman Zippel
2003-05-08 21:34 ` J.A. Magallon
2003-05-08 21:47 ` Brad Boyer
2003-05-08 22:12 ` J.A. Magallon [this message]
2003-05-08 22:50 ` Brad Boyer
2003-05-12 9:58 ` Andreas Schwab
2003-05-12 9:58 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 15:55 Jeffrey Baker
2003-05-07 16:38 ` Miles Lane
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=20030508221202.GE3458@werewolf.able.es \
--to=jamagallon@able.es \
--cc=flar@pants.nu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hfsplus-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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.