public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: flar@pants.nu (Brad Boyer)
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	linux-hfsplus-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] HFS+ driver
Date: Thu, 8 May 2003 15:50:03 -0700	[thread overview]
Message-ID: <20030508225002.GA19618@pants.nu> (raw)
In-Reply-To: <20030508221202.GE3458@werewolf.able.es>


Just as a note, I've removed linux-kernel from the cc: list, since it
seems like we've wandered off anything of general interest...

On Fri, May 09, 2003 at 12:12:02AM +0200, J.A. Magallon wrote:
> Just by chance... I was looking for options...

I guess I should write some documentation.  :)

> 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 ?

Well, HFS+ does allow 255 character filenames, but some versions of the
MacOS will choke on anything longer than the old limit. I haven't tried
any UFS filesystems on any of my Macs. I have some pretty strong comments
from people inside Apple warning against trusting their implementation
of UFS, which kind of scared me off of it. The official word out of Apple
seems to be to use HFS+ unless you have a really, really good reason.

> 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+.

Always a good idea...

> - Moved HFS+ next to HFS in Configure.in

That's where I originally put it, but then a new filesystem showed up
and I didn't pay close enough attention to the merge, I guess.

> - 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 ?)

That would have to be in the code from Roman. I'm not quite done reading
it yet, I must admit. I've been busy with other stuff.

However, I have tended to keep the code clean for as many versions
as possible. There was one major change that keeps really old 2.4.x
versions from being easily source compatible without the horrible
KERNEL_VERSION hacks, and I'd like to avoid such hacks if possible.

> 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 ?

I'll take a look when I get a chance. Thanks for taking an interest
in the project.

	Brad Boyer
	flar@allandria.com


  reply	other threads:[~2003-05-08 22:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:06 [ANNOUNCE] HFS+ driver Roman Zippel
2003-05-07 15:40 ` David S. Miller
2003-05-07 19:39 ` Brad Boyer
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
2003-05-08 22:50       ` Brad Boyer [this message]
2003-05-12  9:58       ` Andreas Schwab

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=20030508225002.GA19618@pants.nu \
    --to=flar@pants.nu \
    --cc=jamagallon@able.es \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hfsplus-devel@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox