From: Martin Costabel <costabel@wanadoo.fr>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.3.99-pre6 sound hfs
Date: Thu, 04 May 2000 22:22:37 +0200 [thread overview]
Message-ID: <3911DC0D.DE0C0C13@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.10005041754250.30927-100000@opal.biophys.uni-duesseldorf.de
Michael Schmitz wrote:
[]
> > >From my personal mail archive, I see that HFS was already broken in
> > 2.3.18 last September.
>
> And it got fixed enough to be working again at least in 2.3.48 - that fix
> (or rather workaround) may have been broken again lately.
This is a little mysterious. It looks almost as if HFS is working for
some people and not for others.
Around 2.3.45, there was a discussion with Ani Joshi who said that it
was working for him. For me it definitely wasn't. It hosed a ZIP disk so
thoroughly that MacOS died every time I just inserted it into the drive.
I had to reformat it first under Linux before MacOS would even touch it.
More recently (already in the 2.3.99's), Tom Rini claimed that HFS was
working for him. And it seems that even now it works for some people.
Weird.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-04 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10005031013310.17388-100000@opal.biophys.uni-duesseldorf.de>
2000-05-03 8:44 ` 2.3.99-pre6 sound hfs Steven Hanley
2000-05-03 10:27 ` Michael Schmitz
2000-05-03 20:49 ` Martin Costabel
2000-05-04 15:57 ` Michael Schmitz
2000-05-04 20:22 ` Martin Costabel [this message]
2000-05-04 22:07 ` Michael Schmitz
2000-05-09 9:47 ` Michael Schmitz
2000-05-05 3:46 ` Ani Joshi
2000-05-05 8:45 ` Martin Costabel
2000-05-02 17:14 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=3911DC0D.DE0C0C13@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.