Date: Thu, 08 May 2003 10:52:52 -0500 From: Chris Pressey <cpressey@catseye.mb.ca> To: collins <erichey2@attbi.com> Cc: freebsd-questions@freebsd.org Subject: Re: /usr/local/bin and so forth Message-ID: <20030508105252.101fda8d.cpressey@catseye.mb.ca> In-Reply-To: <20030508054622.66b3bac7.erichey2@attbi.com> References: <20030508054622.66b3bac7.erichey2@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 8 May 2003 05:46:22 -0600 collins <erichey2@attbi.com> wrote: > Coming from a linux background (gentoo distro), I find it strange to > find all sorts of crap in /usr/local/bin. I'm used to find all > standard software in /usr/bin (or certain binary packages in /opt) and > to find/usr/local/bin reserved for stuff added by the local > administrator. That is the way it works in FreeBSD, if by "standard software" you mean "base install" and by "stuff added by the local administrator" you mean "ports and packages." > 1. What's the rationale behind this for freebsd? /usr/bin is for the operating system's files, /usr/local/bin is for stuff added by the local administrator. > 2. Where does one (as a standard) put truly local scripts, etc. so it > won't get confused with all the stuff in /usr/local/bin? Not sure there is a "standard" for something like this besides "whatever works for the individual." Me personally, I like to put scripts and such in ~/bin, and if other users need to run them I'll create symlinks to them from /usr/local/bin. -Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030508105252.101fda8d.cpressey>