It’s just data

Downsides of Consistency

Now that a shell window is on my laptop is completely indistinguishable from a ssh window into my server (outside of the title bar and the prompt that appears on each and every line, that is), I’ve managed to lose mail (I think I’ve recovered most of it) and accidentally replace the kernel on my server (which has had no ill side effects, but did make me pause).

Which is why I color code all my xterms.

Looks girly. totally works.

Posted by kj at

That reminds me...

Sam Ruby’s effort in accidently replacing kernels on his server via a shell window reminds me of the time a colleague took down a network interface on a development server via shell. I didn’t think twice either... until 2.5sec later when the...

Excerpt from Stunt Show at

A simple approach to solving this is to keep all your configs in a central repository and have something along the lines of

if [ -f .context_machinespecific]
    source .context_machinespecific
fi

at the bottom of each one. I’ve found this the best way to maintain consistency while still allowing a good amount of flexibility.

And colouring the XTerms sounds about right, or at least part of your prompt string ;-)

Posted by Neil Dunn at

Sam Ruby: Downsides of Consistency

Sam Ruby: Downsides of Consistency That is why on my Linux machine, I use aterm with a bright red foreground for all outgoing ssh connections. No chance of mistaking a production server for your local machine. If I am doing something on a test...

Excerpt from Adnans Sysadmin/Dev Blog at

Add your comment