mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Subject: Re: /proc/pci deprecation?
Date: 08 Dec 2002 21:01:55 +0100	[thread overview]
Message-ID: <m3lm30l1os.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <8bPzeb7mw-B@khms.westfalen.de>

kaih@khms.westfalen.de (Kai Henningsen) writes:

> 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.

Still there is lspci. Much better than just a file in /proc, in fact:
you can have short or long output, and you always have device and
vendor names (with /proc/pci it isn't true).
As long as the database contains the names, of course (the same as with
kernel, with the difference that it doesn't use kernel space).

> 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).

Same as "ps xaf". I usually don't look at /proc/*/cmdline etc either.
This doesn't mean I want a file in /proc which contains "ps axf" output.

Anyway, /proc/pci is currently broken (the kernel don't know what
hot-pluggable devices will you use, and doesn't preserve the necessary
names). If we want it in /proc, could it be corrected?


I always thought of /proc/pci as of temporary q&d debug tool.
-- 
Krzysztof Halasa
Network Administrator

  reply	other threads:[~2002-12-09  2:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 21:13 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
2002-12-08 20:01       ` Krzysztof Halasa [this message]
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=m3lm30l1os.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --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

Powered by JetHome