2 ms·
I'm with you. I use the default shell (bash for linux) and don't change it much. I might tweak the prompt a little and add a few aliases and environment variabl
by ams6110 11y ago
I'm with you. I use the default shell (bash for linux) and don't change it much. I might tweak the prompt a little and add a few aliases and environment variables but that's about the limit of it.
The main reason is that I tend to work on a lot of servers, and sticking with default settings gives me a consistent unsurprising environment on all of them.
- kbd 11y ago> The main reason is that I tend to work on a lot of servers... I agree with sticking with bash for that reason, but why not customize that as much as you want since it's easy to scp dotfiles around?
- zo1 11y agoWe keep common profile configs for remote servers in our source code repository. It helps immensely having common aliases and stuff across multiple servers, from dev boxes to production ones.
- rat87 11y agoI think being useful is better then being consistent. Also with git clone from github it's easy to copy settings on any non too security sensitive boxes.
- opk 11y agoIt is possible to adapt fairly easily between different setups. I've got a fairly advanced zsh setup but do a lot of admin on a mix of Linux, Solaris and BSD where I have to put up with whatever the defaults are. I resisted vim for a long time for similar reasons: when doing admin, I often only had vi. When I finally took the plunge and learnt how to make effective use of vim-specific features I regretted not having done it long before. And I can still manage fine on a bare install of Solaris with vi.