Linux Pocket Guide - Lagout
LinuxPocket GuideDaniel J. BarrettBeijing Cambridge Farnham Köln Paris Sebastopol Taipei Tokyo
Linux Pocket Guideby Daniel J. BarrettCopyright 2004 O’Reilly Media, Inc. All rights reserved.Printed in the United States of America.Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North,Sebastopol, CA 95472.O’Reilly Media, Inc. books may be purchased for educational, business, orsales promotional use. Online editions are also available for most titles(safari.oreilly.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or corporate@oreilly.com.Editor:Production Editor:Cover Designer:Interior Designer:Mike LoukidesColleen GormanEmma ColbyDavid FutatoPrinting History:February 2004:First Edition.Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo areregistered trademarks of O’Reilly Media, Inc. The Pocket Guide seriesdesignations, Linux Pocket Guide, the image of a roper, and related tradedress are trademarks of O’Reilly Media, Inc.Many of the designations used by manufacturers and sellers to distinguishtheir products are claimed as trademarks. Where those designations appearin this book, and O’Reilly Media, Inc. was aware of a trademark claim, thedesignations have been printed in caps or initial caps.While every precaution has been taken in the preparation of this book, thepublisher and author assume no responsibility for errors or omissions, or fordamages resulting from the use of the information contained herein.0-596-00628-4[C][4/06]
ContentsWhat’s in This Book?What’s Linux?What’s Fedora Linux?What’s a Command?Users and SuperusersReading This Book122345Getting Help7Fedora: A First ViewThe Role of the ShellHow to Run a Shell91011Logins, Logouts, and Shutdowns11The FilesystemHome DirectoriesSystem DirectoriesOperating System DirectoriesFile Protections1314151819The ShellThe Shell Versus ProgramsSelected bash FeaturesJob Control20212129v
Killing a Command in ProgressTerminating a ShellTailoring Shell Behavior323333Installing Software33Basic File Operations37Directory Operations41File Viewing43File Creation and Editing51File Properties56File Location65File Text Manipulation71File Compression and Packaging82File Comparison86Disks and Filesystems91Backups and Remote Storage95File Printing101Spelling Operations102Viewing Processes104Controlling Processes108Users and Their Environment110Working with User Accounts115vi Contents
Becoming the Superuser118Working with Groups119Basic Host Information121Host Location124Network Connections128Email132Web Browsing136Usenet News140Instant Messaging142Screen Output144Math and Calculations149Dates and Times152Scheduling Jobs155Graphics and Screensavers160Audio and Video163Programming with Shell ScriptsWhitespace and LinebreaksVariablesInput and OutputBooleans and Return CodesConditionalsLoopsBreak and Continue166166166167167170172174Contents vii
Creating and Running Shell ScriptsCommand-Line ArgumentsExiting with a Return CodeBeyond Shell ScriptingFinal WordsAcknowledgmentsviii Contents176177178178179179
Linux Pocket GuideWelcome to Linux! If you’re a new user, this book can serveas a quick introduction to Linux in general, and FedoraLinux specifically, as well as a guide to common and practical commands. If you have Linux experience, feel free to skipthe introductory material.What’s in This Book?This book is a short guide, not a comprehensive reference. Wecover important, useful aspects of Linux so you can workproductively. We do not, however, present every single command and every last option (our apologies if your favoritewas omitted), nor delve into detail about operating systeminternals. Short, sweet, and essential, that’s our motto.We focus on commands, those pesky little words you type ona command line to tell a Linux system what to do, like ls(list files), grep (search for text in a file), xmms (play audiofiles), and df (measure free disk space). We touch briefly ongraphical windowing environments like GNOME and KDE,each of which could fill a Pocket Guide by itself.We’ve organized the material by function to provide a concise learning path. For example, to help you view the contents of a file, we introduce all file-viewing commandstogether: cat for short text files, less for longer ones, od forbinary files, ghostview for Postscript, and so on. Then weexplain each of these commands in turn, briefly presentingits common uses and options.1
We assume you have an account on a Linux system andknow how to log in with your username and password. Ifnot, speak with your system administrator, or if the system isyour own, use the account created when you installed Linux.What’s Linux?Linux is a popular, open-source computer software environment that competes with Microsoft Windows and the AppleMacintosh. It has four major parts:The kernelThe low-level operating system, handling files, disks, networking, and other necessities we take for granted.Supplied programsThousands of programs for file manipulation, text editing, mathematics, typesetting, audio, video, computerprogramming, web site creation, encryption, CD burning. you name it.The shellA user interface for typing commands, executing them,and displaying the results. There are various shells inexistence: the Bourne shell, Korn shell, C shell, and others. This book focuses on bash, the Bourne Again Shell,which is often the default for user accounts. However, allthese shells have similar basic functions.XA graphical system that provides windows, menus, icons,mouse support, and other familiar GUI elements. Morecomplex graphical environments are built on X; the mostpopular are KDE and GNOME. Throughout this book, wediscuss programs that open their own X windows to run.What’s Fedora Linux?Fedora Linux is one particular Linux distribution or “distro,”created by Red Hat, Inc. and the Fedora project (for more2 Linux Pocket Guide
information, see http://fedora.redhat.com) and formerly calledRed Hat Linux.* Our material is based on Fedora Core 1, thefirst official release (November 2003). We focus on the supplied programs and the shell, with brief coverage of X andthe kernel as needed.What’s a Command?A Linux command typically consists of a program name followed by options and arguments, typed within a shell. Theprogram name refers to a program somewhere on disk(which the shell will locate and run). Options, which usuallybegin with a dash, affect the behavior of the program, andarguments usually represent inputs and outputs. For example, this command to count the lines in a file: wc -l myfileconsists of a program (wc, the “word count” program), anoption (-l) saying to count lines, and an argument (myfile)indicating the file to read. (The dollar sign is a prompt fromthe shell, indicating that it is waiting for your command.)Options may be given individually: myprogram -a -b -c myfileThree individual optionsor combined behind a single dash: myprogram -abc myfileSame as -a -b -cthough some programs are quirky and do not recognize combined options.Commands can also be much more complex than running asingle program: They can run several programs at once, either insequence (one after the other) or connected into a “pipeline” with the output of one command becoming theinput of the next.* Red Hat now focuses on its Enterprise Linux products for higher-end applications. Most of this book applies to Enterprise and other Linux distros.What’s in This Book? 3
Options are not standardized. The same option (say, -l)may have different meanings to different programs: in wc-l it means “count lines of text,” but in ls -l it means“produce longer output.” In the other direction, two programs might use different options to mean the samething, such as -q for “run quietly” versus -s for “runsilently.” Likewise, arguments are not standardized. They often represent filenames for input or output, but they can be otherthings too, like directory names or regular expressions. The Linux command-line user interface—the shell—hasa programming language built in. So instead of a command saying “run this program,” it might say, “if today isTuesday, run this program, otherwise run another command six times for each file whose name ends in .txt.”Users and SuperusersLinux is a multiuser operating system. On a given computer,each user is identified by a unique username, like “smith” or“funkyguy,” and owns a (reasonably) private part of the system for doing work. There is also a specially designated user,with username root, who has the privileges to do anything atall on the system. Ordinary users are restricted: though theycan run most programs, in general they can modify only thefiles they own. The superuser, on the other hand, can create,modify, or delete any file and run any program.Some commands in this book can be run successfully only bythe superuser. In this case, we use a hash mark (#) as theshell prompt:# command goes hereOtherwise, we will use the dollar sign prompt indicating anordinary user: command goes here4 Linux Pocket Guide
To become the superuser, you needn’t log out and log backin; just run the su command (see “Becoming the Superuser”on page 118) and provide the superuser password: su -lPassword: ********#Reading This BookWhen we describe a command, we first present its generalusage information. For example, the wc (word count) program has the general usage:wc [options] [files]which means you’d type “wc” followed, if you choose, byoptions and then filenames. You wouldn’t type the squarebrackets “[” and “]”: they just indicate their contents areoptional; and words in italics mean you have to fill in yourown specific values, like names of actual files. If you see avertical bar between options or arguments, perhaps groupedby parentheses:ls (file directory)this indicates choice: when running the ls command, youmay supply either a file or directory name as an argument.Input and outputMost Linux programs accept data from standard input, whichis usually your keyboard, and produce output on standardoutput, which is usually your screen. Additionally, error messages are usually displayed on standard error, which also isusually your screen but kept separate from standard output.*Later we’ll see how to redirect standard input, output, anderror to and from files or pipes. But let’s get our vocabularystraight. When we say a command “reads,” we mean from* For example, you can capture standard output in a file and still have standard error messages appear on screen.What’s in This Book? 5
standard input unless we say otherwise. And when a command “prints,” we mean on standard output, unless we’retalking about computer printers.Standard headingEach command description begins with a heading like thisone for the ls (list files) command.ls [options] [files]/binstdinstdout- file-- opt--helpcoreutils--versionThe heading includes the command name (ls) and usage, thedirectory in which it is located (/bin), the RPM package thatinstalled the command (coreutils), and six properties of thecommand printed in black (supported) or gray (unsupported):stdinThe command reads from standard input, i.e., your keyboard,by default.stdoutThe command writes to standard output, i.e., your screen, bydefault.- fileIf you supply a dash (-) argument in place of an input filename, the command reads from standard input; and likewise,if the dash is supplied as an output filename, the commandwrites to standard output. For example, the following wc(word count) command line reads the files file1 and file2, thenstandard input, then file3: wc file1 file2 - file3-- optIf you supply the command-line option “--” it means “end ofoptions”: anything appearing later on the command line isnot an option. This is sometimes necessary to operate on a filewhose name begins with a dash, which otherwise would be(mistakenly) treated as an option. For example, if you have afile named -foo, the command wc -foo will fail because -foowill be treated as an (invalid) option. wc -- -foo works. If acommand does not support “--”, you can prepend the current6 Linux Pocket Guide
directory path “./” to the filename so the dash is no longer thefirst character: wc ./-foo--helpThe option --help makes the command print a help messageexplaining proper usage, then exit.--versionThe option --version makes the command print its versionnumber and exit.Standard symbolsThroughout the book, we use certain symbols to indicatekeystrokes. Like many other Linux documents, we use the symbol to mean “press and hold the control (Ctrl) key,” sofor example, D (pronounced “control D”) means “press andhold the control key and type D.” We also write ESC tomean “press the Escape key.” Keys like Enter and Spacebarshould be self-explanatory.Your friend, the echo commandIn many of our examples, we’ll print information to thescreen with the echo command, which we’ll formally describein “Screen Output” on page 144. echo is one of the simplestcommands: it merely prints its arguments on standard output, once those arguments have been processed by the shell. echo My dog has fleasMy dog has fleas echo My name shell is USERMy name is smithShell variable USERGetting HelpIf you need more information than this book provides, thereare several things you can do.Getting Help 7
Run the man commandThe man command displays an online manual page, ormanpage, for a given program. For example, to get documentation on listing files with ls, run: man lsTo search for manpages by keyword for a particulartopic, use the -k option followed by the keyword: man -k databaseRun the info commandThe info command is an extended, hypertext help system covering many Linux programs. info lsIf no documentation is found on a given program, infodisplays the program’s manpage. For a listing of available documentation, type info by itself. To learn how tonavigate the info system, type info info.Use the --help option (if any)Many Linux commands respond to the option --help byprinting a short help message. Try: ls --helpExamine the directory /usr/share/docThis directory contains supporting documents for manyprograms, usually organized by program name and version. For example, files for the text editor Emacs, Version 21.3, are found in /usr/share/doc/emacs-21.3.GNOME and KDE HelpFor help with GNOME or KDE, choose the Help item inthe main menu.Fedora-specific web sitesThe official site is http://fedora.redhat.com. An unofficialFAQ has sprung up at http://fedora.artoo.net. And ofcourse there’s the web site for this book:http://www.oreilly.com/catalog/linuxpg/8 Linux Pocket Guide
Usenet newsgroupsUsenet has dozens of newsgroups on Linux topics, suchas comp.os.linux.misc and comp.os.linux.questions. ForRed Hat-specific information, try alt.os.linux.redhat,comp.os.linux.redhat, linux.redhat, and linux.redhat.misc.You can search through newsgroup postings at GoogleGroups, http://groups.google.com, which is a goldmine oftroubleshooting information.GoogleSearch Google for further documentation and tutorials athttp://www.google.com (if you’ve been living in a closet).Fedora: A First ViewWhen you log into a Fedora (or other) Linux system, you’relikely to be greeted by a graphical desktop* like Figure 1,which contains: A Windows-like taskbar across the bottom, with:— A “red hat” icon in the lower left, which whenclicked, pops up a main menu of programs— Icons to run various programs, such as the Mozillaweb browser, Evolution email program, and PrintManager for configuring printers— A desktop switcher (the square with four boxes in it),which lets you maintain and switch between multiple desktops— A blue checkmark indicating that your system software is up to date, or a red exclamation point warning you that it isn’t— A clock Other icons on the desktop, such as a trash can for deleting files, a floppy disk, and your home directory (folder)for storing personal files* Unless you’re logging in remotely over the network, in which case you’llsee a command line, prompting you to type a command.Fedora: A First View 9
Figure 1. Fedora graphical desktopFedora comes with several similar-looking interfaces, and theone you’re viewing is either GNOME or KDE.* You can tellthe difference by clicking the red hat icon to bring up themain menu, and choosing Help. The Help window thatappears will clearly indicate GNOME or KDE.The Role of the ShellExplore the environment of icons and menus in GNOMEand KDE. These graphical interfaces are, for some users, theprimary way to compute with Linux. Various distros, including Fedora, simplify these interfaces so users can edit files,read email, and browse the Web without much effort.Nevertheless, the true power of Linux lies behind the scenes.To get the most out of Linux, you should become proficient* Depending on your system configuration, the interface might look different. GNOME and KDE are very configurable, and Fedora includes a thirdinterface, twm, with yet another look and feel. (And Linux has other graphical interfaces, too.)10 Linux Pocket Guide
in using the shell. It might initially be more difficult thanicons and menus, but once you’re used to it, the shell is quiteeasy to use and very powerful. Most of this book discussesLinux commands run via the shell.How to Run a ShellTo run a shell within GNOME, KDE, or any other graphicalinterface for Linux, you’ll need to open a shell window. Thisis done by programs like xterm, gnome-terminal, konsole, anduxterm. Each of these programs does the same basic thing:open a window that is running a shell, awaiting your input.To run a shell window using the three default windowinginterfaces for Fedora:Interface Take this action.to run this shell window programGNOMEMenu : System Tools : Terminalgnome-terminalor on the desktop:Right Mouse Button : Open TerminalKDEMenu : System Tools : Terminalkonsoleor on the desktop:Right Mouse Button : Open TerminaltwmOn the desktop:Right Mouse Button : XTermxtermDon’t confuse the window program (like konsole) with theshell running inside it. The window is just a container—albeit with fancy features of its own—but the shell is whatprompts you for commands and runs them.If you’re not running a graphical interface—say, you’re logging in remotely over the network, or directly over anattached terminal—a shell will run immediately when youlog in. No shell window is required.Logins, Logouts, and ShutdownsWe assume you know how to log into your Linux account. Tolog out from GNOME or KDE, click the red hat icon in theLogins, Logouts, and Shutdowns 11
taskbar and choose Logout from the main menu. To log outfrom a remote shell, just close the shell (type exit or logout).Never simply turn off the power to a Linux system: it needs amore graceful shutdown. To perform a shutdown fromGNOME, choose Logout Shut Down. From KDE, first logout, then on the login screen, click the Shutdown icon. Toperform a shutdown from a shell, run the shutdown command as the superuser, as follows.shutdown [options] time [message]/sbinstdinstdout- file-- opt--helpSysVinit--versionThe shutdown command halts or reboots a Linux system; only thesuperuser may run it. Here’s a command to halt the system in 10minutes, broadcasting the message “scheduled maintenance” toall users logged in:# shutdown -h 10 "scheduled maintenance"The time may be a number of minutes preceded by a plus sign,like 10, an absolute time in hours and minutes, like 16:25, or theword now to mean immediately.With no options, shutdown puts the system into single-user mode, aspecial maintenance mode in which only one person is logged in (atthe system console), and all nonessential services are off. To exitsingle-user mode, either perform another shutdown to halt or reboot,or type D to bring up the system in normal, multiuser mode.Useful options-rReboot the system.-hHalt the system.-kKidding: don’t really perform a shutdown, just broadcast warning messagesto all users as if the system were going down.-cCancel a shutdown in progress (omit the time argument).-fOn reboot, skip the usual filesystem check performed by the fsck program(described in “Disks and Filesystems” on page 91).-FOn reboot, require the usual filesystem check.12 Linux Pocket Guide
For technical information about shutdowns, single-usermode, and various system states, see the manpages for initand inittab.The FilesystemTo make use of any Linux system, you need to be comfortable with Linux files and their layout. Every Linux file is contained in a collection called a directory. Directories are likefolders on Windows and Macintosh systems. Directoriesform a hierarchy, or tree: one directory may contain otherdirectories, called subdirectories, which may themselves contain other files and subdirectories, and so on, into infinity.The topmost directory is called the root directory and isdenoted by a slash (/).*We refer to files and directories using a “names and slashes”syntax called a path. For instance, this path:/one/two/three/fourrefers to the root directory /, which contains a directorycalled one, which contains a directory two, which contains adirectory three, which contains a final file or directory, four.If a path begins with the root directory, it’s called an absolute path, and if not, it’s a relative path. More on this in amoment.Whenever you are running a shell, that shell is “in” some directory (in an abstract sense). More technically, your shell has acurrent working directory, and when you run commands in thatshell, they operate relative (there’s that word again) to thedirectory. More specifically, if you refer to a relative file path inthat shell, it is relative to your current working directory. Forexample, if your shell is “in” the directory /one/two/three, andyou run a command that refers to a file myfile, then it’s really* In Linux, all files and directories descend from the root. This is unlikeWindows or DOS, in which different devices are accessed by drive letters.The Filesystem 13
/one/two/three/myfile. Likewise, a relative path a/b/c wouldimply the true path /one/two/three/a/b/c.Two special directories are denoted . (a single period) and .(two periods in a row). The former means your current directory, and the latter means your parent directory, one levelabove. So if your current directory is /one/two/three, then .refers to this directory and . refers to /one/two.You “move” your shell from one directory to another usingthe cd command: cd /one/two/threeMore technically, this command changes your shell’s currentworking directory to be /one/two/three. This is an absolutechange (since the directory begins with “/”); of course youcan make relative moves as well: cd d cd ./mydirEnter subdirectory dGo up to my parent, then into directory mydirFile and directory names may contain most characters youexpect: capital and small letters,* numbers, periods, dashes,underscores, and most other symbols (just not “/”; it’s reservedfor separating directories). In general, however, avoid usingspaces, asterisks, parentheses, and other characters that havespecial meaning to the shell. Otherwise, you’ll need to quote orescape these characters all the time. (See “Quoting” on page 27.)Home DirectoriesUsers’ personal files are often found in /home (for ordinaryusers) or /root (for superusers). Your home directory is typically/home/your-username: /home/smith, /home/jones, etc. There areseveral ways to locate or refer to your home directory.cdWith no arguments, the cd command returns you (i.e., setsthe shell’s working directory) to your home directory.* These are not equivalent, since Linux filenames are case-sensitive.14 Linux Pocket Guide
HOME variableThe environment variable HOME (see “Shell variables” onpage 23) contains the name of your home directory. echo HOME/home/smithThe echo command prints its arguments When used in place of a directory, a lone tilde is expandedby the shell to the name of your home directory. echo /home/smithWhen followed by a username (as in smith), the shellexpands this string to be the user’s home directory: cd smith pwd/home/smithThe “print working directory” commandSystem DirectoriesA typical Linux system has tens of thousands of system directories. These directories contain operating system files, applications, documentation, and just about everything exceptprivate user files (which typically live in /home).Unless you’re a system administrator, you’ll rarely visit mostsystem directories—but with a little knowledge you canunderstand or guess their purposes. Their names often contain three parts, which we’ll call the scope, category, andapplication. (These are not standard terms, but they’ll helpyou understand things.) For example, the directory /usr/local/share/emacs, which contains local data for the Emacs texteditor, has scope /usr/local (locally installed system files), category share (program-specific data and documentation), andapplication emacs (a text editor), shown in Figure 2. We’llexplain these three parts, slightly out of onFigure 2. Directory scope, category, and applicationThe Filesystem 15
Directory path part 1: categoryA category tells you the types of files found in a directory. Forexample, if the category is bin, you can be reasonably assuredthat the directory contains programs. Common categories arelisted below.Categories for programsbinPrograms (usually binary files)sbinPrograms (usually binary files) intended to be run by the superuser, rootlibLibraries of code used by programslibexecPrograms invoked by other programs, not usually by users; think“library of executable programs”Categories for documentationdocDocumentationinfoDocumentation files for Emacs’s built-in help systemmanDocumentation files (manual pages) displayed by the man program; thefiles are often compressed, or sprinkled with typesetting commands forman to interpretshareProgram-specific files, such as examples and installation instructionsCategories for configurationetcConfiguration files for the system (and other miscellaneous stuff)init.drc.dConfiguration files for booting Linux; also rc1.d, rc2.d, .Categories for programmingincludeHeader files for programmingsrcSource code for programsCategories for web filescgi-binScripts/programs that run on web pageshtmlWeb pagespublic html Web pages, typically in users’ home directorieswwwWeb pagesCategories for displayfontsFonts (surprise!)X11X window system files16 Linux Pocket Guide
Categories for hardwaredevDevice files for interfacing with disks and other hardwaremntmiscMount points: directories that provide access to disksCategories for runtime filesvarFiles specific to this computer, created and updated as the computer runslockLock files, created by programs to say, “I am running;” the existence of alock file may prevent another program, or another instance of the sameprogram, from running or performing an actionlogLog files that track important system events, containing error, warning,and informational messagesmailMailboxes for incoming mailrunPID files, which contain the IDs of running processes; these files areoften consulted to track or kill particular processesspoolFiles queued or in transit, such as outgoing email, print jobs, andscheduled jobstmpTemporary storage for programs and/or people to useprocOperating system state: see “Operating System Directories” on page 18Directory path part 2: scopeThe scope of a directory path describes, at a high level, the purpose of an entire directory hierarchy. Some common ones are:/System files supplied with Linux (pronounced “root”)/usrMore system files supplied with Linux (pronounced “user”)/usr/gamesGames (surprise!)/usr/kerberosFiles pertaining to the Kerberos authentication system/usr/localSystem files developed “locally,” either for your organization or yourindividual computer/usr/X11R6Files pertaining to the X window systemSo for a category like lib (libraries), your Linux system mighthave directories /lib, /usr/lib, /usr/local/lib, /usr/games/lib, and/usr/X11R6/lib. You might have other scopes as suits the system administrator: /my-company/lib, /my-division/lib, and so on.The Filesystem 17
There isn’t a clear distinction between / and /usr in practice,but there is a sense that / is “lower-level” and closer to theoperating system. So /bin contains fundamental programslike ls and cat, /usr/bin contains a wide variety of applications supplied with your Linux distribution, and /usr/local/bin contains programs your system administrator chose toinstall. These are not hard-and-fast rules but typical cases.Directory path part 3: applicationThe application part of a directory path is usually the nameof a program. After the scope and category (say, /usr/local/doc), a program may have its own subdirectory (say, /usr/local/doc/myprogram) containing files it needs.Operating System Directories/bootFiles for booting the system. This is where the kernellives, typically named /boot/vmlinuz./lost foundDamaged files that were rescued by a disk recovery tool./procDescribes currently-running processes; for advancedusers.The files in /proc provide views into the running kernel andhave special properties. They always appear to be zero sized,read-only, and dated now: ls -l /proc/version-r--r--r-- 1 root root0 Oct3 22:55 /proc/versionHowever, their contents magically contain information aboutthe Linux kernel: cat /proc/versionLinux version 2.4.22-1.2115.nptl .Mostly these files are used by programs. Go ahead andexplore. Here are some examples.18 Linux Pocket Guide
/proc/ioports A list of your computer’s input/output hardware./proc/version The operating system version. The uname command prints the sameinformation./proc/uptime System uptime, i.e., seconds elapsed since the system was last booted.Run the uptime command for a more human-readable result./proc/nnnWhere nnn is a positive integer, information about the Linux processwith process ID nnn./pr
Linux Pocket Guide Welcome to Linux! If you’re a new user, this book can serve as a quick introduction to Linux in general, and Fedora Linux specifically, as well as a guide to common and practi-cal commands. If you have Linux experience, feel free to skip the introductory material. What’s in This Book?
Linux in a Nutshell Linux Network Administrator’s Guide Linux Pocket Guide Linux Security Cookbook Linux Server Hacks Linux Server Security Running Linux SELinux Understanding Linux Network Internals Linux Books Resource Center linux.oreilly.comis a complete catalog of O’Reilly’s books on Linux and Unix and related technologies .
Other Linux resources from O’Reilly Related titles Building Embedded Linux Systems Linux Device Drivers Linux in a Nutshell Linux Pocket Guide Running Linux Understanding Linux Network Internals Understanding the Linux Kernel Linux Books Resource Center linu
Complete Reference, Red Hat Linux, Linux Programming, Red Hat Linux Administrator's Reference, Linux Programmer's Reference, Introductory C with C , Introductory Command Line Unix for Users, and many other books. He is a contributor to linux.sys-con.com (Linux Wo
Perfection PC Perfection PC Inc. Philips Philips Electronics Planar Planar Systems Inc PLEXON Plexon, Inc. Pogo Linux Pogo Linux, Inc. Pogo Linux Altura M2 Pogo Linux, Inc. Pogo Linux Velocity -D50 Pogo Linux, Inc. Pogo Linux Verona 330 Pogo Linux, Inc. Pogo Linux Vor
Pocket WSL-PK-35-XX Same size pocket as Roller 64 6 in. x 9 in. (152 mm x 229 mm) Dual Pocket WSL-PK-6-9-XX Same size pocket as Roller 64 2 in. Flap (51 mm) (must be 3.5 in. pocket compatible) WSL-FLP-2-XX Attached to the hanger that is built into pocket Use 3 in. (76 mm) Flap for Dual Pocket Roller
Yes. Oracle Autonomous Linux, which is based on Oracle Linux, is 100% application binary compatible with IBM's Red Hat Enterprise Linux. This means that applications certified to run on Red Hat Enterprise Linux can run on Oracle Autonomous Linux unmodified. Oracle Linux binaries are provided for patching and updating Red Hat Enterprise Linux
Official Kali Linux Documentation This PDF has been autogenerated on docs.kali.org - Apr 7, 2013 00. Introduction to Kali Linux What is Kali Linux ? Kali Linux is an advanced Penetration Testing and Security Auditing Linux distribution. Kali Linux Features Kali is a complete re-build of BackTrack Linux, adhering completely to Debian development .
Novagen pET System Manual 11th Edition TABLE OF CONTENTS TB055 11th Edition 01/06. 2 USA and Canada United Kingdom and Ireland Germany All Other Countries Tel 800 526 7319 UK Freephone 0800 622935 Freephone 0800 100 3496 Contact Your Local Distributor novatech@novagen.com Ireland Toll Free 1800 409445 techservice@merckbiosciences.de www.novagen.com techservice@merckbiosciences.co.uk .
