Getting X to init corectly W/O a monitor conected

[stan]

On Thu, Aug 27, 2009 at 02:38:22PM -0400, Mark Haney wrote:
> stan wrote:
> > I have a mcahine that lives in a rack. All the machines in tis rack share a
> > common KVM. This is an older KVM ,ad does not provide the corect response
> > to querying for things like monitor resolution, etc, when the machine doing
> > the querying is not slected to the monitor/keyboard.
> 
> > 
> > But it return errors, _and_ when I boot the machine without the monitor
> > conected, and try to run this from the command line it does not work.
> > 
> > Whats the best way to address this issue?
> > 
> > 
> 
> Obligatory old school question.  What is wrong with killing X and using
> the command line?  I mean, do you run remote X sessions from SSH to
> manage the system instead of just learning the CLI?
> 
> If it's in a rack connected to a KVM, how often will you actually access
> the box from the KVM compared to a good old SSH session?
> 
> Granted, this doesn't fix your problem, but it just amazes me that X
> just /has/ to be running even for konsole or yakuake sessions.
> 
aFair enough question. here is the rest of the story. The purpose of this
amchine is to be a VirtualBox host f an XP machine. We VNC to the XP
machine to do work. XP comes up in an unusable res/color depth if X is not
correct, when it starts. Too bad we can't run XP headless.

-- 
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs.