Re: windows behaviour on installing new packages

2007-02-02 Thread Bill Moran
In response to Gobbledegeek [EMAIL PROTECTED]: Hi I noticed over the past few weeks, that after installing numerous packages (pkg_add -r), I could not execute them (not found). They were standard packages installed in the standard locations like /usr/local/bin or sbin (already in

Re: windows behaviour on installing new packages

2007-02-01 Thread Daniel Marsh
On 2/2/07, Gobbledegeek [EMAIL PROTECTED] wrote: Hi I noticed over the past few weeks, that after installing numerous packages (pkg_add -r), I could not execute them (not found). They were standard packages installed in the standard locations like /usr/local/bin or sbin (already in

Re: windows behaviour on installing new packages

2007-02-01 Thread Kris Maglione
On Fri, Feb 02, 2007 at 11:07:58AM +0530, Gobbledegeek wrote: I noticed over the past few weeks, that after installing numerous packages (pkg_add -r), I could not execute them (not found). They were standard packages installed in the standard locations like /usr/local/bin or sbin

Re: windows behaviour on installing new packages

2007-02-01 Thread Kris Maglione
On Fri, Feb 02, 2007 at 12:57:29AM -0500, Kris Maglione wrote: On Fri, Feb 02, 2007 at 11:07:58AM +0530, Gobbledegeek wrote: I noticed over the past few weeks, that after installing numerous packages (pkg_add -r), I could not execute them (not found). They were standard packages

Re: windows behaviour on installing new packages

2007-02-01 Thread Gobbledegeek
yes yes yes yes to all... thanks for the tip about the rehash and csh behaviour though. Regards On 2/2/07, Kris Maglione [EMAIL PROTECTED] wrote: On Fri, Feb 02, 2007 at 12:57:29AM -0500, Kris Maglione wrote: On Fri, Feb 02, 2007 at 11:07:58AM +0530, Gobbledegeek wrote: I noticed over the