DOCSLIB.ORG

Linux Information Can Be Found Scattered in Man Pages, Texinfo Files

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux Information Can Be Found Scattered in Man Pages, Texinfo Files < Day Day Up > Linux Cookbook By Carla Schroder Publisher: O'Reilly Pub Date: November 2004 ISBN: 0-596-00640-3 Pages: 580 Table of • Contents • Index • Reviews Reader Linux information can be found scattered in man pages, texinfo files, and • Reviews source code comments, but the best source is the experts who have built • Errata up a working knowledge of managing Linux systems. The Linux • Academic Cookbook's tested techniques distill years of hard-won experience into Cooking with practical cut-and-paste solutions to everyday Linux dilemmas. Use just • Linux, Part 2 one recipe from this collection of real-world solutions, and the hours of Cooking with tedious trial-and-error saved will more than pay for the cost of the book. • Linux, Part 1 It's more than a time-saver; it's a sanity saver. < Day Day Up > < Day Day Up > Linux Cookbook By Carla Schroder Publisher: O'Reilly Pub Date: November 2004 ISBN: 0-596-00640-3 Pages: 580 Table of • Contents • Index • Reviews Reader • Reviews • Errata • Academic Cooking with • Linux, Part 2 Cooking with • Linux, Part 1 Copyright Dedication Preface Recipe Audience Recipe What Is Included/Omitted Recipe Platforms Recipe Conventions Recipe Downloads and Feedback Recipe Comments and Questions Recipe Acknowledgments Chapter 1. Finding Documentation Section 1.1. Introduction Recipe 1.2. Understanding man Pages Recipe 1.3. Finding Appropriate man Pages Recipe 1.4. Finding Lost man Pages Recipe 1.5. Reading man Pages Without a man Viewer Recipe 1.6. Configuring Your manpath Recipe 1.7. Using info Pages Recipe 1.8. Printing man Pages Recipe 1.9. Printing info Pages Recipe 1.10. Printing Selected man or info Pages Recipe 1.11. Finding All of the Documentation for a Program Chapter 2. Installing and Managing Software on RPM-Based Systems Section 2.1. Introduction Recipe 2.2. Installing RPMs Recipe 2.3. Upgrading RPMs Recipe 2.4. Removing RPMs Recipe 2.5. Collecting Information on Installed RPMs Recipe 2.6. Collecting Information from RPMs That Are Not Installed Recipe 2.7. Finding Recently Installed RPMs Recipe 2.8. Rebuilding the RPM Database Recipe 2.9. Tracking Source-Built Libraries on an RPM-Based System Recipe 2.10. Fixing RPM Installation Problems Recipe 2.11. Installing Source RPMs Recipe 2.12. Customizing Build Options in a Source RPM Recipe 2.13. Installing Yum Recipe 2.14. Configuring Yum Recipe 2.15. Installing and Upgrading Packages with Yum Recipe 2.16. Removing Packages with Yum Recipe 2.17. Getting Information on Installed Packages with Yum Recipe 2.18. Maintaining Yum Chapter 3. Installing and Managing Software on Debian-Based Systems Section 3.1. Introduction Recipe 3.2. Getting Software for a Debian System Recipe 3.3. Installing Debian Packages from CD-ROM Recipe 3.4. Installing Packages on Debian-Based Systems Recipe 3.5. Removing Packages from a Debian System Recipe 3.6. Installing from Sources on a Debian System Recipe 3.7. Upgrading Packages on Debian Recipe 3.8. Upgrading a Debian System Recipe 3.9. Upgrading to a Newer Debian Release Recipe 3.10. Running a Mixed Debian System Recipe 3.11. Finding Out What Is Installed on a Debian System Recipe 3.12. Maintaining the Debian Package Cache Recipe 3.13. Resolving Debian Dependency Conflicts Recipe 3.14. Building a Local Debian Repository Recipe 3.15. Selecting Package Mirrors for apt-proxy.conf Recipe 3.16. Adding Your Existing Package Cache to apt-proxy.conf Chapter 4. Installing Programs from Source Code Section 4.1. Introduction Recipe 4.2. Preparing Your System for Compiling Programs from Sources Recipe 4.3. Generating a List of Files from a Source Install for Easy Uninstalls Recipe 4.4. Installing Programs from Source Code Recipe 4.5. Using CheckInstall to Create Packages from Sources Chapter 5. Discovering Hardware from Outside the Box Section 5.1. Introduction Recipe 5.2. Detecting Hardware with lspci Recipe 5.3. Using dmesg to Collect Hardware Information Recipe 5.4. Getting Live Hardware Snapshots with /proc Recipe 5.5. Viewing Drive Partitions with fdisk Recipe 5.6. Calculating Hard Drive Capacity Chapter 6. Editing Text Files with JOE and Vim Section 6.1. Introduction Recipe 6.2. Finding JOE Commands Recipe 6.3. Customizing JOE Recipe 6.4. Organizing JOE's Preferences in a Separate File Recipe 6.5. Copying Between Two Files in JOE Recipe 6.6. Searching and Replacing in JOE Recipe 6.7. Selecting Text Vertically in JOE Recipe 6.8. Finding and Opening Files in JOE Recipe 6.9. Learning Vim Quickly Recipe 6.10. Creating Autotext with Vim's Abbreviations Recipe 6.11. Mapping Commands to Keystrokes Recipe 6.12. Customizing Vim Recipe 6.13. Navigating Quickly in Vim with Marks Recipe 6.14. Picking Up Where You Left Off: Using Vim's Sessions Recipe 6.15. Setting Your Default Editor Recipe 6.16. Discovering Vim's Compile-Time Options Chapter 7. Starting and Stopping Linux Section 7.1. Introduction Recipe 7.2. Changing Runlevels After Bootup Recipe 7.3. Changing the Default Runlevel Recipe 7.4. Starting and Stopping X Recipe 7.5. Managing Debian's Runlevels Recipe 7.6. Creating Both Text and Graphical Login Runlevels on Debian Recipe 7.7. Managing Red Hat's Runlevels Recipe 7.8. Manually Configuring Startup Services Recipe 7.9. Manually Starting and Stopping Services Recipe 7.10. Shutting Down or Rebooting Linux Recipe 7.11. Disabling or Limiting Access to Ctrl-Alt-Delete Recipe 7.12. Shutting Down Automatically Chapter 8. Managing Users and Groups Section 8.1. Introduction Recipe 8.2. Sorting Human Users from System Users Recipe 8.3. Finding a User's UID and GID Recipe 8.4. Adding Users with useradd Recipe 8.5. Adding Users with adduser Recipe 8.6. Modifying User Accounts Recipe 8.7. Deleting a User Recipe 8.8. Killing User Processes the Easy, Fun Way Recipe 8.9. Disabling Accounts Recipe 8.10. Managing Passwords Recipe 8.11. Adding Groups with groupadd Recipe 8.12. Deleting Groups with groupdel Recipe 8.13. Creating a System User Recipe 8.14. Creating System Groups with addgroup Recipe 8.15. Adding and Deleting Group Members Recipe 8.16. Checking Password File Integrity Recipe 8.17. Adding New Users in Batches Recipe 8.18. Changing Masses of Passwords Recipe 8.19. Adding Batches of Users to Groups Recipe 8.20. Using su to Be Root Temporarily Recipe 8.21. Granting Limited Rootly Powers with sudo Recipe 8.22. Using Disk Quotas Chapter 9. Managing Files and Partitions Section 9.1. Introduction Recipe 9.2. Setting File and Directory Permissions with chmod's Numeric Notation Recipe 9.3. Doing Batch Operations with chmod Recipe 9.4. Setting File and Directory Permissions with chmod's Symbolic Notation Recipe 9.5. Setting File Ownership with chown Recipe 9.6. Doing Batch Operations with chown Recipe 9.7. Setting Up a Shared Directory with setgid and the Sticky Bit Recipe 9.8. Setting Permissions Defaults with umask Recipe 9.9. Mounting and Unmounting Removable Disks Recipe 9.10. Configuring Filesystem Mounts with /etc/fstab Recipe 9.11. Mounting and Unmounting Filesystems on Hard Drives Recipe 9.12. Finding Device Names for mount and fstab Recipe 9.13. Creating Files and Directories Recipe 9.14. Deleting Files and Directories Recipe 9.15. Copying, Moving, and Renaming Files and Directories Recipe 9.16. Creating Linux Disk Partitions with fdisk Recipe 9.17. Creating a Filesystem on a New Partition Chapter 10. Patching, Customizing, and Upgrading Kernels Section 10.1. Introduction Recipe 10.2. Adding New Features to the 2.4 Kernel Recipe 10.3. Slimming a Stock 2.4 Kernel Recipe 10.4. Upgrading to the Latest Stable Version of the 2.4 Kernel Recipe 10.5. Building the 2.6 Kernel Recipe 10.6. Adding New Features to the 2.6 Kernel Recipe 10.7. Adding a New Loadable Kernel Module Recipe 10.8. Patching a Kernel Recipe 10.9. Removing a Kernel Patch Recipe 10.10. Creating an initrd Image Recipe 10.11. Creating a Boot Disk on Debian Recipe 10.12. Creating a Boot Disk on Red Hat Chapter 11. CD and DVD Recording Section 11.1. Introduction Recipe 11.2. Finding the SCSI Address for CD and DVD Writers Recipe 11.3. Enabling SCSI Emulation for IDE/Atapi CD and DVD Writers Recipe 11.4. Making a Data CD for General Distribution Recipe 11.5. Building File Trees on a Data CD Recipe 11.6. Copying a CD or DVD Recipe 11.7. Erasing a CD-RW Recipe 11.8. Recording a Multisession Data CD Recipe 11.9. Creating a Bootable CD Recipe 11.10. Spanning a Large File over Several CDs Recipe 11.11. Recording Data DVDs Recipe 11.12. Recording an Audio CD for Standard CD Players Chapter 12. Managing the Bootloader and Multi-Booting Section 12.1. Introduction Recipe 12.2. Migrating from LILO to GRUB Recipe 12.3. Installing GRUB Without a Floppy Disk Recipe 12.4. Installing GRUB with grub-install Recipe 12.5. Preparing a System for Multibooting Linux Recipe 12.6. Adding More Linuxes to a Multiboot System Recipe 12.7. Discovering Boot Parameters from the GRUB Command Shell Recipe 12.8. Configuring the Boot Partition Recipe 12.9. Creating the GRUB Boot Menu Recipe 12.10. Customizing menu.lst Recipe 12.11. Adding Windows 95/98/ME to a Linux System Recipe 12.12. Adding Windows NT/2000/XP to a Multiboot System Recipe 12.13. Restoring GRUB to the MBR with a Knoppix CD Recipe 12.14. Protecting System Files with a GRUB Password Recipe 12.15.
Load more

Recommended publications
  • Creating Rpms Guide
    CREATING RPMS (Student version) v1.0 Featuring 36 pages of lecture and a 48 page lab exercise This docu m e n t serves two purpose s: 1. Representative sample to allow evaluation of our courseware manuals 2. Make available high quality RPM documentation to Linux administrators A bout this m aterial : The blue background you see simulates the custom paper that all Guru Labs course w are is printed on. This student version does not contain the instructor notes and teaching tips present in the instructor version. For more information on all the features of our unique layout, see: http://ww w . g urulabs.co m /courseware/course w are_layout.php For more freely available Guru Labs content (and the latest version of this file), see: http://www.gurulabs.co m/goodies/ This sample validated on: Red Hat Enterprise Linux 4 & Fedora Core v3 SUSE Linux Enterprise Server 9 & SUSE Linux Professional 9.2 About Guru Labs: Guru Labs is a Linux training company started in 199 9 by Linux experts to produce the best Linux training and course w are available. For a complete list, visit our website at: http://www.gurulabs.co m/ This work is copyrighted Guru Labs, L.C. 2005 and is licensed under the Creative Common s Attribution- NonCom mer cial- NoDerivs License. To view a copy of this license, visit http://creativecom m o n s.org/licenses/by- nc- nd/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 943 0 5, USA. Guru Labs 801 N 500 W Ste 202 Bountiful, UT 84010 Ph: 801-298-5227 WWW.GURULABS.COM Objectives: • Understand
    [Show full text]
  • Downloads." the Open Information Security Foundation
    Performance Testing Suricata The Effect of Configuration Variables On Offline Suricata Performance A Project Completed for CS 6266 Under Jonathon T. Giffin, Assistant Professor, Georgia Institute of Technology by Winston H Messer Project Advisor: Matt Jonkman, President, Open Information Security Foundation December 2011 Messer ii Abstract The Suricata IDS/IPS engine, a viable alternative to Snort, has a multitude of potential configurations. A simplified automated testing system was devised for the purpose of performance testing Suricata in an offline environment. Of the available configuration variables, seventeen were analyzed independently by testing in fifty-six configurations. Of these, three variables were found to have a statistically significant effect on performance: Detect Engine Profile, Multi Pattern Algorithm, and CPU affinity. Acknowledgements In writing the final report on this endeavor, I would like to start by thanking four people who made this project possible: Matt Jonkman, President, Open Information Security Foundation: For allowing me the opportunity to carry out this project under his supervision. Victor Julien, Lead Programmer, Open Information Security Foundation and Anne-Fleur Koolstra, Documentation Specialist, Open Information Security Foundation: For their willingness to share their wisdom and experience of Suricata via email for the past four months. John M. Weathersby, Jr., Executive Director, Open Source Software Institute: For allowing me the use of Institute equipment for the creation of a suitable testing
    [Show full text]
  • GNU Wget 1.10 the Non-Interactive Download Utility Updated for Wget 1.10, Apr 2005
    GNU Wget 1.10 The non-interactive download utility Updated for Wget 1.10, Apr 2005 by Hrvoje Nikˇsi´cand the developers Copyright c 1996–2005, Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being “GNU General Public License” and “GNU Free Documentation License”, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”. Chapter 1: Overview 1 1 Overview GNU Wget is a free utility for non-interactive download of files from the Web. It supports http, https, and ftp protocols, as well as retrieval through http proxies. This chapter is a partial overview of Wget’s features. • Wget is non-interactive, meaning that it can work in the background, while the user is not logged on. This allows you to start a retrieval and disconnect from the system, letting Wget finish the work. By contrast, most of the Web browsers require constant user’s presence, which can be a great hindrance when transferring a lot of data. • Wget can follow links in html and xhtml pages and create local versions of remote web sites, fully recreating the directory structure of the original site. This is sometimes referred to as “recursive downloading.” While doing that, Wget respects the Robot Exclusion Standard (‘/robots.txt’). Wget can be instructed to convert the links in downloaded html files to the local files for offline viewing.
    [Show full text]
  • Toolchains Instructor: Prabal Dutta Date: October 2, 2012
    EECS 373: Design of Microprocessor-Based Systems Fall 2012 Lecture 3: Toolchains Instructor: Prabal Dutta Date: October 2, 2012 Note: Unless otherwise specified, these notes assume: (i) an ARM Cortex-M3 processor operating in little endian mode; (ii) the ARM EABI application binary interface; and (iii) the GNU GCC toolchain. Toolchains A complete software toolchain includes programs to convert source code into binary machine code, link together separately assembled/compiled code modules, disassemble the binaries, and convert their formats. Binary program file (.bin) Assembly Object Executable files (.s) files (.o) image file objcopy ld (linker) as objdump (assembler) Memory layout Disassembled Linker code (.lst) script (.ld) Figure 0.1: Assembler Toolchain. A typical GNU (GNU's Not Unix) assembler toolchain includes several programs that interact as shown in Figure 0.1 and perform the following functions: • as is the assembler and it converts human-readable assembly language programs into binary machine language code. It typically takes as input .s assembly files and outputs .o object files. • ld is the linker and it is used to combine multiple object files by resolving their external symbol references and relocating their data sections, and outputting a single executable file. It typically takes as input .o object files and .ld linker scripts and outputs .out executable files. • objcopy is a translation utility that copies and converts the contents of an object file from one format (e.g. .out) another (e.g. .bin). • objdump is a disassembler but it can also display various other information about object files. It is often used to disassemble binary files (e.g.
    [Show full text]
  • Université De Montréal Context-Aware
    UNIVERSITE´ DE MONTREAL´ CONTEXT-AWARE SOURCE CODE IDENTIFIER SPLITTING AND EXPANSION FOR SOFTWARE MAINTENANCE LATIFA GUERROUJ DEPARTEMENT´ DE GENIE´ INFORMATIQUE ET GENIE´ LOGICIEL ECOLE´ POLYTECHNIQUE DE MONTREAL´ THESE` PRESENT´ EE´ EN VUE DE L'OBTENTION DU DIPLOME^ DE PHILOSOPHIÆ DOCTOR (GENIE´ INFORMATIQUE) JUILLET 2013 ⃝c Latifa Guerrouj, 2013. UNIVERSITE´ DE MONTREAL´ ECOLE´ POLYTECHNIQUE DE MONTREAL´ Cette th`ese intitul´ee: CONTEXT-AWARE SOURCE CODE IDENTIFIER SPLITTING AND EXPANSION FOR SOFTWARE MAINTENANCE pr´esent´eepar: GUERROUJ Latifa en vue de l'obtention du dipl^ome de: Philosophiæ Doctor a ´et´ed^ument accept´eepar le jury d'examen constitu´ede: Mme BOUCHENEB Hanifa, Doctorat, pr´esidente M. ANTONIOL Giuliano, Ph.D., membre et directeur de recherche M. GUEH´ ENEUC´ Yann-Ga¨el, Ph.D., membre et codirecteur de recherche M. DESMARAIS Michel, Ph.D., membre Mme LAWRIE Dawn, Ph.D., membre iii This dissertation is dedicated to my parents. For their endless love, support and encouragement. iv ACKNOWLEDGMENTS I am very grateful to both Giulio and Yann for their support, encouragement, and intel- lectual input. I worked with you for four years or even less, but what I learned from you will last forever. Giulio, your passion about research was a source of inspiration and motivation for me. Also, your mentoring and support have been instrumental in achieving my goals. Yann, your enthusiasm and guidance have always been a strength for me to keep moving forward. Research would not be as much fun without students and researchers to collaborate with. It has been a real pleasure and great privilege working with Massimiliano Di Penta (University of Sannio), Denys Poshyvanyk (College of William and Mary), and their teams.
    [Show full text]
  • Name Synopsis Description Options
    GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) NAME gpgtar −Encrypt or sign files into an archive SYNOPSIS gpgtar [options] filename1 [ filename2, ... ] directory1 [ directory2, ... ] DESCRIPTION gpgtar encrypts or signs files into an archive.Itisangpg-ized tar using the same format as used by PGP’s PGP Zip. OPTIONS gpgtar understands these options: --create Put givenfiles and directories into a vanilla ‘‘ustar’’archive. --extract Extract all files from a vanilla ‘‘ustar’’archive. --encrypt -e Encrypt givenfiles and directories into an archive.This option may be combined with option --symmetric for an archive that may be decrypted via a secret key orapassphrase. --decrypt -d Extract all files from an encrypted archive. --sign -s Makeasigned archive from the givenfiles and directories. This can be combined with option --encrypt to create a signed and then encrypted archive. --list-archive -t List the contents of the specified archive. --symmetric -c Encrypt with a symmetric cipher using a passphrase. The default symmetric cipher used is AES-128, but may be chosen with the --cipher-algo option to gpg. --recipient user -r user Encrypt for user id user.For details see gpg. --local-user user -u user Use user as the key tosign with. Fordetails see gpg. --output file -o file Write the archive tothe specified file file. --verbose -v Enable extra informational output. GnuPG 2.2.12 2018-12-11 1 GPGTAR(1) GNU Privacy Guard 2.2 GPGTAR(1) --quiet -q Trytobeasquiet as possible. --skip-crypto Skip all crypto operations and create or extract vanilla ‘‘ustar’’archives. --dry-run Do not actually output the extracted files.
    [Show full text]
  • With Yocto/Openembedded
    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
    [Show full text]
  • Redesigning Src2pkg, a Linux Package Creation Toolkit
    Redesigning src2pkg, a Linux package creation toolkit Timothy Goya December 4, 2009 Senior Project COMPUTER SCIENCE DEPARTMENT California Polytechnic State University San Luis Obispo 2009 1 Contents 1 Introduction 3 2 Background 4 2.1 GNU Coding Standards . 4 2.2 CheckInstall . 4 2.3 src2pkg 1.x . 4 3 Description 5 3.1 Flexibility and coupling . 5 3.2 A simple example script . 5 3.3 Other interesting functions . 6 3.4 Modules . 6 3.4.1 Build systems . 6 3.4.2 Sandboxing methods . 7 3.4.3 Package formats . 7 4 Evaluation 7 5 Really Cool Bash Features 8 5.1 /dev/tcp . 8 5.2 Manipulating Binary . 9 5.3 Localization . 9 6 Conclusions 9 2 Acknowledgments Many thanks to Dr. Phillip Nico for his saintly patience and understanding during his time as my senior project advisor. Special thanks to Gilbert Ashley, the author of src2pkg, for his approval and support throughout this redesign. Thanks to Piete Sartain for adminstrating the src2pkg wiki and Drew Ames for the writing much of the great documentation on the src2pkg wiki. I would also like to thank Dr. Alexander Dekhtyar for acting as my advisor for my rst senior project idea. Abstract Package managers ease installation and removal of applications. How- ever, as the name indicates, in order for a package manager to be useful, they need packages created from upstream sources to manage. This is the purpose of src2pkg, a toolkit written in Bash shell script which automates many package creation tasks. src2pkg, however, suers from major de- sign aws that cripple its ability to package some exotic upstream sources.
    [Show full text]
  • Replacing PGP 2.X with Gnupg
    Replacing PGP 2.x with GnuPG This article is based on an earlier PGP 2.x/GnuPG compatability guide (http://www.toehold.com/~kyle/pgp- compat.html) written by Kyle Hasselbacher (<[email protected]>). Mike Ashley (<[email protected]>) edited and expanded it. Michael Fischer v. Mollard (<[email protected]>) transformed the HTML source to Doc- Book SGML and also expanded it further. Some of the details described here came from the gnupg-devel and gnupg-user mailing lists. The workaround for both signing with and encrypting to an RSA key were taken from Gero Treuner’s compatability script (http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/changes.html). Please direct questions, bug reports, or suggesstions to the maintainer, Mike Ashley. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Introduction This document describes how to communicate with people still using old versions of PGP 2.x GnuPG can be used as a nearly complete replacement for PGP 2.x. You may encrypt and decrypt PGP 2.x messages using imported old keys, but you cannot generate PGP 2.x keys. This document demonstrates how to extend the standard distribution of GnuPG to support PGP 2.x keys as well as what options must be used to ensure inter- operation with PGP 2.x users.
    [Show full text]
  • Latexsample-Thesis
    INTEGRAL ESTIMATION IN QUANTUM PHYSICS by Jane Doe A dissertation submitted to the faculty of The University of Utah in partial fulfillment of the requirements for the degree of Doctor of Philosophy Department of Mathematics The University of Utah May 2016 Copyright c Jane Doe 2016 All Rights Reserved The University of Utah Graduate School STATEMENT OF DISSERTATION APPROVAL The dissertation of Jane Doe has been approved by the following supervisory committee members: Cornelius L´anczos , Chair(s) 17 Feb 2016 Date Approved Hans Bethe , Member 17 Feb 2016 Date Approved Niels Bohr , Member 17 Feb 2016 Date Approved Max Born , Member 17 Feb 2016 Date Approved Paul A. M. Dirac , Member 17 Feb 2016 Date Approved by Petrus Marcus Aurelius Featherstone-Hough , Chair/Dean of the Department/College/School of Mathematics and by Alice B. Toklas , Dean of The Graduate School. ABSTRACT Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah. Blah blah blah blah blah blah blah blah blah blah blah blah blah blah blah.
    [Show full text]
  • Getting Started with RTEMS Edition 4.7.2, for 4.7.2
    Getting Started with RTEMS Edition 4.7.2, for 4.7.2 14 February 2008 On-Line Applications Research Corporation On-Line Applications Research Corporation TEXinfo 2006-10-04.17 COPYRIGHT c 1988 - 2006. On-Line Applications Research Corporation (OAR). The authors have used their best efforts in preparing this material. These efforts include the development, research, and testing of the theories and programs to determine their effectiveness. No warranty of any kind, expressed or implied, with regard to the software or the material contained in this document is provided. No liability arising out of the application or use of any product described in this document is assumed. The authors reserve the right to revise this material and to make changes from time to time in the content hereof without obligation to notify anyone of such revision or changes. The RTEMS Project is hosted at http://www.rtems.com. Any inquiries concerning RTEMS, its related support components, its documentation, or any custom services for RTEMS should be directed to the contacts listed on that site. A current list of RTEMS Support Providers is at http://www.rtems.com/support.html. i Table of Contents 1 Introduction..................................... 1 1.1 Real-Time Embedded Systems.................................. 1 1.2 Cross Development ............................................. 2 1.3 Resources on the Internet ...................................... 3 1.3.1 Online Tool Documentation ............................... 3 1.3.2 RTEMS Mailing List ...................................... 3 1.3.3 CrossGCC Mailing List.................................... 3 1.3.4 GCC Mailing Lists ........................................ 3 2 Requirements ................................... 5 2.1 Disk Space ..................................................... 5 2.2 General Host Software Requirements ........................... 5 2.2.1 GCC .....................................................
    [Show full text]
  • Checkinstall
    LinuxFocus article number 360 http://linuxfocus.org CheckInstall by Mario M. Knopf (homepage) About the author: Mario enjoys working with Linux, networks Abstract: and security related topics. Checkinstall is utility to automatically build RPM/Debian or Slackware packages from tar.gz source pages. This makes it possible to do a "clean" installation and de−installation of almost any source code tar.gz package. Translated to English _________________ _________________ _________________ by: Mario M. Knopf (homepage) Introduction It often happens that the program which one certainly would like to test, is only available as tar.gz source code (no rpm or Debian package available). In such a case, you download the source package, unpack it and compile it manually. So far, so good. However, what happens if you like to delete the program? The Makefile contains only in very few cases an appropriate routine to uninstall the program. Of course there is the possibility of installing the program into a temporary directory and write down all of the files which were created or modified by the installation for a later removing. But this procedure is painful and very extensive, if programs are frequently compiled from the sources. The tool CheckInstall [1] written by Felipe Eduardo Sánchez Díaz Durán solves this problem. As a rule, you compile and install a GNU Autoconf compliant program under use of the widely known command sequence ./configure && make && make install. The configure shell script attempts to guess correct values for various system−dependent variables, which are used later during the compilation. It checks whether all requirements for compilation are fulfilled and uses those values to create a Makefile in each directory of the package.
    [Show full text]