What to do when a command isn't found?

Les Mikesell lesmikesell at gmail.com
Thu Jul 6 19:03:20 UTC 2006

On Thu, 2006-07-06 at 14:54 -0400, starcycle at gmail.com wrote:
> On 7/6/06, fedora-list-request at redhat.com
> <fedora-list-request at redhat.com> wrote:
> >
> >
> > Both the shell and the 'which' command search the directories in your
> > PATH variable.  ifconfig is in /sbin along with other utilities
> > used for system administration. When you log in as root, /sbin and
> > /usr/sbin is included in the PATH setting. Normally other users don't
> > get those, although like most other things you can change that to
> > suit yourself.  If you "su - " from another logged in user you will
> > pick up root's login environment.  If you su without the '-' you keep
> > the original environment and thus the PATH.
> >
> they weren't for me, on either system i installed. i had to manually
> add those to the path in /root/.bashrc to have access to them without
> typing /sbin/<command> or /usr/sbin/<command>, etc. everytime. damned
> annoying. i haven't read the whole digest on this topic, but i can see
> how someone  new to linux could be confused by not having the command
> available. imo, FC should default to putting the /sbin, /usr/sbin,
> /usr/bin etc. paths in the root $PATH.

Do you log in in some way that avoids running /etc/profile?  Mine
(in a stock install) adds /sbin, /usr/sbin, and /user/local/sbin
if your uid is 0.

  Les Mikesell
   lesmikesell at gmail.com

More information about the users mailing list