Subtitles of the Movie

Rescues if All Else Fails. Sometimes a Linux system just won't boot. Things happen sometimes due to power failures or whatever. While some geeks prefer live CDs for rescue purposes, Fedora 11 also provides a so-called Rescue Mode available on the installation CD. Be aware; this is advanced skill as it requires some detailed knowledge of the Command Line interface; however, there are situations where the live CD will just not be good enough. So to get to Rescue Mode, boot the installation CD, press a key before the installation proceeds automatically and you should see a screen similar to what's shown here. Make sure to highlight the Rescue Installed System Option and then press Enter. I show a snapshot of this option because it actually takes a few minutes to proceed into Rescue Mode. After the system boots and systems are detected, you'll see the first couple of steps the text mode installation process as shown here. You'll choose a language as well as a keyboard. I press Enter each time and in a moment after the system boots, you'll get to configure networking. If you believe you might need to download and install new packages, it's an excellent idea to set up networking. So instead of No I select Yes, press Enter and I'm taken to a network configuration screen where I enable this first Ethernet card, Eth 0, accept Dynamic IP configuration. I can set up static IP configuration if I want and since my hardware can only handle IP Version 4 networking, that's what I enable. I press Tab to highlight OK, press Enter and the network manager configures networking on this Rescue Mode system. Then Rescue Mode proceeds to set up the rescue environment. Generally you should be able to simply choose the Continue option, which sets up the top-level root directory as shown here on the mount/sys image directory. Other directories, such as boot, will be mounted and available under mount/sys image/boot. So I highlight Continue, press Enter. It detects available storage devices, looks into partitions and then set up mounting of the top-level root directory on the mount/sys image subdirectory and as you can see from this message here, once you click OK, you can set up your regular file system by running the troop mount/sys image command. I select OK and I'm taken to a Command Line interface. To help you diagnose problems, it's useful to look at log files. While most log files on regular systems are stored in the Var/log directory, you won't find a Var/log directory here. Log files under Rescue Mode are actually stored in the temp directory. In that directory you'll see a number of files such as Anaconda.log, which give you messages about the rescue boot process, the program.log file documents how volumes were detected, the storage.log file provides information about partitions and the sys log file documents detected hardware. Once you've figured out your problem, possibly from the log files with consultation with colleagues or perhaps a Internet search, you can then go into your basic file system with Troot mount sys image command. Before that let me show you everything is mounted on Mount sys image so that's Troot mount/sys image and now things are mounted as if it were a regular file system, at which point you can install packages, assuming you have a valid network connection. For example, this command would install a text-based web browser. And if there are other solutions that you want to try, you can do so from this Command Line interface.