Changeset 1e247d1 for postlfs/config
- Timestamp:
- 05/12/2005 07:54:26 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 53819cbb
- Parents:
- d3ad3271
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/bootdisk.xml
rd3ad3271 r1e247d1 7 7 8 8 <sect1 id="postlfs-config-bootdisk" xreflabel="Creating a Custom Boot Device"> 9 <sect1info> 10 <othername>$LastChangedBy$</othername> 11 <date>$Date$</date> 12 </sect1info> 13 <?dbhtml filename="bootdisk.html"?> 14 <title>Creating a Custom Boot Device</title> 9 <?dbhtml filename="bootdisk.html"?> 15 10 16 <sect2> 17 <title>Decent Rescue Boot Device Needs</title> 18 <para>This section is really about creating a <emphasis>rescue</emphasis> 19 device. As the name <emphasis>rescue</emphasis> implies, the host 20 system has a problem, often lost partition information or corrupted file 21 systems, that prevent it from booting and/or operating normally. For 22 this reason, you <emphasis>must not</emphasis> depend on resources from 23 the host being "rescued". To presume that any given partition or hard 24 drive <emphasis>will</emphasis> be available is a risky presumption.</para> 11 <sect1info> 12 <othername>$LastChangedBy$</othername> 13 <date>$Date$</date> 14 </sect1info> 25 15 26 <para>In a modern system, there are many devices that can be 27 used as a rescue device: floppy, cdrom, usb drive, or even a network card. 28 Which one you use depends on your hardware and your BIOS. In the past, 29 we usually thought of rescue device as a floppy disk. Today, many 30 systems do not even have a floppy drive.</para> 16 <title>Creating a Custom Boot Device</title> 31 17 32 <para>Building a complete rescue device is a challenging task. In many 33 ways, it is equivalent to building an entire <acronym>LFS</acronym> system. 34 In addition, it would be a repitition of information already available. 35 For these reasons, the procedures for a rescue device image are not 36 presented here.</para> 37 </sect2> 18 <sect2> 19 <title>Decent Rescue Boot Device Needs</title> 38 20 39 <sect2> 40 <title>Creating a Rescue Floppy</title> 21 <para>This section is really about creating a <emphasis>rescue</emphasis> 22 device. As the name <emphasis>rescue</emphasis> implies, the host 23 system has a problem, often lost partition information or corrupted file 24 systems, that prevent it from booting and/or operating normally. For 25 this reason, you <emphasis>must not</emphasis> depend on resources from 26 the host being "rescued". To presume that any given partition or hard 27 drive <emphasis>will</emphasis> be available is a risky presumption.</para> 41 28 42 <para>The software of today's systems has grown large. Linux 2.6 no longer 43 supports booting directly from a floppy. In spite of this, there are solutions 44 available using older version of Linux. One of the best is Tom's Root/Boot 45 Disk available at <ulink url='http://www.toms.net/rb/'/>. This will provide a 46 minimal Linux system on a single floppy disk and provides the ability to 47 customize the contents of your disk if necessary.</para> 29 <para>In a modern system, there are many devices that can be 30 used as a rescue device: floppy, cdrom, usb drive, or even a network card. 31 Which one you use depends on your hardware and your BIOS. In the past, 32 we usually thought of rescue device as a floppy disk. Today, many 33 systems do not even have a floppy drive.</para> 48 34 49 </sect2> 35 <para>Building a complete rescue device is a challenging task. In many 36 ways, it is equivalent to building an entire <acronym>LFS</acronym> system. 37 In addition, it would be a repitition of information already available. 38 For these reasons, the procedures for a rescue device image are not 39 presented here.</para> 50 40 51 <sect2> 52 <title>Creating a Bootable CD-ROM</title> 41 </sect2> 53 42 54 <para>There are several sources that can be used for a rescue CD-ROM. 55 Just about any commercial distribution's installation CD-ROMs or 56 DVDs will work. These include RedHat, Mandrake, and SuSE. One 57 very popular option is Knoppix.</para> 43 <sect2> 44 <title>Creating a Rescue Floppy</title> 58 45 59 <para>In addition, the LFS Community has developed its own Boot 60 CD-ROM available at <ulink url='ftp://anduin.linuxfromscratch.org/isos/'/>. 61 A copy of this CD-ROM is available with the printed version of the Linux 62 From Scratch book. If you download the ISO image, use <xref linkend='cdrecord'/> to 63 copy the image to a CD-ROM.</para> 46 <para>The software of today's systems has grown large. Linux 2.6 no longer 47 supports booting directly from a floppy. In spite of this, there are solutions 48 available using older version of Linux. One of the best is Tom's Root/Boot 49 Disk available at <ulink url='http://www.toms.net/rb/'/>. This will provide a 50 minimal Linux system on a single floppy disk and provides the ability to 51 customize the contents of your disk if necessary.</para> 64 52 65 <para>In the future, the build instructions for this CD-ROM will be presented, 66 but they are not available at this writing.</para> 67 </sect2> 53 </sect2> 68 54 69 <sect2>70 <title>Creating a Bootable USB Drive</title>55 <sect2> 56 <title>Creating a Bootable CD-ROM</title> 71 57 72 <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as 73 a SCSI device. Using one of these devices as a rescue device has the advantage 74 that it is usually large enough to hold more than a minimal boot image. You 75 can save critical data to the drive as well as use it to diagnose and recover 76 a damaged system. Booting such a drive requires BIOS support, but building the 77 system consists of formatting the drive, adding <application>grub</application> 78 as well as the kernel and supporting files.</para> 58 <para>There are several sources that can be used for a rescue CD-ROM. 59 Just about any commercial distribution's installation CD-ROMs or 60 DVDs will work. These include RedHat, Mandrake, and SuSE. One 61 very popular option is Knoppix.</para> 79 62 80 </sect2> 81 </sect1> 63 <para>In addition, the LFS Community has developed its own Boot 64 CD-ROM available at <ulink url='ftp://anduin.linuxfromscratch.org/isos/'/>. 65 A copy of this CD-ROM is available with the printed version of the Linux 66 From Scratch book. If you download the ISO image, use <xref linkend='cdrecord'/> to 67 copy the image to a CD-ROM.</para> 68 69 <para>In the future, the build instructions for this CD-ROM will be presented, 70 but they are not available at this writing.</para> 71 72 </sect2> 73 74 <sect2> 75 <title>Creating a Bootable USB Drive</title> 76 77 <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as 78 a SCSI device. Using one of these devices as a rescue device has the advantage 79 that it is usually large enough to hold more than a minimal boot image. You 80 can save critical data to the drive as well as use it to diagnose and recover 81 a damaged system. Booting such a drive requires BIOS support, but building the 82 system consists of formatting the drive, adding <application>grub</application> 83 as well as the kernel and supporting files.</para> 84 85 </sect2> 86 87 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.