public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: mochel@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc/pci deprecation?
Date: 07 Dec 2002 23:18:00 +0200	[thread overview]
Message-ID: <8bPzeb7mw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0212061601550.1010-100000@localhost.localdomain>

mochel@osdl.org (Patrick Mochel)  wrote on 06.12.02 in <Pine.LNX.4.33.0212061601550.1010-100000@localhost.localdomain>:

> But, look the usage model. Who queries PCI information from the system? I
> would argue a) developers, b) power users, and c) users hitting a bug.
>
> a) are going to use lspci, since it's much more powerful. b) may use
> either text format, but it's also likely they'll use a graphical tool.
> Looking at my gnome setup, I do not find anything that lists PCI devices
> (besides a file browser in sysfs :).  And, c) are most likely going to use
> lspci becaus a developer asks for it. I do not remember the last time I
> saw someone ask for the output of /proc/pci. :)

Hmm. Seems I am in neither group.

I use cat /proc/pci for the same reason I use cat /proc/scsi - when  
configuring a box, or adding new hardware, to figure out what I should  
look for and where it is.

I don't particularly care which part of the file system this omes from,  
but I do care about being able to find it quickly, and about it being easy  
(i.e. not need looking at 7868 separate files) and giving the essential  
info (which is the info that can be found in the relevant docs or be fed  
to google).

> I totally agree with you. But, I don't think the answer is in
> consolidating files; I think it's in writing intelligent and efficient
> tools to grok that data.

I seriously distrust tool-based solutions for this. It is far too likely  
that any new tool will be missing when I most need it, and old tools  
already aren't a particularly convincing solution.

I don't want to grovel through 7868 tools just as I don't want to grovel  
through 7868 files. And the more those are, the less likely I am to even  
have heard of them - from the lsXXX tools, the only one I knew about was  
lspci, and lsusb (which seems to be the other one actually installed)  
seems to be a lot more reluctant to give useful info to the non-USB- 
expert.

MfG Kai

  parent reply	other threads:[~2002-12-07 22:28 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 21:13 /proc/pci deprecation? Patrick Mochel
2002-12-06 22:17 ` Jeff Garzik
2002-12-06 22:13   ` Patrick Mochel
2002-12-07 16:23     ` Krzysztof Halasa
2002-12-07 21:18     ` Kai Henningsen [this message]
2002-12-08 20:01       ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2002-12-06 23:18 Petr Vandrovec
2002-12-07  7:44 ` Willy Tarreau
2002-12-07 13:20   ` Tomas Szepe
2002-12-07 19:03   ` Linus Torvalds
2002-12-08  2:56     ` Patrick Mochel
2002-12-08  4:21       ` Linus Torvalds
2002-12-08 20:56         ` Richard Henderson
2002-12-09  1:54           ` Linus Torvalds
2002-12-09  3:59             ` Patrick Mochel
2002-12-09 13:35             ` Ivan Kokshaysky
2002-12-09 14:11             ` Alan Cox
2002-12-09 17:00               ` Linus Torvalds
2002-12-09 18:29                 ` Alan Cox
2002-12-09 18:11                   ` Linus Torvalds
2002-12-09 18:16                     ` Jeff Garzik
2002-12-10  0:43                     ` Alan Cox
2002-12-10  0:30                       ` Linus Torvalds
2002-12-10  5:57                   ` Eric W. Biederman
2002-12-09 23:27                 ` Vojtech Pavlik
2002-12-09 14:14             ` Alan Cox
2002-12-10 16:42         ` Martin Mares
2002-12-07 12:35 ` Erik Hensema
2002-12-07 13:15   ` Dr. David Alan Gilbert
2002-12-07 17:46     ` Arnaldo Carvalho de Melo
2002-12-09 19:03       ` Rogier Wolff
2002-12-09 19:08         ` Arnaldo Carvalho de Melo
2002-12-07 13:14 ` Tomas Szepe
2002-12-07 18:52   ` Petr Vandrovec
2002-12-08 12:30     ` Erik Hensema
2002-12-09 10:14       ` Geert Uytterhoeven
2002-12-09  9:15 Adam J. Richter
2002-12-09 11:00 Nicolas Mailhot

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=8bPzeb7mw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.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