Seasoned UNIX guys are maniacs at the keyboard. They want vi, autocomplete, and basically everything else that's available on a native Linux console. We shouldn't surmise what they want console access for - it may be to fix a network problem, maybe not. If VM is to support Linux in a transparent way, the console does need to be more usable. I've dealt with quite a few UNIX people who get instantly frustrated with the current setup.
As if vi weren't tough enough for a VMer, I've had to learn sed and several other tricks to revive misconfigured images. I see it as merely quirky, but others see it as a detractor to serious implementation. And yes, that puts me in a small pool of folks willing to bridge the knowledge/education gap. In all, especially where Linux390 is a marginal sell, VM should be offering more than merely 'good enough'. Simplicity & Familiarity are two things that need to be considered in any kind of console solution. Ray Mrohs U.S. Department of Justice 202-307-6896 > Let me pose this question: how many of your colleagues know what to do > after hitting L1-A on a Sun console, or accidentally disconnecting a > serial cable to a console port? If they do know, how did they > learn? Do > they understand the difference between how to respond on a > SPARCstation > versus an E15000 (bonus points if they know *which* console > on the E15K > to use to respond)? > > If they do, then that's the result of education, not > technology. I think > the same consideration applies here -- but now we're in the realm of > philosophy, not technology. > > Let's try both approaches and see what comes of it. My > approach will fit > either one; maybe we're solving different levels of the same problem. > ---------------------------------------------------------------------- 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
