From: Mathias Kretschmer <posting@blx4.net>
To: linux-kernel@vger.kernel.org
Cc: axboe@suse.de
Subject: 2.4.27rc2, DVD-RW support broke DVD-RAM writes
Date: Wed, 21 Jul 2004 14:40:37 -0400 [thread overview]
Message-ID: <40FEB8A5.6020601@blx4.net> (raw)
Hi,
With 2.4.27rc2 (and I assume anything later than pre5 - that's when
DVD-RW got added) DVD-RAMs have become read-only. Opening a DVD-RAM for
writing results in "EROFS (Read-only file system)" (reported by
'strace'. Let me know if I can provide any further info.
I'd be happy to test any fixes.
Also, any chance we get proper 'DVD-RAM is write-protected' support in
2.4.x ? It'd be really nice if write()/open(O_WRONLY) would fail in
those cases.
Tx,
Mathias
next reply other threads:[~2004-07-21 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 18:40 Mathias Kretschmer [this message]
[not found] <40926261-E3D3-11D8-B01E-00039398BB5E@ieee.org>
[not found] ` <1091397374.6458 .9.camel@patibmrh9>
[not found] ` <20040802121712.GD15884@logos.cnet>
2004-08-02 14:34 ` 2.4.27rc2, DVD-RW support broke DVD-RAM writes Pat LaVarre
2004-08-03 20:07 ` Pat LaVarre
2004-08-03 21:31 ` Pat LaVarre
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=40FEB8A5.6020601@blx4.net \
--to=posting@blx4.net \
--cc=axboe@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox