From: Martin Costabel <costabel@wanadoo.fr>
To: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Cc: Ani Joshi <ajoshi@shell.unixbox.com>
Subject: Re: 2.3.99-pre6 sound hfs
Date: Fri, 05 May 2000 10:45:57 +0200 [thread overview]
Message-ID: <39128A45.6C1BA8F1@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.10005042042280.19981-100000@shell.unixbox.com
Ani Joshi wrote:
>
> As some of you have said before, the HFS issue in 2.3 is due to all the
> VFS changes, page cache stuff being a big one. anyhow, i poked around a
> bit last nite and have stabalized it a bit more (though not perfect yet),
> mounting and reads work fine, writes work sometimes and not, very strange.
>
> below is a patch which makes hfs use generic file read/writes, obviously
> more needs to be done then this, hopefully i'll post some more patches
> soon...
With this patch, I still cannot mount hfs CDs (the LinuxPPC 2000 CD),
and after a while of copying and gcc'ing on a hfs ZIP, it still freezes
the system. It seems, however, to survive somewhat longer than before,
and it freezes more gracefully, i.e. it puts me in a state (like vi
insert mode without Esc key) where I can type, even change consoles, but
it doesn't react. MagicSysRQ is still working, which wasn't the case
before.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-05 8:45 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
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 [this message]
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=39128A45.6C1BA8F1@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=ajoshi@shell.unixbox.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 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.