mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Reppert <repp0017@umn.edu>
To: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>,
	linux-kernel@vger.kernel.org
Subject: Re: SCSI emulation - CD-R
Date: Wed, 17 Mar 2004 15:09:27 CST	[thread overview]
Message-ID: <200403172109.i2HL9RcP007960@qix.software.umn.edu> (raw)

On 17 Mar 2004, Karel Kulhavy <Karel Kulhavy
<clock@atrey.karlin.mff.cuni.cz>> wrote:
> Hello
> 
> When I want an ATAPI CD-writer to appear on device (21,0) (/dev/sg0)
> using the scsi emulation mechanisms, which bits have to be on and off
> from the following 4 config bits in make menuconfig?
> * IDE/ATAPI CDROM support
> * SCSI emulation support
> * SCSI CDROM support
> * SCSI generic support
> 
> How can this information be derived from linux kernel documentation? I
> would like to understand the mechanism beyond deriving this information
> from the linux kernel documentation so that next time, when solving some
> other problem, I could use the same approach and not need to write here
> on linux-kernel.

The first time I had to set up a CD writer to work with Linux, I checked
(what is now) the Linux Documentation Project http://www.tldp.org/ which
has a nice CD-writer HOWTO document, detailing not only how you need to
configure your kernel, but also how to use the userspace tools to burn
CDs.

However, with recent kernels and tools, you don't need to (and shouldn't)
use ide-scsi to use ATAPI CD writers. cdrecord dev=/dev/hdc (assuming
that's
the correct IDE device) works just fine.

Matt


             reply	other threads:[~2004-03-17 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 21:09 Matthew Reppert [this message]
2004-03-18 12:48 ` Karel Kulhavy
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 20:23 Karel Kulhavy

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=200403172109.i2HL9RcP007960@qix.software.umn.edu \
    --to=repp0017@umn.edu \
    --cc=clock@atrey.karlin.mff.cuni.cz \
    --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®