linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: dialectical deprecation Re: cdrecord hangs my computer
Date: 9 Dec 2003 21:19:17 GMT	[thread overview]
Message-ID: <br5e8l$nne$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3FD4CF90.3000905@nishanet.com

In article <3FD4CF90.3000905@nishanet.com>, Bob  <recbo@nishanet.com> wrote:

| Today I realize that it's not double deprecation, it's dialectical
| deprecation, for a user who gets caught between the deprecation
| of ide-scsi and cdrecord targbuslun "flat" naming and then the
| cdrecord error message when trying to use a full devpath. The
| user's head is volleyed back and forth as cdrecord maintains
| its "denial".
| 
| cdrecord whines about the full devpath in the first instance,
| will not work if I use 1,0,0 in both places, but seems to
| catch a clue about the devpath stub from the first instance
| in order to use its 1,0,0 nomenclature below that.
| 
| #/etc/default/cdrecord
| CDR_DEVICE=ATAPI:/dev/scsi/host1/bus0/target0/lun0/generic
| #ATAPI:1,0,0 won't work in CDR_DEVICE, but...
| yamaha=   ATAPI:1,0,0   -1      -1      ""
| 
| I'm scared(under-informed) to drop ide-scsi since
| I'm using 3ware and don't know if just scsi-generic
| would be enough for that hd controller(needs ide-scsi?
| 3ware's site doc is not easy to find).

First, I would think you want the device with ATAPI, not the generic. I
don't use that nomenclature so I may be misreading it. I have used plain
/dev/hdc and had it work.

Second, did you use -scanbus to see which three numbers cdrecord wants
with ide-scsi and try those? You don't want ATAPI in front of it, just
dev=1,0,0 or similar.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2003-12-09 21:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-06  8:01 cdrecord hangs my computer Tero Knuutila
2003-12-06  8:12 ` Linus Torvalds
2003-12-06  8:54   ` Ethan Weinstein
2003-12-06 11:59     ` Måns Rullgård
2003-12-06 13:40     ` Wakko Warner
2003-12-06 14:37       ` John Bradford
2003-12-06 21:57       ` Linus Torvalds
2003-12-06 22:02         ` Larry McVoy
2003-12-06 22:32           ` Linus Torvalds
2003-12-07 11:01             ` Eduard Bloch
2003-12-07 16:18               ` Linus Torvalds
2003-12-08 16:21                 ` bill davidsen
2003-12-08 17:46                   ` Linus Torvalds
2003-12-09 12:38                     ` Bill Davidsen
2003-12-08 17:53                   ` Valdis.Kletnieks
2003-12-08 18:53                     ` Linus Torvalds
2003-12-08 19:40                       ` Valdis.Kletnieks
2003-12-09 14:50                         ` Ian Soboroff
2003-12-09 20:42                           ` Mikael Pettersson
2003-12-08 16:24                 ` Martin J. Bligh
2003-12-08 19:22                   ` dialectical deprecation " Bob
2003-12-09 21:19                     ` bill davidsen [this message]
2003-12-09 22:31                     ` David Lang
2003-12-09 21:51                       ` Måns Rullgård
2003-12-08  4:36           ` Bob
2003-12-08  4:51             ` Larry McVoy
2003-12-07  0:16         ` Wakko Warner
2003-12-07  3:31           ` William Lee Irwin III
2003-12-07  4:49           ` Linus Torvalds
2003-12-08 16:13         ` bill davidsen
2003-12-08 17:38           ` Linus Torvalds
2003-12-08 19:41             ` bluefaceplate demographics " Bob
2003-12-06 16:42     ` Linus Torvalds

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='br5e8l$nne$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --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;
as well as URLs for NNTP newsgroup(s).