From: Andrew Morton <akpm@osdl.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Christian Lohmaier <lohmaier@gmx.de>
Subject: Re: [Bugme-new] [Bug 6745] New: kernel hangs when trying to read atip wiith cdrecord
Date: Sun, 25 Jun 2006 04:37:02 -0700 [thread overview]
Message-ID: <20060625043702.e7e2d20f.akpm@osdl.org> (raw)
In-Reply-To: <1151233643.4940.13.camel@laptopd505.fenrus.org>
On Sun, 25 Jun 2006 13:07:23 +0200
Arjan van de Ven <arjan@infradead.org> wrote:
> On Sat, 2006-06-24 at 14:47 -0700, Andrew Morton wrote:
> > > I simply try to use "cdrecord dev=ATAPI:1,0,0 -atip" as root.
>
>
> one issue is that it's a lot better to use --dev=/dev/hda (or whatever
> your cdrom device is.. usually even /dev/cdrom or /dev/cdwriter will
> work, depends on your distro)... that is what most people use and that
> is the interface that's actively supported and debugged...
cc added.
next prev parent reply other threads:[~2006-06-25 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606242036.k5OKaSvp031813@fire-2.osdl.org>
2006-06-24 21:47 ` [Bugme-new] [Bug 6745] New: kernel hangs when trying to read atip wiith cdrecord Andrew Morton
2006-06-25 11:05 ` Jan Engelhardt
2006-06-25 11:36 ` Andrew Morton
2006-06-25 19:00 ` Christian Lohmaier
2006-06-25 11:07 ` Arjan van de Ven
2006-06-25 11:37 ` Andrew Morton [this message]
2006-06-26 18:59 ` Christian Lohmaier
2006-06-25 10:53 Joerg Schilling
2006-06-25 11:06 ` Andrew Morton
2006-06-25 11:46 ` Joerg Schilling
2006-06-25 19:35 ` Joerg Schilling
-- strict thread matches above, loose matches on Subject: below --
2006-06-25 19:40 Joerg Schilling
2006-06-26 0:01 ` Christian Lohmaier
2006-06-26 18:21 Joerg Schilling
2006-06-26 18:49 Christian Lohmaier
2006-06-28 7:18 Joerg Schilling
2006-06-28 7:29 Joerg Schilling
2006-06-28 11:19 ` Christian Lohmaier
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=20060625043702.e7e2d20f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lohmaier@gmx.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