From: Martin Costabel <costabel@wanadoo.fr>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.3.whatever and hfs
Date: Tue, 21 Sep 1999 08:17:58 +0200 [thread overview]
Message-ID: <37E72316.B63EBD9E@wanadoo.fr> (raw)
In-Reply-To: v03130302b40ca89cb4be@[192.168.1.1]
"David D. Kilzer" wrote:
>
> David Riley <happyoscar42@usa.net> wrote:
> >The current vger 2.3 kernel (whatever it is, maybe 2.3.18) compiles
> >without a hitch, except at the end when it's linking it all up and it
> >dies with an unresolved symbol "update_vm_chache" in hfs.o. I'd like to
> >be able to use hfs with my 2.3 kernel; is there a fix for this?
>
> Yes. Someone must rewrite the HFS code to use the new unified buffer code.
> I think both minixfs and ext2fs have been rewritten, but HFS and other
> 'foreign' file systems have not been rewritten.
>
> The short-term solution is not to include support for HFS in your kernel.
>
> The long-term solution is to fix HFS to work with the new unified buffer
> code. Unfortunately, the HFS maintainer is busy and may not be able to fix
> this until well into 2.4.
So in the next stable kernel version, we will not have HFS support and,
of course, even less HFS+ support! Is there really nobody in the
linuxppc developers community who can do this? The current maintainer
has been inactive since 7 months (see the archives from February), so he
could not really object if someone else took over.
> Personally, I think that, "if you break it, you fix it," but apparently
> this doesn't always apply to kernel internals.
And never has applied to the PPC port, unfortunately.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-21 6:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-21 1:54 2.3.whatever and hfs David Riley
1999-09-21 3:23 ` David D. Kilzer
1999-09-21 6:05 ` Sriranga Veeraraghavan
1999-09-21 6:17 ` Martin Costabel [this message]
1999-09-22 12:28 ` Brad Boyer
-- strict thread matches above, loose matches on Subject: below --
1999-10-15 6:55 Lou Langholtz
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=37E72316.B63EBD9E@wanadoo.fr \
--to=costabel@wanadoo.fr \
--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).