Gentoo Archives: gentoo-user

From: Volker Armin Hemmann <volker.armin.hemmann@××××××××××××.de>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Date: Thu, 13 Nov 2008 22:38:24
Message-Id: 200811132338.17210.volker.armin.hemmann@tu-clausthal.de
In Reply to: Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem by Dan Wallis
1 On Thursday 13 November 2008, Dan Wallis wrote:
2 > On 13/11/2008, Jorge Peixoto de Morais Neto
3 >
4 > <please.no.spam.here@×××××.com> wrote:
5 > > On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis <mrdanwallis@×××××.com> wrote:
6 > > > On 12/11/2008, Volker Armin Hemmann
7 > > >
8 > > > <volker.armin.hemmann@××××××××××××.de> wrote:
9 > > >> as root: lspci
10 > > >
11 > > > Why as root? I get exactly the same output when I run it as my own
12 > > > user as when I run it as root. Or have I got my system set up
13 > > > different to everyone else?
14 > >
15 > > $ lspci
16 > > bash: lspci: command not found
17 > > echo ${PATH}
18 > >
19 > > /usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.
20 > >2:/opt/sun-jre-bin-1.5.0.06/bin:/opt/sun-jre-bin-1.5.0.06/javaws:/usr/game
21 > >s/bin At least in my system, the lspci binary resides in /usr/sbin, which
22 > > is not in ${PATH}
23 > > So you should either call lspci as root or issue the explicit command
24 > > /usr/sbin/lspci
25 >
26 > Yes, I do have that directory in my PATH.
27 >
28 > > That said, if you want to use the -v flag of lspci (for extra
29 > > verbosity), you should be root, or you will see some fields filled
30 > > with <access denied>
31 >
32 > Thanks for the tip; I didn't know about the verbose flag. It looks
33 > like that'll come in useful when I do my next build in a few weeks.
34
35 not really. For an enduser --verbose isn't very helpfull.

Replies

Subject Author
Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem Dirk Uys <dirkcuys@×××××.com>