From: Dale Amon <amon@vnl.com>
To: linux-kernel@vger.kernel.org
Subject: Problem with ufs nextstep in 2.6.18 (debian)
Date: Sun, 15 Apr 2007 02:38:49 +0100 [thread overview]
Message-ID: <20070415013848.GG4770@vnl.com> (raw)
I recently noticed that I can no longer read my
images of NeXTstep floppies on certain machines.
All are running an up to date etch distribution
but the difference between where I can read or not
read seems to be the linux version. On a 2.6.18
machine:
# mount -t ufs -o ro,ufstype=nextstep,loop nextfloppy-fd0a.ufs /floppy
# ls /floppy
ls: reading directory /floppy: Input/output error
On a 2.6.13 machine it still works fine:
# mount -t ufs -o ro,ufstype=nextstep,loop nextfloppy-fd0a.ufs /floppy
# ls /floppy/
private
# ls /floppy/private
Drivers
Have there been any recent changes that would cause a
breakage in this area?
next reply other threads:[~2007-04-15 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 1:38 Dale Amon [this message]
2007-04-15 23:11 ` Problem with ufs nextstep in 2.6.18 (debian) Dale Amon
-- strict thread matches above, loose matches on Subject: below --
2007-04-16 7:32 Evgeniy Dushistov
2007-04-16 16:04 ` Dale Amon
2007-04-17 1:10 ` Dale Amon
2007-04-19 16:39 ` Dale Amon
2007-11-20 20:29 Dave Bailey
2007-11-21 15:37 ` Jan Kara
2007-11-22 4:19 ` Evgeniy Dushistov
2007-11-25 1:26 Dave Bailey
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=20070415013848.GG4770@vnl.com \
--to=amon@vnl.com \
--cc=linux-kernel@vger.kernel.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.