Moba. Xterm Xserver with SSH, telnet, RDP, VNC and X1. If you use Moba. Xterm inside your company, you should consider subscribing to Moba. Xterm Professional Edition: your subscription will give you access to professional support and to the "Customizer" software. This customizer will allow you to generate personalized versions of Moba. Xterm including your own logo, your default settings and your welcome message. Please contact us for more information. User’s Guide for Virtual. GL 2. 1. 1 and Turbo. VNC 0. 5. User’s Guide for Virtual. ![]()
GL 2. 1. 1 and Turbo. VNC 0. 5. Intended audience: System Administrators, Graphics Programmers. Researchers, and others with knowledge of the Linux or Solaris operating. Open. GL and GLX, and X windows. Legal Information. This document and all associated illustrations are licensed under the. Commons Attribution 2. License. Any. works which contain material derived from this document must cite The. Virtual. GL Project as the source of the material and list the current. Solaris 11 is the latest Operating System in the Solaris server OS range from Oracle, previously Sun Microsystems. It incorporates many features from Solaris 10 such. How to get OpenLDAP, OpenSSL, and PAM all working together happily under Solaris in a secure fashion. URL for the Virtual. GL web site. This product includes software developed by the. Project for use in the Open. SSL Toolkit. Further information is contained in. LICENSE- Open. SSL. The Virtual. GL server components include software developed by the. Project and distributed under the terms. FLTK License. The Virtual. GL Windows packages include. Virtual. GL includes portions of. Virtual. GL is licensed under the wx. Windows Library. License, v. GNU. Lesser General Public License (LGPL). Overview. Virtual. GL is an open source package which gives any Unix or Linux remote. Open. GL applications with full 3. D. hardware acceleration. ![]() Some remote display software, such as VNC. Open. GL applications at all. Other remote. display software forces Open. GL applications to use a slow software- only. Open. GL renderer, to the detriment of performance as well as compatibility. The traditional method of displaying Open. GL applications to a remote. X server (indirect rendering) supports 3. D hardware acceleration, but. Open. GL commands and 3. D data to be sent. This is not. a tenable proposition unless the data is relatively small and static. Open. GL application. X- Windows environment. With Virtual. GL, the Open. GL commands and 3. D data are instead redirected. D graphics accelerator on the application server, and only the. D images are sent to the client machine. Virtual. GL thus. D graphics hardware, allowing it to be co- located. Virtual. GL also allows 3. D graphics hardware to be shared among multiple. This makes it possible for large. D workstations to be replaced with laptops or even thinner. More importantly, however, Virtual. GL eliminates the workstation. Users can now visualize. Normally, a Unix Open. GL application would send all of its drawing commands. D and 3. D, to an X- Windows server, which may be located. Virtual. GL, however. D commands from the application to go to a 3. D graphics card in the. VGL accomplishes this by pre- loading a dynamic. DSO) into the application at run time. This DSO intercepts. GLX, Open. GL, and X1. Whenever a window is created by the application, Virtual. GL. creates a corresponding 3. D pixel buffer (“Pbuffer”) on. D graphics card in the application server. Whenever the application. Open. GL rendering context be created for the window. Virtual. GL intercepts the request and creates the context on the corresponding. Pbuffer instead. Whenever the application swaps or flushes the drawing. Virtual. GL. reads back the Pbuffer and sends the rendered 3. D image to the client. The beauty of this approach is its non- intrusiveness. Virtual. GL monitors. X1. 1 commands and events to determine when windows have been resized. D. X1. 1 commands to the X server. For the most part, VGL does not interfere. Open. GL commands to the graphics card, either (there. VGL merely forces the Open. GL commands to be delivered to a server- side. Once the Open. GL. Pbuffer, everything. Open. GL extensions, fragment/vertex programs, etc.). In most cases, if an application runs. D server/workstation, that same application will run. Virtual. GL. However, if it were. Most of the time spent developing Virtual. GL has been spent working. Virtual. GL can currently use one of three “image transports”. D images to the client machine: 1. VGL Image Transport (Formerly “Direct Mode”). The VGL Image Transport is most often used whenever the 2. D X server. (the X server used to draw the application’s GUI and transmit. D X server is running on the user’s desktop machine. Virtual. GL. uses its own protocol on a dedicated TCP socket to send the rendered. D images to the client machine, and the Virtual. GL Client application. X window. The VGL Transport can either deliver uncompressed images (RGB encoded). JPEG codec. It also supports the delivery of stereo image pairs, which can be reconstructed. Virtual. GL Client. Figure 2. 1: The VGL Image Transport with a Remote 2. D X Server. 2. X1. Image Transport (Formerly “Raw Mode”). The X1. 1 Image Transport simply draws the rendered 3. D images into the. X window using XPut. Image() and similar X- Windows commands. This is most useful in conjunction with an “X Proxy”, which. Unix remote display applications, such. VNC. These X proxies are essentially “virtual” X servers. They appear to the application as a normal X server, but they perform. X1. 1 rendering to a virtual framebuffer in main memory rather than to. This allows the X proxy to. X- Windows. rendering commands. When using the X1. Transport, Virtual. GL does not. perform any image compression or encoding itself. It instead relies. X proxy to encode and deliver the images to the client(s). Since the use of an X proxy eliminates the need to send X- Windows commands. Virtual. GL over high- latency. The Virtual. GL Project provides an accelerated. VNC, called “Turbo. VNC”, which is meant to be. Virtual. GL’s X1. Transport. The combination of the. D solution, even on slow networks. Turbo. VNC also provides rudimentary collaboration capabilities, allowing. D application. Figure 2. The X1. 1 Image Transport with an X Proxy. Sun Ray Image Transport. The Sun Ray thin client environment from Sun Microsystems consists. X proxy (the Sun Ray Server Software) and a series of ultra- thin. It is. similar in concept to VNC, in that a virtual X server is created for. Unlike VNC, however, the client is not a piece of software. The client is a fanless, diskless. USB ports, a network jack, and. This environment. Virtual. GL The first challenge is that. Sun Ray 1 and Sun Ray 2 series clients contain relatively slow. CPUs, so they are not fast enough to decompress JPEG in real time. The second challenge is that Sun Ray servers are generally provisioned. Virtual. GL’s X1. Transport would put undue stress on both the Sun Ray servers and the. Thus, Sun Microsystems designed a plugin. Virtual. GL which allows VGL to compress images using a protocol. Sun Ray hardware client without having. Sun Ray server first. Since the plugin uses the. Sun Ray image compression technology, it is currently closed. Shared Visualization product. This. product also includes Virtual. GL, Turbo. VNC, and other goodies. Figure 2. 3: The Sun Ray Image Transport. System Requirements. Linux/x. 86. Server (x. Server (x. 86- 6. Client. Recommended CPUPentium 4, 1. GHz or faster (or equivalent). For optimal performance, the processor should support SSE2 extensions. Dual processors recommended. Pentium 4/Xeon with EM6. T, or…AMD Opteron or Athlon. GHz or faster. For optimal performance with 6. Virtual. GL, the processor should. SSE3 extensions. AMD 6. SSE3. Dual processors recommended. Pentium III or Pentium 4, 1. GHz or faster (or equivalent)Graphics. Any decent 3. D graphics card that supports Pbuffers. Install the vendor drivers for the server’s 3. D graphics card. Do not use the drivers that ship with Linux, as these do not provide. D acceleration or Pbuffer support. Any graphics card with decent 2. D performance. If using a 3. D graphics card, install the vendor drivers for that 3. D. graphics card. Recommended O/SOther Software. X server configured to export True Color (2. Linux/Itanium. Virtual. GL should build and run on Itanium Linux, but it has not been. A pre- built Turbo. JPEG binary package is not available for Linux/Itanium. Turbo. JPEG from source using the Intel. Integrated Performance Primitives for Itanium processors. Solaris/x. 86. Server. Client. Recommended CPUPentium 4/Xeon with EM6. T, or…AMD Opteron or Athlon. GHz or faster. Dual processors recommended. Pentium III or Pentium 4, 1. GHz or faster (or equivalent)Graphicsn. Vidia 3. D graphics card. Any graphics card with decent 2. D performance. O/S. Solaris 1. 0 (or newer). Open. Solaris 2. 00. Other Software. Sun. Lib (v. 2. 5 or higher recommended. Patch 1. 18. 34. 5- 0. X server configured to export True Color (2. Lib (v. 2. 5 or higher recommended. X server configured to export True Color (2. Lib 2. 5 is included in Solaris 1. If you are running an older version of Solaris, it is recommended that you download and install the media. Lib 2. 5 upgrade from the link above.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |