New answers tagged directory-structure
This because /usr/bin/X11 is a symlink to /usr/bin (the dot at the end means the same directory as the link is in ): $ ls -l /usr/bin/X11 lrwxrwxrwx 1 root root 1 May 5 2013 /usr/bin/X11 -> . If you browse or cd to this directory, you are really just looking at /usr/bin.
Linux follows different rules from Windows. Linux favors the use of a package manager to manage installed software. The way to know whether a program is installed is not by looking for its files, but by searching the list of installed packages. Different distributions use different package manager; under Ubuntu, the GUI is the Software Center, and there are ...
It does actually tend to be consistent. The standard is the FHS specification and while it is admittedly not always followed it mostly is: /bin : Essential user command binaries (for use by all users) /boot : Static files of the boot loader /dev : Device files /etc : Host-specific system configuration /home : User home directories (optional) /lib : ...
The Unix file system has evolved over time, nothing is set in stone, but their are conventions. It is worth familiarising yourself with it, but doesn't have to be memorised in detail. Wikipedia article I wouldn't fiddle with your Komodo install, leave it be, as time goes on, you'll become more familiar with the layout.
If you want to symlink, it would be better to symlink to /usr/local/bin. On my server, I tend to install local software into /opt/NAME and symlink the binaries to /usr/local/bin.
On linking You generally do not link /usr/local/* with /bin, but this is more of a historical practice, in general, there are a few "technical" reason why you cannot do what you're suggesting. Making links to executables in /bin can cause problems: Probably the biggest caveat would be if you're system is having packages managed by some sort of package ...
Answering to the questions asked: Is this correct? No, it is a poor practice. Are there some hidden side-effects to my suggestion? Yes there are several side effects. Your suggestion might work or not depending on the application, and might regress or be broken in the long term. There are sensible reasons not to create such a symbolic link: ...
Forget the wrapper stuff:-) All you need is a .file (dot file) with the user configuration options, in the $USER directoy. You can have one in /etc for system wide config options as well. Make your script check for these .fils (dot file) and if they exist, use them. HTH, .
The Filesystem Hierarchy Standard specifies where to put files. If you're installing files outside of the package manager, always put them under /usr/local or under /opt. Never touch anything under /usr except via the package manager, except for things under /usr/local. /usr/local/bin: executables intended to be executed by users (interactively or from ...
Top 50 recent answers are included