no its not there,I was wondering why it wouldnt already be there for anybody who wants their own binaries installed there
It is my understanding that /usr/local is meant to hold things that an administrator installs on a system, separate from what's included in a vanilla install. Perhaps Apple follows this convention literally. By definition, if you haven't installed any binaries or libraries, you have a vanilla install and thus wouldn't have anything in /usr/local.
crackpip
I just create /usr/local/bin as soon as I do an install, but most of my scripts live in bin in my home directory. If you make it, OS X will include it in its $PATH automatically (at least I don't remember adding it to $PATH).
Nothing wrong with that unless you have a bunch of other users using your binaries.
crackpip
Hi,
I actually know nothing about this (I am a graphic designer), however my "Computer Savvy" 9 1/2 year old son would like to offer the following suggestions:
"Hi, To go into the usr/local/bin directory open Terminal then type (In 1 line)
"cd ../..; cd usr; open ." Then hit enter. It will open a new finder window that is directly inside the usr folder. Then you can double click on local then bin to go into usr/local/bin. Just to tell you guys the usr folder is invisible and is only visible in Terminal. I hope this helps! I bet you are surprised about how young I am. From, Justin"
Hi this is Justin again,
To go to the opt folder: Open a new Terminal window type (In 1 line)
"cd ../..; cd opt; open ."
This will also open a new finder window that will have the opt folder opened without you having to make it.
cd ../.. is not needed cd /usr or /opt is simpler. Open . will not create a folder it will just open a new Finder window in the current folder. /usr/local/bin should be created manually because will MacOSX doesn't ship with any user specific binaries, ergo create it once needed.
open /usr
mkdir -p /usr/local/bin
cd ../.. is not needed cd /usr or /opt is simpler. Open . will not create a folder it will just open a new Finder window in the current folder. /usr/local/bin should be created manually because will MacOSX doesn't ship with any user specific binaries, ergo create it once needed.
But it is already created for you.
Why would you create it if it is already there?
"cd /usr" and "cd /opt" is definitely simpler but "cd../..; cd usr; open ." and "cd ../..; cd opt; open ." was the first thing I thought of.
Also, if you want the finder window with that folder showing, just add ";open .".
There's no such thing as a Linux standard.
There's no such thing as a Linux standard. It's not standard UNIX since OS X conforms to the UNIX specification. There is a /usr/local which is for executables and and libraries not included by the basic OS.
Well I guess now we are getting into semantics, yes its not part of the unix standard, but it a unix convention. We were using /usr/local/bin on Irix machines in the late 80s/early 90s before Linux even existed
sudo mkdir /usr/local; sudo mkdir /usr/local/bin
type the following in Terminal :
Code:sudo mkdir /usr/local; sudo mkdir /usr/local/bin
Anyway, any half decent installer should create directories when they don't exist.
ls /usr/local/bin
mkdir /usr/local/bin