Muutke küpsiste eelistusi

E-raamat: Linux Philosophy for SysAdmins: And Everyone Who Wants To Be One

  • Formaat: PDF+DRM
  • Ilmumisaeg: 03-Aug-2018
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484237304
  • Formaat - PDF+DRM
  • Hind: 80,26 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Formaat: PDF+DRM
  • Ilmumisaeg: 03-Aug-2018
  • Kirjastus: APress
  • Keel: eng
  • ISBN-13: 9781484237304

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Reveals and illustrates the awesome power and flexibility of the command line, and the design and usage philosophies that support those traits. This understanding of how to extract the most from the Linux command line can help you become a better SysAdmin. Understand why many things in the Linux and Unix worlds are done as they are, and how to apply the Linux Philosophy to working as a SysAdmin.

The original Unix/Linux Philosophy presented foundational and functional tenets - rules, guidelines, and procedural methods - that worked well. However, it was intended for the developers of those operating systems. Although System Administrators could apply many of the tenets to their daily work, many important tenets were missing.

Over the years that David Both has been working with Linux and Unix, he has formulated his own philosophy one which applies more directly to the everyday life of the System Administrator. This book defines a philosophy, and then illuminates the practical aspects of that philosophy with real-world experiments you can perform. Inspired by Davids real mentors, and dedicated to them, The Linux Philosophy for System Administrators is a mentor to SysAdmins everywhere; remember - "If you fail you learn."

What You Will Learn









Apply the Linux philosophy to working as a SysAdmin

Unlock the power of the knowledge you already have

Fully understand and access the vast power of the command line

Review the power of Linux as a function of the philosophies that built it







Who This Book Is For

If you want to learn the secrets that make the best Linux SysAdmins powerful far beyond that of mere mortals; if you want to understand the concepts that unlock those secrets; if you want to be the SysAdmin that everyone else turns to when the bytes hit the fan then this book is for you. 
About the Author xix
About the Technical Reviewer xxi
Acknowledgments xxiii
Part I Introduction
1(22)
Chapter 1 Introduction to the Linux Philosophy
3(12)
Am I a SysAdmin?
5(2)
The Structure of the Philosophy
7(2)
Who Should Read This Book
9(2)
But I Don't Meet Those Requirements
10(1)
Who Should Not Read This Book
11(1)
The Linux Truth
11(1)
Restrictive Operating Systems
12(1)
Linux Is Open and Free
12(1)
Real Knowledge
13(1)
Enlightenment
14(1)
Chapter 2 Getting Ready
15(8)
The Experiments
15(2)
System Requirements
17(4)
How to Access the Command Line
18(1)
Create the Student User
19(1)
Preparing the USB Thumb Drive
19(2)
What to Do if the Experiments Do Not Work
21(2)
Part II Foundation
23(84)
Chapter 3 Data Streams
27(16)
Text Streams -- A Universal Interface
27(1)
STDIO File Handles
28(1)
Generating Data Streams
29(2)
Test a Theory with Yes
31(2)
Exploring the USB Drive
33(6)
Streams of Randomness
39(2)
Summary
41(2)
Chapter 4 Transforming Data Streams
43(16)
Data Streams as Raw Materials
44(1)
Pipe Dreams
44(2)
Building Pipelines
46(1)
Redirection
47(5)
Redirecting STDERR
50(2)
The Pipeline Challenge
52(6)
The Problem
52(2)
The Solutions
54(3)
Thoughts on the Solutions
57(1)
Summary
58(1)
Chapter 5 Everything Is a File
59(22)
What Is a File?
59(1)
Device Files
60(1)
Device File Creation
60(1)
Udev Simplification
61(2)
Naming Rules
62(1)
Device Data Flow
63(1)
Device File Classification
64(2)
Fun with Device Files
66(5)
Randomness, Zero, and More
71(3)
Back Up the Master Boot Record
74(5)
Implications of Everything Is a File
79(1)
Summary
79(2)
Chapter 6 Using the Linux FHS
81(26)
Definitions
81(1)
The Standard
82(3)
Using a Well-Defined filesystem Structure
85(1)
Linux Unified Directory Structure
86(1)
Special filesystems
87(14)
The /proc filesystem
88(6)
The /sys filesystem
94(5)
SELinux
99(2)
Problem Solving
101(4)
Using the filesystem Incorrectly
102(1)
Email Inboxes
103(1)
Adhering to the Standard
103(1)
Where Does This File Go?
104(1)
Summary
105(2)
Part III Function
107(218)
Chapter 7 Embrace the CLI
109(22)
Defining the Command Line
110(1)
CLI Terminology
110(14)
Command Prompt
110(1)
Command Line
111(1)
Command-Line Interface
111(1)
Terminal
111(2)
Console
113(1)
Virtual Console
114(1)
Terminal Emulator
115(2)
Pseudo Terminal
117(1)
Session
117(1)
Shell
118(3)
Secure Shell (SSH)
121(1)
Screen
121(3)
The GUI and the CLI
124(1)
Non-Restrictive Interface
125(5)
The Mailing List
125(3)
Baffle Them with Big Data
128(2)
CLI Power
130(1)
Chapter 8 Be a Lazy SysAdmin
131(34)
Preparation
131(1)
True Productivity
132(1)
Preventative Maintenance
133(1)
Minimize Typing
134(2)
Aliases
134(2)
Other Typing Shortcuts
136(1)
File Naming
136(1)
BASH Efficiency
136(10)
Completion Facility
136(3)
Command-Line Recall and Editing
139(1)
History
139(1)
Using the History
140(6)
Logs Are Your Friend
146(10)
SAR
146(3)
Mail Logs
149(1)
messages
150(1)
dmesg
151(1)
secure
152(3)
Following Log Files
155(1)
Systemd Logs
156(4)
logwatch
160(3)
Success as a Lazy SysAdmin
163(2)
Chapter 9 Automate Everything
165(30)
Why I Use Scripts
165(1)
How I Got Here
166(1)
Scripting Repetitive Tasks
167(2)
Making It Easier
167(1)
From Desirable to Necessity
168(1)
Updates
169(12)
Additional Levels of Automation
181(2)
Using cron for Timely Automation
183(8)
crontab
183(3)
cron.d
186(2)
anacron
188(2)
Scheduling Tips
190(1)
Thoughts About cron
190(1)
Cron Resources
191(1)
Other Automation Possibilities
191(1)
Some Alt Ideas
192(1)
Deepening the Philosophy
192(3)
Chapter 10 Always Use Shell Scripts
195(22)
Definition
195(2)
The SysAdmin Context
197(4)
Requirements
197(1)
Development Speed
198(1)
Performance Speed
199(1)
Variables
200(1)
Testing
200(1)
Open and Open Source
201(1)
Shell Scripts as Prototypes
201(1)
Process
202(13)
Quick and Dirty
202(1)
Planning and Foresight
203(12)
Final Thoughts
215(2)
Chapter 11 Test Early, Test Often
217(30)
Procedures
218(4)
Create a Test Plan
218(2)
Start Testing at the Beginning
220(1)
Final Testing
220(1)
Testing in Production
221(1)
Fuzzy Testing
222(1)
Automated Testing
223(1)
Trying It Out
224(21)
Requirements for MOTD Script
225(1)
Test Plan for MOTD Script
226(1)
Developing the Script
227(4)
Add Sanity Checks
231(14)
Fixing a Script
245(1)
Summary
246(1)
Chapter 12 Use Commonsense Naming
247(10)
Script and Program Names
247(3)
Variables
250(5)
Naming Variables
250(1)
Make Everything a Variable
251(4)
Procedures
255(1)
Hosts
255(1)
Organizational Naming
256(1)
Summary
256(1)
Chapter 13 Store Data in Open Formats
257(16)
Closed Is Impenetrable
257(1)
Open Is Knowable
258(1)
Flat ASCII Text
259(13)
System Configuration Files
260(5)
Global Bash Configuration
265(3)
User Configuration Files
268(2)
ASCII Rocks
270(2)
Final Thoughts
272(1)
Chapter 14 Use Separate filesystems for Data
273(20)
Why We Need Separate filesystems
273(2)
Hard Drive Crashes
274(1)
Full filesystems
274(1)
Laptop Lament
275(3)
Data Security
278(1)
Recommendations
279(6)
/boot
280(1)
/home
281(1)
/usr
282(1)
/opt
283(1)
/var
283(1)
/tmp
284(1)
The Other Branches
284(1)
Starting with Separate filesystems
285(1)
Adding Separate filesystems Later
285(7)
Final Thoughts
292(1)
Chapter 15 Make Programs Portable
293(18)
Intel PC to Mainframe
293(1)
Architectures
294(1)
Portability Restrictions
295(2)
Licensing
295(1)
Technology
295(2)
LibreOffice
297(1)
Shell Scripts
297(3)
Portability with Windows
298(2)
The Internet and Portability
300(1)
Creating Web Pages
300(9)
Static Content
301(1)
Dynamic Web Pages for a New Job
302(5)
CGI -- Open and Portable
307(1)
WordPress
308(1)
Final Thoughts
309(2)
Chapter 16 Use Open Source Software
311(14)
Definition of Open Source
311(1)
The Open Source Definition (Annotated)
312(3)
Introduction
312(3)
Why This Is Important
315(1)
Coining the Term
316(1)
Licensing Our Own Code
316(2)
Organizational Code Sharing
318(3)
Silos Suck
318(1)
Open Organizations and Code Sharing
319(1)
Things to Avoid
320(1)
Code Availability
321(3)
How Do I Share My Code?
321(1)
Code Sharing Considerations
322(2)
Parting Thoughts
324(1)
Part IV Becoming Zen
325(168)
Chapter 17 Strive for Elegance
327(26)
Hardware Elegance
327(4)
The PCB
328(1)
Motherboards
328(1)
Computers
329(1)
Data Centers
329(1)
Power and Grounding
330(1)
Software Elegance
331(5)
Fixing My Web Site
336(2)
Removing Cruft
338(12)
Old or Unused Programs
338(4)
Old Code in Scripts
342(1)
Old Files
343(7)
A Final Word
350(3)
Chapter 18 Find the Simplicity
353(18)
Complexity in Numbers
353(2)
Simplicity in Basics
355(1)
The Never-Ending Process of Simplification
356(1)
Simple Programs Do One Thing
356(3)
Simple Programs Are Small
359(2)
Simplicity and the Philosophy
361(1)
Simplifying My Own Programs
361(1)
Simplifying Others' Programs
362(5)
Uncommented Code
362(5)
Hardware
367(1)
Linux and Hardware
368(1)
The Quandary
369(1)
The Last Word
370(1)
Chapter 19 Use Your Favorite Editor
371(10)
More Than Editors
372(1)
Linux Startup
372(2)
Why I Prefer SystemV
373(1)
Why I Prefer systemd
373(1)
The Real Issue
374(1)
Desktop
374(1)
Sudo or Not sudo
375(4)
Bypass sudo
376(2)
Valid Uses for sudo
378(1)
A Few Closing Words
379(2)
Chapter 20 Document Everything
381(14)
The Red Baron
382(1)
My Documentation Philosophy
383(5)
The Help Option
383(1)
Comment Code Liberally
384(3)
My Code Documentation Process
387(1)
Man Pages
388(1)
Systems Documentation
388(4)
System Documentation Template
389(3)
Document Existing Code
392(1)
Keep Docs Updated
393(1)
File Compatibility
393(1)
A Few Thoughts
394(1)
Chapter 21 Back Up Everything - Frequently
395(22)
Data Loss
395(2)
Backups to the Rescue
397(8)
The Problem
397(7)
Recovery
404(1)
Doing It My Way
405(9)
Backup Options
405(8)
Off-Site Backups
413(1)
Disaster Recovery Services
414(1)
Other Options
415(1)
What About the "Frequently" Part?
415(1)
Summary
415(2)
Chapter 22 Follow Your Curiosity
417(28)
Charlie
417(1)
Curiosity Led Me to Linux
418(5)
Curiosity Solves Problems
423(17)
Securiosity
423(17)
Follow Your Own Curiosity
440(3)
Be an Author
441(1)
Failure Is an Option
441(1)
Just Do It
442(1)
Summary
443(2)
Chapter 23 There Is No Should
445(18)
There Are Always Possibilities
445(1)
Unleashing the Power
446(1)
Problem Solving
447(8)
Critical Thinking
449(1)
Reasoning to Solve Problems
450(3)
Integrated Reason
453(2)
Self-Knowledge
455(1)
Finding Your Center
455(1)
The Implications of Diversity
456(1)
Measurement Mania
457(1)
The Good Manager
458(1)
Working Together
458(4)
Silo City
460(1)
The Easy Way
461(1)
Thoughts
462(1)
Chapter 24 Mentor the Young SysAdmins
463(14)
Hiring the Right People
464(1)
Mentoring
465(2)
BRuce the Mentor
466(1)
The Art of Problem Solving
467(7)
The Five Steps of Problem Solving
467(2)
Knowledge
469(1)
Observation
469(3)
Reasoning
472(1)
Action
473(1)
Test
473(1)
Example
474(1)
Iteration
475(1)
Concluding Thoughts
475(2)
Chapter 25 Support Your Favorite Open Source Project
477(8)
Project Selection
477(1)
Code
478(1)
Test
479(1)
Submit Bug Reports
479(1)
Documentation
480(1)
Assist
481(1)
Teach
482(1)
Write
482(1)
Donate
483(1)
Thoughts
484(1)
Chapter 26 Reality Bytes
485(8)
People
485(1)
The Micromanager
486(1)
More Is Less
487(1)
Tech Support Terror
488(1)
You Should Do It My Way
489(1)
It's OK to Say No
490(1)
The Scientific Method
490(1)
Understanding the Past
491(1)
Final Thoughts
492(1)
Bibliography
493
Books
493(1)
Web sites
494(7)
Index 501
David Both is a Linux and Open Source advocate who resides in Raleigh, North Carolina. He has been in the IT industry for over forty years and taught OS/2 for IBM where he worked for over 20 years. While at IBM, he wrote the first training course for the original IBM PC in 1981. He has taught RHCE classes for Red Hat and has worked at MCI Worldcom, Cisco, and the State of North Carolina. He has been working with Linux and Open Source Software for 20 years. David has written articles for OS/2 Magazine, Linux Magazine, Linux Journal and OpenSource.com. His article "Complete Kickstart," co-authored with a colleague at Cisco, was ranked 9th in the Linux Magazine Top Ten Best System Administration Articles list for 2008. He has spoken at POSSCON and All Things Open (ATO).