From: Steven Hanley <sjh@wibble.net>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.3.99-pre6 sound hfs
Date: Wed, 03 May 2000 18:44:18 +1000 [thread overview]
Message-ID: <390FE6E2.1DDB8599@wibble.net> (raw)
In-Reply-To: Pine.LNX.4.10.10005031013310.17388-100000@opal.biophys.uni-duesseldorf.de
> Your point being?
I was replying to Scott Knight <scott@re-104-1.read.indiana.edu>
> Alright, i have a couple questions.
...
> Secondly is hfs support. Its nutty. I cant
> mount any hfs cdroms. I can mount hfs hard drives but if something is
> tried to copy to it it crashes the computer hard and emsse up the ahrd
> drive a bit. Anyone know what the deal is with this? And yes I have hfs
> support compiled in. ANy advice or help would be greatly apprecaited.
pointing out why hfs is not working, as he obviously was under the
assumption it was supposed to work in the latest devel kernels.
sorry for not quoting this originally if it added confusion, I tend to
edit out as much as possible in replies
See You
Steve
--
sjh@wibble.net http://wibble.net/~sjh/
Look Up In The Sky
Is it a bird? No
Is it a plane? No
Is it a small blue banana?
YES
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-05-03 8:44 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 ` Steven Hanley [this message]
2000-05-03 10:27 ` 2.3.99-pre6 sound hfs 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
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=390FE6E2.1DDB8599@wibble.net \
--to=sjh@wibble.net \
--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 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).