usage of /usr/bin

[Polytropon]

On Wed, 07 Apr 2010 20:21:57 -0400, Lowell Gilbert <freebsd-questions-local at be-well.ilk.org> wrote:
> Fbsd1 <fbsd1 at a1poweruser.com> writes:
> > Your wrong. I installed the package of postfix and it installed it
> > self into /usr/bin with out any help from me.
> 
> Believe it or not, I checked before responding, so I'm *not* wrong.  I
> said that the port populates into /usr/local like it should, and having
> it on several machines for nearly a decade now, I knew that to be the
> case.  You then changed that to refer to a package rather than a port; I
> don't know where you got your packages from, but I checked the packages
> for 8-STABLE and for 8.0-RELEASE, and saw that they install into
> /usr/local as well.  So it sounds like your packages didn't come from
> the FreeBSD project, if they are really installing anything into
> /usr/bin.  
> 
> Just as a sanity check:  what, specifically, is installed into /usr/bin
> on your system?  Most of the postfix executables go into sbin rather
> than bin anyway, so it's possible that something in the mailwrapper
> system is confusing you.  If you don't have a /usr/local/sbin/postfix,
> but have a /usr/sbin/postfix instead, then this is not the case.

A comfortable, maybe overcomplicated way to check what a package
will install - without actually installing it - is to use the
option -n for pkg_add (which obviously operates on packages,
not on ports).

So you could do:

	pkg_add -fKnrv postfix > /tmp/postfix_add.txt

This even works if postfix is already installed. The options,
for a short reference, are: -f = force, -K = keep, -n = no
install, -r = remote and -v = verbose. You can then search
for lines that address specific locations in /usr/bin rather
than /usr/local/bin.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...