Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem

[Volker Armin Hemmann]

On Freitag 14 November 2008, Dirk Uys wrote:
> On Fri, Nov 14, 2008 at 12:38 AM, Volker Armin Hemmann
>
> <volker.armin.hemmann@××××××××××××.de> wrote:
> > On Thursday 13 November 2008, Dan Wallis wrote:
> >> On 13/11/2008, Jorge Peixoto de Morais Neto
> >>
> >> <please.no.spam.here@×××××.com> wrote:
> >> > On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis <mrdanwallis@×××××.com>
wrote:
> >> >  > On 12/11/2008, Volker Armin Hemmann
> >> >  >
> >> >  > <volker.armin.hemmann@××××××××××××.de> wrote:
> >> >  >> as root: lspci
> >> >  >
> >> >  > Why as root? I get exactly the same output when I run it as my own
> >> >  > user as when I run it as root. Or have I got my system set up
> >> >  > different to everyone else?
> >> >
> >> > $ lspci
> >> >  bash: lspci: command not found
> >> >  echo ${PATH}
> >> >
> >> > /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/
> >> >game s/bin At least in my system, the lspci binary resides in
> >> > /usr/sbin, which is not in ${PATH}
> >> >  So you should either call lspci as root or issue the explicit command
> >> >  /usr/sbin/lspci
> >>
> >> Yes, I do have that directory in my PATH.
> >>
> >> >  That said, if you want to use the -v flag of lspci (for extra
> >> >  verbosity), you should be root, or you will see some fields filled
> >> >  with <access denied>
> >>
> >> Thanks for the tip; I didn't know about the verbose flag. It looks
> >> like that'll come in useful when I do my next build in a few weeks.
> >
> > not really. For an enduser --verbose isn't very helpfull.
>
> Don't know if I qualify as an end-user, but I find:
>         Kernel driver in use:
> very usefull.

ok, I know my hardware well enough for that ;)