Adding a new command
smithi at nimnet.asn.au
Sun Jul 8 06:57:50 UTC 2007
On Sat, 7 Jul 2007 16:20:53 -0500 Jeffrey Goldberg wrote:
> On Jul 7, 2007, at 11:42 AM, Peter Boosten wrote:
> > It's more obvious to put local scripts in /usr/local/bin, IMHO.
> Let me add to this (as someone who recently moved from linux to
> FreeBSD). Unlike Linux, FreeBSD isn't just a kernel, but a complete
> operating system. So the things in /bin and /usr/bin are as fully
> part of FreeBSD as the kernel itself, while on Linux distributions,
> those things are bundled with Linux as part of a distribution.
> So this is one reason why it is best to put tools like you describe in
My preference for such local scripts that ought not be confused with any
system (or local port) scripts is to put them in /root/bin .. no chance
of any sort of upgrade clobbering them there, and your own scripts are
all together. You need to specify full path for any of these where used
in a crontab, but that's good practice anyway.
If you're using [t]csh, as Lisa appears to be (needing to run 'rehash'
to find newly added commands), $HOME/bin is already in the default path.
More information about the freebsd-questions