From: Erik Hensema <usenet@hensema.xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: /proc/pci deprecation?
Date: Sun, 8 Dec 2002 12:30:00 +0000 (UTC) [thread overview]
Message-ID: <slrnav6eq7.6d2.usenet@dexter.hensema.net> (raw)
In-Reply-To: <20021207185252.GC1588@ppc.vc.cvut.cz>
Petr Vandrovec (vandrove@vc.cvut.cz) wrote:
> On Sat, Dec 07, 2002 at 02:14:24PM +0100, Tomas Szepe wrote:
>> > > IMO, yes, since those tools provide the summary, and exist almost purely in
>> > > userspace. I forgot to mention in the orginal email that we could also drop
>> > > the PCI names database, right? This would save a considerable amount in the
>> > > kernel image alone..
>> >
>> > If you want, make it user configurable like it was during 2.2.x. But
>> > I personally prefer descriptive names and system overview I can parse
>> > without having mounted /usr to get working lspci.
>>
>> Actually I'm inclined to insist that lspci belong in /sbin. Really. :)
>
> Try it. At least on Debian it is useless without name database, which lives in
> /usr/share/misc/pci.ids... I can read numbers directly from /proc/bus/pci, if
> I want numbers.
Hmmmm, on SuSE 8.0 too. I consider this a bug. Or at least a misfeature.
Binaries in /bin and /sbin should not need anything from /usr.
--
Erik Hensema <erik@hensema.net>
next prev parent reply other threads:[~2002-12-08 12:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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-13 12:36 ` kernel isapnp (2.4.20) h-peter recktenwald
2002-12-09 13:35 ` /proc/pci deprecation? 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 [this message]
2002-12-09 10:14 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:00 Nicolas Mailhot
2002-12-09 9:15 Adam J. Richter
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
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=slrnav6eq7.6d2.usenet@dexter.hensema.net \
--to=usenet@hensema.xs4all.nl \
--cc=erik@hensema.xs4all.nl \
--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
all inboxes | Powered by JetHome®