On Thu, 29 Jun 2006, David Boyes wrote: > 1) There is *zero* reason to log into the console of a running guest to > do administration unless the guest system is completely broken and off > the network entirely, and if it's *that* broken, it's not serving any > useful functions anyway.
I can think of only one reason to use the console on a HEALTHLY system, and that's assuming the system is secured correctly. And that would be to verify the root password. Normal operation, there should be no case for using the root password. Remote access via ssh should be via ssh-keys or sudo. No application should prompt for root! So how does one make sure root's password is known? Console login. Granted, the rest of David's points stand. Using the console means knowing the implications and acting accordingly. Bill Carlson -- Systems Administrator [EMAIL PROTECTED] | Anything is possible, HCIS | given time and money. University of Iowa Hospitals and Clinics | Opinions are mine, not my employer's. | ---------------------------------------------------------------------- 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
