Comment 79 for bug 219630

Oliver hasn't specified the system on which he tested this, so I cannot comment on his results.

However, I have tested this on a variety of Geode-based systems by a variety of vendors and found the exact same behavior on each of them: that leaving the symbolic link confuses X, while removing it makes LTSP work where it previously didn't and doesn't affect operation on standalone hosts that don't use a static config (hosts with a static config need their config updated because of the X anyhow).

As for the symbolic link, after trying various approaches, I have come to the conclusion that removing it and expecting users to upgrade their static config (if any - not everyone uses it) once for all was the best approach, while leaving the symbolic link there only postpones the unavoidable day when the config has to be upgraded. It also removes the confusion that X experiences with the -configure option.

I'll also point out that blacklisting the framebuffer is entirely the wrong approach and essentially moves the problem to another package where it doesn't belong. Besides, on some systems, such as the OLPC, the driver is *expected* to leverage the framebuffer.