Friend is interested to learn Linux Sys admin, will it help for his Career 4671

On Tue, 06 Sep 2005 06:26:23 GMT, Christopher Browne staggered into the Black Sun and said:

Hm. I was looking for a job a few months back, before the people I work for started paying me on time with checks that didn't bounce. The recruiters didn't seem insanely interested in my skillset. Maybe this is just local economic conditions, or possibly lack of buzzwords.

This is true, and if someone's applying for a Linux admin position and they've never compiled a kernel, they're probably not going to get the job.

Who's "we", white man? :-) The word "documentation" is overloaded here, and as usual, overloading can cause confusion. At my workplace, "documentation" without qualifiers means "end-user documentation". The things you mention (lists of IP addresses for internal machines, phone#s for the folks who manage the upstream routers, what to do when the tape drive on $MACHINE goes catatonic) are stored in ASCII in a directory called "TechnicalDept". YMMV as always.

The things you mentioned are useful and in some cases vital.

Also, for the OP and other folks, if you write a non-trivial script (or even a widely used trivial script) make sure it accepts -h and-or --help as an argument, and have that script display a usage summary if that option is present. It's much easier to run "fixbizarreproblem.sh --help" than it is to read the script again if you haven't had to run fixbizarreproblem.sh for 6 months.

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL