From: James Pearson <james-p@moving-picture.com>
To: Charles Mason <mason@csit.fsu.edu>, linux-kernel@vger.kernel.org
Subject: Re: HFS bug
Date: Wed, 12 Nov 2003 20:32:48 +0000 [thread overview]
Message-ID: <3FB298F0.7030604@moving-picture.com> (raw)
> This may or may not be a bug, but I figured that sending out the message
> would do better good than not sending one out at all:
>
> when I run the command:
>
> # mount -t hfs /dev/scd0 /mnt/cdrom
>
> The kernel gives an Oops that traces back to line buffer.c:2555 (kernel
> version 2.4.23-pre1). I'd attach the Oops output, but I'm on a remote
> machine now.
You could try something like:
mount -r -t hfs -o loop /dev/scd0 /mnt/cdrom
Or, have a look at Roman Zippel's new HFS+/HFS driver at:
http://www.ardistech.com/hfsplus/
James Pearson
next reply other threads:[~2003-11-12 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 20:32 James Pearson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-12 19:26 HFS bug Charles Mason
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=3FB298F0.7030604@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@csit.fsu.edu \
/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