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 1L0jyL-0007dl-RS for garchives@archives.gentoo.org; Thu, 13 Nov 2008 21:43:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7AEE8E033C; Thu, 13 Nov 2008 21:43:28 +0000 (UTC) Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.154]) by pigeon.gentoo.org (Postfix) with ESMTP id 58906E033C for ; Thu, 13 Nov 2008 21:43:28 +0000 (UTC) Received: by yx-out-1718.google.com with SMTP id 4so552936yxp.46 for ; Thu, 13 Nov 2008 13:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=o3DftNnJ+h9DI8XUWoJqqUjS3FaQ926854UoT68WBYA=; b=YD0V9przjA4sneTvL0Jkx4TnFrCd6b/ozI7zGHHsfnX+AcLWYUg+Ygzkd2cLcT/GKb DylacSbMdp7IyZJ9QCoM/a6PecBy8Jv7cim3v//9JOegVQd0TfUApok6i8qkyoEcJ/Ak jwO8ZcEhj4lFJMFasVb5+opt1unEWkuw2TDx0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IjEqsix9EuE1BKdfiWBw5dWu+IzPgSTBjvOk8EAlBYNEX7ofW8R74/JYeUN1w16C95 BD26+JDH831gQkDNnd4/qSfJMspksLJJEfIZub4+rR4W1mVD5O4RGdZR3cSqRNio7hJa gQ7Terff3/KmFDnbjp7xXWkKrXwKshZcNRMEc= Received: by 10.142.221.11 with SMTP id t11mr44663wfg.86.1226612605086; Thu, 13 Nov 2008 13:43:25 -0800 (PST) Received: by 10.143.19.19 with HTTP; Thu, 13 Nov 2008 13:43:24 -0800 (PST) Message-ID: <919d41310811131343k5e24734eq2526e6b595ee519b@mail.gmail.com> Date: Thu, 13 Nov 2008 21:43:24 +0000 From: "Dan Wallis" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: How to fix a hefty (emerge) blocking problem In-Reply-To: <38af3d670811131312h508dcacenf08d9c53bce4045d@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=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <87od0komh9.fsf@newsguy.com> <200811121945.32409.volker.armin.hemmann@tu-clausthal.de> <87fxlwojdn.fsf@newsguy.com> <200811122055.28907.volker.armin.hemmann@tu-clausthal.de> <919d41310811131305s73e4ddbet753778d61500b167@mail.gmail.com> <38af3d670811131312h508dcacenf08d9c53bce4045d@mail.gmail.com> X-Archives-Salt: 4c745138-7160-480e-a93e-59373184dfc3 X-Archives-Hash: 2f1dba56a543e61f21895dd1525c59db 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/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 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