On Thu, 2008-05-29 at 08:18 -0430, Patrick O'Callaghan wrote:
On Thu, 2008-05-29 at 05:15 -0400, Matthew Saltzman wrote:
> On Wed, 2008-05-28 at 23:00 -0430, Patrick O'Callaghan wrote:
> > On Wed, 2008-05-28 at 21:31 -0400, Marc Ferguson wrote:
> > > Hi,
> > >
> > > The PATH variable seems to already have a value in it:
> > >
> > > PATH=$PATH:$HOME/bin
> >
> > I should hope so. $PATH is where the Shell looks for commands to
> > execute. It's a list of directories to look in.
> >
> > lspci and friends are in /sbin (or sometimes in /usr/sbin). /sbin/lspci
> > etc. will run them. Or do this in .bash_profile:
> >
> > PATH=/sbin:/usr/sbin:$PATH
>
> Better is
>
> PATH=$PATH:/sbin:/usr/sbin
>
> There are some programs with the same name in both /bin and /sbin
> and /usr/bin and /usr/sbin that behave differently. If you are a
> regular user, you want the /bin and /usr/bin ones, not the /sbin
> and /usr/sbim ones.
Yes, but in the context of the question I'm assuming he's root, when you
want it the other way round.
Fair enough, but if he really is *logged in* as root (in a login shell),
these should be in his path already. That's set in /etc/profile.
If he su'd to root without the - (--login) option that would explain his
problem.
poc
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs