Re: (native build & other issues - Was: xvfb not built on vax...)

[der Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> What do that virtual frame buffer do, by the way?

It - Xvfb - provides an X server to point programs at, without needing
framebuffer hardware.  In theory, you can also peek at what's being
displayed without needing to go through the X facilities.  I've never
had that work, but I've never put any real effort into finding out why
not; I could just be doing it wrong.

Since there are no real input devices, it's useless for programs that
do interactive X stuff, but it's fine for things like gnuplot that can
be useful without any X input.  Also useful for testing - for example,
if you want to make sure your program starts OK on a 27-bpp DirectColor
display but don't have any such hardware, Xvfb is your friend.

Until I added -nowin to mterm, I used a 1x1 Xvfb as a display to point
mterm at when I had no sessions running, to keep the mterm alive.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B