I have a lot of accounts on a lot of computers. I have 70 servers at work that I use for scientific computing, some are Fedora, some are Red Hat Linux, some are Windows Server. Then I have my workstations, my PCs, and my laptop. So I spend a lot of time installing OS's and accounts. I like to have my account set up the way I like it on each machine - ideally, I like to remote mount my home directory.
Today was getting-back-to-pair-networks day. My account there is on a generic Linux server so that much is familiar. However I like a few things different, for instance I'm still a tcsh user who never really made much effort to switch to bash, though I acknowledge its superiority in some points. I also like the GNU core and bin utilities, for things like having ls not list the emacs backup files, and file name coloring. My server at pair didn't have GNU coreutils, so I used wget to download it, then I compiled it and installed it in my usual location which is ~/BIN. I put ~/BIN/bin first in my PATH on all my machines so that I pick up any locally-installed utilities first. And I add ~/BIN/include, ~/BIN/man and so forth to the appropriate environment variables. It's a nice way to add some consistency.
Today was getting-back-to-pair-networks day. My account there is on a generic Linux server so that much is familiar. However I like a few things different, for instance I'm still a tcsh user who never really made much effort to switch to bash, though I acknowledge its superiority in some points. I also like the GNU core and bin utilities, for things like having ls not list the emacs backup files, and file name coloring. My server at pair didn't have GNU coreutils, so I used wget to download it, then I compiled it and installed it in my usual location which is ~/BIN. I put ~/BIN/bin first in my PATH on all my machines so that I pick up any locally-installed utilities first. And I add ~/BIN/include, ~/BIN/man and so forth to the appropriate environment variables. It's a nice way to add some consistency.
