A simple question :oops:

[lazyilmaz]

Like i said before i'm a total *nix newbie, that's why i have a simple question. In Windows you have .exe files to execute a file, the question is what are the executables of PC-BSD? i mean when you install firefox, which file does get executed when you double click it. I know it's a stupid question but i need to know this for Camel.

[Valio]

Users executables are located in /usr/bin, /usr/local/bin, System executables are /bin

Dont know what is the difference between /usr/bin and /usr/local/bin but /bin has like rmdir = remove directory, all the basic commands

I'll hope this helps


Edit: I think when you install software with root it goes to /usr/bin

when you install software with user it goes to /usr/local/bin

[darkside]

/usr/bin --> Systems programs

/usr/local/bin --> Users programs

[scottro]

ls /bin will show you things like ls, sh, csh and the like

ls /usr/bin will show you things like vi, passwd, pkill and the like.

ls /usr/sbin will show you things like sendmail, sshd.

ls /usr/local/bin will show you installed programs, as will ls /usr/X11R6/bin where a lot X related programs are installed, such as xterm.

ls /usr/local/sbin will show things like postfix, apache commands, and other programs that don't come with a base system, but can be considered system programs. (This can often leed to needless debate, but people are used to it.)

Most 3rd party programs (and this goes for tarballs downloaded for Linux as well) install in /usr/local/bin by default.

So, the local in this case, refers to programs which you decide install.

You can find the location of a program with the which command, eg

which firefox

gives an answer of /usr/X11R6/bin/firefox.

Then, if you do

file firefox

you get the answer of Bourne shell script text executable.

This means that it's actually a shell script that calls a binary.

Hopefully, this has given enough information without giving so much information that you're confused.

[lazyilmaz]

:? :? :? :? :?

I didn't know that it was so complex!

Why not like this

The best solution yet to emerge for application installation is the NeXT/OS X AppFolder concept. Put simply, the entire application is packaged into an folder with a special extension. When the file browser sees a folder with this extension, it treats it as if it were a special file instead of a directory. As a result, the user sees a single icon for an application, and is free to move or copy this icon to wherever he chooses - even a remote computer. Installation is as simple as extracting the folder and moving it to your favorite location, un-installation is as simple as deleting the folder, and tons of meta-info (such as associations) can automatically be pulled from the directory package.

Thanks to bhna

Full article