linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cdrecord hangs my computer
Date: Mon, 8 Dec 2003 09:38:53 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312080927510.13236@home.osdl.org> (raw)
In-Reply-To: <br27v2$fdh$1@gatekeeper.tmr.com>



On Mon, 8 Dec 2003, bill davidsen wrote:

> In article <Pine.LNX.4.58.0312061044450.2092@home.osdl.org>,
> Linus Torvalds  <torvalds@osdl.org> wrote:
> |
> | And you liked the fact that you were supposed to write "dev=0,0,0" or
> | something strange like that? What a piece of crap it was.
>
>   Actually, dev=0,0,0 or dev=/dev/hdc are neither particularly portable;
> each can be something else on another machine. At least /dev/sr0 (or
> scd0 if you go to that church) are a bit less likely to change.

Actually, the sane thing to do is to use "/dev/cdrom", which is likely to
be right, and if it isn't, you can always fix it (and you can fix it
_dynamically_ with something like "udev" - so it will do the right thing
even if your cdrom happens to be hot-pluggable).

The only time that ends up being confusing is if you have multiple CD-roms
(which used to be common - DVD reader and CD writer - but is going away
again on "normal" machines due to combo drives). And then you really
actually care about position, so then you are likely happy to go back to
"/dev/hdc" or "/dev/usb-cdrom" or something like that to specify _which_
CD-RW you're talking about.

>   If I were going to do that at all, I would have used controller, bus,
> device, LUN notation, (0,0,0,0) and been done with it.

Well, even that isn't enough.

What's the format for iSCSI? What's the format for buses that are
hierarchical? The thing is, naming is _hard_, and the only way to name
things in a generic manner is:
 - allow multiple levels (ie not a fixed "always 3/4 levels" format)
 - don't use numbers (part of the name might be a hostname or whatever).

Which means that you have to have names that are (a) hierarchical and (b)
strings as the individual path components.

In addition, you clearly _do_ want to have the "simplified" form (aka
the "just point me to the 'cdrom', dammit!" format). Because quite
frankly, the regular user that doesn't care, doesn't really want to know
how his (single) CD-ROM is connected, and if he has to look it up he'll
have all the right in the world to say "This computer is _stupid_".

And guess what you end up with if you have these requirements? A
filesystem. No, "/dev/cdrom" and "/dev/iscsi/cdrom.work.com/cd5" aren't
the _only_ ways of naming things, but they are clear, and they are
sufficient.

And "0,0,0,0" fails _both_ of these obvious requirements. It's neither
clear _nor_ sufficient.

			Linus

  reply	other threads:[~2003-12-08 17:39 UTC|newest]

Thread overview: 40+ 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
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 [this message]
2003-12-08 19:41             ` bluefaceplate demographics " Bob
2003-12-06 16:42     ` Linus Torvalds
2003-12-06 12:39 Tero Knuutila
2003-12-06 18:27 Tero Knuutila
2003-12-06 19:08 Tero Knuutila
2003-12-08  9:31 Douglas Gilbert
2003-12-11 12:56 ` Jens Axboe
2003-12-11 16:15   ` Linus Torvalds
2003-12-15 13:29 Paul Marinceu

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=Pine.LNX.4.58.0312080927510.13236@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=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).