From: Giuliano Pochini <pochini@shiny.it>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org,
Hollis Blanchard <hollis-lists@austin.rr.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Tom Rini <trini@kernel.crashing.org>,
Martin Costabel <costabel@wanadoo.fr>
Subject: Re: hfs cdrom broken in 2.4.13pre
Date: Tue, 23 Oct 2001 15:16:12 +0200 (CEST) [thread overview]
Message-ID: <XFMail.20011023151612.pochini@shiny.it> (raw)
In-Reply-To: <Pine.LNX.4.33.0110231311010.1680-100000@opal.biophys.uni-duesseldorf.de>
> One would hope so. All I remember about CDROMs is they use a different
> blocksize which causes all sorts of funny side effects in generic code
> that assumes the only sane blocksize is 512.
No. The point is that filesystems should not make assumptions about
hardware block size (except it being power of 2 I believe). If there
was code in block layer to provide broken FS's compatibility and that
code has been removed, then we must fix the FS. Who's HFS maintainer ?
> So mounting HFS CDROMs no longer panics ?
They always worked fine for me.
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-23 13:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011022155617.B6673@cpe-24-221-152-185.az.sprintbbd.net>
2001-10-23 10:08 ` hfs cdrom broken in 2.4.13pre Michael Schmitz
2001-10-23 11:04 ` Martin Costabel
2001-10-23 11:26 ` Michael Schmitz
2001-10-23 13:16 ` Giuliano Pochini [this message]
2001-10-23 13:26 ` Alan Cox
2001-10-23 15:24 ` Michael Schmitz
2001-10-23 15:52 ` Alan Cox
2001-10-23 16:31 ` Michael Schmitz
2001-10-23 16:51 ` Alan Cox
2001-10-23 20:08 ` Michael Schmitz
2001-10-23 20:49 ` Alan Cox
2001-10-24 7:21 ` Michael Schmitz
2001-10-23 19:59 ` Benjamin Herrenschmidt
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=XFMail.20011023151612.pochini@shiny.it \
--to=pochini@shiny.it \
--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).