| 1 |
On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis <mrdanwallis@×××××.com> wrote: |
| 2 |
> On 12/11/2008, Volker Armin Hemmann |
| 3 |
> <volker.armin.hemmann@××××××××××××.de> wrote: |
| 4 |
>> as root: lspci |
| 5 |
> |
| 6 |
> Why as root? I get exactly the same output when I run it as my own |
| 7 |
> user as when I run it as root. Or have I got my system set up |
| 8 |
> different to everyone else? |
| 9 |
$ lspci |
| 10 |
bash: lspci: command not found |
| 11 |
echo ${PATH} |
| 12 |
/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.2:/opt/sun-jre-bin-1.5.0.06/bin:/opt/sun-jre-bin-1.5.0.06/javaws:/usr/games/bin |
| 13 |
At least in my system, the lspci binary resides in /usr/sbin, which is |
| 14 |
not in ${PATH} |
| 15 |
So you should either call lspci as root or issue the explicit command |
| 16 |
/usr/sbin/lspci |
| 17 |
|
| 18 |
That said, if you want to use the -v flag of lspci (for extra |
| 19 |
verbosity), you should be root, or you will see some fields filled |
| 20 |
with <access denied> |
| 21 |
|
| 22 |
-- |
| 23 |
Software is like sex: it is better when it is free - Linus Torvalds |
Archives