Chapter 2 Study Guide |
47 |
Lab Exercises
Lab 2-1 Examining kernel information
1.Using an Internet accessible PC and Web browser, look up the latest version of the Linux kernel at www.kernel.org and record it.
2.Note if the kernel is stable or developmental.
3.Find documentation on updating a kernel to the new version.
4.Find detailed and quick-start directions for performing the upgrade.
5.Verify that the upgrade is compatible on the PC that you are using.
Answers to Chapter Questions
Chapter Pre-Test
1.The Linux kernel is released via the Internet, as it has been since its inception.
2.Linus Torvalds releases the newest kernel versions.
3.It shows the major features, stability, and revisions.
4.You can find many Linux resources, the best of which are www.linux.org, www.kernel.org, and www.linuxdoc.org.
5.A Package is a set of binary code that creates a program.
6.These are programs that run on the Linux kernel
7.A distribution is a Linux kernel distributed with customized programs
8.The major Linux distributions are based on Red Hat or Debian Linux.
9.Linux has been released for virtually every computer platform.
10.Buying a Linux distribution often entitles you to support from the vendor.
Assessment Questions
1.A. Modules allow new hardware to be supported by the Linux kernel, Plug-ins are for Web browsers, Tarball is a package creation, and a patch fixes an existing issue. For review, see the “Linux Kernel” section.
2.A. The first section of the Linux kernel version provides the major number, the second section provides the minor number, the third section provides the revision, and the fourth section provides the patch on Red Hat systems. For review, see the “Kernel versions” section.
48 |
Chapter 2 Study Guide |
3.A. The major number in the Linux kernel version is used to indicate a major change in the kernel. The minor number indicates the stability, revision numbers indicate every change, and Answer D is the applied patch in a Red Hat system. For review, see the “Kernel versions” section.
4.B. An odd minor number indicates a developmental kernel, an even number indicates a stable kernel, a pre-release can have either number, and Linux doesn’t use Beta kernels. For review, see the “Kernel versions” section.
5.A. An even minor number indicates a stable kernel, an odd number indicates a developmental kernel, a pre-release can have either number, and Linux doesn’t use Beta kernels. For review, see the “Kernel versions” section.
6.D. Previous versions of the kernel are stored at www.kernel.org; www.linux.org supports information about Linux but directs you to www.kernel.org; www.linux.com doesn’t support previous Linux kernel archives; and finally, www.kernel.com is a commercial site. For review, see the “Linux Kernel” section.
7.D. The most up-to-date information on Red Hat Linux is at www.redhat.com, www.linux.org and www.kernel.org are not devoted to Red Hat, and www.redhat.linux.com is not supported by Red Hat Linux. For more information, see the “Red Hat” section.
8.B. Only Yellow Dog uses the PowerPC platform; Bluecat is for embedded systems; Red Hat supports virtually all platforms; and DragonLinux was created to run on top of Microsoft products. For more information, see the “Linux Distributions” and “Yellow Dog Linux” sections.
9.A. Kevin Fenzi was the co-author of Linux Security HOWTO; he didn’t write the HOWTO for tar, the kernel, or the Hurd. For more information, see the “KRUD” section.
10.D. KYZO Linux runs from compact flash memory; it doesn’t run from hard drives or CD-ROM. For more information, see the “KYZO” section.
11.A. Hard Hat Linux is being used in IBM’s PowerPC-based set-top box. Elfstone is a server Linux distribution; Bluecat is for embedded devices but not for this particular device; and LEM was not selected for the IBM box. For more information, see the “Hard Hat Linux” section.
12.D. TurboLinux is a clustering leader; Corel and DragonLinux don’t cluster; and LinuxPPC is for the PowerPC and is not a clustering leader. For more information, see the “TurboLinux” section.
13.D. The Linux creation for NASA is FlightLinux. Astaro is a router replacement; KYZO is an embedded solution for PCs; and KRUD is a customized version of Red Hat. For more information, see the “FlightLinux” section.
14.B. Files that create a program are called a package. A distribution is a group of packages; Tarball is a single file made from many files; and source code creates a program. For more information, see the “Packages and Packaging Solutions” section.
Chapter 2 Study Guide |
49 |
15.A. Red Hat Package Manager is covered under the GNU GPL. It isn’t Freeware, nor is it covered under an Artistic License or Closed Source license. For more information, see the “Red Hat Package Manager” section.
16.B. RPM provides all but package dependencies; it informs the installer of missing dependences, but doesn’t install or reinstall them. RPM provides for upgrading, verification, and pristine sources. For more information, see the “Red Hat Package Manager” section.
17.B. Red Hat Package Manager uses the .rpm extension; Debian uses .deb; Tarball uses .tar; and a GZIP Tarball uses .tar.gz. For more information, see the “Red Hat Package Manager” section.
18.B. You can most likely find the Linux mini-HOWTOs at www.linuxdoc.org; the others support Linux in other ways or don’t exist. For more information, see the “Linux Resources” section.
19.C. The first place to look for information when you are trying to use the PING command is the MAN pages; the others may work, but when in doubt, use the MAN pages. For more information, see the “Linux Resources” section.
20.A. Tar is an archive — not a compression; tar is usually compressed with GZIP; RPM and Debian are compressed files. For more information, see the “Tarball” section.
Scenarios
1.The best place to start is www.linuxdoc.org because this site supports guides, HOWTO, mini-HOWTOs, and FAQs. A secondary place to look is www.redhat.com. For more information, see the “Linux Resources” section.
2.Kernel 2.5.0 is a developmental kernel and may not be configured to support your hardware, or be very stable. For review, see the “Linux Kernel” section.
3.RPM is designed to install a program completely, whereas Tarball just opens up and dumps the files wherever you open it. For more information, see the “Red Hat Package Manager” section.
Installation
After you have decided on the type of Linux distribution that you want and what role this system will play, you
must plan the implementation. Identifying all system hardware and verifying that it is supported by Linux is essential for a successful implementation. The chapters in this part walk you through pre-implementation planning and the installation process in either in a GUI (graphical user interface) or a text-based environment. Installing Linux will be a customary routine on the job and a prevalent topic on the CompTIA Linux+ exam. In fact, 12 percent of the exam is focused solely on the installation of Linux. This part teaches you everything that you need to know for the CompTIA Linux+ exam, but also what you need to know in the real world when installing Linux.
P A R T
II
In This Part
Chapter 3
Pre-Installation
Planning
Chapter 4
Installing Linux
Chapter 5
Advanced Installation
Pre-Installation
Planning
EXAM OBJECTIVES
1.2 Identify all system hardware required and validate that it is supported by Linux (e.g., CPUs, RAM, graphics cards, storage devices, network interface cards, modem)
1.3 Determine what software and services should be installed (e.g., client applications for workstation, server services for desired task), check requirements and validate that it is supported by Linux
1.6 Identify the function of different Linux services (e.g., Apache, Squid, SAMBA, Sendmail, ipchains, BIND)
1.8 Describe the functions, features, and benefits of a Linux solutions as compared with other operating systems (e.g., Linux players, distributions, available software)
1.10 Identify where to obtain software and resources
1.11 Determine customer resources for a solution (e.g., staffing, budget, training)
C 3H A P T E R
54 |
Part II Installation |
CHAPTER PRE-TEST
1.Where can Linux be used in the Enterprise?
2.Can Linux be used as a Windows file server?
3.Can Linux be used to prevent outside access?
4.Is e-mail supported by Linux?
5.Can Linux provide the services required of a Web server?
6.Can Linux co-exist with an Apple Macintosh?
7.Does Linux provide the type of services that are offered by other operating systems?
8.Can Linux replace every other operating system?
9.Is Linux limited by hardware compatibility?
10.Where can a customer find information about a Linux service?
Answers to these questions can be found at the end of the chapter.