mfillpot wrote:

To accomplish the same task with custom scripts and applications I have added an additional entry to my PATH variable that points to my scripts directory, then placed that entry into my .bashrc file so it is only available to the single user

This is what I've done as well, and it's a lot easier to maintain between reinstalls since you don't wipe out /home without backups that often... Personally, I also keep my script folder in Dropbox, so that the scripts are automatically distributed to all my Linux computers.

By the way, if you insist on symlinking your scripts into the system path, the conventional place is /usr/local/bin/ :)

jabirali wrote:

[b]mfillpot wrote:[/b]
[quote]To accomplish the same task with custom scripts and applications I have added an additional entry to my PATH variable that points to my scripts directory, then placed that entry into my .bashrc file so it is only available to the single user

This is what I've done as well, and it's a lot easier to maintain between reinstalls since you don't wipe out /home without backups that often... Personally, I also keep my script folder in Dropbox, so that the scripts are automatically distributed to all my Linux computers.

By the way, if you insist on symlinking your scripts into the system path, the conventional place is /usr/local/bin/ :)[/quote]

I rather sync the script folder to all the computer I work on (I find dropbox to be worse than a binary driver)

What mfillpot said. Create a bin directory in your home ( "mkdir ~/bin" ) and put your scripts and applications there. Placing them in /bin, or even a link to them in /bin is VERY unsafe, and can compromise your system. You have to make them available to other users, then normally the scripts/application executables/libraries are installed into /usr/local/(bin | lib).