From: Svein Ove Aas <svein.ove@aas.no>
To: Alex Goddard <agoddard@purdue.edu>, svein@brage.info
Cc: Alexander Hoogerhuis <alexh@ihatent.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-tst2-mm4 and ide-scsi
Date: Wed, 6 Aug 2003 03:46:41 +0200 [thread overview]
Message-ID: <200308060346.45771.svein.ove@aas.no> (raw)
In-Reply-To: <Pine.LNX.4.56.0308052041560.3753@dust>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
onsdag 6. august 2003, 03:43, skrev Alex Goddard:
> On Wed, 6 Aug 2003 svein@brage.info wrote:
> > > [Snip]
> > >
> > > Tried burning without ide-scsi? As long as you have a recent enough
> > > version of cdrtools, ide-scsi is no longer necessary in 2.5/2.6. I
> > > haven't used ide-scsi in months, and CD burning works just fine.
> >
> > Well, then, what about cdrdao?
> > I sometimes need to make more exact copies of a CD than cdrtools allows,
> > and cdrdao doesn't seem top support IDE devices yet.
>
> I'm pretty much positive that cdrecord has a disk at once version that
> doesn't make anything explode.
The only one I'm aware of is the '-dao' option, but that's no good when what I
really want to do is burn a CUE sheet and files, or copy another CD. It still
expects an ISO file(or WAV, whatever) as input.
Actualy, the only use for that option that I'm aware of is to help a few
troubled CD-readers.
- - Svein Ove Aas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/MF4B9OlFkai3rMARAmO0AKCU/KURqWB13moIM/voB0QdVLgcEACgoNqG
ZFYF/sa/VxLYXbJtianvTyA=
=FuR3
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-08-06 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 19:27 2.6.0-tst2-mm4 and ide-scsi Alexander Hoogerhuis
2003-08-04 20:21 ` Alex Goddard
2003-08-06 1:31 ` svein
2003-08-06 1:43 ` Alex Goddard
2003-08-06 1:46 ` Svein Ove Aas [this message]
2003-08-06 2:15 ` Con Kolivas
2003-08-06 2:13 ` Svein Ove Aas
2003-08-06 2:21 ` Con Kolivas
2003-08-06 13:57 ` Svein Ove Aas
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=200308060346.45771.svein.ove@aas.no \
--to=svein.ove@aas.no \
--cc=agoddard@purdue.edu \
--cc=alexh@ihatent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=svein@brage.info \
/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).