|
Home | Switchboard | Unix Administration | Red Hat | TCP/IP Networks | Neoliberalism | Toxic Managers |
(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix |
|
I believe Red Hat represents the dominant enterprise Linux distribution. Generally books about Red Hat were the most numerous and of the best quality among all other Linux distributions books. Please note that many of the books about Red Hat are annual of by-annual reprints of the same book in "infinite" series catching to releases of the OS (this is especially typical for Fedora books). You can save money buying the book devoted to the previous version.
While recently the number of Red Hat books diminished substantially as Ubuntu became the most sexy Linux distribution, books about Red Hat still dominate the Linux books landscape:
Most published about Red Hat books are of "pulp fiction" quality and do not cover system administration in sufficient depth. So they are useless for in-depth study required for passing the exam.
Still there are a few reasonably good books that can really help (and you need all the help you can get, if you do not attend RHEL training couse(s) as the exam is pretty challenging). they are also most useful for those who administer RHEL servers in enterprise environment.
It is not necessary to use only RHEL6 related book to pass RHEL 6 exam. Some RHEL 5 books are still extremely useful (and much cheaper). After all differences between RHEL 5 and RHEL 6 are minor.
The cost of the exam justifies spending money on at least half-dozen books. The key here is not the number of books as such but getting additional books as you run into difficulties trying to configure you own "lab network" based on a couple of "real" desktops (with one serving as a default router to other and a couple of virtual servers (RHEL limits the number of virtual clients, so you can use CentOS) to imitate the environment in which you will be put in the test. Networking issues can be earned only on real hardware. Spending too much time on resolving network problems during exam greatly diminishes your chances of success. You need clearly understand Linux routing (default and not default) and related topics to success.
|
Please understand that the last "reasonable" version of RHEL which still resembles "classic" Unix was version 6. In version 7 they did one big Chinese-style Great Leap Forward toward Windows and introduced Systemd. Which changes a lot of things related to system administration besides startup (formally systemd is a replacement for initd, but in reality it is much more then that) including system logging. History will tell whether this was a good idea, but at present level of popularity it is difficult to dislodge Red Hat from being primary enterprise Linux distribution despite their transgressions. One thing is certain is that you should more use CentOS then RHEL from now on, whenever possible (and quality of Red Hat support became so dismal that the money paid on more expensive license are essentially wasted ;-)
This is a good book that really helps to prepare for the exam. Among other things it covers booting using bash shell (to reset root password, see also Linux root password recovery
Addison-Wesley Professional. This is good but not in depth book that covered the topics of the exam.
This is a good, freely available but somewhat outdated book. But it covers routing well and this is one of key topics that you need to understand to pass the exam
The UNIX CD Bookshelf, containing six books from O'Reilly plus the software from UNIX Power Tools -- all on a convenient CD-ROM. A bonus hard-copy book, UNIX in a Nutshell: System V Edition, is also included. Included on the CD-ROM are UNIX in a Nutshell: System V Edition; UNIX Power Tools, 2nd Edition (with software); Learning the UNIX Operating System, 4th Edition; Learning the vi Editor, 5th Edition; sed & awk, 2nd Edition; and Learning the Korn Shell. Never has it been easier to learn, or look up, what you need to know online. Formatted in HTML, The UNIX CD Bookshelf can be read by any Web browser. The books are fully searchable and are cross-referenced. In addition to individual indexes for each book, a master index for the entire library is provided.
Red Hat used to have two major certifications certifications: Red Hat Certified Technician (RHCT) and Red Hat Certified Engineer (RHCE). RHCT is a subset of RHCE. it ignores such RHCE topics as network services and network security. It focuses instead on such routine systems administration topics as installation and configuration. If one taking the RHCE exam fails part of the test, but pass the part relevant to RHCT, and still be granted RHCT status. If your goal is to become an RHCE, it makes sense to first become an RHCT before undertaking the larger battery of exams.
Both exam are given on a live machine. Expect to fail the first attempt as you do not know the requirements and can't anticipate them. The second attempt with proper preparation is usually enough to pass the exam.
Here is more a complete description of those two certifications:
RHCT is an intermediate level certification
To quote the Red Hat site:
Red Hat Certified Engineer (RHCE) Red Hat Certified Engineer (RHCE) is also a test on live systems. the number of topics is wider and complexity of problems is higher too.
RHCT Exam topics generally correspond the course RH133 Red Hat Linux System Administration (No Xen part). It stresses boot process, LVM and Software RAID, networking and troubleshooting topics.
Unit 1 - System Initialization
- Objectives
- Boot Sequence Overview
- Boot Loader Components
- GRUB and grub.conf
- Starting the Boot Process: GRUB
- Kernel Initialization
- init Initialization
- Run Levels
- /etc/rc.d/rc.sysinit
- /etc/rc.d/rc
- System V run levels
- /etc/rc.d/rc.local
- Controlling Services
- Hands-on Lab 1: Managing Startup
Unit 2 - Package Management
- RPM Package Manager
- Installing and Removing Software
- Updating a Kernel RPM
- rpm Queries
- rpm Verification
- About yum
- Using yum
- Searching packages/files
- Configuring Additional Repositories
- Creating a private repository
- Red Hat Network
- Red Hat Network Server
- Entitlements
- Red Hat Network Client
- Hands-on Lab 2: Working with packages
Unit 3 - Kernel Services
- Objectives
- The Linux Kernel
- Kernel Images and Variants
- Kernel Modules
- Kernel Module Utilities
- Managing the initrd Image
- Accessing Drivers Through /dev
- Device Node Examples
- Managing /dev With udev
- Adding Files Under /dev
- Kernel Configuration With /proc
- /proc Examples
- sysctl : Persistent Kernel Configuration
- Exploring Hardware Devices
- Monitoring Processes and Resources
- Hands-on Lab 3: Configuring the kernel
Unit 4 - System Services
- Network Time Protocol
- System Logging
- syslog Configuration
- XOrg: The X11 Server
- XOrg Server Configuration
- XOrg in runlevel 3
- XOrg in runlevel 5
- Remote X Sessions
- SSH: Secure Shell
- VNC: Virtual Network Computing
- cron
- Controlling Access to cron
- System crontab Files
- Daily Cron Jobs
- The anacron System
- CUPS
- Hands-on Lab 4: System Services
Unit 5 - User Administration
- Adding a New User Account
- User Private Groups
- Modifying / Deleting User Accounts
- Group Administration
- Password Aging Policies
- Switching Accounts
- sudo
- Network Users
- Authentication Configuration
- Example: NIS Configuration
- Example: LDAP Configuration
- SUID and SGID Executables
- SGID Directories
- The Sticky Bit
- Default File Permissions
- Access Control Lists (ACLs)
- SELinux
- SELinux: Targeted Policy
- SELinux: Management
Unit 6 - Filesystem Management
- Objectives
- Overview: Adding New Filesystems to the Filesystem Tree
- Device Recognition
- Disk Partitioning
- Managing Partitions
- Making Filesystems
- Filesystem Labels
- tune2fs
- Mount Points and /etc/fstab
- Mounting Filesystems with mount
- Unmounting Filesystems
- mount By Example
- Handling Swap Files and Partitions
- Mounting NFS Filesystems
- Automounter
- Direct Maps
- gnome-mount
- Hands-on Lab 6: Adding New Filesystems to the Filesystem Tree
Unit 7 - Advanced Filesystem Management
- Configuring the Quota System
- Setting Quotas for Users
- Reporting Quota Status
- What is Software RAID?
- Software RAID Configuration
- Software RAID Testing and Recovery
- What is Logical Volume Manager (LVM)?
- Creating Logical Volumes
- Resizing Logical Volumes
- Logical Volume Manager Snapshots
- Using LVM Snapshots
- Archiving tools: tar
- Archiving Tools: dump/restore
- Archiving Tools: rsync:
- Hands-on Lab 7: Advanced Filesystem Mangement
Unit 8 - Network Configuration
- Objectives
- Network Inferfaces
- Driver Selection
- Speed and Duplex Settings
- IPv4 Addresses
- Dynamic IPv4 Configuration
- Static IPv4 Configuration
- Device Aliases
- Routing Table
- Default Gateway
- Configuring Routes
- Verify IP Connectivity
- Defining the Local Host Name
- Local Resolver
- Remote Resolvers
- Verify DNS Connectivity
- Network Configuration Utilities
- Transparent Dynamic Configuration
- Implementing IPv6
- IPv6: Dynamic Interface Configuration
- IPv6: StaticInterface Configuration
- IPv6: Routing Configuration
- New and Modified Utilities
- Hands-on Lab 8: Manage Network Settings
Unit 9 - Installation
- Anaconda, the Red Hat Enterprise Linux Installer
- First Stage: Starting the Installation
- First Stage: Boot Media
- Accessing the Installer
- First Stage: Installation Method
- Network Installation Server
- Second Stage: Installation Overview
- Configuring File Systems
- Advanced Partitioning
- Package Selection
- First Boot: Post-Install Configuration
- Kickstart
- Starting a Kickstart Installation
- Anatomy of a Kickstart File
- Kickstart: Commands Section
- Kickstart: Commands section
- Kickstart: Packages Section
- Kickstart: %pre, %post
- Hands-on Lab 9: Installation and System-Initialization
Unit 10 - Virtualization with Xen
- Virtualization with Xen
- Hardware Considerations
- Preparing Domain-0
- Virtual Resources
- Domain-U Configuration
- Installing a new Domain-U
- Domain Management with xm
- Activating Domains on boot
- Hands-on Lab 10: Exploring Virtualization
Unit 11 - Troubleshooting
- Method of Fault Analysis
- Fault Analysis: Gathering Data
- Things to Check: X
- Things to Check: Networking
- Order of the Boot Process
- Filesystem Corruption
- Filesystem Recovery
- Recovery Run-levels
- Rescue Environment
- Rescue Environment Utilities
- Rescue Environment Details
- Hands-on Lab 11: System Rescue and Troubleshooting
To determine your level of experience, take our pre-assessment questionnaires or read the descriptions below for the Standard and Rapid Tracks.
Here is one good recommendation from Blog O’ Matty
... I picked up a copy of the Red Hat Certified Engineer Linux Study Guide and read it from cover-to-cover. Michael Jang did a great job with the book, and it shed some light on things I never use (e.g., Linux printing).
Once I finished reading Michael’s book I printed the RHCE objectives. For each objective I did the following:
- Researched which packages are needed to support each objective.
- Installed the software from a local yum repository I created.
- Read through the configuration files for each service and looked up each directive to see what it did.
- Configured the service and integrated it with my home network.
- Broke the service various ways and tried to figure out what I needed to do to fix it.
- Figured out how SELinux integrated with each service. Also did a lot of SELinux debugging!
If you have opportunity attending Red Hat courses are a great learning experience. It's too expensive unless you company paid for them.
Courses you should take: | Level of Linux Expertise: | |||
---|---|---|---|---|
None | Some | Much | Expert | |
Standard Track * | Rapid Track ** | |||
RH033 Red Hat Linux Essentials | yes | |||
RH131
Red Hat System Administration or RH133 Red Hat Linux Administration (and RHCT Exam) |
yes | yes | ||
RH253 Red Hat Linux Networking and Security Administration | yes | yes | ||
RH300 Red Hat Rapid Track Course (and RHCE Exam) | yes | |||
RH302 RHCE Exam | yes | yes | yes |
The Standard Track consists of three courses -- RH033, RH133, RH253 -- and is aimed at persons who need more review of key concepts or who are new to both UNIX and Linux.
The Rapid Track consists of one course -- RH300 Red Hat Rapid Track Course (and RHCE Exam) -- and is aimed at persons who are experienced UNIX and Linux users, networking specialists, and system administrators and need specific Red Hat Enterprise Linux training to pass the RHCE Exam (which is included)
|
Switchboard | ||||
Latest | |||||
Past week | |||||
Past month |
Nov 02, 2018 | www.amazon.com
kievite, November 2, 2018 4.0 out of 5 stars
Some valuble tips. Can serve as fuel for your own thoughts.
This book is most interesting probably for people who can definitely do well without it – seasoned sysadmins and educators.
Please ignore the word "philosophy" in the title. Most sysadmins do not want to deal with "philosophy";-). And this book does not rise to the level of philosophy in any case. It is just collection of valuable (and not so valuable) tips from the author career as a sysadmin of a small lab, thinly dispersed in 500 pages. Each chapter can serve as a fuel for your own thoughts. The author instincts on sysadmin related issues are mostly right: he is suspicious about systemd and another perversion in modern Linuxes, he argues for simplicity in software, and he warns us about PHBs problem in IT departments. In some cases, I disagreed with the author, or view his treatment of the topic as somewhat superficial, but still, his points created the kind of "virtual discussion" that has a value of its own. And maybe it is the set of topics that the author discusses is the main value of the book.
I would classify this book as "tips" book when the author shares his approach to this or that problem (sometimes IMHO wrong, but still interesting ;-), distinct from the more numerous and often boring, but much better-selling class of "how to" books. The latter explains in gory details how to deal with a particular complex Unix/Linux subsystem, or a particular role (for example system administrator of Linux servers). But in many cases, the right solution is to avoid those subsystems or software packages like the plague and use something simpler. Recently, avoiding Linux flavors with systemd also can qualify as a solution ;-)
This book is different. It is mostly about how to approach some typical system tasks, which arise on the level of a small lab (that the lab is small is clear from the coverage of backups). The author advances an important idea of experimentation as a way of solving the problem and optimizing your existing setup and work habits. As well a very overview of good practices of using some essential sysadmin tools such as screen and sudo. In the last chapter, the author even briefly mentions (just mentions) a very important social problem -- the problem micromanagers. The latter is real cancer in Unix departments of large corporations (and not only in Unix departments)
All chapters contain "webliography" at the end adding to the value of the book. While Kindle version of the book is badly formatted (and I subtracted one star for that), the references in Kindle version are clickable, and I would recommend reading some them along with reading the book, including the author articles at opensource.com For example, among others, the author references a rare and underappreciated, but a very important book "Putt's Law and the Successful Technocrat: How to Win in the Information Age by Archibald Putt (2006-04-28)". From which famous Putt's Law "Technology is dominated by two types of people, those who understand what they do not manage and those who manage what they do not understand," and Putt's Corollary: "Every technical hierarchy, in time, develop a competence inversion" were originated. This reference alone is probably worth half-price of the book for sysadmins, who never heard about Putt's Law.
Seasoned sysadmins can probably just skim Part I-III (IMHO those chapters are somewhat simplistic. ) For example, you can skip Introduction to author's Linux philosophy, his views on contribution to open source, and similar chapters that contain trivial information ). I would start reading the book from Part IV (Becoming Zen ), which consist of almost a dozen interesting topics. Each of them is covered very briefly (which is a drawback). But they can serve as starters for your own thought process and own research. The selection of topics is very good and IMHO constitutes the main value of the book.
For example, the author raises a very important issue in his chapter 20: Document Everything, but unfortunately, this chapter is too brief, and he does not address the most important thing: sysadmin should work on some way to organize your personal knowledge. For example as a private website. Maintenances of such a private knowledgebase is a crucial instrument of any Linux sysadmin worth his/her salary and part of daily tasks worth probably 10% of sysadmin time. The quote "Those who cannot learn from history are doomed to repeat it" has a very menacing meaning in sysadmin world.
Linux (as of monstrous RHEL 7 with systemd, network manager and other perversions, which raised the complexity of the OS at least twice) became a way to complex for a human brain. It is impossible to remember all the important details and lessons learned from Internet browsing, your SNAFU and important tickets. Unless converted into documentation, most of such valuable knowledge disappears say in six months or so. And the idea of using corporate helpdesk as a knowledge database is in most cases a joke.
The negative part of the book is that the author spreads himself too thin and try to cover too much ground. That means that treatment of most topics became superficial. Also provided examples of shell scripts is more of a classic shell style, not Bash 4.x type of code. That helps portability (if you need it) but does not allow to understand new features of bash 4.x. Bash is available now on most Unixes, such as Solaris and HP-UX and that solves portability issues in a different, and more productive, way. Portability was killed by systemd anyway unless you want to write wrappers for systemctl related functions ;-)
For an example of author writing, please search for his recent (Oct 30, 2018) article "Working with data streams on the Linux command line" That might give you a better idea of what to expect.
In my view, the book contains enough wisdom to pay $32 for it (Kindle edition price), especially if you can do it at company expense. The books is also valuable for educators. Again, the most interesting part is part IV:
Part IV: Becoming Zen 325
Chapter 17: Strive for Elegance 327
- Hardware Elegance 327
- ThePC8 328
- Motherboards 328
- Computers 329
- Data Centers 329
- Power and Grounding 330
- Software Elegance 331
- Fixing My Web Site 336
- Removing Crutt 338
- Old or Unused Programs 338
- Old Code In Scripts 342
- Old Files 343
- A Final Word 350
Chapter 18: Find the Simplicity 353
- Complexity in Numbers 353
- Simplicity In Basics 355
- The Never-Ending Process of Simplification 356
- Simple Programs Do One Thing 356
- Simple Programs Are Small 359
- Simplicity and the Philosophy 361
- Simplifying My Own Programs 361
- Simplifying Others' Programs 362
- Uncommented Code 362
- Hardware 367
- Linux and Hardware 368
- The Quandary. 369
- The Last Word
... ... ...
Chapter 20: Document Everything 381
- The Red Baron 382
- My Documentation Philosophy 383
- The Help Option 383
- Comment Code Liberally 384
- My Code Documentation Process 387
- Man Pages 388
- Systems Documentation 388
- System Documentation Template 389
- Document Existing Code 392
- Keep Docs Updated 393
- File Compatibility 393
- A Few Thoughts 394
Chapter 21: Back Up Everything - Frequently 395
- Data Loss 395
- Backups to the Rescue 397
- The Problem 397
- Recovery 404
- Doing It My Way 405
- Backup Options 405
- Off-Site Backups 413
- Disaster Recovery Services 414
- Other Options 415
- What About the "Frequently" Part? 415
- Summary 415
... ... ...
Chapter 26: Reality Bytes 485
- People 485
- The Micromanager 486
- More Is Less 487
- Tech Support Terror 488
- You Should Do It My Way 489
- It's OK to Say No 490
- The Scientific Method 490
- Understanding the Past 491
- Final Thoughts 492
Nov 02, 2018 | www.amazon.com
This book is most interesting probably for people who can definitely do well without it – seasoned sysadmins and educators.
Please ignore the word "philosophy" in the title. Most sysadmins do not want to deal with "philosophy";-). And this book does not rise to the level of philosophy in any case. It is just collection of valuable (and not so valuable) tips from the author career as a sysadmin of a small lab, thinly dispersed in 500 pages. Each chapter can serve as a fuel for your own thoughts. In many cases, I disagreed with the author, but still, his points created the kind of "virtual discussion" that has a value of its own.
I would classify this book as "tips" book when the author shares his approach to this or that problem (often IMHO wrong, but still interesting;-), distinct from the more numerous and often boring, but much better-selling class of "how to" books. The latter explains in gory details how to deal with a particular Unix/Linux subsystem or a particular role (for example system administrator of Linux servers). But in many cases, the right solution is to avoid those subsystems or software packages like plague, and use something simpler ;-)
This book is different. It is mostly about tips on how to approach this or that typical system task, which arises of the level of a small research lab (that is clear from his coverage of backups). As well a very brief overview of good practices of using some tools. In the last chapter, the author even briefly mentions (just mentions) a very important social problem -- the problem micromanagers. The latter is real cancer in Unix departments of large corporations (and not only in Unix departments ;-)
All chapters contain "webliography" at the end adding to the value of the book. While Kindle version of the book is formatted (and I subtracted one start for that), they are clickable.
The books provide authors views (not always right, but still interesting) on why this or that particular feature should be used and how it can be combined with other. Seasoned sysadmins can probably skip Part I-III (IMHO those chapters are simplistic ( for example you can skip Introduction to the Linux philosophy, contribution to open source, and similar weak chapters ) and start with Part IV ( Becoming Zen ) , which consist of almost a dozen interesting topics. They are covered very briefly, just to serve as a starter for your own thought process. But the selection of topics is very good.
He raises a very important issue in his chapter 20: Document Everything, but unfortunately, this chapter is too brief and does not address the way to organize your personal "knowledgebase" which now should be a crucial instrument of any Linux sysadmin worth his/her salary. Linux (as of monstrous RHEL 7 with systemd and other perversions, which raised the complexity of the OS at least twice) became a way to complex for your brain to remember all the important details and lessons learned from Internet browsing, your SNAFU and important tickets.
The negative part of the book is that the author spreads himself too thin and try to cover too much ground. That means that treatment of some topics became superficial. Also provided examples of shell scripts is more of a classic shell style, not Bash 4.x type of code. That helps portability (if you need it) but does not allow to understand new features of bash 4.x. Bash is available now on most Unixes, such as Solaris and HP-UX and that solves portability issues in a different, and more productive, way. Portability was killed by systemd anyway unless you want to write wrappers for systemctl related functions ;-)
For an example of author writing, please search for his recent (Oct 30, 2018) article "Working with data streams on the Linux command line" That might give you a better idea of what to expect.
In my view, the book contains enough wisdom to pay $32 for it (Kindle edition price). Especially for educators.
Full contst is at The Linux Philosophy for SysAdmins And Everyone Who Wants To Be One
Again, the most interesting part is part IV:
Part IV: Becoming Zen 325
Chapter 17: Strive for Elegance 327
- Hardware Elegance 327
- ThePC8 328
- Motherboards 328
- Computers 329
- Data Centers 329
- Power and Grounding 330
- Software Elegance 331
- Fixing My Web Site 336
- Removing Crutt 338
- Old or Unused Programs 338
- Old Code In Scripts 342
- Old Files 343
- A Final Word 350
Chapter 18: Find the Simplicity 353
- Complexity in Numbers 353
- Simplicity In Basics 355
- The Never-Ending Process of Simplification 356
- Simple Programs Do One Thing 356
- Simple Programs Are Small 359
- Simplicity and the Philosophy 361
- Simplifying My Own Programs 361
- Simplifying Others' Programs 362
- Uncommented Code 362
- Hardware 367
- Linux and Hardware 368
- The Quandary. 369
- The Last Word
... ... ...
Chapter 20: Document Everything 381
- The Red Baron 382
- My Documentation Philosophy 383
- The Help Option 383
- Comment Code Liberally 384
- My Code Documentation Process 387
- Man Pages 388
- Systems Documentation 388
- System Documentation Template 389
- Document Existing Code 392
- Keep Docs Updated 393
- File Compatibility 393
- A Few Thoughts 394
Chapter 21: Back Up Everything - Frequently 395
- Data Loss 395
- Backups to the Rescue 397
- The Problem 397
- Recovery 404
- Doing It My Way 405
- Backup Options 405
- Off-Site Backups 413
- Disaster Recovery Services 414
- Other Options 415
- What About the "Frequently" Part? 415
- Summary 415
... ... ...
Chapter 26: Reality Bytes 485
- People 485
- The Micromanager 486
- More Is Less 487
- Tech Support Terror 488
- You Should Do It My Way 489
- It's OK to Say No 490
- The Scientific Method 490
- Understanding the Past 491
- Final Thoughts 492
Oct 08, 2018 | www.amazon.com
5.0 out of 5 starsBy kievite on October 8, 2018
This is a better primary book for self-study then Michael Jang and Alessandro OrsariaThis book is a better primary book for self-study then Michael Jang and Alessandro Orsaria's book. The material is more logically organized and explained and is easier to follow. The author provides a few valuable tips, which I did not find in any other book.
RHEL 7 looks like a different flavor of Linux, not a continuation of RHEL 6 in many respects, and first of all due to addition of systemd and replacement of many previously used daemons (NTP daemon, firewall daemon, etc) as well as inclusion into the exam new topics such as built-in virtualization capabilities.
That means that the amount of material in RHEL 7 exam is much larger than in RHEL 6 exam and different topics are stressed (systemd, virtual machines, more complex networking staff including setting up kickstart, etc.). Michael Jang book is an adaptation of RHEL 6 book. This book is written for RHEL 7 from the ground up, and this is an important advantage.
As for which book to use, either-or is a naïve approach. You need to use both, especially, if the exam is paid from your own pocket, as a failure will cost you $400. Just don't take the failure too seriously -- the table is stacked against self-study folk like you -- and the second time you will do much better.
I just recommend you to use this one as the primary book. You should use Jang book too, as some information in it is missing in this book but, for example, I like better how such an important topic as how to recover root password is explained in this book.
I like his recommendation to use CentOS instead od RHEL for the preparation for the exam. This is a reasonable approach although there are some low-cost RHEL subscriptions as well. Using a plain vanilla RHEL without subscription makes the installation of software difficult as you do not have access to repositories. This is an important plus of this book.
I also noticed the attention to details that can be acquired only by actually working of RHEL for years, not just writing books -- for example the author mentions -A and -B options in grep, while Jang does not. Unfortunately, the differences between grep and egrep and when you need to use egrep (or grep -E) are not explained well in both books.
There are some reviews which concentrate on typos (yes, for example, the option -E typeset as -e in some examples) but this is a pretty naïve criteria to judge the book on such a complex topic. Of course, there will be multiple typos, but fixing them is a part of training and they do not diminish the value of the book, as those readers who can't fix are not ready to take the exam anyway. And if the person who supposedly passed RHEL 6 exam complains about such trivial staff, there is something fishy if his/her approach to the topic.
Generally breaking the configuration and then fixing it should be an important part of training and this book at least gives some hints of how to deal with booting problems (which are multiplied in RHEL 7 due to systemd craziness)
More important is an implicit level of the author who writes the book. A4nd my impression is that the level of Sander van Vugt is higher.
Red Hat exam stresses many Red Hat specific topics and as such taking it plunges you into priorities of Red Hat that were unknown to you. You can expect that some of those priorities/topics are peripheral to that you are doing at your job, and you will be taken by surprise the first time you take the exam, even if you deligently stidied the book and did all exercises. In this sense, it is better to pay for exam twice then to attend more expensive "Fast track" course, if you are paying money from your own pocket.
There are a lot of posts on the Internet about how easy is to pass this exam -- I do not trust them. While all materials are entry level and the resulting qualification is also entry level the mere amount of material is overwhelming and presents substantial difficulties even for people who administer RHEL and/or CentOS/Oracle Linux/Academic linux for many years.
Paperback: 1072 pages
Publisher: McGraw-Hill Education; 6 edition (July 8, 2011)
Language: English
ISBN-10: 0071765654
ISBN-13: 978-0071765657Ken Aldrich on December 19, 2011
Good for a newbie - despite what some reviewers say I'm a linux Newbie. I've never installed or configured it. I looked at the available books on the subject and chose this one. Even though this book is targeted towards those trying to achieve certifications, I find the practical approach to the book useful.
I like the book because he takes you through, step by step, how to set up machines and perform tasks. There are special margin notes on what things you might focus on if you're taking the exam, and what things you might focus on if you're trying to learn this for a job.I read some of the negative reviews before purchasing. After having read through the first two chapters and completing the labs, I have these several things to say:
1) If you were confused about what resources you needed to allocate to the VMs, then you did not pay close enough attention. There is no confusion about how many GBs you should allocate to the Host VM you're setting up and the VMs inside. I did view the errata documents the author posted on the publisher's website. I did not find any of the information there "critical" to understanding the book. I'd have gotten by just fine without having to review that PDF document that illustrates the relationships of the VMs. I'd have gotten by without having to review the textual corrections.2) I have had no confusion about which IPs to assign to which machines. Although, I will admit, due to the effects of an intermittently faulty old switch I was using for my testlab, I did have some confusion on one point. Just know this about the KVM virtual machines and networking. When you set up the virtual network of 192.168.221.x inside the VM host, it is an entirely separate virtualized network. You do not need to have an external router handling gateway, DNS, DHCP, etc for the 192.168.221.x network. For example, the NIC on my physical machine (the KVM host) had an IP of 10.10.10.160 which allowed me to have it on my own home network. However, for VMs inside, it would access my KVM host at 192.168.221.1 because it was also the gateway for the virtual network. I didn't need to have multiple NICs on my physical machine. It was all handled virtually. It all just works like you'd want it to work. To some, this may be obvious. However, I was questioning it because it wasn't working due to squirrely hardware.
3) When reading through the chapters you will encounter Exercises. At first I was under the impression that I should be following along and performing these exercises in my test environment. I since learned that you should hold off until you reach the end of the chapter to do the labs. I recommend reading through the exercises and absorbing the material, but you will get plenty of chance to perform those tasks when you do the labs. What is important is the labs will give you some more specific instructions that you do not encounter during the Exercises. These specific instructions are important for setting up the machines in a way that will be important in later chapters. When you do the labs, you'll basically page back in the book and follow along the exercises, performing those operations on your machines.
4) Some of the reviews expressed frustration over how much the author "skips around". I can sort of see where that is coming from. Take this quote from Chapter 2 in the book, "...you can also connect the local system to the installation source created in Chapter 1, Lab 2 using the techniques described in Chapter 7." For some, that can be a source of logical frustration. What happened is that while you were doing something in Chapter 1 of the book, the author referenced techniques in Chapter 7... something you haven't even read yet. Not only that, now we're in Chapter 2 and he's referencing something in Chapter 1 that referenced something in Chapter 7. Believe it or not, this is not an uncommon occurrence in the book. I think this frustrates some readers. I am here to say that you don't have to let it bother you, just ignore it. So far, not ONCE have I had to go forward to a later chapter to understand the content. Actually, the author is being very helpful here. The "forward reference" to a chapter later in the book, so far for me, has always been an Optional reference that provides more detail about a subject. You don't need to know that "more detail" to accomplish the current task. Those "forward references" are likely more useful for more advanced users that want to delve deeper into a topic the first time it is broached. Newbies, like me, can just ignore for now. So while it can seem to read like the author is skipping all over the darn place... you don't have to. I'm just reading and going forward in line. The content builds on itself in a very logical and helpful way. The only "skipping" I do is when I get to the labs after I've read the chapter, is I skip back to the relevant exercises in the chapter so I can see his examples and follow along. I like it because it exposes me to the material twice. The first time I'm just reading through the exercises and it exposes me to the content in a context with the rest of the material. Then I go back and actually DO IT on my test machines to help solidify what I've learned.
I hope this helps some people that read some of the reviews and are reticent to choose this book. I'm a total newbie and in less than a day I've learned to install the server from CD with many packages, update it, set up FTP and HTTP servers, share out the install files for Red Hat, set up Virtual Machine host, create some machines inside of there by using the install files I shared out from the server.... all this while using an automated Kickstart answer file. This is a very hands on approach that lets you DO this stuff at very minimal cost. I bought a cheap Athlon X2, 64-bit computer with 8 gigs of RAM and a 500 Gig hard drive.
I'm able to practice networking machines together, testing access to resources through the firewall (from multiple virtual test subnets), etc, etc all on that one investment of $300 of hardware.
This book was the right choice for me.
Paperback: 960 pages
Publisher: Sams; 8 edition (February 14, 2008)
Language: English
ISBN-10: 0672329778
ISBN-13: 978-0672329777Nikolai N Bezroukov
This is an excellent book. Highly recommended,February 21, 2011 To write a good intro book for the huge and complex distribution like Fedora is a very difficult task. The spectrum of users is too wide and selection of the topics is even wider. That means that some category of users always be dissatisfied. Authors managed to solve this dilemma in their own unique way and created a really excellent book that contain wealth of information for beginners, but some interesting tips for seasoned system admin as well.
One of the important advantages of the book is that the authors use MC (Midnight commander) as a tool for performing some tasks (including important task of undeletion of files on Ext3/Ext4 filesystems). This selection instantly made treatment of those topics superior to the same treatment in Sobey's books. The other positive feature of the book is that they introduce and explain how to use sudo -- a rare feature for an intro book. Using screen is also explained in the book. Such important topics as bootup, backup of your filesystems and adding default router are also covered well.
The authors pay due attention to scripting and provide many useful rudimentary scripts for performing various tasks. Generally Parts III, IV and V are very strong and alone are worth the price of the book. So you can view parts I and II as a bonus.
As for shortcomings I would remove information about using C/C++ and Mono from the book and increased the coverage of bash. Inclusion of too many languages unnecessarily complicated the book.
Generally this is a good book on a very difficult to cover topic. Highly recommended.
Paperback: 1224 pages Publisher: Prentice Hall; 5 edition (February 21, 2010) Language: English ISBN-10: 0137060882 ISBN-13: 978-0137060887
- Paperback: 1104 pages
- Publisher: Wiley; Package edition (May 10, 2006)
- Language: English
- ISBN: 0471754919
- Product Dimensions: 9.1 x 7.4 x 2.4 inches
- Shipping Weight: 3.65 pounds
- average customer review: ***** based on 5 reviews.
In this book, you'll learn how to:
- Install Fedora and perform basic administrative tasks
- Configure the KDE and GNOME desktops
- Get power management working on your notebook computer and hop on a wired or wireless network
- Find, install, and update any of the thousands of packages available for Fedora
- Perform backups, increase reliability with RAID, and manage your disks with logical volumes
- Set up a server with file sharing, DNS, DHCP, email, a Web server, and more
- Work with Fedora's security features including SELinux, PAM, and Access Control Lists (ACLs)
- Paperback: 338 pages
- Publisher: O'Reilly Media; 3 edition (February 8, 2005)
- Language: English
- ISBN: 0596005482
- average customer review: based on 5 reviews.
- Amazon.com
Average tech book for the Linux crowd - not Unix crowd, May 17, 2004
- Paperback: 600 pages ; Dimensions (in inches): 1.22 x 9.20 x 7.02
- Publisher: APRS; 1 edition (September 1, 2003)
- ISBN: 1590592123
- Average Customer Review: Based on 5 reviews.
- Amazon.com Sales Rank: 22,795
If what you want is a bok that's a cross platform as the title suggests, this might not be a book worth buying. Examples in this book make horrible assumptions, along the lines of removing all native commands and replacing them with GNU commands. In a Linux only environment, this may not be a problem. In many other environments where enterprise level support isn't a concern, this may also be acceptable. But the place where automation is needed the most is the larget enterprise production environments. While ideas and basic tennets outlined in this book are what you ultimately need, the scope of the examples have problems scaling beyond 20-100 systems, let alone 5,000+. As for the basic tennets, you can cheat and be reminded what they are: common configurations, keep good documentation as to the differences, and manage systems, in a secure manner, in a common fashion that relies on the common configuration and documented differences.The errors and ommissions in this book should be easily caught by any technical senior administrator of the OSes in question. For me, that's Solaris and Linux.
For a Linux only environment, it is a solid book. The writing style is drier than most of the manuals I read from various Unix/Linux vendors, and truly is the first tech publication since I supported PBX systems to put me to sleep.
As for the "subjective" analysis of various tools to assist in automation, I was highly disappointed. On various occasions, only 2 or 3 tools were discussed in an attempt to make the assesments fair. In each case, I came up with twice as many tools that I use on a regular basis, that were also F/OSS (as was usually the criteria the author used to talk about a product) that perform similar, if not identical, tasks much better. And those tools aren't that new: most predate the tools he refers to. Plus, most Linux distributions come with them installed and configured by default!
Since all I got out of the book were the above tennets that I already have known for the past 10+ years, I was VERY disappointed. Just make sure you know who you're letting borrow your copy, and what is expected that they'll take away, otherwise you'll end up with junior admins scripting their way into destroying your enterprise.
A reader from Milano, MI Italy
- Used & new from $22.85
- Paperback: 608 pages ; Dimensions (in inches): 1.52 x 8.96 x 7.50
- Publisher: Sybex; ; 1st edition (February 15, 2001)
- ISBN: 0782127355
- Average Customer Review: Based on 14 reviews.
- Amazon.com Sales Rank: 32,868
A honest book for Linux primers, April 15, 2002
This is a honest book for a Linux primer. It is simple and clear, but with some strange holes (p.e. nothing on ext2 fs attributes, or FTP).
There are also several errors (typos or similar) in the examples and figures that I would like to be removed in a next edition.A reader from Montgomery, AL United States
A reader from silver spring, MD United StatesSolid Book, December 20, 2001
Great book to get you started with Linux Admin. Covers many issues a sys admin is expected to know. However it doesn't cover ftp. It just mentions it.
It has a pretty good chapter on Sendmail.
To get your server up and running I would recommend Kabir's RedHat book.
Stanfield's book will help you mantain the server.
Don't miss the all new Linux Administration Handbook ISBN 0-13-008466-2.
john_patrick_hoke (see more about me) from Floral Park, NY United StatesTrue Linux System Administration, June 22, 2001
One of my Unix lab professors once said that Unix was so vast that one lifetime is not enough to really get to master all aspects of it. After reading several Unix/Linux books, this operating system still remained somewhat of a mystery.
Thanks to the authors of this book, I can really say that I'm well on my way to a decent level of proficiency. No question, this book is of the highest quality. The material is presented and explained in such a way, you get a sense that the authors truly possess a profound understanding of the SA and Linux fields. The book tries to be distribution neutral by covering Redhat linux (vesion 6 to 7) and dishing out to other distributions (especially Debian) when things are done differently.
Unlike other books that are recipe oriented or adaptations of technical documents, this is a true SA book because it helps you gain control of your Linux system.
Alex Valentine (see more about me) from State College, PA United StatesBrings the beginners to the next level..., September 30, 2002
This book is perfect for the person who has been tinkering with Linux long enought to have started outgrowing the GUI based tools that the distros are spoon feeding users with.
This book takes a reader who is ready to leave webmin or other "wizard" approaches behind and wants to take the bull (er... config files) by the horns and REALLY control their machines.
The vendor/distro neutral coverage is fair and even handed, giving time to both Redhat based distros as well as Debian.
If you are itching to stop having to point and click all over the place to change a line in a config file, and are ready to learn the faster, quicker, less error prone way... here you go!
Become an SA :)
Well Written and Current, June 20, 2002
Linux System Administration does a great job of covering a vast amount of Linux topics with just the right amount of detail for most users. This book appeals to a wide variety of readers, it is written in way that doesn't scare off newbies, but manages to have enough meat for experienced Linux users. The great thing about this book is it spends a fair amount of time explaining how to do things on a variety of distros.
Parts of the book that stand out in my mind are the chapters dealing with kernel recompilation, scripting and security. The kernel recompilation chapter is by far the best material I've seen on the subject to date, it almost makes kernel recompilation sound too easy. The security chapter is good starting point for sysadmins that are new to Linux. The book also provides a nice little introduction to scripting, although if your going to be a Linux sysadmin, the Orielly books on bash and perl are a must.
There were very few things that I didn't like about this book. One thing that stands out in my mind is the author's insistence on using paper journal books for logging system changes. With the proper backup procedures in place, a web based system log is a much more efficient way of keeping tracking of changes. Overall, the book is must read for anyone new to Linux and is also a good pickup for seasoned Linux users. I've been recommending this book over Running Linux as of late, since the Oreilly offering is showing its age.
for admins, not your mom, December 4, 2002
Reviewer: Kip Perkins (see more about me) from Old Hickory, TN United StatesI picked up this book because I have used the 2nd and 3rd editions of UNIX Administration Handbook for years. This book is easy to read and provides some entertainment with the authors' insight into Linux administration. As with it's brother the UAH, this book follows the same format but IS updated to reflect the Linux specifics. I picked it up also because it covers RH 7.2 and the UAH only covered 6.2. This book is a must for people who admin linux servers for large corporations, small businesses, or simply are running their own mail/dns/web server from their DSL connection at home.
If you are looking for a book that gets you setup on KDE or GNOME, this is not the book. If you want to learn and use the power of a networked Linux server, this is for you.
I have worked with UNIX for 6 years, Linux for 5 and recommend this book to anyone who will admin it.
- Paperback: 560 pages ; Dimensions (in inches): 1.03 x 9.27 x 7.43
- Publisher: Addison Wesley Professional; ; 1st edition (September 18, 2001)
- ISBN: 0201719347
- Average Customer Review: Based on 13 reviews.
Vince Scimeca from Connecticut
Robert Gamble (see more about me) from Falmouth, MA United StatesTop notch linux book for all!!, November 4, 2002
Marcel Gagne's Linux System Administration A User's Guide is by far the best book on linux I have read. I have gone through a number of different books regarding linux, but this one I find myself refering back to over and over again. There is something in here for seasoned linux administrators and linux newbies alike. If you are looking for a one stop shop linux book this is it!! In the past I would have to refer to a number of different books to find what I needed, but this book has it all. Easy to read and understand. Top notch job - highly recommended!
Vince Scimeca
Senior IT Manager
JupitermediaGreat for the 'non-idiot' or 'non-dummy'., August 12, 2002
Simply put, this book is probably one of the best choices for a new user to Linux who has computer experience, and possibly previous UNIX experience. I'm not sure how it would be as a beginner's book because I wasn't a beginner, but I think it would work well as a second book certainly. Even for a beginner, most of the important parts of Linux are focused on. The emphasis is on the basic areas that are important for the average user, or a small business system's administrator. Topics include the file systems, how to do backups, how to set-up hardware (including my personal bugaboo - printers), how to manage users, some good security information, how to use the various GUIs, how to automate tasks, how to get started with programming, etc. Areas like Apache, sendmail and nameservers are covered enough to get started with them, which is probably enough for the average user. One of the strengths is that the book points out ways to use the command prompt and then at least two other (usually) ways to do the same thing with the two most popular windowing systems Gnome and KDE.
Another strength is that the book expects you to try things. A topic is introduced, some basic ways to do things are shown and then usually at least one or two more advanced topics, followed by encouragement to explore. There is no CD included, but numerous http links are given throughout.
This book is the one I open first when I have a question that needs answering and should be in most Linux bookshelves. It's easy to read, with some humor sprinkled throughout. The author assumes you're intelligent, which is greatly appreciated. Most of all, the book teaches ways for the home user or small business user to get the most out of their investment.
Extremely Readable, November 20, 2001
Reviewer: Brad Sanders from Cambridge, Ontario, Canada
Mr. Gagne exhibits a very easy reading style when explaining a subject as complex as Linux. The writing style is not too "techie" as to assume you possess extensive knowledge of the subject while at the same time doesn't treat you as if you're an idiot and know nothing - it stikes a very nice balance that makes for good reading. He actually makes what many would consider a dull subject interesting by injecting humor and variety.
Mr. Gagne includes only pertinent information that is both practical and useful. He doesn't dwell on the theoretical or any side issues.
In summary, I believe he achieves the goal of the book - to provide sufficient information to the reader in order for them to become an effective administrator of a Linux system.
Comprehensive, clear, and witty, November 5, 2001
Reviewer: Robert J. Sawyer (see more about me) from Mississauga, ON Canada Gagne, author of the popular "Cooking with Linux" columns in LINUX JOURNAL, has brought his trademark wit and whimsy to the topic of Linux system administration. Authoritative, clearly written, well-organized, comprehensively indexed -- this is an indispensible reference volume, flawlessly executed. Bravo!
You've asked for it; now it's here: the second edition of The UNIX CD Bookshelf, containing a powerhouse of updated books from O'Reilly, plus the software from UNIX Power Tools--all on a convenient CD-ROM. A bonus print copy of UNIX in a Nutshell, 3rd Edition, is also included. The CD-ROM supplies UNIX in a Nutshell, System V Edition;UNIX Power Tools, 2nd Edition (with software); Learning the UNIX Operating System, 4th Edition; Learning the vi Editor, 6th Edition; sed & awk, 2nd Edition; and Learning the Korn Shell. Never has it been easier to learn, or look up, what you need to know online. Formatted in HTML, The UNIX CD Bookshelf can be read by any web browser. The books are fully searchable and cross-referenced. In addition to individual indexes for each book, there's a master index for the entire library is provided. --This text refers to an out of print or unavailable edition of this title.
by Mark G. Sobell
[email protected] from Seattle, USA , April 14, 1999 *****
The perfect combination!
This book toes a very difficult line between being a textbook with tutorials
and a reference guide, and it succeeds admirably. For the intermediate computer
user who is new to Linux, the book provides excellent instructions, with relevant
questions at the end of each section. For the seasoned Linux user, it provides
a good reference. If you have Linux up and running but are looking for a well
laid out format by which you can proceed, this is the book for you. It is not
a compilation of man pages, nor is it an installation guide. It is a well structured
means to aquire skills.
Solid read, February 20, 2003
Reviewer: John Read from Oceanside, CA United States New users to Linux (Power Users or Windows Admins) will find this book a solid read. I'm not sure how it would be as a beginner's book with no previous experience. I suppose even a beginner could use it, since it covers all the important parts of administration, Linux or whatever. It contains lots of skill building exercises and projects, as well as reusable blueprints. It emphasizes basic areas small business system's administrators would use It covers topics like file systems, backups, printers, user management, security (SSH), various GUIs, task automation, etc. It covers stuff like Apache, sendmail and nameservers, talking to Windows with Samba, exceptionally well.
***+ Average.
is just what it says, June 11, 2000
If you are familiar with Linux or Unix and want to start into some network services, this book is a solid introduction. As the title says, this book is for beginner's, but the author doesn't assume that means weenie. He has done a nice job of selecting basic tasks, and for each one lays out the commands, file locations, and basic configurations for the files. Other books either relied on GUI utilities, or used twice as many pages going into too much detail on some sections and not enough on others. This book is just what it says, a beginner's
guide to help you get started with Linux servers and/or integrating
Linux into an existing NT network |
Great for MCSEs!, April 8, 2002
Steve Shah clearly presents Linux concepts and common administrative tasks in a straight forward manner. For those of us more accustomed to the MS Windows world, he frequently compares the way Linux works to Windows 2000. A must have for MCSEs living in a heterogeneous network environment! |
**** Good.
Paperback: 1072 pages
Publisher: O'Reilly Media; 1 edition (December 29, 2005)
Language: English
ISBN-10: 0596002556
ISBN-13: 978-0596002558Harvey Sugar: 5.0 out of 5 stars The best Linux networking software book to start with, October 14, 2006
I have read a number of books on the TCP/IP protocols and their implementations; both the original Berkeley (BSD) Unix TCP/IP stack and the Linux TCP/IP stack. I must say that this is the best of all of them.
This book makes the subject very approachable for the newcomer to network protocol software but the explanations are detailed enough to satisfy an old dog like me. Benvenuti's writing style is clear and very readable. He liberally provides diagrams to illustrate the concepts he is discussing.
My only fault with the book is that the transport layer protocols (UDP and TCP) are not covered. Benvenuti provides a list of important areas of the networking software that are not covered in the book but gives other references for most of these. I hope that he is working on a volume 2 to cover these areas.
I would sum up by saying that if you want to learn about the Linux networking software or network protocol software in general, start with this book. This book will give you the background to understand other, less well written books that cover the remaining networking software topics.
- Paperback Our Price:$39.99
You Save: $10.00 (20%)
Nicholas D. Wells, Nicholas Wells / Paperback / Published Feb. 1998
Caldera based (CD includes Caldera Lite). The author definitely know staff he is writing about. Book can be considered as a 1997 book and is already slightly outdated especially software. Contains much information is on strategic level and will not help you to install and run the system. Some imporant isuue are not covered in details (connection to ISP). IDG site
Warren Gay / Paperback / Published 2000
Our Price: $25.49 ~
Society
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
Quotes
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
Classic books:
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|
You can use PayPal to to buy a cup of coffee for authors of this site |
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.
Last modified: November 06, 2018