DOCSLIB.ORG

Introduction to the Command Line the Fat-Free Guide to Unix and Linux Commands Second Edition

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Introduction to the Command Line The Fat-Free Guide to Unix and Linux Commands Second Edition Introduction to the Command Line The Fat-Free Guide to Unix and Linux Commands Second Edition Copyright © 2010 Nicholas Marsh All rights reserved. ISBN: 1450588301 EAN-13: 9781450588300 www.DontFearTheCommandLine.com AIX® is a registered trademark of IBM Corp. BSD® is a registered trademark of the University of California, Berkeley CentOS is property of CentOS Ltd. Debian® is a registered trademark of Software in the Public Interest, Inc Fedora® is a registered trademark of Red Hat, Inc. FreeBSD® is a registered trademark of The FreeBSD Foundation Gentoo® is a registered trademark of The Gentoo Foundation HP-UX® and Tru-64® are registered trademarks of Hewlett-Packard Company IRIX® is a registered trademark of Silicon Graphics, Inc. Linux® is the registered trademark of Linus Torvalds. Mac OS X® is a registered trademark of Apple, Inc. Windows® is a registered trademark of Microsoft Corporation NetBSD® is a registered trademark of The NetBSD Foundation OpenBSD® is a registered trademark of Theo DeRaadt Red Hat® is a registered trademark of Red Hat, Inc. Solaris® and OpenSolaris are registered trademarks of Sun Microsystems SUSE® is a trademark of Novell, Inc. Ubuntu® is a registered trademark of Canonical Ltd. UNIX® is a registered trademark of The Open Group UnixWare® and OpenServer® are registered trademarks of The SCO Group All other trademarks used in this book are the property of their respective owners. Use of any trademark in this book does not constitute an affiliation with or endorsement from the trademark holder. All information in this book is presented on an "as-is" basis. No warranty or guarantee is provided and the author and/or publisher shall not be held liable for any loss or damage. Contents at a Glance Introduction .................................................................................. 6 Section 1: Overview of Unix, Linux and BSD Architecture ............. 10 Section 2: Command Line Basics .................................................. 18 Section 3: Advanced Shell Features and Commands .................... 38 Section 4: Text Editing and Extraction .......................................... 60 Section 5: Users, Groups, and Security ......................................... 81 Section 6: Process Control and Scheduling .................................. 106 Section 7: Startup and Shutdown .............................................. 122 Section 8: Network Commands ................................................. 139 Section 9: Hardware Management Commands .......................... 167 Section 10: File Systems ............................................................ 177 Section 11: Backup and Restore Commands .............................. 192 Section 12: Monitoring and Troubleshooting ............................. 200 Section 13: Printing Commands ................................................. 224 Section 14: Software Installation ............................................... 231 Section 15: System Administration Utilities ................................ 245 Appendix A: Bash Shortcut Keys ................................................ 248 "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." – Dennis Ritchie Creator of the C programming language and co-creator of UNIX Introduction The command line can be an intimidating and unforgiving environment. Unlike working in graphical environments, it's not entirely clear what commands one must execute in a terminal to accomplish a given task. Couple this with the fact that the command line does not prevent you from doing things that might cause irreparable damage to your system, and it becomes clear why many people never take the time to learn how to use it. Despite the hidden dangers and uncertainty faced by new users (known jokingly as "newbies" in the technology industry), you shouldn't fear the command line. Armed with the information in this book you will acquire the skills necessary to become more proficient in the command line environment. You will discover that most Unix, Linux, and BSD systems share the same core architecture, with only a few subtle differences. After learning the basic architecture and commands of Unix, Linux, and BSD systems you will easily be able to transition between the different platforms. To aid the learning process, I recommend downloading one or more of the free operating systems listed below to practice the commands in this guide. Operating System Type Website Ubuntu Linux www.ubuntu.com Fedora Linux www.fedoraproject.org CentOS Linux www.centos.org openSUSE Linux www.opensuse.org OpenSolaris Unix www.opensolaris.org FreeBSD BSD www.freebsd.org It's a worthwhile experience to experiment with multiple Unix, Linux, and BSD distributions to get a broader knowledge of the various platforms. This will help expand your knowledge of the various Unix-like operating systems and give you the skills necessary to work in any command line environment. Linux is the recommended starting point for beginners. It has support for all the latest hardware and provides a user-friendly installation process. The OpenSolaris Unix platform is also a good starting point, as it is one of the most newbie-friendly Unix-based systems. BSD installation is a bit more challenging and requires advanced technical knowledge or previous experience with Unix and Linux systems. I highly recommend Ubuntu Server Edition. It provides an easy install experience and an excellent command line learning environment. Visit Tip www.ubuntu.com for more information about the Ubuntu Server Linux distribution. If you are a Microsoft Windows user, you may already have some command line experience. If you have ever opened a DOS prompt and executed a command such as ping, nslookup, or ipconfig then you know these can be immensely helpful. Unix, Linux, and BSD systems offer similar commands. For example, the ping and nslookup commands work the same on Unix/Linux as they do in DOS. You should note, however, that the DOS ipconfig command's counterpart in the Unix/Linux/BSD world is ifconfig. If you're not a DOS veteran, don't worry - we will cover all of these topics throughout this guide. Are you running Mac OS X? If so, then you are already running a Unix-based operating system. Behind the shiny graphical user interface of Mac OS X is a solid Unix core. To access the command line in Mac OS X simply launch the Terminal application (located in Applications > Utilities > Terminal). From there you will have access to all the standard Unix command line utilities discussed in this guide. Brief History of Unix, Linux, and BSD Unix was created in 1969 at Bell Laboratories which was, at the time, a research and development division of AT&T. Since that time, Unix has branched into many different commercial and open source implementations, most of which are based on the original AT&T standard. Modern Unix-based systems are typically classified into one of the following groups: Unix Commercial implementations derived from the original AT&T code base BSD Open source operating system derived from the original Unix code base Linux Open source Unix compatible clone written from scratch In the 1970s, researchers at the University of California, Berkeley began developing BSD (short for Berkeley Software Distribution). BSD was originally based on the AT&T Unix codebase, but has been rewritten over time to remove AT&T copyrighted code from the system. This allows BSD to be distributed with minimal restrictions. Since that time, the BSD code-base has split to form a number of popular operating systems including FreeBSD, OpenBSD, and NetBSD. BSD code can also be found in proprietary proprietary operating systems created by Microsoft, Apple, and Sun Microsystems. Commercial Unix systems began to appear in the early 1980s. These systems combined various amounts of Unix and BSD code along with vendor-specific enhancements to create new platforms such as AIX, HP-UX, and Sun Solaris. Today, commercial Unix systems can be found in data centers at many large companies running mission critical applications. In 1991, a computer science student at the University of Helsinki in Finland named Linus Torvalds created the Linux operating system. While Linux shares much of the core concepts of Unix, it contains no Unix code. This means it can be freely distributed in the same manner as BSD (although under a different license). The first commercial Linux distributions hit the market in the mid 1990s. Since then hundreds of Linux variants have been developed. The open nature of the Linux operating system has contributed to its success and helped make it one of the most popular server operating systems in use today. The Unix platform has been around since long before graphical user interfaces were invented. The fact that Unix-based systems are still a commanding force in modern computing is a testament to the industrial design of the platform. With Unix, Linux, and BSD popularity at an all time high, now is the perfect time to explore these platforms and join the movement. Conventions Used in This Book /path/to/file File and directory paths are displayed in a fixed width font command Commands are displayed in a bold fixed width font [FILE], [DIRECTORY], [ETC] Items enclosed in brackets represent a variable parameter to be specified by the user (such as a file or directory) $ ping 192.168.1.1 Examples using the $ shell prompt are executed with a non-privileged
Recommended publications
  • A Postgresql Development Environment

    A Postgresql Development Environment

    A PostgreSQL development environment Peter Eisentraut [email protected] @petereisentraut The plan tooling building testing developing documenting maintaining Tooling: Git commands Useful commands: git add (-N, -p) git ls-files git am git format-patch git apply git grep (-i, -w, -W) git bisect git log (-S, --grep) git blame -w git merge git branch (--contains, -d, -D, --list, git pull -m, -r) git push (-n, -f, -u) git checkout (file, branch, -b) git rebase git cherry-pick git reset (--hard) git clean (-f, -d, -x, -n) git show git commit (--amend, --reset, -- git status fixup, -a) git stash git diff git tag Tooling: Git configuration [diff] colorMoved = true colorMovedWS = allow-indentation-change [log] date = local [merge] conflictStyle = diff3 [rebase] autosquash = true [stash] showPatch = true [tag] sort = version:refname [versionsort] suffix = "_BETA" suffix = "_RC" Tooling: Git aliases [alias] check-whitespace = \ !git diff-tree --check $(git hash-object -t tree /dev/null) HEAD ${1:-$GIT_PREFIX} find = !git ls-files "*/$1" gtags = !git ls-files | gtags -f - st = status tags = tag -l wdiff = diff --color-words=[[:alnum:]]+ wshow = show --color-words Tooling: Git shell integration zsh vcs_info Tooling: Editor Custom settings for PostgreSQL sources exist. Advanced options: whitespace checking automatic spell checking (flyspell) automatic building (flycheck, flymake) symbol lookup ("tags") Tooling: Shell settings https://superuser.com/questions/521657/zsh-automatically-set-environment-variables-for-a-directory zstyle ':chpwd:profiles:/*/*/devel/postgresql(|/|/*)' profile postgresql chpwd_profile_postgresql() { chpwd_profile_default export EMAIL="[email protected]" alias nano='nano -T4' LESS="$LESS -x4" } Tooling — Summary Your four friends: vcs editor shell terminal Building: How to run configure ./configure -C/--config-cache --prefix=$(cd .

  • Administering Unidata on UNIX Platforms

    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
  • Embedding Redhat Linux in a Diskonchip - HOWTO

    Embedding Redhat Linux in a Diskonchip - HOWTO

    Embedding Redhat Linux in a DiskOnChip - HOWTO Don Davies, Prosig Ltd ( [email protected]) October 2002 Describes the configuration and setup of a development environment for a Single Board Computer running Redhat Linux from a DiskOnChip device. Contents 1.0 Introduction ..........................................................................................................3 1.1 Hardware Details..................................................................................................3 1.2 System Configuration ...........................................................................................4 2.0 DOS Development Environment...........................................................................5 2.1 DiskOnChip Tools ................................................................................................5 2.2 Boot Loader..........................................................................................................6 2.3 MS-DOS System Startup......................................................................................6 3.0 Linux Development Environment ......................................................................7 3.1 Custom Kernel Configuration ............................................................................8 3.2 Building Custom Kernel ..................................................................................10 3.3 Booting Custom Kernel ...................................................................................10 3.4 Formatting DiskOnChip for Linux
  • MLNX OFED Documentation Rev 5.0-2.1.8.0

    MLNX OFED Documentation Rev 5.0-2.1.8.0

    MLNX_OFED Documentation Rev 5.0-2.1.8.0 Exported on May/21/2020 06:13 AM https://docs.mellanox.com/x/JLV-AQ Notice This document is provided for information purposes only and shall not be regarded as a warranty of a certain functionality, condition, or quality of a product. NVIDIA Corporation (“NVIDIA”) makes no representations or warranties, expressed or implied, as to the accuracy or completeness of the information contained in this document and assumes no responsibility for any errors contained herein. NVIDIA shall have no liability for the consequences or use of such information or for any infringement of patents or other rights of third parties that may result from its use. This document is not a commitment to develop, release, or deliver any Material (defined below), code, or functionality. NVIDIA reserves the right to make corrections, modifications, enhancements, improvements, and any other changes to this document, at any time without notice. Customer should obtain the latest relevant information before placing orders and should verify that such information is current and complete. NVIDIA products are sold subject to the NVIDIA standard terms and conditions of sale supplied at the time of order acknowledgement, unless otherwise agreed in an individual sales agreement signed by authorized representatives of NVIDIA and customer (“Terms of Sale”). NVIDIA hereby expressly objects to applying any customer general terms and conditions with regards to the purchase of the NVIDIA product referenced in this document. No contractual obligations are formed either directly or indirectly by this document. NVIDIA products are not designed, authorized, or warranted to be suitable for use in medical, military, aircraft, space, or life support equipment, nor in applications where failure or malfunction of the NVIDIA product can reasonably be expected to result in personal injury, death, or property or environmental damage.
  • Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle Database Licensing Information, 11G Release 2 (11.2) E10594-26

    Oracle® Database Licensing Information 11g Release 2 (11.2) E10594-26 July 2012 Oracle Database Licensing Information, 11g Release 2 (11.2) E10594-26 Copyright © 2004, 2012, Oracle and/or its affiliates. All rights reserved. Contributor: Manmeet Ahluwalia, Penny Avril, Charlie Berger, Michelle Bird, Carolyn Bruse, Rich Buchheim, Sandra Cheevers, Leo Cloutier, Bud Endress, Prabhaker Gongloor, Kevin Jernigan, Anil Khilani, Mughees Minhas, Trish McGonigle, Dennis MacNeil, Paul Narth, Anu Natarajan, Paul Needham, Martin Pena, Jill Robinson, Mark Townsend This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
  • Editores, Compilación Y Ejecución)

    Editores, Compilación Y Ejecución)

    Guía práctica de estudio 06: Entorno de C (editores, compilación y ejecución) Elaborado por: Ing. Laura Sandoval Montaño Juan Francisco De reza Trujillo Guía práctica de estudio 06: Entorno de C (editores, compilación y ejecución) Objetivo: Conocer y usar los ambientes y herramientas para el desarrollo y ejecución de programas en Lenguaje C, como editores y compiladores en diversos sistemas operativos. Actividades: . Utilizando un editor de GNU/Linux, crear un archivo de texto . Modificar/actualizar un archivo ya existente con un editor GNU/Linux. Crear, compilar y ejecutar un programa simple escrito en C en GNU/Linux . En algún entorno de desarrollo de Windows, crear, compilar y ejecutar un programa simple escrito en C. Introducción Un lenguaje de programación permite expresar una serie de instrucciones que podrán ser realizadas por una computadora. Unos de los lenguajes de programación mayormente difundidos es el lenguaje C. Éste es muy utilizado ya que la forma de dar instrucciones es muy cercana a lo que un humano podría abstraer, es decir, las instrucciones no son tal cual las que una computadora podría entender, para ello se necesitaría conocer a fondo el microprocesador, el sistema operativo entre otros aspectos. Por esta razón, C es conocido como un lenguaje de alto nivel, esto significa a que las instrucciones podrían ser entendidas fácilmente por un humano. En contraparte, un lenguaje de bajo nivel, son instrucciones que son cercanas a lo que la máquina puede entender y difícilmente pueden ser comprendidas por una persona que no tenga conocimientos de la máquina en que operarán. Algunos autores consideran al lenguaje C como un lenguaje de mediano nivel, ya que no es totalmente transparente sino tiene elementos que tienen que ver con la arquitectura de la máquina a la hora de programar.
  • Oracle® Linux 7 Monitoring and Tuning the System

    Oracle® Linux 7 Monitoring and Tuning the System

    Oracle® Linux 7 Monitoring and Tuning the System F32306-03 October 2020 Oracle Legal Notices Copyright © 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
  • Lecture 7 Network Management and Debugging

    Lecture 7 Network Management and Debugging

    SYSTEM ADMINISTRATION MTAT.08.021 LECTURE 7 NETWORK MANAGEMENT AND DEBUGGING Prepared By: Amnir Hadachi and Artjom Lind University of Tartu, Institute of Computer Science [email protected] / [email protected] 1 LECTURE 7: NETWORK MGT AND DEBUGGING OUTLINE 1.Intro 2.Network Troubleshooting 3.Ping 4.SmokePing 5.Trace route 6.Network statistics 7.Inspection of live interface activity 8.Packet sniffers 9.Network management protocols 10.Network mapper 2 1. INTRO 3 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO QUOTE: Networks has tendency to increase the number of interdependencies among machine; therefore, they tend to magnify problems. • Network management tasks: ✴ Fault detection for networks, gateways, and critical servers ✴ Schemes for notifying an administrator of problems ✴ General network monitoring, to balance load and plan expansion ✴ Documentation and visualization of the network ✴ Administration of network devices from a central site 4 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO Network Size 160 120 80 40 Management Procedures 0 AUTOMATION ILLUSTRATION OF NETWORK GROWTH VS MGT PROCEDURES AUTOMATION 5 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO • Network: • Subnets + Routers / switches Time to consider • Automating mgt tasks: • shell scripting source: http://www.eventhelix.com/RealtimeMantra/Networking/ip_routing.htm#.VvjkA2MQhIY • network mgt station 6 2. NETWORK TROUBLES HOOTING 7 LECTURE 7: NETWORK MGT AND DEBUGGING NETWORK TROUBLESHOOTING • Many tools are available for debugging • Debugging: • Low-level (e.g. TCP/IP layer) • high-level (e.g. DNS, NFS, and HTTP) • This section progress: ping trace route GENERAL ESSENTIAL TROUBLESHOOTING netstat TOOLS STRATEGY nmap tcpdump … 8 LECTURE 7: NETWORK MGT AND DEBUGGING NETWORK TROUBLESHOOTING • Before action, principle to consider: ✴ Make one change at a time ✴ Document the situation as it was before you got involved.
  • A Brief History of UNIX File Systems

    A Brief History of UNIX File Systems

    A Brief History of UNIX File Systems Val Henson IBM, Inc. [email protected] Summary • Review of UNIX file system concepts • File system formats, 1974-2004 • File system comparisons and recommendations • Fun trivia • Questions and answers (corrections ONLY during talk) 1 VFS/vnode architecture • VFS: Virtual File System: common object-oriented interface to fs's • vnode: virtual node: abstract file object, includes vnode ops • All operations to fs's and files done through VFS/vnode in- terface • S.R. Kleiman, \Vnodes: An Architecture for Multiple File System Types in Sun UNIX," Summer USENIX 1986 2 Some Definitions superblock: fs summary, pointers to other information inode: on-disk structure containing information about a file indirect block: block containing pointers to other blocks metadata: everything that is not user data, including directory entries 3 Disk characteristics • Track - contiguous region, can be read at maximum speed • Seek time - time to move the head between different tracks • Rotational delay - time for part of track to move under head • Fixed per I/O overhead means bigger I/Os are better 4 In the beginning: System V FS (S5FS) (c. 1974) • First UNIX file system, referred to as \FS" • Disk layout: superblock, inodes, followed by everything else • 512-1024 byte block size, no fragments • Super simple - and super slow! 2-5% of raw disk bandwidth 5 Berkeley Fast File System (FFS or UFS) (c. 1984) • Metadata spread throughout the disk in \cylinder groups" • Block size 4KB minimum, frag size 1KB (to avoid 45% wasted space) • Physical
  • Plw Sc/Nt/Ntr/Ls

    Plw Sc/Nt/Ntr/Ls

    K Service Source PLW SC/NT/NTR/LS Personal LaserWriter SC, Personal LaserWriter NT, Personal LaserWriter NTR, Personal LaserWriter LS, Personal LaserWriter LS/L K Service Source Basics PLW SC/NT/NTR/LS Basics Product Information - 1 Product Information The printers covered in this manual are • Personal LaserWriter SC • Personal LaserWriter NT • Personal LaserWriter NTR • Personal LaserWriter LS • Personal LaserWriter LS/L Compatibility Not all parts are compatible among the five models. Refer to Illustrated Parts for compatibility cross references. The cassette feeder tray and its associated parts are optional on the LS, LS/L, and NTR models. Basics Paper Paths - 2 Paper Paths There are four paper paths in the Personal LaserWriter. Paper is fed from the cassette or multipurpose tray and delivered to the face-down or face-up delivery trays. Note: Face signifies image side. Default delivery is face- down at the top of the printer. Basics LS–LS/L Identification - 3 LS–LS/L Identification I/O Board Bracket The LS/L is a cost-reduced version of the LS but is sold and packaged under the same LS name. Parts are not necessarily interchangeable between the two models. Power Switch External distinguishing characteristics: • LS: The power switch is on the left rear of printer; the rear cover has an opening for an I/O board bracket and Personal LaserWriter LS displays the family number M2000. • LS/L: The power switch is on the right rear of printer; Solid Rear Cover the rear cover is solid plastic and displays the family number M2002. Power Switch Personal LaserWriter LS/L Basics Sensing System Theory - 4 Sensing System Theory There are six sensors in the PS11 Personal LaserWriter: four PS12 paper sensors and two printer-open sensors.
  • Geek Guide > Beyond Cron

    Geek Guide > Beyond Cron

    GEEK GUIDE BEYOND CRON Table of Contents Ease of Use ..................................................................... 8 Multi-Server-Friendly .................................................... 10 Dependency Management ............................................ 13 Easy to Visualize ........................................................... 16 Delegation of Authority ................................................. 18 Management by Exception ........................................... 21 Flexible Scheduling ....................................................... 23 Revision Control ........................................................... 24 Conclusion .................................................................... 24 MIKE DIEHL has been using Linux since the days when Slackware came on 14 5.25” floppy disks and installed kernel version 0.83. He has built and managed several servers configured with either hardware or software RAID storage under Linux, and he has hands-on experience with both the VMware and KVM virtual machine architectures. Mike has written numerous articles for Linux Journal on a broad range of subjects, and he has a Bachelor’s degree in Mathematics with a minor in Computer Science. He lives in Blythewood, South Carolina, with his wife and four sons. 2 GEEK GUIDE BEYOND CRON GEEK GUIDES: Mission-critical information for the most technical people on the planet. Copyright Statement © 2015 Linux Journal. All rights reserved. This site/publication contains materials that have been created, developed or
  • Beyond Compare User Guide

    Beyond Compare User Guide

    Copyright © 2012 Scooter Software, Inc. Beyond Compare Copyright © 2012 Scooter Software, Inc. All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Published: July 2012 Contents 3 Table of Contents Part 1 Welcome 7 1 What's. .N..e..w............................................................................................................................. 8 2 Standa..r.d.. .v..s. .P..r..o..................................................................................................................... 9 Part 2 Using Beyond Compare 11 1 Home. .V...i.e..w..........................................................................................................................