From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L0t2j-0003sH-70 for garchives@archives.gentoo.org; Fri, 14 Nov 2008 07:24:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 143E3E02A0; Fri, 14 Nov 2008 07:24:36 +0000 (UTC) Received: from poseidon.rz.tu-clausthal.de (poseidon.rz.tu-clausthal.de [139.174.2.21]) by pigeon.gentoo.org (Postfix) with ESMTP id E2723E02A0 for ; Fri, 14 Nov 2008 07:24:35 +0000 (UTC) Received: from poseidon.rz.tu-clausthal.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B5C1B212E0F for ; Fri, 14 Nov 2008 08:24:33 +0100 (CET) Received: from tu-clausthal.de (poseidon [139.174.2.21]) by poseidon.rz.tu-clausthal.de (Postfix) with ESMTP id 9A3FD212E06 for ; Fri, 14 Nov 2008 08:24:33 +0100 (CET) Received: from [2001:638:605:eea0:219:66ff:fe86:ce12] (account wevah HELO energy.localnet) by tu-clausthal.de (CommuniGate Pro SMTP 5.2.10) with ESMTPSA id 38826043 for gentoo-user@lists.gentoo.org; Fri, 14 Nov 2008 08:24:33 +0100 From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem Date: Fri, 14 Nov 2008 08:24:30 +0100 User-Agent: KMail/1.10.90 (Linux/2.6.27.5r4; KDE/4.1.71; x86_64; ; ) References: <87od0komh9.fsf@newsguy.com> <200811132338.17210.volker.armin.hemmann@tu-clausthal.de> <79e3aefb0811132240u15c8911exe58417c765104f14@mail.gmail.com> In-Reply-To: <79e3aefb0811132240u15c8911exe58417c765104f14@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811140824.30658.volker.armin.hemmann@tu-clausthal.de> X-Virus-Scanned: by PureMessage V5.4 at tu-clausthal.de X-Archives-Salt: d258dbc6-9f21-4486-a944-21d8b169e700 X-Archives-Hash: a9d6ab39dbfb6b3d6967b467e9020cd9 On Freitag 14 November 2008, Dirk Uys wrote: > On Fri, Nov 14, 2008 at 12:38 AM, Volker Armin Hemmann > > wrote: > > On Thursday 13 November 2008, Dan Wallis wrote: > >> On 13/11/2008, Jorge Peixoto de Morais Neto > >> > >> wrote: > >> > On Thu, Nov 13, 2008 at 7:05 PM, Dan Wallis wrote: > >> > > On 12/11/2008, Volker Armin Hemmann > >> > > > >> > > 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 > >> > >> 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 ;)