Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Red Hat Enterprise Linux Troubleshooting Guide

You're reading from   Red Hat Enterprise Linux Troubleshooting Guide Identify, capture and resolve common issues faced by Red Hat Enterprise Linux administrators using best practices and advanced troubleshooting techniques

Arrow left icon
Product type Paperback
Published in Oct 2015
Publisher
ISBN-13 9781785283550
Length 458 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benjamin Cane Benjamin Cane
Author Profile Icon Benjamin Cane
Benjamin Cane
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Troubleshooting Best Practices 2. Troubleshooting Commands and Sources of Useful Information FREE CHAPTER 3. Troubleshooting a Web Application 4. Troubleshooting Performance Issues 5. Network Troubleshooting 6. Diagnosing and Correcting Firewall Issues 7. Filesystem Errors and Recovery 8. Hardware Troubleshooting 9. Using System Tools to Troubleshoot Applications 10. Understanding Linux User and Kernel Limits 11. Recovering from Common Failures 12. Root Cause Analysis of an Unexpected Reboot Index

Understanding /dev


The /dev directory is a special directory where the contents are created by the kernel at installation time. This directory contains special files that allow users or applications to interact with physical and sometimes logical devices.

If we look at the previous ls command's results, we can see that within the /dev directory there are several files that begin with sd.

In the previous chapter, we learned that files that start with sd are actually seen as SCSI or SATA drives. In our case, we have both /dev/sda and /dev/sdb; this means, on this system, there are two physical SCSI or SATA drives.

The additional devices /dev/sda1, /dev/sda2, /dev/sdb1, and /dev/sdb2 are simply partitions of those disks. In fact, with disk drives, a device name that ends with a numeric value is often a partition of another device, just as /dev/sdb1 is a partition of /dev/sdb. While there are of course some exceptions to this rule, it is often safe to make this assumption when troubleshooting disk...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime