Passing 'vnc' on the boot line causes a failure right around the
time that the vnc server should start, looks like something in the X
server config is broken?
Probing for mouse type: No - mouse
No video hardware found, assuming headless
WARNING!!! VNC server running with NO PASSWORD!
You can use the vncpassword=<password> boot option
if you would like to secure the server.
The VNC server is now running.
Please connect to altix2.lab.boston.redhat.com:1 to begin the
X SERVER STARTED, THEN FAILEDTraceback (most recent call last):
File "/usr/bin/anaconda", line 941, in ?
File "/usr/bin/anaconda", line 217, in startVNCServer
File "/usr/bin/anaconda", line 257, in doStartupX11Actions
raise RuntimeError, "X server failed to start"
RuntimeError: X server failed to start
install exited abnormally
sending termination signals...done
sending kill signals...done
you may safely reboot your system
Or vnc broke on ia64 again... will look at after lunch.
Actually, this was just a general problem caused by an explicit
listing of libstdc++.so.5 in upd-instroot. Made more general so that
it will get the (new) libstdc++.so.6 instead.
This works now, I tried it yesterday on the 0816 RHEL4 build.