13

There are numerous scripts that I have written for my server. Some of them are in my ~/scripts and some of them are in application directories.

I am just wondering is there a directory that you would normally use to keep your shell scripts?

HopelessN00b
  • 53,385
  • 32
  • 133
  • 208
Kiril
  • 261
  • 1
  • 2
  • 7

6 Answers6

38

Personal ones for my account, ~/bin. System-wide ones go in /usr/local/bin or /usr/local/sbin as appropriate (scripts which should only be run as root go in sbin, while scripts intended to help ordinary users go in bin), rolled out via configuration management to ensure that all machines that need them have them (and the latest versions, too).

womble
  • 95,029
  • 29
  • 173
  • 228
  • 1
    +1 This is exactly what I do. – David Pashley Jul 22 '09 at 09:10
  • 4
    You should explain the appropriateness of `bin` versus `sbin` :) – Dan Carley Jul 22 '09 at 10:02
  • 3
    sbin is meant for "Superuser BINaries", programs that usually need root access to run properly. "bin" is for all the rest. – wazoox Jul 22 '09 at 10:11
  • 14
    The origin of sbin came from "Statically-linked BINaries". When /usr (and its shared libraries) were mounted outside of single-user mode, it was found necessary to keep around some statically linked programs (sh, tar) that *always* worked. Since only the SysAdmin was interested in these binaries, the misnomer began. – kmarsh Jul 22 '09 at 12:21
  • I wondered about that too, I fear none of my scripts are worthy of the distinction :) –  Jul 22 '09 at 13:33
  • I do the same thing but with an extra level of directory for $ARCH -- so ~/pub/$ARCH/{bin,man,share} to allow for i386, x86_64 and any other architectures you have binaries for (I used to use SGI machines and various Sparcs, so this was more useful then :) – David Gardner Jul 22 '09 at 22:29
  • 1
    If you're managing to write architecture-specific shell scripts, I weep for whoever else has to maintain your code. – womble Jul 23 '09 at 03:25
8

For more complex stuff, especially something that could be shared between multiple machines I tend to make distribution packages, Debian in my case. I use /usr/bin, and give scripts some common prefix. That way it's easier to deploy and keep track of them. For my personal stuff, ~/bin is good enough.

klozovin
  • 281
  • 2
  • 8
5

At the moment I use ~/bin for my personal (quick and dirty :P) scripts and /usr/local/bin (or sbin) for system wide ones

Both directories are under revision control via git.

scetoaux
  • 1,269
  • 2
  • 12
  • 25
3

I currently use /usr/local/$company/scripts for system-wide scripts, and ~/bin for personal. I also have a ~/code folder that contains work-in-progress stuff.

2

I use ~/.bin
The folder is hidden for file managers and ls: i rarely modify anything inside, so let it be :)

kolypto
  • 10,738
  • 12
  • 51
  • 66
0

If you don't want to mix your own scripts with scripts placed in ~/bin by installed packages and programs, you can store your scripts in a directory of your choice and bind it to ~/bin. Your scripts will be visible in ~/bin and you will be able to run them from a terminal with a simple name without having to specify a path.

For one time use you can run this command (effect will disappear after reboot):

sudo mount --bind ~/path-to-your-scripts-directory ~/bin

You can create a new script with this command and run it automatically at login to remount this binding after a reboot.

Or

To bind permanently, add these lines to fstab:

# bind my scripts to ~/bin
/home/myaccount/path-to-your-scripts-directory /home/myaccount/bin     none    bind    0   0
almaceleste
  • 101
  • 2