DOCSLIB.ORG

Lpi Linux Certification in a Nutshell

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lpi Linux Certification in a Nutshell LPI LINUX CERTIFICATION IN A NUTSHELL LPI LINUX CERTIFICATION IN A NUTSHELL Third Edition Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo LPI Linux Certification in a Nutshell, Third Edition by Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger Copyright © 2010 Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger. 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. Online editions are also available for most titles (http://my.safaribooksonline.com). For more infor- mation, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Andy Oram Indexer: Jay Marchand Production Editor: Adam Zaremba Cover Designer: Karen Montgomery Copyeditor: Genevieve d’Entremont Interior Designer: David Futato Proofreader: Jennifer Knight Illustrator: Robert Romano Printing History: May 2001: First Edition. July 2006: Second Edition. June 2010: Third Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trade- marks of O’Reilly Media, Inc. LPI Linux Certification in a Nutshell, the image of a bull, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. TM This book uses RepKover™, a durable and flexible lay-flat binding. ISBN: 978-0-596-80487-9 [M] 1276182761 Table of Contents Preface . ........................................................... xiii 1. LPI Exams . ..................................................... 1 2. Exam 101 Study Guide . .......................................... 5 Exam Preparation 5 3. System Architecture (Topic 101.1) . ................................. 7 Objective 1: Determine and Configure Hardware Settings 7 BIOS 7 USB Topology 10 USB Controllers 10 USB Devices 11 USB Drivers 11 USB Hotplug 12 Reporting Your Hardware 12 Manipulating Modules 14 Device Management Definitions 20 4. Change Runlevels and Shut Down or Reboot System (Topics 101.2 and 101.3) . ....................................................... 21 Objective 2: Boot the System 21 Boot-time Kernel Parameters 21 Introduction to Kernel Module Configuration 22 Objective 3: Change Runlevels and Shut Down or Reboot System 24 Single-User Mode 25 Overview of the /etc Directory Tree and the init Process 26 v Setting the Default Runlevel 28 Determining Your System’s Runlevel 28 5. Linux Installation and Package Management (Topic 102) . 33 Objective 1: Design a Hard Disk Layout 34 System Considerations 34 Swap Space 37 General Guidelines 38 Objective 2: Install a Boot Manager 38 LILO 39 GRUB 41 Objective 3: Manage Shared Libraries 44 Shared Library Dependencies 44 Linking Shared Libraries 45 Objective 4: Use Debian Package Management 46 Debian Package Management Overview 46 Managing Debian Packages 47 Objective 5: Use Red Hat Package Manager (RPM) 52 RPM Overview 52 Running rpm 53 YUM Overview 58 6. GNU and Unix Commands (Topic 103) . ............................. 63 Objective 1: Work on the Command Line 64 The Interactive Shell 65 Command History and Editing 71 Manpages 75 Objective 2: Process Text Streams Using Filters 77 Objective 3: Perform Basic File Management 91 Filesystem Objects 91 File-Naming Wildcards (File Globbing) 100 Objective 4: Use Streams, Pipes, and Redirects 102 Standard I/O and Default File Descriptors 102 Pipes 103 Redirection 104 Using the tee Command 106 The xargs Command 106 Objective 5: Create, Monitor, and Kill Processes 107 Processes 107 Process Monitoring 108 Signaling Active Processes 115 Terminating Processes 117 Shell Job Control 118 Objective 6: Modify Process Execution Priorities 120 nice 120 Objective 7: Search Text Files Using Regular Expressions 123 vi | Table of Contents Regular Expression Syntax 123 Using grep 125 Using sed 127 Examples 130 Objective 8: Perform Basic File Editing Operations Using vi 135 Invoking vi 135 vi Basics 135 7. Devices, Linux Filesystems, and the Filesystem Hierarchy Standard (Topic 104) . ......................................... 139 Objective 1: Create Partitions and Filesystems 140 Disk Drives Under Linux 140 Objective 2: Maintain the Integrity of Filesystems 151 Monitoring Free Disk Space and Inodes 151 Monitoring Disk Usage 153 Modifying a Filesystem 154 Checking and Repairing Filesystems 157 Objective 3: Control Filesystem Mounting and Unmounting 161 Managing the Filesystem Table 161 Mounting Filesystems 163 Unmounting Filesystems 166 Objective 4: Set and View Disk Quotas 167 Quota Limits 168 Quota Commands 169 Enabling Quotas 175 Objective 5: Manage File Permissions and Ownership 176 Linux Access Control 176 Setting Access Modes 181 Setting Up a Workgroup Directory 186 Objective 6: Create and Change Hard and Symbolic Links 187 Why Links? 188 Objective 7: Find System Files and Place Files in the Correct Location 192 Datatypes 193 The root Filesystem 194 Locating Files 200 8. Exam 101 Review Questions and Exercises . 205 System Architecture (Topic 101) 205 Review Questions 205 Exercises 206 Linux Installation and Package Management (Topic 102) 206 Review Questions 206 Exercises 207 GNU and Unix Commands (Topic 103) 208 Review Questions 208 Exercises 208 Table of Contents | vii Devices, Linux Filesystems, and the Filesystem Hierarchy Standard (Topic 104) 211 Review Questions 211 Exercises 212 9. Exam 101 Practice Test . ........................................ 215 Questions 215 Answers 226 10. Exam 101 Highlighter’s Index . 229 System Architecture 229 Objective 101.1: Determine and Configure Hardware Settings 229 Objective 101.2: Boot the System 230 Objective 101.3: Change Runlevels and Shut Down or Reboot System 230 Linux Installation and Package Management 230 Objective 102.1: Design Hard Disk Layout 230 Objective 102.2: Install a Boot Manager 231 Objective 102.3: Manage Shared Libraries 231 Objective 102.4: Use Debian Package Management 232 Objective 102.5: Use Red Hat Package Manager (RPM) 232 GNU and Unix Commands 232 Objective 103.1: Work on the Command Line 232 Objective 103.2: Process Text Streams Using Filters 233 Objective 103.3: Perform Basic File Management 235 Objective 103.4: Use Streams, Pipes, and Redirects 237 Objective 103.5: Create, Monitor, and Kill Processes 238 Objective 103.6: Modify Process Execution Priorities 239 Objective 103.7: Search Text Files Using Regular Expressions 239 Objective 103.8: Perform Basic File Editing Operations Using vi 241 Devices, Linux Filesystems, and the Filesystem Hierarchy Standard 243 Objective 104.1: Create Partitions and Filesystems 243 Objective 104.2: Maintain the Integrity of Filesystems 244 Objective 104.3: Control Filesystem Mounting and Unmounting 244 Objective 104.4: Set and View Disk Quotas 246 Objective 104.5: Manage File Permissions and Ownership 246 Objective 104.6: Create and Change Hard and Symbolic Links 248 Objective 104.7: Find System Files and Place Files in the Correct Location 248 11. Exam 102 Overview . .......................................... 251 12. Exam 102 Study Guide . ........................................ 253 Exam Preparation 253 viii | Table of Contents 13. Shells, Scripting, and Data Management (Topic 105) . 255 Objective 1: Customize and Use the Shell Environment 256 An Overview of Shells 256 The Bash Shell 257 Objective 2: Customize or Write Simple Scripts 267 Script Files 267 Basic Bash Scripts 272 Objective 3: SQL Data Management 285 Accessing a MySQL Server 285 Database Overview 287 Aggregate Functions 292 Multitable Queries 293 14. The X Window System (Topic 106) . 297 An Overview of X 298 Objective 1: Install and Configure X11 298 Selecting and Configuring an X Server 299 X Fonts 306 Controlling X Applications with .Xresources 308 Objective 2: Set Up a Display Manager 308 Configuring xdm 308 X Terminals 311 Configuring KDM 311 Configuring GDM 314 Objective 3: Accessibility 316 15. Administrative Tasks (Topic 107) . 319 Objective 1: Manage User and Group Accounts and Related System Files 319 User Accounts and the Password File 320 Groups and the Group File 321 The Shadow Password and Shadow Group Systems 322 User and Group Management Commands 323 Objective 2: Automate System Administration Tasks by Scheduling Jobs 326 Using cron 326 Using at 329 Controlling User Access to cron and at 330 Objective 3: Localization and Internationalization 330 16. Essential System Services (Topics 108.1 and 108.2) . 333 Objective 1: Maintain System Time 333 NTP Concepts 334 The NTP Software Package Components 334 The Hardware Clock 339 Table of Contents | ix Time Zones 340 Objective 2: System Logging 341 Configuring syslogd 341 Client/Server Logging 343 Logfile Rotation 343 Examining Logfiles 344 17. Mail Transfer Agent (MTA) Basics (Topic 108.3) . 347 Objective 3: Mail Transfer Agent (MTA) Basics 347 Configuration of Sendmail 348 Configuration of Postfix 351 Configuration of Qmail 353 Configuration of Exim
Load more

Recommended publications
  • Auswirkungen Der Benutzung Von Zentralen Und Dezentralen Versionsverwaltungssystemen in Open Source Projekten
    Auswirkungen der Benutzung von zentralen und dezentralen Versionsverwaltungssystemen In Open Source Projekten Masterarbeit an der Freien Universität Berlin für den Abschluss zum Master of Computer Science Jana von dem Berge 16. April 2009 Fachbereich Mathematik und Informatik Arbeitsgruppe Software Engineering Betreuer: Christopher Oezbek II Selbstständigkeitserklärung: Hiermit erkläre ich, dass ich diese Arbeit vollkommen selbständig verfasst und keine anderen als die angegebenen Quellen und Hilfsmittel benutzt sowie Zitate kenntlich gemacht habe. Berlin, 16. April 2009 Jana von dem Berge III IV Inhalt 1 Einleitung............................................................................................................. 1 1.1 Open Source Projekte .................................................................................. 1 1.2 Aufgabenstellung.......................................................................................... 1 1.3 Versionsverwaltungssysteme....................................................................... 3 1.3.1 Einführung............................................................................................. 3 1.3.2 Zentrale Versionsverwaltungssysteme.................................................. 5 1.3.3 Dezentrale Versionsverwaltungssysteme ............................................. 8 2 Forschungsmethode.......................................................................................... 10 2.1 Grounded Theory ......................................................................................
    [Show full text]
  • Linux Kernel and Driver Development Training Slides
    Linux Kernel and Driver Development Training Linux Kernel and Driver Development Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 9, 2021. Document updates and sources: https://bootlin.com/doc/training/linux-kernel Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/470 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/470 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/470 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
    [Show full text]
  • The Linux Graphics Stack Attributions
    I - Hardware : Anatomy of a GPU II - Host : The Linux graphics stack Attributions Introduction to GPUs and to the Linux Graphics Stack Martin Peres CC By-SA 3.0 Nouveau developer Ph.D. student at LaBRI November 26, 2012 1 / 36 I - Hardware : Anatomy of a GPU II - Host : The Linux graphics stack Attributions General overview Outline 1 I - Hardware : Anatomy of a GPU General overview Driving screens Host < − > GPU communication 2 II - Host : The Linux graphics stack General overview DRM and libdrm Mesa X11 Wayland X11 vs Wayland 3 Attributions Attributions 2 / 36 I - Hardware : Anatomy of a GPU II - Host : The Linux graphics stack Attributions General overview General overview of a modern GPU's functions Display content on a screen Accelerate 2D operations Accelerate 3D operations Decode videos Accelerate scientific calculations 3 / 36 I - Hardware : Anatomy of a GPU II - Host : The Linux graphics stack Attributions General overview CPU Clock Front-side Graphics Generator bus card slot Chipset Memory Slots High-speed graphics bus (AGP or PCI Northbridge Memory Express) bus (memory controller hub) Internal Bus PCI Bus Onboard Southbridge graphics PCI (I/O controller controller Bus hub) IDE SATA USB Cables and Ethernet ports leading Audio Codec CMOS Memory off-board PCI Slots LPC Bus Super I/O Serial Port Parallel Port Flash ROM Floppy Disk Keyboard (BIOS) Mouse 4 / 36 I - Hardware : Anatomy of a GPU II - Host : The Linux graphics stack Attributions General overview Hardware architecture GPU: Where all the calculations are made VRAM: Stores
    [Show full text]
  • Freiesmagazin 07/2009
    freiesMagazin Juli 2009 Topthemen dieser Ausgabe ZevenOS – Linux goes BeOS Seite 4 Ein biologisches Phänomen hat längst Einzug in die Linux-Welt gehalten: Mimikry. Das bedeu- tet, dass eine Spezies wegen bestimmter Vorteile eine andere Spezies nachahmt, z. B. legt sich eine harmlose Fliegenart das Aussehen von Wespen zu. Einer der neueren Fälle in der Linux-Welt ist ZevenOS, eine Linux-Distribution, die auf Ubuntu aufbaut. Das Besondere: Sie will im Aussehen und in der Benutzung etwas vom Feeling des legendären und leider im Nebel der Geschichte verschwundenen Betriebssystems BeOS vermitteln. (weiterlesen) easyVDR – The easy VDR Distribution Seite 12 Die Distribution easyVDR ist eine unter der GNU General Public License (GPL) veröffentlichte Distribution, die sich den Themen Video und TV widmet. Hat man noch ausgemusterte Rech- ner zuhause, lassen sich diese mit der Hilfe von easyVDR als digitaler Videorekorder nutzen – mit dem Vorteil, in vielen Belangen anpassbar zu sein; ein digitaler Selbstbaukasten sozusa- gen. (weiterlesen) Was bieten freie CRM-Lösungen? – Im Vergleich: SugarCRM und vtiger CRM Seite 34 CRM steht für Customer Relationship Management und beschreibt die Verwaltung von Kunden- daten und Kundenbeziehungen. Anhand eines konkreten Anwendungsfalls der fiktiven Firma EVENTO, einer Veranstaltungsagentur mit dem Schwerpunkt auf außergewöhnliche Orte, wer- den zwei CRM-Lösungen verglichen. Aus der Vielzahl an frei verfügbaren Programmen wurden die zwei populären Vertreter SugarCRM Version 5.2.0c und vtiger CRM Version 5.0.4 ausge- wählt. (weiterlesen) © freiesMagazin GNU FDL Ausgabe 07/2009 ISSN 1867-7991 MAGAZIN Editorial Anleitung: Wie verprellt man eine Community? Wir befinden uns im Jahre 2009 n. Chr. Die ganze ten [5].
    [Show full text]
  • 0000000000000000000000000
    Why use version control? Setting up CVS Saves all previous versions of all files so that Create the repository: you can undo (buggy) edits. % mkdir ~/cvsroot % [set permissions for ~/cvsroot] % setenv CVSROOT ~/cvsroot Logs changes to files so you can trace how % cvs init your sources have evolved over time. Set the CVSROOT environment variable in Mediates conflicting changes made by your .cshrc file. several different users---helps keep consistency. Repository Creating a Project Project 1 Project 2 Project 3 Create a project from existing files: % cd base64 % cvs import -m “base64” base64 carlk start Checkout the new project and delete the old files. % cvs checkout base64 Working copies Development Process with CVS Dealing with Conflicts If another user has committed changes to Get working copy Get any changes cvs checkout cvs update lines you have edited, CVS will report a conflict. Your version Edit files decode (infile, stdout); <<<<<<< decode64.c if( fclose (infile) ) return 0; ======= cvs commit if( fclose (infile) ) printf(" couldn't close file."); >>>>>>> 1.5 no Repository version Conflicts? Manually edit to remove the conflict. yes cvs update Edits on different lines are automatically Most of the merged. Resolve time you stay conflicts in shaded loop. 1 Frequently Used Commands Keywords Get the latest revisions of files with: Useful to put dynamic information in source file. % cvs update When you get a new revision, keywords are replaced with information about the file. Write changes back to repository with: % cvs commit -m“log msg” Keyword Replaced with $Author$ Username who checked in this revision. If you omit –m the editor given in the EDITOR $Date$ Date the this revision was checked in.
    [Show full text]
  • Armadillo-640 製品マニュアル
    Armadillo-640 製品マニュアル A6400-U00Z A6400-D00Z A6400-B00Z Version 1.14.0 2020/07/13 株式会社アットマークテクノ [https://www.atmark-techno.com] Armadillo サイト [https://armadillo.atmark-techno.com] Armadillo-640 製品マニュアル 株式会社アットマークテクノ 製作著作 © 2018-2020 Atmark Techno, Inc. Version 1.14.0 2020/07/13 Armadillo-640 製品マニュアル Armadillo-640 製品マニュアル 目次 1. はじめに ........................................................................................................................................ 15 1.1. 本書で扱うこと扱わないこと ............................................................................................. 15 1.1.1. 扱うこと .................................................................................................................. 15 1.1.2. 扱わないこと ........................................................................................................... 15 1.2. 本書で必要となる知識と想定する読者 ............................................................................... 15 1.3. ユーザー限定コンテンツ .................................................................................................... 16 1.4. 本書および関連ファイルのバージョンについて ................................................................. 16 1.5. 本書の構成 ......................................................................................................................... 16 1.6. 表記について ...................................................................................................................... 17 1.6.1. フォント .................................................................................................................
    [Show full text]
  • Linux, Yocto and Fpgas
    Embedded Open Source Experts Linux, Yocto and FPGAs Integrating Linux and Yocto builds into different SoCs From a Linux software perspective: ➤ Increased demand for Linux on FPGAs ➤ Many things to mange, both technical and practical ➤ FPGAs with integrated CPU cores – very similar many other SoCs Here are some experiences and observations... © Codiax 2019 ● Page 2 Why use Linux? ➤ De-facto standard ➤ Huge HW support ➤ FOSS ➤ Flexible ➤ Adaptable ➤ Stable ➤ Scalable ➤ Royalty free ➤ Vendor independent ➤ Large community ➤ Long lifetime Why not Linux? ➤ Too big ➤ Real-time requirements ➤ Certification ➤ Boot time ➤ Licensing ➤ Too open? Desktop Shells: Desktop Display server: Display BrailleDisplay Touch-Screen Mouse & Keyboard Wayland Compositor Wayland + development tools = a lot code!of source Linux system example weston, clayton,mutter,KWin evdev libinput GNOME Shell D radeon nouveau lima etna_viv freedreno tegra-re lima nouveau radeon freedreno etna_viv e libwayland-server libwayland-server s Cinnamon k t o kms p Linux kernel, Linux kernel, Plasma 2 w i (Kernel Mode Setting) Mode (Kernel d g Cairo-Dock e t s drm (Direct Rendering Manager) Rendering (Direct drm cache coherent L2-Caches L2-Caches cache coherent CPU &GPU Enlight. DR19 System libraries: System oflibraries): form (in the Toolkits Interface User µClibc Pango glibc glibc main memory possibly adaptations to Wayland/Mir libwayland / COGL libwayland Cairo Cairo (Xr) GTK+ Clutter 2D Application 2D GModule GThread GThread GLib GObject Glib GIO ATK devicedrivers other& modules System
    [Show full text]
  • Technical Report
    Eric-Hg Technical Report S-PM 140524 Mercurial Version Control of Eric Projects Technical Report – 1 – Eric-Hg Technical Report Copyright Page S-PM 140400 No commercial uses, No modifications allowed; Jurisdiction International, Format Text This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. Current edition PDF file, Eric_Deliver site URL: http://www.box.net/shared/k64yenrpey under the “Creative Commons License” Disclaimer The information in this document is subject to change without notice. The author and publisher have made their best efforts about the contents of this book, nevertheless the author and the publisher make no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accept no liability of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any loss or damages of any kind caused or alleged to be caused directly or indirectly from this book. Brand Names Brand names such as Linux, Windows, Python are assumed to be universally known, and are here used in full respect of their respective owners. Planned edition On paper, under traditional copyright Published by [not yet—just appointed] Town & Country Reprographics, Inc. 230 N Main St Concord, NH 03301 (U.S.A.) All rights reserved No part of this book may be reproduced, if not for personal use, in any form or by any means, such as: graphic, electronic, or mechanical, including photocopying, recording, videotaping, or information storage and retrieval systems, without written permission of the publisher.
    [Show full text]
  • Zynq Ultrascale+ Mpsoc TRD User Guide (UG1221)
    Zynq UltraScale+ MPSoC Base Targeted Reference Design User Guide UG1221 (v2016.4) March 22, 2017 Revision History The following table shows the revision history for this document. Date Version Revision 03/22/2017 2016.4 Released with Vivado Design Suite 2016.4 with no changes from previous version. 12/15/2016 2016.3 Updated for Vivado Design Suite 2016.3: Updated Reference Design Overview. Replaced Chapter 2, Reference Design. Updated Figure 3-1 and the following paragraph. Updated Figure 4-1 and perfapm library descriptions in Chapter 4, RPU-1 Software Stack (Bare-metal). Updated Figure 6-1, Figure 6-2, and DDR region descriptions under Memories in Chapter 6. Updated Figure 7-1, Figure 7-4, and Figure 7-5. Added X11 section, deleted first paragraph under EGLFS QPA, and modified “Evdev” section to “Libinput” in Chapter 7, APU Software Platform. Updated Table 8-2 and clock descriptions under Clocks, Resets and Interrupts in Chapter 8. 07/22/2016 2016.2 Updated for Vivado Design Suite 2016.2: Added “GPU” to hardware interfaces and IP under Key Features. Changed link under Design Modules from the wiki site to the HeadStart Lounge and updated link under Tutorials to the Base TRD wiki site. Deleted steps 2 and 4 under Tutorials and added reference tutorial (last bullet). Added second to last sentence to second paragraph under Boot Process. Added “Load PMU FW” component to Figure 6-1. Clarified Message Passing section (text only). Changed “PCA9546” to PCA9548” in Figure 8-7. 06/29/2016 2016.1 Initial Xilinx release. Zynq UltraScale+ MPSoC Base TRD www.xilinx.com Send Feedback 2 UG1221 (v2016.4) March 22, 2017 Table of Contents Revision History .
    [Show full text]
  • Tortoisecvs User's Guide Version 1.8.0
    TortoiseCVS User's Guide Version 1.8.0 Ben Campbell Martin Crawford Hartmut Honisch Francis Irving Torsten Martinsen Ian Dees Copyright © 2001 - 2004 TortoiseCVS Table of Contents 1. Getting Started What is CVS? What is TortoiseCVS? Where to Begin? 2. Basic Usage of TortoiseCVS Sandboxes Checking out a Module Windows Explorer and TortoiseCVS Total Commander and TortoiseCVS Updating your Sandbox Committing your Changes to the Repository Resolving Conflicts Adding Files and Directories to the Repository 3. Advanced Usage of TortoiseCVS Creating a New Repository or Module Watch, Edit and Unedit Tagging and Labeling Reverting to an Older Version of a File Branching And Merging Creating a Branch Selecting a Branch to Work On Merging from a Branch Going Back to the Head Branch Binary and Unicode Detection File Revision History History Dialog Revision Graph Dialog Web Log Making a Patch File 4. Customizing TortoiseCVS Overlay Icons Selecting a Different Set of Overlay Icons Changing how the Overlay Icons Work 5. Command Reference for TortoiseCVS Installing TortoiseCVS Obtaining a Working Copy: CVS Checkout... Getting Other People's Changes: CVS Update CVS Update Special... Making Your Changes Available to Others: CVS Commit... Adding New Files: CVS Add and CVS Add Contents... Discarding Obsolete Files: CVS Remove Finding Out What Has Changed: CVS Diff... Making a Snapshot: CVS Tag... Lines of Development: CVS Branch... CVS Merge... CVS Make New Module Watching And Locking Finding Out Who to Blame: CVS Annotate Showing More Information: CVS Explorer Columns Keyboard Shortcuts How Web Log Autodetects the Server URL 6. Dialog Reference for TortoiseCVS Add Dialog Checkout Dialog Update Special Dialog Commit Dialog Branch Dialog Make New Module Dialog Progress Dialog Tag Dialog Preferences Dialog Merge Dialog History Dialog Revision Graph Dialog About Dialog 7.
    [Show full text]
  • The Pulseaudio Sound Server Linux.Conf.Au 2007
    Introduction What is PulseAudio? Usage Internals Recipes Outlook The PulseAudio Sound Server linux.conf.au 2007 Lennart Poettering [email protected] Universit¨atHamburg, Department Informatik University of Hamburg, Department of Informatics Hamburg, Germany January 17th, 2007 Lennart Poettering The PulseAudio Sound Server 2 What is PulseAudio? 3 Usage 4 Internals 5 Recipes 6 Outlook Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction Lennart Poettering The PulseAudio Sound Server 3 Usage 4 Internals 5 Recipes 6 Outlook Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction 2 What is PulseAudio? Lennart Poettering The PulseAudio Sound Server 4 Internals 5 Recipes 6 Outlook Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction 2 What is PulseAudio? 3 Usage Lennart Poettering The PulseAudio Sound Server 5 Recipes 6 Outlook Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction 2 What is PulseAudio? 3 Usage 4 Internals Lennart Poettering The PulseAudio Sound Server 6 Outlook Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction 2 What is PulseAudio? 3 Usage 4 Internals 5 Recipes Lennart Poettering The PulseAudio Sound Server Introduction What is PulseAudio? Usage Internals Recipes Outlook Contents 1 Introduction 2 What is PulseAudio? 3 Usage 4 Internals 5 Recipes 6 Outlook Lennart Poettering The PulseAudio Sound Server Introduction What is PulseAudio? Usage Internals Recipes Outlook Who Am I? Student (Computer Science) from Hamburg, Germany Core Developer of PulseAudio, Avahi and a few other Free Software projects http://0pointer.de/lennart/ [email protected] IRC: mezcalero Lennart Poettering The PulseAudio Sound Server Introduction What is PulseAudio? Usage Internals Recipes Outlook Introduction Lennart Poettering The PulseAudio Sound Server It’s a mess! There are just too many widely adopted but competing and incompatible sound systems.
    [Show full text]
  • A Brief Overview of the Re-Implementation of the Android Push Event Stream Model
    ANDROID PUSH EVENT MODEL 1 A Brief Overview of the Re-Implementation of the Android Push Event Stream Model Dustin McAfee and Brad Vander Zanden E-mail: [email protected], [email protected] F 1 INTRODUCTION The work described, here, is an ongoing attempt to 2 METHODS re-implement an existing model, the Android Event Push Stream Model (ESM), put forth in a number of papers by The Android input stack is comprised of multiple layers Drs. Marz, Vander Zanden, and Gao at the University of for polling input and demultiplexing it to the user processes Tennessee, Knoxville, [1], [2], [3]. This re-implementation (applications). The polling interface to the Linux kernel that differs from Marz’s original implementation in that it at- the Android operating system uses is epoll (see ”frame- tempts to implement only the event push model in the works/native/services/inputflinger/EventHub.cpp” in the Android kernel while Marz’s implementation implemented Android source code, and ”fs/eventpoll.c” in the Linux the event push model in the Android kernel, moved the kernel source code). The Linux kernel running inside of display system into the kernel, and implemented a GUI Android uses the evdev input event interface (see ”driver- scheduler to better manage different GUI tasks. At this point s/input/evdev.c” in the Linux kernel source code). After an we are only re-implementing the event push model so that input event fires an interrupt in the Linux kernel, evdev is we can examine its ability to reduce the power consumption responsible for directing the input event to the correct input of apps using sensor events.
    [Show full text]