X Window System Version 6.4.2 Release Notes
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Managing Projects with GNU Make, Third Edition by Robert Mecklenburg
ManagingProjects with GNU Make Other resources from O’Reilly Related titles Unix in a Nutshell sed and awk Unix Power Tools lex and yacc Essential CVS Learning the bash Shell Version Control with Subversion oreilly.com oreilly.com is more than a complete catalog of O’Reilly books. You’ll also find links to news, events, articles, weblogs, sample chapters, and code examples. oreillynet.com is the essential portal for developers interested in open and emerging technologies, including new platforms, pro- gramming languages, and operating systems. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today with a free trial. THIRD EDITION ManagingProjects with GNU Make Robert Mecklenburg Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Managing Projects with GNU Make, Third Edition by Robert Mecklenburg Copyright © 2005, 1991, 1986 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. -
Functional C
Functional C Pieter Hartel Henk Muller January 3, 1999 i Functional C Pieter Hartel Henk Muller University of Southampton University of Bristol Revision: 6.7 ii To Marijke Pieter To my family and other sources of inspiration Henk Revision: 6.7 c 1995,1996 Pieter Hartel & Henk Muller, all rights reserved. Preface The Computer Science Departments of many universities teach a functional lan- guage as the first programming language. Using a functional language with its high level of abstraction helps to emphasize the principles of programming. Func- tional programming is only one of the paradigms with which a student should be acquainted. Imperative, Concurrent, Object-Oriented, and Logic programming are also important. Depending on the problem to be solved, one of the paradigms will be chosen as the most natural paradigm for that problem. This book is the course material to teach a second paradigm: imperative pro- gramming, using C as the programming language. The book has been written so that it builds on the knowledge that the students have acquired during their first course on functional programming, using SML. The prerequisite of this book is that the principles of programming are already understood; this book does not specifically aim to teach `problem solving' or `programming'. This book aims to: ¡ Familiarise the reader with imperative programming as another way of imple- menting programs. The aim is to preserve the programming style, that is, the programmer thinks functionally while implementing an imperative pro- gram. ¡ Provide understanding of the differences between functional and imperative pro- gramming. Functional programming is a high level activity. -
No Slide Title
Embedded Systems Class overview, Embedded systems introduction, Raspberry Pi, Linux OS, X-windows, Window manager, Desktop Environment Prof. Myung-Eui Lee (A-405) [email protected] Embedded Systems 1-1 KUT Embedded Systems Class Overview ⚫ Embedded Systems Class Operations » Past : 3 (credit) -2 (lecture) -2 (practice) » Now : 3 (credit) -1 (lecture) -1 (design) -2 (practice) » Future : 4 (credit) -2 (lecture) -2 (design) -0 (practice) ⚫ PBL : Problem or Project Based Learning » Problem : 4 problems » Project : 2 projects ⚫ 4 hours Class » 1 hour (lecture) + 1 hour (lecture or design) + 2 hours (practice) ▪ 1 hour (lecture) + 1 hour (lecture or design) : me ▪ 2 hours (practice) : Ph.D Park ⚫ Target Board : Raspberry Pi 3 » ARM + Linux Embedded Systems 1-2 KUT Embedded Systems Class Overview ⚫ Class Grade : » Mid Term Exam : 15 % [30 %] » Final Term Exam : 15 % [30 %] » Peer Evaluation : 10 % (Project #1 : 5% + Project #2 : 5%) » Project #1 Evaluation : 10 % » Project #2 Evaluation : 15 % » Experimental Lab. : 20 % [20 %] » Class Participation : 15 % [20 %] » Social Problem (Project #2) Optional : +5 % ⚫ Lecture Notes: http://microcom.koreatech.ac.kr Embedded Systems 1-3 KUT Embedded Systems ⚫ Definition of embedded system » Embedded system = H/W + S/W ▪ H/W = CPU + Memory + I/O ▪ S/W = Device driver + OS (or non OS) + Application program » Any electronic system that uses a CPU chip, but that is not a general-purpose workstation, desktop or laptop computer. » In embedded systems, the software typically resides in memory device, such as a flash memory or ROM chip. In contrast to a general-purpose computer that loads its programs into RAM each time. » Sometimes, single board and rack mounted general-purpose computers are called "embedded computers" if used to control. -
Linux on IBM Zseries and S/390: Application Development
Front cover Linux on IBM zSeries and S/390: Application Development Tools and techniques for Linux application development Using the Eclipse IDE and Jakarta Project tools Sample code to illustrate programming techniques Gregory Geiselhart Andrea Grahn Frans Handoko Jörg Hundertmark Albert Krzymowski Eliuth Pomar ibm.com/redbooks International Technical Support Organization Linux on IBM ^ zSeries and S/390: Application Development July 2002 SG24-6807-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xiii. First Edition (July 2002) This edition applies to zVM 4.2 (ESP) and many different Linux distributions. SuSE Linux Enterprise Server 7.0 was used. © Copyright International Business Machines Corporation 2002. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xiii Trademarks . xiv Preface . xv The team that wrote this redbook. xvi Become a published author . xvii Comments welcome. xvii Part 1. Programming tools . 1 Chapter 1. The basic tools you need. 3 1.1 Where you can look for information. 4 1.1.1 Man pages . 4 1.1.2 Info - the help system . 5 1.2 Compiling C/C++ source code . 6 1.2.1 Starting gcc . 6 1.2.2 Source files . 6 1.2.3 Directory search . 7 1.2.4 Compilation stages . 7 1.2.5 Macros . 8 1.2.6 Warnings . 8 1.2.7 Extra information for debuggers . 8 1.2.8 Code optimization . 9 1.2.9 Configuring gcc as a cross-compiler . -
The Virtualization Cookbook for SLES 10
z/VM and Linux on IBM System z: The Virtualization Cookbook for z/VM 6.2 RHEL 6.2 and SLES 11 SP2 A “cookbook” for installing and customizing z/VM 6.2, RHEL 6.2 and SLES 11 SP2 on the mainframe Michael MacIsaac Brad Hinson Marian Gasparovic . Contents Preface . xi Parts of this book . xi Summary of changes in the July 2012 version . xi Summary of changes in the January 2012 version . xii Conventions . xiii Operating system releases used . xiii The team that wrote this book . xiii Special thanks . xiii Comments welcome. xiv Part 1. Introduction and z/VM . 1 Chapter 1. Introduction to z/VM and Linux . 1 1.1 What is virtualization? . 3 1.2 A philosophy adopted in this book . 4 1.3 Choices and decisions made in this book . 4 1.4 Single System Image design. 4 1.5 Infrastructure design . 5 1.6 Usability tests performed. 6 Chapter 2. Planning . 7 2.1 Planning for an SSI and LGR . 7 2.1.1 Hints and Tips . 7 2.1.2 Need for ECKD DASD . 9 2.2 Bill of materials . 9 2.2.1 Hardware resources . 9 2.2.2 Software resources . 9 2.2.3 Networking resources . 10 2.3 z/VM conventions . 10 2.3.1 Volume labeling convention . 10 2.3.2 Backup file naming convention . 11 2.3.3 The command retrieve convention . 11 2.4 Disk planning. 12 2.5 Memory planning. 13 2.6 Password planning . 13 2.7 Planning worksheets . 14 2.7.1 z/VM resources used in this book . -
Building the Package
5 Building the package Nowwehav e configured our package and we’re ready to build. This is the Big Moment: at the end of the build process we should have a complete, functioning software product in our source tree. In this chapter,we’ll look at the surprises that make can have instore for you. Youcan find the corresponding theoretical material in Chapter 19, Make. Preparation If you’re unlucky, a port can go seriously wrong. The first time that error messages appear thick and fast and scroll offthe screen before you can read them, you could get the impression that the packages were built this way deliberately to annoyyou. Alittle bit of preparation can go a long way towards keeping you in control of what’sgoing on. Here are some suggestions: Makesure you have enough space One of the most frequent reasons of failure of a build is that the file system fills up. If possi- ble, ensure that you have enough space before you start. The trouble is, howmuch is enough? Hardly anypackage will tell you howmuch space you need, and if it does it will probably be wrong, since the size depends greatly on the platform. If you are short on space, consider compiling without debugging symbols (which takeupalot of space). If you do run out of space in the middle of a build, you might be able to save the day by stripping the objects with strip,inother words removing the symbols from the file. Use a windowing system The sheer size of a complicated port can be a problem. -
Bonus Chapter B Programming for X
Bonus Chapter B Programming for X In this chapter and the next, we’ll take a look at writing programs to run in the usual Linux graphical environment, the XWindow System or X, http://www.x.org/Xorg.html. Modern UNIX systems and nearly all Linux distributions are shipped with a version of X. We’ll be concentrating on the programmer’s view of X, and we’ll assume that you are already comfortable with configuring, running, and using X on your system. We’ll cover ❑ X concepts ❑ X Windows managers ❑ X programming model ❑ Tk—its widgets, bindings, and geometry managers In the next chapter, we’ll move on to the GTK+ toolkit, which will allow us to program user interfaces in C for the GNOME system. What Is X? X was created at MIT as a way of providing a uniform environment for graphical programs. Nowadays it should be fair to assume that if you’ve used computers, you’ve come across either Microsoft Windows, X, or Apple MacOS before, so you’ll be familiar with the general concepts underlying a graphical user interface, or GUI. Unfortunately, although a Windows user might be able to navigate around the Mac interface, it’s a different story for programmers. Each windowing environment on each system is programmed differently. The ways that the display is handled and the programs communicate with the user are different. Although each system provides the programmer with the ability to open and manipulate windows on the screen, the functions used will be different. Writing applications that can run on more than one system (without using additional toolkits) is a daunting task. -
Common Desktop Environment 1.0 Programmer's Overview
Common Desktop Environment 1.0 Programmer’s Overview This edition of the Common Desktop Environment Advanced User’s and System Administrator’s Guide applies to AIX Version 4.2, and to all subsequent releases of these products until otherwise indicated in new releases or technical newsletters. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and FAR 52.227-19. THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. The code and documentation for the DtComboBox and DtSpinBox widgets were contributed by Interleaf, Inc. Copyright 1993, Interleaf, Inc. Copyright 1993, 1994, 1995 Hewlett-Packard Company Copyright 1993, 1994, 1995 International Business Machines Corp. Copyright 1993, 1994, 1995 Sun Microsystems, Inc. Copyright 1993, 1994, 1995 Novell, Inc. All rights reserved. This product and related documentation are protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form by any means without prior written authorization. All rights reserved. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the United States Government is subject to the restrictions set forth in DFARS 252.227-7013 (c)(1)(ii) and AR 52.227-19. Part 1 —Common Desktop Environment Architectural Overview 1. Architectural Overview. 1 Conceptual Overview. 1 Data Interaction GUIs. 2 Multiuser Collaboration. 3 Desktop Management. -
Abkürzungs-Liste ABKLEX
Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte -
XL C/C++ Compiler and Runtime Migration Guide for the Application Programmer
z/OS Version 2 Release 3 XL C/C++ Compiler and Runtime Migration Guide for the Application Programmer IBM GC14-7306-30 Note Before using this information and the product it supports, read the information in “Notices” on page 129. This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2019-02-15 © Copyright International Business Machines Corporation 1996, 2017. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents About this document.............................................................................................xi z/OS XL C/C++ on the World Wide Web.................................................................................................... xix Where to find more information...........................................................................................................xix Technical support...................................................................................................................................... xix How to send your comments to IBM.........................................................................................................xix If you have a technical problem........................................................................................................... xx Part 1. Introduction.............................................................................................. -
007-2006-100 Contributors
Indigo Magic™ Desktop Integration Guide Document Number 007-2006-100 CONTRIBUTORS Written by Beth Fryer, Jed Hartman, Ken Jones, and Pete Sullivan Illustrated by Beth Fryer and Seth Katz Edited by Christina Cary Production by Derrald Vogt, Cindy Stief, and Linda Rae Sande Engineering contributions by Bob Blean, Susan Dahlberg, Susan Ellis, John Krystynak, Chandra Pisupati, Jack Repenning, CJ Smith, Dave Story, Steve Strasnick, Rebecca Underwood, Steve Yohanan, and Betsy Zeller St Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. © Copyright 1994, 1995, 1996 Silicon Graphics, Inc.— All Rights Reserved The contents of this document may not be copied or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. Silicon Graphics, the Silicon Graphics logo, and IRIS are registered trademarks and IRIS, IRIS GL, IRIS IM, IRIS InSight, IRIS ViewKit, IRIX, GoldenGate, IconSmith, Indigo Magic, the Graphics Library, OpenGL, Open Inventor, and RapidApp are trademarks of Silicon Graphics, Inc. Apple is a registered trademark and Apple Quicktime is a trademark of Apple Computer, Inc. -
An Introduction to X Window Application Development
Calhoun: The NPS Institutional Archive Theses and Dissertations Thesis Collection 1992-03 An introduction to X Window application development. Rust, David Michael Monterey, California. Naval Postgraduate School http://hdl.handle.net/10945/23933 FV KNOX LIBRARY •Ud SCHOOL SivAL POSTGRADUATE SoNTEHEV.CAUFORN.AG^^ CURITY CLASSIFICATION OF THIS PAGE REPORT DOCUMENTATION PAGE 1b. RESTRICTIVE MARKINGS REPORT SECURITY CLASSIFICATION UNCLASSIFIED a SECURITY CLASSIPICAT I6M AUTH6RITV 3. bisTRiBuTi6N7AVAlLABiUTY 6P REP5RT Approved for public release; b. dECLAssIFICATIoN/doWNgRADINg SCHEDULE distribution is unlimited PERFORMING ORGANIZATION REP6RT NUM&ER(S) 5. M6niT6Ring6Rgani2aTi6n rep6rT numbER(S) *. NAME 6F PERFORMING 6R6ANIZATI6N 6b OFFICE SYMBOL 7a. NAME 6E M6NIT6R1NG ORGANIZATION vdministrative Sciences Department (if applicable) Naval Postgraduate School Javal Postgraduate School AS :. ADDRESS (City, State, and ZIP Code) 7b. ADDRESS (City, State, and ZIP Code) /lonterey, CA 93943-5000 Monterey, CA 93943-5000 NAME OF FUNDING/SPONSORING 8b. OFFICE SYMBOL g PROCURE M E N T I NST RUMEN T ID E N T I FI CATION NUMBE R ORGANIZATION (if applicable) 6. ADDRESS (City, State, and ZIP Code) 10. SOURCE OF FUNDING NUMBERS PROGRAM 1 PR6JECT TTa^R" WoRkUNiT ELEMENT NO. NO. NO. ACCESSION NO. 1 . TITLE (Include Security Classification) ^N INTRODUCTION TO X WINDOW APPLICATION DEVELOPMENT (U) 2 PERSONAL AUTHOR(S) lust, David M. 3a. type of report 13b. time covered 14. DATE OF REPORT (Year, Month, Day) 16. PAGE COUNT Master's Thesis from 10/90 to 03/92 1992, March, 23 70 supplementary notation 6 The views expressed in this ^sis ^ those of the author md do not reflect the official policy or position of the Department of Defense or the United States Government.