public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	Kurt Garloff <garloff@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Linux SCSI list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] /proc/scsi/map
Date: Thu, 20 Jun 2002 22:55:37 +0200	[thread overview]
Message-ID: <3D124149.6010901@evision-ventures.com> (raw)
In-Reply-To: Pine.LNX.4.44.0206201115460.8225-100000@home.transmeta.com

Użytkownik Linus Torvalds napisał:

> For example, to be useful, every driver that knows about disks should make
> sure they show up with some standard name (the old "disk" vs "disc" war
> ;), exactly so that you _should_ be able to do something like
> 
> 	find /devices -name disk*

Not good. find /devices -name "/sd@* -- will be unambigious.
There are good reaons they do it like they do on the "other unix OS"...

> and be able to enumerate every disk in the whole system.

> 
> 	/devices/disks/disk0 -> ../../pci0/00:02.0/02:1f.0/03:07.0/disk0
                  ^^^^^^^^^^ You notice the redundancy in naming here :-).

> 	               disk1 -> ../../pci0/00:02.3/usb_bus/001000/dev1
> 
> the same way that Pat already planned to do the mappings for network
> devices in /devices/network/eth*.

Boah the chierachies are already deep enough. /devices/net/eth@XX
will cut it.

> Is this done? No. But is it fundamentally hard? Nope. Useful? You be the
> judge.  Imagine yourself as a installer searching for disks. Or imagine
> yourself as a initrd program that runs at boot, setting up irq routings
> etc before the "real boot".

Yes but again the most content files found there are already inventing
interfaces on the heap. /name /irq /resources /power this will end the same
as similar attempts ended already - in a mess.

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2002-06-20 20:55 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020620112543.GD26376@gum01m.etpnet.phys.tue.nl>
2002-06-20 15:34 ` [PATCH] /proc/scsi/map Linus Torvalds
2002-06-20 16:30   ` Martin Dalecki
2002-06-20 16:58     ` James Bottomley
2002-06-20 18:27       ` Linus Torvalds
2002-06-20 20:55         ` Martin Dalecki [this message]
2002-06-20 21:04           ` Linus Torvalds
2002-06-20 21:36             ` Martin Dalecki
2002-06-20 20:12     ` Patrick Mochel
2002-06-20 22:29       ` Martin Dalecki
2002-06-22 18:42         ` Pavel Machek
     [not found]       ` <20020621092943.D1243@austin.ibm.com>
2002-06-21 16:17         ` Patrick Mochel
2002-07-03  4:29         ` [PATCH] driverfs scsi for 2.5.24 Douglas Gilbert
2002-07-03 14:34           ` James Bottomley
2002-07-05  1:45             ` Douglas Gilbert
2002-07-05 18:50               ` Patrick Mochel
2002-07-05 18:31             ` Patrick Mochel
2002-06-21 21:33       ` [PATCH] /proc/scsi/map Oliver Xymoron
2002-06-22  4:38         ` Nick Bellinger
2002-06-22 19:41           ` Douglas Gilbert
2002-06-22 19:11             ` Nick Bellinger
2002-06-25 18:13             ` Patrick Mochel
2002-06-25 16:05         ` Patrick Mochel
2002-06-25 16:57           ` Oliver Xymoron
2002-06-25 18:58             ` Patrick Mochel
2002-07-03  1:01               ` Pavel Machek
2002-06-20 18:32   ` Kurt Garloff
2002-06-20 18:53     ` Linus Torvalds
2002-06-21  9:07     ` Kurt Garloff
2002-06-22 17:24 David Brownell
2002-06-22 17:48 ` Roman Zippel
2002-06-22 20:11   ` Douglas Gilbert
2002-06-22 20:57     ` Roman Zippel
2002-06-22 18:18 ` Nick Bellinger
2002-06-24  1:50   ` David Brownell
2002-06-25 16:46   ` Patrick Mochel
2002-06-25 16:33 ` Patrick Mochel
2002-06-25 17:49   ` David Brownell
2002-06-26 23:39     ` Nick Bellinger
2002-07-03  0:59     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 23:59 Grover, Andrew
     [not found] <200206200711.RAA10165@thucydides.inspired.net.au>
2002-06-20 15:13 ` Linus Torvalds
2002-06-20 15:36   ` Dave Jones
2002-06-20 17:01     ` Linus Torvalds
2002-06-20 16:55   ` Andries Brouwer
     [not found]   ` <20020620165553.GA16897@win.tue.nl>
2002-06-20 17:52     ` Patrick Mansfield
2002-06-20 18:36       ` Linus Torvalds
2002-06-20 18:52         ` James Bottomley
2002-06-20 19:15           ` Linus Torvalds
2002-06-20 16:28             ` Benjamin Herrenschmidt
2002-06-21  0:46               ` Linus Torvalds
2002-06-20 16:49                 ` Benjamin Herrenschmidt
2002-06-20 20:06             ` Oliver Xymoron
2002-06-22 18:27         ` Pavel Machek
2002-06-20 18:11     ` Linus Torvalds
2002-06-20 22:59       ` Martin Schwenke
2002-06-20 23:13         ` Linus Torvalds
2002-06-22 18:25           ` Pavel Machek
2002-06-26 16:03       ` Ihno Krumreich
2002-06-20 19:55     ` Greg KH
2002-06-20 19:18   ` Patrick Mochel
2002-06-21  6:28   ` Mike Touloumtzis
2002-06-20  0:44 Kurt Garloff
2002-06-20  5:03 ` Linus Torvalds
2002-06-20  7:09   ` Martin Schwenke
2002-06-20 11:25   ` Kurt Garloff

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=3D124149.6010901@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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