> Unfortunately, not many. I'd say 10 out of 50 would know. I'd consider that pretty good, actually. You're ahead of the crowd there.
> The rest > depend on a remote terminal server product we use. They telnet to host > and port, authenticate, and there's the console... or in a couple of > cases, a menu to choose a console. They know the basics of telnet ^] > send brk. Now some of them *use* to know how to do more, but haven't > had to use it in years and lost it. For our E10k and Sunfire systems, > we again, had a subset of admins who were trained on how manage them. > They had the same problem, if you weren't on the E10k/Sunfire subteam, > you avoided supporting the systems on them because you didn't know the > way to do it. Sure we'd try and cross train others... but they used it > so rarely, they forgot how. Even worse, "Where's that link on how to do > this/that?" emails. In the end, only the subteam ends up supporting them. Sounds like the problem is actually one of how to find the right docs, rather than the console access problem. > A small note, though... if you actually did know how to get to a console > on the E10k and Sunfire systems, once there, it was fully usable, unlike > 3270. True. But Sun didn't recommend (and still doesn't) using it for anything other than emergency recovery. Mistakes could accidentally stop other domains and do all sorts of other evil without really trying hard. Ditto with big Superdomes and pSeries boxen. > And unless I'm misunderstanding you, your line mode approach > breaks lots of things as well, like a TUI (see Yast), or bash command > line history functions, for example. No, it's just a preliminary step -- just like the getting to the console step on the Sunfires. You get the guest back on the network with the line mode stuff, then you log in using a normal telnet/SSH client and *get off the console*. You do whatever you need to do using the telnet/SSH session. In that case the TUI, Yast, bash functions, etc are fully functional and work like normal. That's one of the reasons I like the netconfig script idea -- can all that knowledge into a script, get it back on the air, and then deal with the long term fix. ---------------------------------------------------------------------- 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
