From mboxrd@z Thu Jan 1 00:00:00 1970 From: flar@pants.nu (Brad Boyer) Subject: Re: [ANNOUNCE] HFS+ driver Date: Thu, 8 May 2003 15:50:03 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20030508225002.GA19618@pants.nu> References: <20030508213401.GA3458@werewolf.able.es> <20030508214746.GB19450@pants.nu> <20030508221202.GE3458@werewolf.able.es> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Roman Zippel , linux-hfsplus-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org Return-path: Received: from adsl-216-102-214-42.dsl.snfc21.pacbell.net ([216.102.214.42]:21772 "EHLO cynthia.pants.nu") by vger.kernel.org with ESMTP id S262189AbTEHWh3 (ORCPT ); Thu, 8 May 2003 18:37:29 -0400 To: "J.A. Magallon" Content-Disposition: inline In-Reply-To: <20030508221202.GE3458@werewolf.able.es> List-Id: linux-fsdevel.vger.kernel.org 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