virtual terminal vs. virtual frame buffer

virtual terminal vs. virtual frame buffer

Post by maxwell.. » Wed, 05 Jan 2000 04:00:00



I know that there is an Xfree86 patch(x86) that will allow
it to work with Solaris 8 which has no support for virtual terminals
(I know what vt's are from running linux and switching between them),
but my question is this:

What is the difference between virtual terminals and
virtual frame buffer (the Xvfb program under the X11R6.4
distribution).  I am using the Sun x-server, but I have
the X11R6.4 binaries installed under Solaris 7(Sparc)
so that I can run Xvfb and generate web images without
using my running x-server's colors.  When I upgrade
to the final release of 8, will I lose this capability?

Thanks,
Robert Mullenax

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

virtual terminal vs. virtual frame buffer

Post by Casper H.S. Dik - Network Security Engine » Wed, 05 Jan 2000 04:00:00


[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]


>What is the difference between virtual terminals and
>virtual frame buffer (the Xvfb program under the X11R6.4
>distribution).  I am using the Sun x-server, but I have
>the X11R6.4 binaries installed under Solaris 7(Sparc)
>so that I can run Xvfb and generate web images without
>using my running x-server's colors.  When I upgrade
>to the final release of 8, will I lose this capability?

What's the difference?  There's no relationship between virtual
terminals and Xvfb.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

1. Xvfb virtual frame-buffer trouble with LOCAL-ZONES in sol10x86?

Hi there...

I was wondering if anyone else experienced this problem with sol10x86.
(seems to work fine for SPARC).

...so this is a bit of a science project... I may fall back to Xvnc...

in the GLOBAL: the following works fine...

/usr/openwin/bin/Xvfb screen 1024x768x24

--

Doing the same in a LOCAL ZONE gives:

# /usr/openwin/bin/Xvfb screen 1024x768x24
There is no XDISPLAY information for display 0.
Check the OWconfig file(s) and try again.

Fatal server error:
The server will now exit because of configuration problems.
# able to restore text mode on vfb#
#

So lets get a little fancy to get rid of the "XDISPLAY" error...
edit /usr/openwin/server/etc/OWconfig and add:

# Virtual X Display for virtuals

class="XDISPLAY" name="5"
coreKeyboard="NKBD" corePointer="NMOUSE"
dev1="vfb";

(To be honest, I got the above from some google-link, I don't really
know if the dev1 entry or the SYNTAX is 100% right...)

Ok, now lets try the Xfb command in the LOCAL again...

#
# /usr/openwin/bin/Xvfb :5 screen 1024x768x24

Fatal server error:
The server can't access IO registers.

#

trussing this event shows lots of stuff, but no smoking gun (from what I
can tell...)

Its either a bug/feature, or I'm not modifying the OWconfig file
properly... (this works fine on SPARC, even without the OWconfig file mods.)

--

Can anyone shed some light on this one?

thanks,

-- MikeE

2. Future Domain 9C50 SCSI chip (as in Orchid SoundWave 32 pro SCSI)

3. Virtual X frame buffer & TrueType Fonts

4. Linux 1.2.8, AHA-2940 and Large HDs

5. Kernel 2.2.3 & bttv & virtual frame buffer & quake II

6. "write" "to" "flon" commands

7. X Virtual Frame Buffer

8. mars_nwe & PIPE-FS

9. Help ! Virtual Frame Buffer Usage !

10. virtual frame buffers

11. Virtual Frame Buffer

12. AIX 4.3.3 X11.vfb Virtual Frame Buffer

13. Virtual Server vs. Virtual Host