mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Franck <afranck@gmx.de>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: ATAPI burner and IDE SCSI emulation
Date: Tue, 27 Mar 2001 01:13:56 +0200	[thread overview]
Message-ID: <01032701135600.13773@dg1kfa> (raw)

Hello people,

after having "upgraded" (?) my distro from my wonderfully hand-configured 
Debian system (which I unfortunately wrecked up lately) to S*SE 7.1, I'm now 
really displeasured about the IDE-SCSI emulation thing for my ATAPI CD 
roaster. Not that I was not able to set it up correctly, but being a bit 
fastidious and used to be able to configure almost everything I wanted, 
including what drivers I wanted to load, by choosing modules I was deeply 
disappointed about the sof the IDE SCSI emulation driver, which seems really 
baroque. 

For the unknowing, here are the general "newbie" steps nneded to make a 
simple ATAPI CD roaster roast at all: Compile the kernel with IDE-SCSI 
support enabled (or as a module), then you have to pass a mysterious 
"hdx=ide-scsi" on the kernel commandline (through LILO or whatsoever), then 
the "normal" IDE driver refuses to take any control over your CD burner. This 
makes it possible for the IDE SCSI driver to take this job.

To actually USE my burner, it even gets more complicated (... I always speak 
for the "Joe Blow" user, I have gone through all this and succeeded 
finally...) - I have not only to load the SCSI CD-ROM driver to be able to 
read any CDs with the burner, reset the /dev/cdrom (or /dev/cdburner) link 
accordingly, but I also need this mysterious generic SCSI module loaded...

People, my say this is the biggest mess of configuration for me since I last 
built up my first WNOS TCP/IP system, which was 7 years ago. And this is my 
mission:

Clean this mess up. Make CD roasting work fine without this SCSI crap (sorry, 
no offense intended, but from the "user perspective" its friendliness goes 
far to -ininity...)

I'd appreciate any comments, am willing to take big slaps on my head from any 
major wood part, and would like to know if anything/anyone is already working 
towards this, or is doing any other tasks in this area.

Im particular I'd better look at the packet writing stuff (who's involved? 
Jens Axboe?) before I start anything too big :) Again, any comments or 
pointers to other projects are welcome, I can't wait to be able to toast CDs 
on my machine without going through this nightmare again :-)

Greetings (and: please don't take anything personal or too serious, it's just 
me being frustrated after having set up my system and nothing working 
again...)

Andreas

             reply	other threads:[~2001-03-26 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 23:13 Andreas Franck [this message]
2001-03-27  2:41 ` Ben Ford

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=01032701135600.13773@dg1kfa \
    --to=afranck@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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®