On the testers mailing list it has been mentioed that redhat plans to ship
3.3.6 xservers for those that do not work in 4.0. However, there may be a
problem with this that need to be "fixed".
In order to run the betas under vmware, I need to install vmware's special
xserver. To make this work, I found that I needed to do the following:
1. Install my xserver into /usr/X11R6/bin
2. rename or delete /usr/X11R6/bin/XFree86
3. Make a symbolic link to my xserver as /usr/X11R6/bin/XFree86
4. Make a symbokic link to /etc/X11/XF86Config as /etc/XF86Config
Without renaming XFree86 and creating the symbolic link, the 4.0 driver was
still started regardless of where /etc/X11/X pointed.
This also works on real hardware with a 3.3.6 xserver such as XF86_Mach64.
Using strings, the only binary program I could find the had "XFree86" was
Was /usr/X11R6/bin/X linked to XFree86 or something else?
With the 4.0.1 and associated updates, this is no longer a problem.
/usr/X11R6/bin/X now points to Xwrapper.
I am closing this bug.