From: Nix <nix@esperi.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: writable packet CD mounting and non-root formatting in 2.6.26.x?
Date: Wed, 06 Aug 2008 20:18:52 +0100 [thread overview]
Message-ID: <87abfqvtnn.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <87ej52vtxq.fsf@hades.wkstn.nix> (nix@esperi.org.uk's message of "6 Aug 2008 20:13:41 +0100")
On 6 Aug 2008, nix@esperi.org.uk told this:
> It seems to be impossible to mount packet-written CD-RWs writably in
> 2.6.26.x, even as root. Things worked in 2.6.25.x.
Formatting them as non-root (with cdrwtool 1.0.0b3) seems broken too:
nix@hades 129 /home/nix% cdrwtool -d /dev/cdrw -q < /dev/null
using device /dev/cdrw
7294KB internal buffer
setting write speed to 4x
wait_cmd: Bad address
Command failed: bb 00 ff ff 02 c0 00 00 00 00 00 00 - sense 00.00.00
set speed
can't unlock door
It seems to work as root (well, it's got further but the lengthy
formatting process is still continuing).
next prev parent reply other threads:[~2008-08-06 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 19:12 writable packet CD mounting " Nix
2008-08-06 19:18 ` Nix [this message]
2008-08-08 3:14 ` Alexey Dobriyan
2008-08-08 5:37 ` Alexey Dobriyan
2008-08-21 23:25 ` Nix
2008-08-23 21:48 ` Writable packet CD-RW mounting broken in 2.6.26 by your commit 68154e90c9d1492d570671ae181d9a8f8530da55 Nix
2008-08-24 5:48 ` FUJITA Tomonori
2008-08-24 17:33 ` Nix
2008-08-25 5:22 ` [PATCH 0/2] bio: blk_rq_map_* bounce support fixes FUJITA Tomonori
2008-08-25 5:22 ` [PATCH 1/2] bio: fix bio_copy_kern() handling of bio->bv_len FUJITA Tomonori
2008-08-25 5:22 ` [PATCH 2/2] bio: fix __bio_copy_iov() " FUJITA Tomonori
2008-08-25 18:34 ` [PATCH 0/2] bio: blk_rq_map_* bounce support fixes Jens Axboe
2008-08-25 5:32 ` Writable packet CD-RW mounting broken in 2.6.26 by your commit 68154e90c9d1492d570671ae181d9a8f8530da55 FUJITA Tomonori
2008-08-25 10:12 ` Nix
2008-08-09 9:24 ` pktcdvd: BKL pushdown fallout (was Re: writable packet CD mounting in 2.6.26.x?) Alexey Dobriyan
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=87abfqvtnn.fsf@hades.wkstn.nix \
--to=nix@esperi.org.uk \
--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
all inboxes | Powered by JetHome®