From: jingai <jingai@floatingpenguins.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Re: hfs
Date: Wed, 03 May 2000 22:57:37 EDT [thread overview]
Message-ID: <200005040257.WAA03944@shell.faradic.net> (raw)
> > Does anyone have any ideas as to why it stopped working in the first
> > place?
>
> It has been broken since the introduction of the "new" page cache code
> about a year ago in early 2.3.x. The official maintainer (A Sun of
> netatalk fame) seems to be still alive, but nothing in terms of fixing
> the code came from him for a year. Sometimes some changes show up in the
> kernel trees, so that the code at least compiles, but it is still
> broken.
Maybe I'm talking about something different here, since I haven't really
been following this thread, but as of an rsync last night, the HFS support
in Paul's 2.3.99pre6 kernel works fine for me... it *did* quit working from
2.3.52 to some unknown date, but it does work now, at least for me.
-j
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-05-04 2:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-04 2:57 jingai [this message]
2000-05-04 2:23 ` Re: hfs Scott Knight
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=200005040257.WAA03944@shell.faradic.net \
--to=jingai@floatingpenguins.com \
--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).