From: Roman Zippel <zippel@linux-m68k.org>
To: linux-hfsplus-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] new HFS(+) driver
Date: Thu, 2 Oct 2003 10:37:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0310021029110.17548-100000@serv> (raw)
Hi,
This is a rather big update to the HFS+ driver. It includes now also an
updated HFS driver. Both drivers use now almost the same btree code and
the general structure is very similiar, so one day it will be possible to
merge both drivers. The HFS driver got a major cleanup and a lot of broken
options were removed, most notably if you want to continue using netatalk
with this driver, you have to fix netatalk first.
The HFS+ driver has a number of improvements and fixes:
- blocks are now preallocated.
- allocation file is now in the page cache too
- better extent caching
- btrees are now able to grow arbitrarily
- allocation block size can now be larger than a page
- actual fs block size is adjusted to avoid alignment problems
- cdrom session/partition support (note that this is a crutch and has
problems)
This is basically the version I'd liked to get merged into 2.6 (minus lots
of ifdefs and some debug prints). You can find the driver at
http://www.ardistech.com/hfsplus/
bye, Roman
next reply other threads:[~2003-10-02 8:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 8:37 Roman Zippel [this message]
2003-10-02 18:02 ` Dave O
2003-10-02 18:30 ` Roman Zippel
2003-10-02 19:00 ` Dave O
2003-10-03 0:26 ` Mike Fedyk
2003-10-03 2:43 ` Dave O
2003-10-02 18:06 ` viro
2003-10-02 18:24 ` Roman Zippel
2003-10-02 18:52 ` Brad Boyer
2003-10-06 19:38 ` Mike Fedyk
2003-10-06 19:47 ` Brad Boyer
2003-10-03 7:04 ` J.A. Magallon
2003-10-03 10:30 ` Roman Zippel
2003-10-03 22:39 ` J.A. Magallon
2003-10-04 3:00 ` Matthew Wilcox
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=Pine.LNX.4.44.0310021029110.17548-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hfsplus-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®