Marcy Cortes wrote:
Sounds like Brandon's sysadmin role must be a little different from ours. Either that or he's got 500+ servers? Heck, I'd be happy to have 5 linux sysadmin in my group! We have various other support teams support teams - db2, mq, websphere, etc. So the ones who can screw it up so badly that you need a console are few - and we all know how to fix it.
That could very well be the case. Without getting myself in trouble for revealing trade secrets, lets just say we've made a significant move towards having any Unix SA be able to support any Unix box. Our system build and sustaining support groups handle hundreds (maybe thousands? Not sure) of Unix servers. Various flavors of Unix. And on almost all of those distributed Unix systems, remote console is the key to making it possible. No running to the data center to hook up dumb terminal on a cart, needing to know if your pin-outs are right, if your serial terminal settings are right. The few systems that can't work this way are either being phased out, or supported by a small group of people (2-5)... and if they can, they'll talk the customer out of ever buying something like that again. Mainframe is just that much more different. Things my fellow admins face when trying to support z/Linux: * Different backup solution than the rest of distrubted Unix/Linux. * Different system health monitoring system. * A console that confuses them and if they do the wrong thing can freeze the vm. * Pages for run-away vm's (They charge for CPU?!? You're kidding! they say) Plus all the differences between SuSE Linux and any other Unix. Stuff like this seriously impacts how a "Jack of all Unix" group can support it. *Brandon ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
