The key to mastering any Unix system, especially Linux and Mac OS X, is a thorough knowledge of shell scripting. Scripting is a way to harness and customize the power of any Unix system, and it's an essential skill for any Unix users, including system administrators and professional OS X developers. But beneath this simple promise lies a treacherous ocean of variations in Unix commands and standards.bash Cookbook teaches shell scripting the way Unix masters practice the craft. It presents a variety of recipes and tricks for all levels of shell programmers so that anyone can become a proficient…mehr
The key to mastering any Unix system, especially Linux and Mac OS X, is a thorough knowledge of shell scripting. Scripting is a way to harness and customize the power of any Unix system, and it's an essential skill for any Unix users, including system administrators and professional OS X developers. But beneath this simple promise lies a treacherous ocean of variations in Unix commands and standards.bash Cookbook teaches shell scripting the way Unix masters practice the craft. It presents a variety of recipes and tricks for all levels of shell programmers so that anyone can become a proficient user of the most common Unix shell -- the bash shell -- and cygwin or other popular Unix emulation packages. Packed full of useful scripts, along with examples that explain how to create better scripts, this new cookbook gives professionals and power users everything they need to automate routine tasks and enable them to truly manage their systems - rather than have their systems manage them
Carl Albing has worked for large companies and small startups, in technical as well as in managerial and marketing roles. He wrote compiler software while at NCR, medical image processing software at a small startup, distributed computing software for the premier supercomputing company Cray Research, Inc. His experience in software development goes back to the early 1970's working with the C Language and Unix. In the last few years, he has put new Linux and Java technologies to use for real-world business solutions. His education includes graduate work in Computer Science as well as a degree in Mathematics and an International MBA.
Cameron Newham lives in Perth, Western Australia. After completing a Bachelor of Science majoring in information technology and geography at the University of Western Australia, Cameron joined Universal Defence Systems (later to become Australian Defence Industries) as a software engineer. He has been with ADI for six years, working on various aspects of command and control systems. In his spare time Cameron can be found surfing the Internet, ballroom dancing, or driving his sports car. He also has more than a passing interest in space science, 3D graphics, synthesiser music, and Depeche Mode.
JP Vossen has been working with computers since the early 80s and has been in the IT industry since the early 90s, specializing in Information Security since the late 90s. He's been fascinated with scripting and automation since he first understood what an autoexec.bat was, and was delighted to discover the power and flexibility of bash and GNU on Linux in the mid-90s. He has previously written for Information Security Magazine and SearchSecurity.com, among others. On those few occasion when he's not in front of a computer, he is usually taking something apart, putting something together, or both.
Inhaltsangabe
From the contents: Preface 1. Beginning bash 1.1 Decoding the Prompt 1.2 Showing Where You Are 1.3 Finding and Running Commands 1.4 Getting Information About Files 1.5 Showing All Hidden (dot) Files in the Current Directory 1.6 Using Shell Quoting 1.7 Using or Replacing Built-ins and External Commands 1.8 Determining If You Are Running Interactively 1.9 Setting bash As Your Default Shell 1.10 Getting bash for Linux 1.11 Getting bash for xBSD 1.12 Getting bash for Mac OS X 1.13 Getting bash for Unix 1.14 Getting bash for Windows 1.15 Getting bash Without Getting bash 1.16 Learning More About bash Documentation 2. Standard Output 2.1 Writing Output to the Terminal/Window 2.2 Writing Output but Preserving Spacing 2.3 Writing Output with More Formatting Control 2.4 Writing Output Without the Newline 2.5 Saving Output from a Command 2.6 Saving Output to Other Files 2.7 Saving Output from the ls Command 2.8 Sending Both Output and Error Messages to Different Files 2.9 Sending Both Output and Error Messages to the Same File 2.10 Appending Rather Than Clobbering Output 2.11 Using Just the Beginning or End of a File 2.12 Skipping a Header in a File 2.13 Throwing Output Away 2.14 Saving or Grouping Output from Several Commands 2.15 Connecting Two Programs by Using Output As Input 2.16 Saving a Copy of Output Even While Using It As Input 2.17 Connecting Two Programs by Using Output As Arguments 2.18 Using Multiple Redirects on One Line 2.19 Saving Output When Redirect Doesn't Seem to Work 2.20 Swapping STDERR and STDOUT 2.21 Keeping Files Safe from Accidental Overwriting 2.22 Clobbering a File on Purpose 3. Standard Input 3.1 Getting Input from a File 3.2 Keeping Your Data with Your Script 3.3 Preventing Weird Behavior in a Here-Document 3.4 Indenting Here-Documents 3.5 Getting User Input 3.6 Getting Yes or No Input 3.7 Selecting from a List of Options 3.8 Prompting for a Password 4. Executing Commands 4.1 Running Any Executable 4.2 Telling If a Command Succeeded or Not 4.3 Running Several Commands in Sequence 4.4 Running Several Commands All at Once 4.5 Deciding Whether a Command Succeeds 4.6 Using Fewer if Statements 4.7 Running Long Jobs Unattended 4.8 Displaying Error Messages When Failures Occur 4.9 Running Commands from a Variable 4.10 Running All Scripts in a Directory 5. Basic Scripting: Shell Variables ...
From the contents: Preface 1. Beginning bash 1.1 Decoding the Prompt 1.2 Showing Where You Are 1.3 Finding and Running Commands 1.4 Getting Information About Files 1.5 Showing All Hidden (dot) Files in the Current Directory 1.6 Using Shell Quoting 1.7 Using or Replacing Built-ins and External Commands 1.8 Determining If You Are Running Interactively 1.9 Setting bash As Your Default Shell 1.10 Getting bash for Linux 1.11 Getting bash for xBSD 1.12 Getting bash for Mac OS X 1.13 Getting bash for Unix 1.14 Getting bash for Windows 1.15 Getting bash Without Getting bash 1.16 Learning More About bash Documentation 2. Standard Output 2.1 Writing Output to the Terminal/Window 2.2 Writing Output but Preserving Spacing 2.3 Writing Output with More Formatting Control 2.4 Writing Output Without the Newline 2.5 Saving Output from a Command 2.6 Saving Output to Other Files 2.7 Saving Output from the ls Command 2.8 Sending Both Output and Error Messages to Different Files 2.9 Sending Both Output and Error Messages to the Same File 2.10 Appending Rather Than Clobbering Output 2.11 Using Just the Beginning or End of a File 2.12 Skipping a Header in a File 2.13 Throwing Output Away 2.14 Saving or Grouping Output from Several Commands 2.15 Connecting Two Programs by Using Output As Input 2.16 Saving a Copy of Output Even While Using It As Input 2.17 Connecting Two Programs by Using Output As Arguments 2.18 Using Multiple Redirects on One Line 2.19 Saving Output When Redirect Doesn't Seem to Work 2.20 Swapping STDERR and STDOUT 2.21 Keeping Files Safe from Accidental Overwriting 2.22 Clobbering a File on Purpose 3. Standard Input 3.1 Getting Input from a File 3.2 Keeping Your Data with Your Script 3.3 Preventing Weird Behavior in a Here-Document 3.4 Indenting Here-Documents 3.5 Getting User Input 3.6 Getting Yes or No Input 3.7 Selecting from a List of Options 3.8 Prompting for a Password 4. Executing Commands 4.1 Running Any Executable 4.2 Telling If a Command Succeeded or Not 4.3 Running Several Commands in Sequence 4.4 Running Several Commands All at Once 4.5 Deciding Whether a Command Succeeds 4.6 Using Fewer if Statements 4.7 Running Long Jobs Unattended 4.8 Displaying Error Messages When Failures Occur 4.9 Running Commands from a Variable 4.10 Running All Scripts in a Directory 5. Basic Scripting: Shell Variables ...
Rezensionen
"Das Buch ist klar strukturiert und bietet unzählige Beispiele zur Arbeit mit der Bash-Shell. Einsteiger, die anhand von Beispielen die Bash-Nutzung lernen wollen, werden Schritt für Schritt an die Materie herangeführt. Lesen und Probieren helfen beim Verständnis.
Aber auch Fortgeschrittene und Kenner der Bash bekommen reichlich Tipps und Anregungen zur effizienten Nutzung des Tools. Zusätzlich erweist sich das Bash-Cookbook als nützliche Quelle zum Nachschlagen." -- AMIGA-MAGAZIN, Ausgabe 8, August 2007
"Selbst Unix-Gurus grübeln hin und wieder über dem ein oder anderen Skript-Problem. Abhilfe schafft hier das bash Cookbook, eine umfangreiche Sammlung von praktischen Codeschnipseln. Hier finden sich Lösungen für alltägliche und nicht ganz alltägliche Fragestellungen, die beim Arbeiten immer wieder auftauchen. Auf rund 600 Seiten geht es dabei pragmatisch zu: Statt mit ebenso kunstvollen wie komplexen Konstrukten zu glänzen, raten dei Autoren, lieber leicht lesbaren Code zu schreiben. So stellen Sie sicher, dass Sie auch anderthalb Jahre und drei Projekte später noch verstehen, was Sie programmiert haben." -- Linux User, Ausgabe 09, August 2007
Es gelten unsere Allgemeinen Geschäftsbedingungen: www.buecher.de/agb
Impressum
www.buecher.de ist ein Internetauftritt der buecher.de internetstores GmbH
Geschäftsführung: Monica Sawhney | Roland Kölbl | Günter Hilger
Sitz der Gesellschaft: Batheyer Straße 115 - 117, 58099 Hagen
Postanschrift: Bürgermeister-Wegele-Str. 12, 86167 Augsburg
Amtsgericht Hagen HRB 13257
Steuernummer: 321/5800/1497
