- •About the Author
- •Credits
- •How This Book Is Organized
- •Part I: Linux Basics
- •Part II: Installation
- •Part III: Configuration
- •Part IV: Administration
- •Part V: Maintaining the Linux System
- •How Each Chapter Is Structured
- •How to Use This Book
- •Conventions Used in This Book
- •What is Linux?
- •The origin of UNIX
- •Who started Linux?
- •Understanding Open Source
- •Understanding Closed Source
- •Understanding Artistic License
- •Is Freeware really free?
- •Is Shareware never free?
- •A comparison and contrast of licensing methods
- •The Growth of Linux
- •Linux on a Personal Computer
- •Graphical installation
- •Hardware detection
- •Graphical user interface
- •Linux limitations on the PC
- •Linux succeeds on the PC
- •Linux on workstations
- •Linux on servers
- •Summary
- •Assessment Questions
- •Scenarios
- •Answers to Chapter Questions
- •Assessment Questions
- •Scenarios
- •Linux Kernel
- •Kernel versions
- •Kernel availability
- •Linux Distributions
- •Beehive
- •BlueCat
- •Caldera OpenLinux
- •Debian
- •Corel
- •DragonLinux
- •Elfstone
- •Gentoo
- •Hard Hat Linux
- •KRUD
- •LinuxPPC
- •Mandrake
- •Phat Linux
- •Slackware
- •StormLinux
- •SuSE
- •TurboLinux
- •Yellow Dog Linux
- •Mini and Specialty Distributions
- •Astaro
- •KYZO
- •FlightLinux
- •NetMAX
- •Packages and Packaging Solutions
- •Red Hat Package Manager
- •Debian Package Management System
- •Tarball
- •Linux Resources
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Assessment Questions
- •Scenarios
- •Linux In the Real World
- •Word Processing
- •Spreadsheets and databases
- •Web browsing
- •File transfer
- •More, more, and more applications
- •The Server and DNS
- •A Linux Web server
- •Linux e-mail server
- •File servers
- •Proxy, news, and search servers
- •FTP servers
- •Firewalls
- •Determining Linux Roles and Services
- •Comparing Linux with other operating systems
- •Hardware compatibility
- •Summary
- •Assessment Questions
- •Scenarios
- •Answers to Chapter Questions
- •Assessment Questions
- •Scenarios
- •Installing Linux
- •Final Preparations for Installation
- •Verification
- •Package selection
- •Final hardware verification
- •Pre-installation partitioning planning
- •Installing Linux
- •Text or GUI installation
- •Basic setup of Linux
- •Selecting the machine type
- •Partitioning the hard disk drive
- •Installing a boot manager
- •Creating the Boot Diskette
- •Networking
- •Additional installation information
- •Accounts and passwords
- •Additional packages to install
- •GUI installation
- •Obtaining video card information
- •Configuring the X windows system
- •Selecting the windows manager or desktop environment
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Answers to Assessment Questions
- •Scenarios
- •Alternative to the GUI Installation
- •Command Line installation
- •Install the Linux system
- •Network installations of Linux
- •Review of a Linux Installation
- •Installation media
- •Initial selections
- •Installation type or class
- •Disk partitioning and formatting
- •Installing LILO
- •Network configuration
- •User accounts
- •Authentication methods
- •Package selection and installation
- •A Dual-Boot Installation of Linux
- •Linux with Microsoft Windows
- •Linux with Microsoft Windows NT and 2000
- •Linux and Solaris
- •Linux and other operating systems
- •Installing Additional Software with gzip and tar
- •Installing Additional Software with RPM
- •Removing software with RPM
- •Upgrading software with RPM
- •Query the RPM software
- •Verify the RPM software
- •Verify the package files
- •Upgrading the Kernel
- •Upgrading a Linux Kernel
- •System Log Files
- •The Final Test of the Installation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •What is the X Window System?
- •The X Window System
- •X Client and Server communications
- •X Window Manager
- •Configuring X Window Systems
- •Custom X Window System Programs
- •Manual Configuration of the X Window System
- •Documentation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Basic Network Services
- •TCP/IP Protocol Suite
- •Connection protocols needed
- •Other network protocols
- •Configuring Basic Network Services
- •Host name
- •IP addressing
- •DHCP
- •Netmask
- •Hardware resources
- •Routing and gateways
- •PPP, SLIP and PLIP connections
- •Server Tasks with
- •IP aliases for virtual hosts
- •Apache Web Server
- •Samba File Server
- •Home directories
- •Disk shares
- •Configuring Client Services
- •SMB/CIFS
- •NIS client configuration
- •NFS client configuration
- •Configuring Internet Services
- •Web browser
- •POP and SMTP
- •TFTP
- •SNMP
- •Remote Access
- •Rlogin
- •Telnet
- •OpenSSH
- •Documentation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Adding Hardware
- •Memory
- •Swap
- •Adding a hard drive
- •Video and monitor
- •Printers
- •Configuration files
- •Setting environment variables
- •BASH
- •Documentation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Basic User and Group Administration
- •What are users and groups?
- •Creating users
- •Change user information
- •Deleting users
- •Creating groups
- •Getting Around Linux
- •Navigating Linux
- •Common file and directory commands
- •Setting File and Directory Permissions
- •Mounting and Managing File Systems
- •Mount
- •Umount
- •Mounted file systems
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Multi-User Environment
- •The creation of Virtual Consoles
- •The Linux Terminal Server Project
- •Configurations for remote systems
- •Monitoring remote connections
- •Common Shell Commands
- •Basic shell scripts
- •Caution using root access
- •Navigating the GUI interface
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Linux Runlevels
- •init
- •Shutting down Linux
- •Managing Linux Services
- •Configuring Linux Printing
- •lpd daemon
- •/etc/printcap
- •Printing management
- •Using the vi Editor
- •vi operation modes
- •Editing text files
- •Using the
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Disk and File System Management
- •Repairing Partitions
- •System Automation and Scheduling
- •cron
- •Core Dumps
- •Analyzing core dumps
- •GNU Debugger
- •Managing Networking Interfaces
- •Installing System Packages and Patches
- •Compressed archive
- •Debian Package Installer
- •Slackware Package Installation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Linux Processes
- •Core services versus non-critical services
- •Process administration
- •Process control
- •Monitoring Log Files
- •Maintaining Documentation
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Linux Security
- •Securing the Environment
- •Location
- •Environment
- •System Security
- •System/user files
- •Permissions
- •Log auditing
- •Backups
- •Linux Security Best Practices
- •Network security
- •Firewall
- •System security
- •Securing a Web server
- •Securing an FTP server
- •FTP program version
- •FTP configuration files
- •Process security
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Disaster Recovery Planning
- •Types of data
- •Frequency and Scheduling
- •Storage and media types
- •Recovering data
- •Offsite storage
- •Linux Backup Tools and Commands
- •Third party tools
- •Tape devices
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Identifying the Problem
- •Methodology and Best Practices
- •Troubleshooting Resources
- •Documentation resources
- •Internet resources
- •System Log Files
- •Tools for Log Files
- •Output to another file
- •Locating files
- •Process Configuration and Management
- •Stopping, Starting, and Restarting Processes
- •Configuration Files
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Examining the Startup Process
- •Boot process steps
- •Analyzing Boot Process Errors
- •Common Boot Problems
- •Using System Status Tools
- •File System Check
- •System Resource Commands
- •Using the System Boot Disk
- •Types of boot disks
- •Creating a boot disk
- •Creating a rescue/utility disk
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Common User Problems
- •Login problems
- •File and directory permissions
- •Printing problems
- •Mail problems
- •Software Package Problems
- •Package dependencies
- •Software and version conflicts
- •Backup and Restore Errors
- •Backup hardware
- •Backup software
- •File restore errors
- •Application Failures
- •Log files
- •Process and daemon errors
- •Web server errors
- •Telnet
- •Mail services
- •Basic Networking Troubleshooting
- •Networking connectivity
- •Network hardware problems
- •Summary
- •Assessment Questions
- •Scenarios
- •Lab Exercises
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •Mainboard Components
- •BIOS
- •System memory
- •System Resources
- •I/O addresses
- •Direct memory access
- •Laptop Considerations
- •PCMCIA
- •Linux Peripheral Configuration
- •Installing and Configuring SCSI Devices
- •SCSI definitions
- •SCSI technologies
- •SCSI cabling and termination
- •SCSI device configuration
- •Linux SCSI devices
- •ATA/IDE Devices
- •IDE drive configuration
- •Linux ATA/IDE Drive configuration
- •Linux Support for Other Devices
- •IEEE 1394 (Firewire)
- •Summary
- •Assessment Questions
- •Scenarios
- •Answers to Chapter Questions
- •Chapter Pre-test
- •Assessment Questions
- •Scenarios
- •What’s on the CD-ROM
- •System Requirements
- •Using the CD with Microsoft Windows
- •Using the CD with Linux
- •Microsoft Windows applications
- •Linux applications
- •Troubleshooting
- •Sample Exam
- •Exam Questions
- •Exam Answers
- •Taking a CompTIA Exam
- •How to register for an exam
- •What to expect at the testing center
- •Your exam results
- •If you don’t receive a passing score
- •About the Linux + Exam
- •Preparing for the Linux+ Exam
- •For More Information
- •Preamble
- •No Warranty
- •Glossary
- •Index
Chapter 19 Installing and Maintaining System Hardware |
569 |
peripherals may not work, or may conflict with critical devices, such as disk controllers and network cards. Here are some points to consider when installing certain devices under Linux:
Video Cards: Linux works with all video cards in simple text mode. Unless you need X-windows capability, you have no need to install an X server on your Linux system — especially if you are running it as a server. X-windows uses a lot of RAM, and you must also carefully check that you have drivers available for your video card to work in X-windows.
Sound Cards: Generally, you have no need for a sound card on a server system, but if you need it on a desktop multimedia system, keep a few things in mind. Be careful when choosing which I/O port, IRQ, and DMA resources that the sound card will use. Network and SCSI cards are often configured with the same resources. This will cause a resource conflict, and it may disable your SCSI hard drive bus, resulting in a system that won’t boot. In the case of a network card conflict, the server won’t be able to communicate with the network.
Installing and Configuring SCSI Devices
7.3 Assure that system hardware is configured correctly prior to installation (e.g., IRQs, BIOS, DMA, SCSI settings, cabling) by identifying proper procedures for installing and configuring SCSI and IEEE 1394 devices
7.6Remove and replace hardware and accessories (e.g., cables and components) based on symptoms of a problem by identifying basic procedures for adding and removing field replaceable components
7.7Remove and replace hardware and accessories (e.g., cables and components) based on symptoms of a problem by identifying common symptoms and problems associated with each component and how to troubleshoot and isolate problems
7.10 Identify proper procedures for diagnosing and troubleshooting SCSI devices
SCSI (Small Computer Systems Interface) is an advanced system bus built for high performance disks and peripheral communications. Although much more expensive than IDE/ATA, SCSI is preferred in server installations for its robust performance and flexible expansion options. Many devices can be chained together on a SCSI bus, which is required for large disk space installations and fault-tolerant RAID systems.
SCSI definitions
Before describing some of the wide variety of SCSI technologies, I need to define several key characteristics of SCSI devices in order to compare the different technologies:
Clock Speed: The clock speed of the SCSI bus, measured in MHz.
Bus Speed: The speed of the SCSI bus, measured in MB/s.
570 |
Part VI Troubleshooting and Maintaining System Hardware |
Bus Width: The width of the SCSI bus. Narrow SCSI is 8-bit, Wide SCSI is 16-bit.
Signaling: The type of voltage signaling used to trigger events. The three types are Single Ended (SE), Low-Voltage Differential (LVD), and High Voltage Differential (HVD).
Termination: Describes the various types of terminators needed on the SCSI bus. Termination of a SCSI bus is critical to block signal reflection noise.
Cable Type and Length: Different SCSI technologies require certain cable types and lengths.
Devices Supported: The number of devices allowed at one time on the SCSI bus chain.
SCSI technologies
There have been a wide variety of SCSI standards — each building upon the other in terms of newer technologies that increase the speed and the bandwidth of SCSI communications. The following lists each of the SCSI types that you may encounter and their technical characteristics.
SCSI: The original SCSI 1 standard introduced an 8-bit parallel bus that can perform transfers of up to 5 MB/sec.
WIDE SCSI: Also part of the SCSI 2 standard, it increased the width of the bus from 8 bits to 16 bits. This allows double the amount of information transfer, and also increases the maximum number of devices on the SCSI chain to 16 — the normal SCSI can only have a maximum of 8.
FAST SCSI: Part of the SCSI 2 standard that raised speeds to 10 MB/sec. It also introduced a different type of bus called a differential bus, as opposed to the single-ended bus of SCSI 1. The differential type of bus offered better protection from interference, and increased the bus length to 25 meters from 6 meters.
ULTRA SCSI: Another implementation in the SCSI 2 standard, Ultra SCSI technology doubles the transfer information using the same clock rate speed. This doubles the speed of the bus to 20 MB/sec.
ULTRA WIDE SCSI: This technology refers to using the same doubled transfer capability over a wide SCSI bus. Because the ULTRA SCSI bus is running over 16 bits instead of 8, the effective transfer rate is 40 MB/sec.
ULTRA 2 WIDE SCSI: Utilizing a Low Voltage Differential signaling method, this allows the ULTRA 2 WIDE SCSI bus to double its clock speed, offering an effective transfer rate of 80 MB/sec. This LVD bus can also run in single-ended mode to be compatible with older UTLRA technology. If you do run an Ultra SCSI device on an Ultra2 bus, the bus will always run at the speed of the slowest component.
ULTRA 160 SCSI: This technology improves on the transfer rate again, and offers a transfer rate of 160 MB/sec over a 16-bit bus.
Chapter 19 Installing and Maintaining System Hardware |
571 |
ULTRA 320 SCSI: A new type of SCSI bus that uses a 16-bit wide LVD bus with a doubled clock speed to offer transfer rates up to 320 MB/sec. It is also backwards-compatible with older devices.
Table 19-3 shows a comparison of different SCSI technologies:
Table 19-3
Comparison of different SCSI technologies
SCSI Type |
Bus Clocking |
Bus Width |
Transfer Speed |
Signaling |
|
Speed (MHz) |
(Bits) |
(MB/s) |
Method |
|
|
|
|
|
SCSI |
5 |
8 |
5 |
SE/HVD |
|
|
|
|
|
Wide SCSI |
5 |
16 |
10 |
SE/HVD |
|
|
|
|
|
Fast SCSI |
10 |
8 |
10 |
SE/HVD |
|
|
|
|
|
Ultra SCSI |
20 |
8 |
20 |
SE/HVD |
|
|
|
|
|
Ultra Wide SCSI |
20 |
16 |
40 |
SE/HVD |
|
|
|
|
|
Ultra 2 Wide SCSI |
40 |
16 |
80 |
LVD/SE |
|
|
|
|
|
Ultra 160 SCSI |
80 |
16 |
160 |
LVD/SE |
|
|
|
|
|
Ultra 320 SCSI |
160 |
16 |
320 |
LVD/SE |
|
|
|
|
|
SCSI cabling and termination
Because SCSI comes in a wide of variety of bus speeds, clock rates, and signaling methods, it also offers a wide variety of cable and termination requirements for the different SCSI types:
SCSI 1 50-Pin Connectors (Narrow): SCSI 1 devices use either a 50-pin “D” connector, or a 50-pin Centronics type of connector. The “D” connector is named for the shape of the shell that surrounds the pins. It is also called a DB-50, and resembles a DB25 or DB9 type serial and parallel connector. The Centronics connector (which is named after the type of printer that used this type of connector for a parallel interface) does not actually have pins, but
50 flat contacts. Internally, SCSI 1 devices use a rectangular connector of 50 pins, split into two 25-pin rows.
SCSI 2 High density 50 and 68-Pin (Wide) Connectors: Similar to the “D” shaped connectors used by SCSI 1 devices, but they are much smaller, with the pins closer together. The 68-pin versions are also referred to as Wide connectors. For internal cabling, SCSI-2 devices use high-density 50-pin or 68-pin wide connectors.
572 |
Part VI Troubleshooting and Maintaining System Hardware |
SCSI-3 68-Pin Centronics Connector (VHDCI): The Very High Density Cable Interconnect resembles the large 50-Pin Centronics connector. These connectors use 68 contacts, which sit very close to each other. Its size makes it much easier to plug two cables into the back of a host adapter.
SCA Adapters: For RAID or multi-disk systems with many SCSI hard drives, the connectors used are Single Connector Attachment adapters. Their special connections allow all signaling and power to be fed through one connector (that the hard drive plugs right into) without any cabling. This technology is most important for hot swapping drives: The ability to remove and replace drives without having to power off the system. The SCA connector utilizes
80 pins in a Centronics type of setting. The server will usually consist of a SCSI backplane with several of the connectors where the hard drives can be plugged into.
Cable lengths
Depending on the type of signaling technology that is employed, maximum cabling lengths can vary. For older single-ended signaling, the degradation rate for the signal increases dramatically as the cable length increases. For a fast bus speed on a single-ended system, the maximum cable lengths are fairly short. For LVD-type signaling, the signal degradation is much less, resulting in longer maximum cable lengths for the SCSI bus. Refer to Table 19-4 for a summary of SCSI cable lengths.
Table 19-4
Summary of SCSI cable lengths
SCSI Type |
Contacts/Pins |
Cabling Length(meters) |
|
|
|
SCSI |
50 |
6 SE/25 HVD |
|
|
|
Wide SCSI |
68 |
6 SE/25 HVD |
|
|
|
Fast SCSI |
50 |
3 SE/25 HVD |
|
|
|
Fast Wide SCSI |
68 |
3 SE/25 HVD |
|
|
|
Ultra SCSI |
50 |
3 SE/25 HVD |
|
|
|
Wide Ultra SCSI |
68 |
3 SE/25 HVD |
|
|
|
Ultra 2 SCSI |
50 |
12 LVD/25 HVD |
|
|
|
Wide Ultra 2 SCSI |
68 |
12 LVD/25 HVD |
|
|
|
Ultra 3 SCSI |
68 |
25 LVD |
|
|
|
Termination
Termination of the SCSI bus is necessary to provide a way of stopping cable signals from reflecting from the end of the bus back onto the wire and causing data corruption. The terminator must be connected to the end of the SCSI bus at the end of the