THINC: a Virtual Display Architecture for Thin-Client Computing
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
THINC: a Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices
THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2011 c 2011 Ricardo A. Baratto This work may be used in accordance with Creative Commons, Attribution-NonCommercial-NoDerivs License. For more information about that license, see http://creativecommons.org/licenses/by-nc-nd/3.0/. For other uses, please contact the author. ABSTRACT THINC: A Virtual and Remote Display Architecture for Desktop Computing and Mobile Devices Ricardo A. Baratto THINC is a new virtual and remote display architecture for desktop computing. It has been designed to address the limitations and performance shortcomings of existing remote display technology, and to provide a building block around which novel desktop architectures can be built. THINC is architected around the notion of a virtual display device driver, a software-only component that behaves like a traditional device driver, but instead of managing specific hardware, enables desktop input and output to be intercepted, manipulated, and redirected at will. On top of this architecture, THINC introduces a simple, low-level, device-independent representation of display changes, and a number of novel optimizations and techniques to perform efficient interception and redirection of display output. This dissertation presents the design and implementation of THINC. It also intro- duces a number of novel systems which build upon THINC's architecture to provide new and improved desktop computing services. The contributions of this dissertation are as follows: • A high performance remote display system for LAN and WAN environments. -
CNTR: Lightweight OS Containers
CNTR: Lightweight OS Containers Jorg¨ Thalheim, Pramod Bhatotia Pedro Fonseca Baris Kasikci University of Edinburgh University of Washington University of Michigan Abstract fundamental to achieve high efficiency in virtualized datacenters and enables important use-cases, namely Container-based virtualization has become the de-facto just-in-time deployment of applications. Moreover, standard for deploying applications in data centers. containers significantly reduce operational costs through However, deployed containers frequently include a higher consolidation density and power minimization, wide-range of tools (e.g., debuggers) that are not required especially in multi-tenant environments. Because of all for applications in the common use-case, but they these advantages, it is no surprise that containers have seen are included for rare occasions such as in-production wide-spread adoption by industry, in many cases replacing debugging. As a consequence, containers are significantly altogether traditional virtualization solutions [17]. larger than necessary for the common case, thus increasing the build and deployment time. Despite being lightweight, deployed containers often include a wide-range of tools such as shells, editors, CNTR1 provides the performance benefits of lightweight coreutils, and package managers. These additional tools containers and the functionality of large containers by are usually not required for the application’s core function splitting the traditional container image into two parts: the — the common operational use-case — but they are “fat” image — containing the tools, and the “slim” image included for management, manual inspection, profiling, — containing the main application. At run-time, CNTR and debugging purposes [64]. In practice, this significantly allows the user to efficiently deploy the “slim” image and increases container size and, in turn, translates into then expand it with additional tools, when and if necessary, slower container deployment and inefficient datacenter by dynamically attaching the “fat” image. -
Linux on the Road
Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes. -
No Starch Press, Inc
Table of Contents The Book of VMware—The Complete Guide to VMware Workstation.......................................................1 Chapter 1: Introduction.....................................................................................................................................3 Overview..................................................................................................................................................3 1.1 Who Should Read This Book............................................................................................................3 1.2 Terms and Conventions.....................................................................................................................4 1.3 Book Layout......................................................................................................................................4 1.4 VMware Applications........................................................................................................................6 1.4.1 Quality Assurance (QA)....................................................................................................6 1.4.2 Network Programming and Testing...................................................................................6 1.4.3 Operating System Development, Research, and Education..............................................7 1.4.4 Other VMware Products....................................................................................................7 Chapter 2: The VMware Virtual Machine.......................................................................................................8 -
Checkpoints of GUI-Based Applications Victor C
Checkpoints of GUI-based Applications Victor C. Zandy and Barton P. Miller Computer Sciences Department University of Wisconsin – Madison, USA {zandy,bart}@cs.wisc.edu Abstract tion’s GUI might migrate as the application itself migrates, or independently of the application. Both We describe a new system, called guievict, that enables the types of migration require the ability to capture the graphical user interface (GUI) of any application to be application’s window session, a transportable represen- transparently migrated to or replicated on another display tation of its GUI. Window sessions are difficult to cap- without premeditative steps such as re-linking the application ture because not all of the state they represent is resident program binary or re-directing the application process’s in the application. Portions of an application’s GUI state window system communication through a proxy. Guievict is reside in the window server, a separate system that han- based on a small X window server extension that enables an dles the display of all GUI-based applications on the application to retrieve its window session, a transportable representation of its GUI, from the window server and a library same host. Most window servers do not provide a way to of GUI migration functionality that is injected in the extract the state of an individual application’s resources. application process at run time. We discuss the underlying Guievict has been implemented for the X window technical issues: controlling and synchronizing the system [19] and has the following characteristics: communication between the application and the window ❏ Migration occurs at application granularity; users system, identifying and retrieving the GUI resources that form the window session, regenerating the window session in a new can select and move the GUI of individual applica- window system, and maintaining application transparency. -
Conception Et Développement D'une Infrastructure De Communication
Conception et développement d’une infrastructure de communication collaborative Septimia-Cristina Pop To cite this version: Septimia-Cristina Pop. Conception et développement d’une infrastructure de communication collab- orative. Réseaux et télécommunications [cs.NI]. Institut National Polytechnique de Grenoble - INPG, 2005. Français. tel-00081666 HAL Id: tel-00081666 https://tel.archives-ouvertes.fr/tel-00081666 Submitted on 23 Jun 2006 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. INSTITUT NATIONAL POLYTECHNIQUE DE GRENOBLE No attribu´epar la biblioth`eque THESE` pour obtenir le grade de DOCTEUR DE L’INPG Sp´ecialit´e: « Informatique : Syst`emeset Communications » pr´epar´eeau laboratoire LSR – IMAG dans le cadre de l’Ecole´ Doctorale « Math´ematiques,Sciences et Technologies de l’Information » pr´esent´eeet soutenue publiquement par Septimia-Cristina Pop Le 19 D´ecembre 2005 Titre : Conception et d´eveloppement d’une infrastructure de communication collaborative Directeur de th`ese : M. Andrzej Duda JURY M. Jacques Mossiere, Pr´esident M. Guy Bernard, Rapporteur M. Michel Riveill, Rapporteur M. Andrzej Duda, Directeur de th`ese A` ma m`ere. A` la m´emoire de mon p`ere. Influenc´eepeut-ˆetre par la beaut´ede la r´egiongrenobloise, j’ai toujours imagin´ela pr´epa- ration de la th`esecomme une randonn´ee`ala montagne. -
Linux Laptop-HOWTO
Linux Laptop−HOWTO Linux Laptop−HOWTO Table of Contents Linux Laptop−HOWTO.....................................................................................................................................1 Werner Heuser <[email protected]>....................................................................................................1 1. Preface..................................................................................................................................................1 2. Copyright, Disclaimer and Trademarks...............................................................................................1 3. Which Laptop to Buy?.........................................................................................................................1 4. Laptop Distribution..............................................................................................................................2 5. Installation...........................................................................................................................................2 6. Hardware In Detail...............................................................................................................................2 7. Palmtops, Personal Digital Assistants − PDAs, Handheld PCs − HPCs.............................................2 8. Cellular Phones, Pagers, Calculators, Digital Cameras, Wearable Computing...................................3 9. Accessories..........................................................................................................................................3 -
Section 2: a Quick Window Manager and Unix Tutorial
2. A quick windowmanager and Unix tutorial (This section last updated August 2012) This section provides •some "getting started" pointers on the graphical windowing environments you will be using, primar- ily on the ECMC Linux system in the room 52 studio, but also with some references and comparisons to comparable Mac OSX and Windows procedures; and •anintroduction to some basic Unix commands and utility programs that can be run from a shell windowonECMC Linux and Macintosh music production systems As noted in section 1, the core of a computer operating system, which implements the most basic sys- tem protocols and operations, is called the kernel.The open source Linux kernel is developed and main- tained by an international group of thousands of volunteers under the direction of Linus Torvalds, who wrote much of the first Linux kernel, modeled after the functionality of Unix operating systems, during the early 1990s. The Linux kernel is updated several times each year,and includes both a stable branch, designed for most users (likeus), and a developmental branch, used by Linux developers to test newfea- tures before theyare incorporated into stable versions of the kernel. Technically,the term "Linux"refers only to an operating system kernel developed by the team of Linux Project programmers under Torvolds’ direction. The GNU (pronounced "ga-NOO") Project is a non- profit organization that supports the development of a broad range of open source applications, without which the Linux kernel would be useless. Manyusers of GNU software on Linux kernels prefer to call their operating system GNU Linux or GNU/Linux.Incommon usage, however, the term Linux often is used loosely to refer to all GNU operating system components as well as the Linux kernel. -
1. Why POCS.Key
Symptoms of Complexity Prof. George Candea School of Computer & Communication Sciences Building Bridges A RTlClES A COMPUTER SCIENCE PERSPECTIVE OF BRIDGE DESIGN What kinds of lessonsdoes a classical engineering discipline like bridge design have for an emerging engineering discipline like computer systems Observation design?Case-study editors Alfred Spector and David Gifford consider the • insight and experienceof bridge designer Gerard Fox to find out how strong the parallels are. • bridges are normally on-time, on-budget, and don’t fall ALFRED SPECTORand DAVID GIFFORD • software projects rarely ship on-time, are often over- AS Gerry, let’s begin with an overview of THE DESIGN PROCESS bridges. AS What is the procedure for designing and con- GF In the United States, most highway bridges are budget, and rarely work exactly as specified structing a bridge? mandated by a government agency. The great major- GF It breaks down into three phases: the prelimi- ity are small bridges (with spans of less than 150 nay design phase, the main design phase, and the feet) and are part of the public highway system. construction phase. For larger bridges, several alter- There are fewer large bridges, having spans of 600 native designs are usually considered during the Blueprints for bridges must be approved... feet or more, that carry roads over bodies of water, preliminary design phase, whereas simple calcula- • gorges, or other large obstacles. There are also a tions or experience usually suffices in determining small number of superlarge bridges with spans ap- the appropriate design for small bridges. There are a proaching a mile, like the Verrazzano Narrows lot more factors to take into account with a large Bridge in New Yor:k. -
Robert Ancell Lightdm: Cross Desktop Display Manager
LightDM: Cross Desktop Display Manager Robert Ancell What is a Display Manager? ● High level: ● Run display servers (X) ● Authenticate users (greeter) ● Start sessions (GNOME, KDE, XFCE, ...) ● Remote login (XDMCP) What is a Display Manager? ● Low level: ● Persistent daemon ● Manage display server and session processes ● Support multiple logins ● Switch users In the past... XDM ...there was XDM Today... XDM GDM KDM LXDM SLiM uxlaunch ..we have many What's the difference? XDM GDM KDM LXDM SLiM uxlaunch What's the difference? X GTK+ Qt GTK+ X XDM GDM KDM LXDM SLiM uxlaunch Mostly different GUIs Why not this? X GTK+ Qt GTK+ X One Display Manager to rule them all Introducing LightDM ● Freedesktop project ● Specification (TODO) ● Sponsored by Canonical for Ubuntu ● lp:lightdm ● GPL3 ● C/GObject Core features ● GObject / Qt greeter support ● Automatic login ● Guest accounts ● User switching ● XDMCP ● Multi-seat ● Test mode ● Regression tests Planned features ● Wayland support ● VNC / RDP login ● Improved two-factor authentication ● Fallback session support Example greeter (GObject) #include <lightdm.h> static void show_prompt (LightDMGreeter *greeter, const gchar *text, LightDMPromptType type) { lightdm_greeter_respond (greeter, “password”); } static void authentication_complete_cb (LightDMGreeter *greeter) { if (lightdm_greeter_get_is_authenticated (greeter)) lightdm_greeter_start_session_sync (greeter, NULL, NULL); } int main (int argc, char **argv) { GMainLoop *main_loop = g_main_loop_new (NULL, FALSE); LightDMGreeter *greeter = lightdm_greeter_new -
Database Containers: Made by Distributions
Database Containers: Made by Distributions Honza Horak <[email protected]> PgConf.eu, Tallinn, November 2016 The goal today ● Get feedback ● Show how we think about containers ● Convince you that you shouldn’t ignore them ● Introduce technologies that we care about in Red Hat Database Containers Made by Distributions Honza Horak Brno, Czech Republic ● Red Hat, Platform Engineering ● Databases, Python, Ruby ● RHEL, Fedora, CentOS ● Software Collections Database Containers Made by Distributions Honza Horak Brno, Czech Republic ● Red Hat, Platform Engineering ● Databases, Python, Ruby ● RHEL, Fedora, CentOS ● Software Collections ● AND CONTAINERS Database Containers Made by Distributions What this talk includes 1. Containers basics 2. Why containers matter 3. PostgreSQL Docker container 4. System containers 5. Tools containers 6. GUI apps in containers 7. OS containers 8. Ansible Containers 9. OCI Database Containers Made by Distributions 1. CONTAINERS BASICS Database Containers Made by Distributions Containers and images ● Container ○ Process isolated by Linux kernel features ○ Virtualization technology ● Image ○ Static container used to run containers ● Container is an instance of a (container) image Database Containers Made by Distributions Container is not a virtual machine Traditional Virtual Machine Linux Containers (e.g. Docker) App App App Bin/Libs Bin/Libs Bin/Libs App App App Guest OS Guest OS Guest OS Bin/Libs Bin/Libs Bin/Libs Hypervisor Container Engine (Docker daemon) Host OS (kernel) Host OS (kernel) Infrastructure Infrastructure Database Containers Made by Distributions Container is not a virtual machine Traditional Virtual Machine Linux Containers (e.g. Docker) App App App Bin/Libs Bin/Libs Bin/Libs App App App Guest OS Guest OS Guest OS Bin/Libs Bin/Libs Bin/Libs Hypervisor Docker Engine Host OS (kernel) Host OS (kernel) Infrastructure Infrastructure Database Containers Made by Distributions Container is not a virtual machine Traditional Virtual Machine Linux Containers (e.g. -
HP Compaq 8000 Elite PC Overview
QuickSpecs HP Compaq 8000 Elite PC Overview Ultra-slim Desktop 1. Optical Disc Drive (slimline) 5. 2.5” internal hard disk drive bay 2. Secure Digital (SD) Card Reader 6. 135W 87% efficient external Power Adapter 3. Rear I/O includes (6) USB 2.0 ports, DisplayPort and VGA 7. HP USDT Tower Stand (sold separately) video interfaces, PS/2 mouse and keyboard ports, RJ-45 network interface, audio in/out jacks 8. HP Optical Mouse 4. Front I/O includes (4) USB 2.0 ports, dedicated headphone 9. HP Keyboard output, and a microphone/headphone jack 10. HP Monitor (sold separately) DA - 13424 EMEA — Version 12 — April 16, 2010 Page 1 QuickSpecs HP Compaq 8000 Elite PC Overview Small Form Factor 1. Rear I/O includes (6) USB 2.0 ports, serial port, PS/2 mouse 6. 3.5” external drive bay supporting a media card reader or a and keyboard ports, RJ-45 network interface, DisplayPort and secondary hard disk drive VGA video interfaces, and audio in/out jacks 7. 5.25” external drive bay supporting an optical disk drive 2. Low profile expansion slots include (1) PCI slot, (2) PCI Express x1 slots and (1) PCI Express x16 graphics slot 8. 3.5” internal drive bay supporting primary hard disk drive 3. Front I/O includes (4) USB 2.0 ports, dedicated headphone 9. 240W standard or 89% high efficiency Power Supply output, and a microphone/headphone jack 10. HP Monitor (sold separately) 4. HP Optical Mouse 5. HP Keyboard DA - 13424 EMEA — Version 12 — April 16, 2010 Page 2 QuickSpecs HP Compaq 8000 Elite PC Overview Convertible Minitower 1.