Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Feb 2007 08:21:06 -0500
From:      Bill Moran <wmoran@collaborativefusion.com>
To:        Gobbledegeek <gobbledegeek@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: windows behaviour on installing new packages
Message-ID:  <20070202082106.d7ed0919.wmoran@collaborativefusion.com>
In-Reply-To: <463aea570702012137m48215342of428b69a18641c71@mail.gmail.com>
References:  <463aea570702012137m48215342of428b69a18641c71@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
In response to Gobbledegeek <gobbledegeek@gmail.com>:

> 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 $PATH).  Running ldconfig, logging
> out and  logging back in did not help either.  *Rebooting*  helps
> however.
> 
> What gives?    Are the  package install scripts missing  some  install
> command ? System is 6.2  production release.
> 
> Mine is a home desktop, but in the context of  a server this  is
> completely  unacceptable.
> 
> Please copy  me  as I  am not subscribed.

I really think you're going to have to provide a _specific_ example.

The behaviour you describe is neither intended nor expected.  I don't
see it on either of my desktop machines, or my laptop.

-- 
Bill Moran
Collaborative Fusion Inc.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20070202082106.d7ed0919.wmoran>