Ignore:
Timestamp:
03/25/2020 03:07:11 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
986f53b9
Parents:
fa3edfef
Message:

Format postlfs config

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22886 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • postlfs/config/bootdisk.xml

    rfa3edfef r81a73ed8  
    1919    <title>Decent Rescue Boot Device Needs</title>
    2020
    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 prevents 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>
     21    <para>
     22      This section is really about creating a <emphasis>rescue</emphasis>
     23      device.  As the name <emphasis>rescue</emphasis> implies, the host
     24      system has a problem, often lost partition information or corrupted file
     25      systems, that prevents it from booting and/or operating normally.  For
     26      this reason, you <emphasis>must not</emphasis> depend on resources from
     27      the host being "rescued".  To presume that any given partition or hard
     28      drive <emphasis>will</emphasis> be available is a risky presumption.
     29    </para>
    2830
    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     a rescue device was thought to be a floppy disk.  Today, many
    33     systems do not even have a floppy drive.</para>
     31    <para>
     32      In a modern system, there are many devices that can be used as a
     33      rescue device: floppy, cdrom, usb drive, or even a network card.
     34      Which one you use depends on your hardware and your BIOS.  In the past,
     35      a rescue device was thought to be a floppy disk.  Today, many
     36      systems do not even have a floppy drive.
     37    </para>
    3438
    35     <para>Building a complete rescue device is a challenging task.  In many
    36     ways, it is equivalent to building an entire LFS system.
    37     In addition, it would be a repetition of information already available.
    38     For these reasons, the procedures for a rescue device image are not
    39     presented here.</para>
     39    <para>
     40      Building a complete rescue device is a challenging task.  In many
     41      ways, it is equivalent to building an entire LFS system.
     42      In addition, it would be a repetition of information already available.
     43      For these reasons, the procedures for a rescue device image are not
     44      presented here.
     45    </para>
    4046
    4147  </sect2>
     
    4450    <title>Creating a Rescue Floppy</title>
    4551
    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 versions 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>
     52    <para>
     53      The software of today's systems has grown large.  Linux 2.6 no longer
     54      supports booting directly from a floppy.  In spite of this, there are
     55      solutions available using older versions of Linux.  One of the best is
     56      Tom's Root/Boot Disk available at <ulink
     57      url='http://www.toms.net/rb/'/>.  This will provide a minimal Linux
     58      system on a single floppy disk and provides the ability to customize
     59      the contents of your disk if necessary.
     60    </para>
    5261
    5362  </sect2>
     
    5665    <title>Creating a Bootable CD-ROM</title>
    5766
    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, Ubuntu, and SuSE.  One
    61     very popular option is Knoppix.</para>
     67    <para>
     68      There are several sources that can be used for a rescue CD-ROM.
     69      Just about any commercial distribution's installation CD-ROMs or
     70      DVDs will work.  These include RedHat, Ubuntu, and SuSE.  One
     71      very popular option is Knoppix.
     72    </para>
    6273
    63     <para>Also, the LFS Community has developed its own LiveCD available at
    64     <ulink url='http://www.&lfs-domainname;/livecd/'/>.  This LiveCD, is no
    65     longer capable of building an entire LFS/BLFS system, but is still a
    66     good rescue CD-ROM.  If you download the
    67     ISO image, use <xref linkend="xorriso"/> to copy the image to a
    68     CD-ROM.</para>
     74    <para>
     75      Also, the LFS Community has developed its own LiveCD available at
     76      <ulink url='http://www.&lfs-domainname;/livecd/'/>.  This LiveCD, is no
     77      longer capable of building an entire LFS/BLFS system, but is still a
     78      good rescue CD-ROM.  If you download the
     79      ISO image, use <xref linkend="xorriso"/> to copy the image to a
     80      CD-ROM.
     81    </para>
    6982
    70     <para>The instructions for using GRUB2 to make a custom rescue CD-ROM are
    71     also available in <ulink
    72     url='http://www.&lfs-domainname;/lfs/view/stable/chapter08/grub.html'>LFS
    73     Chapter 8</ulink>.</para>
     83    <para>
     84      The instructions for using GRUB2 to make a custom rescue CD-ROM are
     85      also available in <ulink
     86      url='http://www.&lfs-domainname;/lfs/view/stable/chapter08/grub.html'>LFS
     87      Chapter 8</ulink>.
     88    </para>
    7489
    7590  </sect2>
     
    7893    <title>Creating a Bootable USB Drive</title>
    7994
    80     <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as
    81     a SCSI device.  Using one of these devices as a rescue device has the advantage
    82     that it is usually large enough to hold more than a minimal boot image.  You
    83     can save critical data to the drive as well as use it to diagnose and recover
    84     a damaged system.  Booting such a drive requires BIOS support, but building the
    85     system consists of formatting the drive, adding <application>GRUB</application>
    86     as well as the Linux kernel and supporting files.</para>
     95    <para>
     96      A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux
     97      as a SCSI device.  Using one of these devices as a rescue device has
     98      the advantage that it is usually large enough to hold more than a
     99      minimal boot image.  You can save critical data to the drive as well
     100      as use it to diagnose and recover a damaged system.  Booting such a
     101      drive requires BIOS support, but building the system consists of
     102      formatting the drive, adding <application>GRUB</application> as well
     103      as the Linux kernel and supporting files.
     104    </para>
    87105
    88106    <para condition="html" role="usernotes">User Notes:
    89     <ulink url='&blfs-wiki;/CreatingaCustomBootDevice'/></para>
     107    <ulink url='&blfs-wiki;/CreatingaCustomBootDevice'/>
     108    </para>
    90109
    91110  </sect2>
Note: See TracChangeset for help on using the changeset viewer.