Bug 74213 - Where do I get PCIutils binary?
Summary: Where do I get PCIutils binary?
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: pciutils   
(Show other bugs)
Version: null
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-09-17 23:16 UTC by Nick Mumbach
Modified: 2014-03-17 02:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-09-21 08:18:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Nick Mumbach 2002-09-17 23:16:05 UTC
Description of Problem: While examining my system log, I saw a message about a
redundant entry requesting me to send info + 'lspci -vv' output to a list
address for analysis. However, 'lspci' is not available on my system, except in
an SRPM on CD 4 or 5. 

Version-Release number of selected component (if applicable):

How Reproducible: completely

Steps to Reproduce:

Actual Results:

Expected Results:

Additional Information:
Being a total Linux novice, I have no chance in hell of even extracting the
source RPM, much less compiling and executing it. I can't even figure out how to
get my printer to print! After 3 months, I am starting to wonder if I will be
successful in replacing the evil Redmondian OS ... although I have considered
myself a reasonably competent hacker (in the positive sense) for 30 years!

Comment 1 Barry K. Nathan 2002-09-21 08:18:30 UTC
The pciutils binary package is on disc 1: RedHat/RPMS/pciutils-2.1.10-2.i386.rpm
Also, this package installs lspci as /sbin/lspci. Try "rpm -q pciutils" to make
sure it's really not on your system.

Comment 2 Bill Nottingham 2002-09-23 15:52:23 UTC
lspci is in the pciutils package, and is in the /sbin directory when installed.

Note You need to log in before you can comment on or make changes to this bug.