wb2oyc wrote:

>     Huh?  Whats happening here?
>     Installed some packages.  Create a link in /usr/bin to the executable.
> 
>     Try it; command not found!
>     Hmmm?  Oh well, scratchin' my noggin' we'll just try somethin' else 
> here.
> 
>     Another one.....sameo sameo....What gives?  Go to the dir where it 
> lives,
>     ./blah_blah, it runs fine!  Hmmmm?
> 
>     Later, after having gone back to MacOS, and then rebooting to NetBSD
>     it works!  Not just it, but they all work! (Pine, pico, lynx, etc)....
> 
>     What didn't I do?  Anyone?  Worse than that, why did rebooting fix it?
> ?

This one is rather straightforward.  When you start up a shell, it creates
a hash of all the binaries in your path as specified by either the PATH
environment variable or the path shell variable.  This hash is only
changed when you modify the path variable or do a "rehash".

So, when you added this link, the current hash table didn't know about the
command.  You could either logout and log back in, start a new shell, or
simply do a "rehash" to fix this.

So, the reason rebooting "fixed" it was that you started a new shell once
you rebooted and logged back in.

> Paul
>   Oh, I did this as root.  Yeah, I know....don't, but I haven't found 
> adduser
>   yet, or gotten it off one of my Linux boxes.

There isn't currently a NetBSD adduser.  Instead, adduser(8) is a man page
describing the process to add a user.  It is really quite straightforward,
and I would recommend knowing how to do it, since you really can't depend
on scripts to do it for you in all circumstances.

I hope this helps.

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.