public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dan Wallis" <mrdanwallis@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Date: Thu, 13 Nov 2008 21:43:24 +0000	[thread overview]
Message-ID: <919d41310811131343k5e24734eq2526e6b595ee519b@mail.gmail.com> (raw)
In-Reply-To: <38af3d670811131312h508dcacenf08d9c53bce4045d@mail.gmail.com>

On 13/11/2008, Jorge Peixoto de Morais Neto
<please.no.spam.here@gmail.com> wrote:
> On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis <mrdanwallis@gmail.com> wrote:
>  > On 12/11/2008, Volker Armin Hemmann
>  > <volker.armin.hemmann@tu-clausthal.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/games/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.

Thanks

Dan



  reply	other threads:[~2008-11-13 21:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 17:58 [gentoo-user] How to fix a hefty (emerge) blocking problem Harry Putnam
2008-11-12 18:31 ` Dan Wallis
2008-11-12 18:53   ` [gentoo-user] " Harry Putnam
2008-11-12 18:38 ` [gentoo-user] " Mark Knecht
2008-11-12 18:44 ` Dirk Heinrichs
2008-11-12 19:11   ` [gentoo-user] " Harry Putnam
2008-11-12 19:15     ` Dirk Heinrichs
2008-11-12 19:20       ` Harry Putnam
2008-11-12 21:05         ` Dirk Heinrichs
2008-11-12 21:22       ` Neil Bothwick
2008-11-12 19:55     ` Volker Armin Hemmann
2008-11-12 20:03   ` Harry Putnam
2008-11-12 20:36     ` Volker Armin Hemmann
2008-11-12 21:04       ` Dirk Heinrichs
2008-11-12 18:45 ` [gentoo-user] " Volker Armin Hemmann
2008-11-12 19:05   ` [gentoo-user] " Harry Putnam
2008-11-12 19:25     ` Andrey Falko
2008-11-12 19:33       ` Harry Putnam
2008-11-12 19:27     ` Harry Putnam
2008-11-12 19:55     ` Volker Armin Hemmann
2008-11-13 21:05       ` Dan Wallis
2008-11-13 21:12         ` Alan McKinnon
2008-11-13 21:12         ` Jorge Peixoto de Morais Neto
2008-11-13 21:43           ` Dan Wallis [this message]
2008-11-13 22:38             ` Volker Armin Hemmann
2008-11-14  6:40               ` Dirk Uys
2008-11-14  7:09                 ` Dale
2008-11-14  7:24                 ` Volker Armin Hemmann
2008-11-13 21:34         ` Volker Armin Hemmann
2008-11-12 20:23   ` Harry Putnam
2008-11-12 21:11     ` Alan McKinnon
2008-11-12 21:24     ` Neil Bothwick
2008-11-12 20:54   ` Harry Putnam
2008-11-12 18:49 ` [gentoo-user] " Andrey Falko
2008-11-12 19:13   ` Dirk Heinrichs

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=919d41310811131343k5e24734eq2526e6b595ee519b@mail.gmail.com \
    --to=mrdanwallis@gmail.com \
    --cc=gentoo-user@lists.gentoo.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