From: Bob <recbo@nishanet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: dialectical deprecation Re: cdrecord hangs my computer
Date: Mon, 08 Dec 2003 14:22:56 -0500 [thread overview]
Message-ID: <3FD4CF90.3000905@nishanet.com> (raw)
In-Reply-To: <1201390000.1070900656@[10.10.2.4]>
Martin J. Bligh wrote:
>>In contrast, the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP!
>>It's an interface that is based on some random hardware layout mechanism
>>that isn't even TRUE any more, and hasn't been true for a long time. It's
>>not helpful to the user, and it doesn't match how devices are accessed by
>>everything else on the system.
>>
>>It's bad from a technical standpoint (anybody who names a generic device
>>with a flat namespace is just basically clueless), and it's bad from a
>>usability standpoint. It has _zero_ redeeming qualities.
>>
>>
>
>I think the appropriate phrase is "user malevolent" software. Making
>the user interface fit some arcane technica rather than the user is
>rather tragic. Reality is quite complicated enough as it is, without
>deliberately setting out to make it more so.
>
>M.
>
>
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).
-Bob
next prev parent reply other threads:[~2003-12-08 19:04 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 ` Bob [this message]
2003-12-09 21:19 ` dialectical deprecation " bill davidsen
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=3FD4CF90.3000905@nishanet.com \
--to=recbo@nishanet.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).