Changeset e1100da for postlfs/config


Ignore:
Timestamp:
09/18/2018 10:03:52 PM (6 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
basic
Children:
57e3994
Parents:
987384c1
Message:

Initial commit of basic branch

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/branches/basic@20509 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:
postlfs/config
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • postlfs/config/bootdisk.xml

    r987384c1 re1100da  
    3636    ways, it is equivalent to building an entire LFS system.
    3737    In addition, it would be a repetition of information already available.
    38     For these reasons, the procedures for a rescue device image are not
     38    For these reasons, the procedures for creating a rescue device image are not
    3939    presented here.</para>
    4040
    … …  
    6565    longer capable of building an entire LFS/BLFS system, but is still a
    6666    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>
     67<!--    ISO image, use <xref linkend="xorriso"/> to copy the image to a-->
     68    ISO image, use <ulink url="&blfs-book;multimedia/libisoburn.html">xorriso</ulink>
     69    to copy the image to a CD-ROM.</para>
    6970
    7071    <para>The instructions for using GRUB2 to make a custom rescue CD-ROM are
    … …  
    7879    <title>Creating a Bootable USB Drive</title>
    7980
    80     <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as
     81    <para>A USB pen drive, sometimes called a thumb drive, is recognized by Linux as
    8182    a SCSI device.  Using one of these devices as a rescue device has the advantage
    8283    that it is usually large enough to hold more than a minimal boot image.  You
    … …  
    8687    as well as the Linux kernel and supporting files.</para>
    8788
     89    <para>Creating a bootable USB drive from a downloaded iso file is
     90    relatively simple. For example, if the iso file is some-rescue.iso and when
     91    inserting a usb drive into the system the drive is recognized as /dev/sdg,
     92    the file can be copied to the drive (as the root user) with:</para>
     93
     94<screen><userinput>dd of=/dev/sdg bs=8M status=progress oflag=direct if=some-rescue.iso</userinput></screen>
     95
    8896    <para condition="html" role="usernotes">User Notes:
    8997    <ulink url='&blfs-wiki;/CreatingaCustomBootDevice'/></para>

  • postlfs/config/config.xml

    r987384c1 re1100da  
    4040  <xref linkend="postlfs-config-vimrc"/>.</para>
    4141
    42   <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,
     42<!--  <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,
    4343  <phrase revision="sysv"><xref linkend="postlfs-config-random"/>,</phrase>
    4444  and <xref linkend="autofs"/> are then addressed, in that order. They
    45   don't have much interaction with the other topics in this chapter.</para>
     45  don't have much interaction with the other topics in this chapter.</para> -->
    4646
    47   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="bootdisk.xml"/>
    48   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="console-fonts.xml"/>
    49   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="firmware.xml"/>
    50   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="devices.xml"/>
    51   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="skel.xml"/>
    52   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users.xml"/>
    53   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="profile.xml"/>
    54   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="vimrc.xml"/>
    55   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="logon.xml"/>
     47  <xi:include xmlns:xi="&xinclude;" href="bootdisk.xml"/>
     48  <xi:include xmlns:xi="&xinclude;" href="console-fonts.xml"/>
     49  <xi:include xmlns:xi="&xinclude;" href="firmware.xml"/>
     50  <xi:include xmlns:xi="&xinclude;" href="../filesystems/initramfs.xml"/>
     51  <xi:include xmlns:xi="&xinclude;" href="devices.xml"/>
     52<!--  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="skel.xml"/>
     53  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="users.xml"/>-->
     54  <xi:include xmlns:xi="&xinclude;" href="profile.xml"/>
     55  <xi:include xmlns:xi="&xinclude;" href="vimrc.xml"/>
     56<!--  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="logon.xml"/>-->
    5657
    5758  <!-- sysv only -->
    58   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="random.xml"/>
     59  <!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="random.xml"/>
    5960
    60   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="lsb-release.xml"/>
     61  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="lsb-release.xml"/>-->
    6162
    6263</chapter>

  • postlfs/config/console-fonts.xml

    r987384c1 re1100da  
    2222  <para>
    2323    An LFS system can be used without a graphical desktop, and unless or until
    24     you install <xref linkend="x-window-system"/> you will have to work in the
     24<!--    you install <xref linkend="x-window-system"/> you will have to work in the-->
     25    you install <ulink url="&blfs-book;x/installing.html">the X Window System</ulink>
     26    you will have to work in the
    2527    console. Most, if not all, PCs boot with an 8x16 font - whatever the actual
    2628    screen size. There are a few things you can do to alter the display on the
    … …  
    5355      <literal>root=/dev/sda2 video=1024x768 ro</literal> based on the
    5456      example in LFS section 8.4.4 :
    55       <phrase revision="sysv">
     57      <!--<phrase revision="sysv">
    5658      <ulink url="&lfs-root;/chapter08/grub.html"/></phrase>
    57       <phrase revision="systemd">
    58       <ulink url="&lfs-rootd;/chapter08/grub.html"/></phrase>.
     59      <ulink url="&lfs-root;/chapter08/grub.html"/></phrase>-->
     60      <ulink url="&lfs-webroot;lfs/view/stable/chapter08/grub.html"/>
     61      <!--<phrase revision="systemd">
     62      <ulink url="&lfs-rootd;/chapter08/grub.html"/></phrase>.-->
    5963    </para>
    6064
    … …  
    9195      to 512 characters (in which  case, the bright colours will not be
    9296      available). Clearly, these console fonts cannot be used to display CJK
    93       text - that would need thousands of available glyphs.
     97      text &mdash; that would need thousands of available glyphs.
    9498    </para>
    9599
    … …  
    154158      When you find a font which to wish to use, as the
    155159      <systemitem class="username">root</systemitem> user) edit
     160      the appropriate configururation file. 
     161     
     162      If your version of LFS is
     163      System V based, see LFS section 7.6.5 at
     164      <ulink url="&lfs-webroot;lfs/view/stable/chapter07/usage.html"/>.
     165     
     166      If your version of LFS is
     167      systemd based, see LFS section 7.6 at
     168      <ulink url="&lfs-webroot;lfs/view/stable-systemd/chapter07/console.html"/>.
     169      <!--
    156170      <phrase revision="sysv">
    157       <filename>/etc/sysconfig/console</filename> as described in
    158171      LFS section 7.6.5
    159172      <ulink url="&lfs-root;/chapter07/usage.html"/>.</phrase>
    … …  
    162175      LFS section 7.6
    163176      <ulink url="&lfs-rootd;/chapter07/console.html"/>.</phrase>.
     177      -->
    164178    </para>
    165179
    … …  
    218232      By default <application>terminus-fonts</application> will try to create
    219233      several types of font, and it will fail if <command>bdftopcf</command>
    220       from <xref linkend="xorg7-app"/> has not been installed. The configure
     234      from <!--<xref linkend="xorg7-app"/>--> has not been installed. The configure
    221235      script is only really useful if you go on to install
    222236      <emphasis>all</emphasis> the fonts (console and X11 bitmap) to the

  • postlfs/config/devices.xml

    r987384c1 re1100da  
    126126    <note><para>The above line is used for descriptive purposes only. The
    127127    scanner <application>udev</application> rules are put into place when
    128     installing <xref linkend='sane'/>.</para></note>
     128<!--    installing <xref linkend='sane'/>.</para></note>-->
     129    installing  <ulink url='&blfs-book;/pst/sane.html'>sane</ulink>.</para></note>
    129130
    130131  </sect2>

  • postlfs/config/firmware.xml

    r987384c1 re1100da  
    8080  firmware in order to load it into the system:
    8181    <xref linkend="cpio"/>,
    82     <xref linkend="git"/>,
    83     <xref linkend="pciutils"/>, and
    84     <xref linkend="wget"/></para></note>
     82    <xref linkend="pciutils"/>,
     83    <xref linkend="wget"/>, and
     84  <!--  <xref linkend="git"/>, -->
     85    <ulink url="&blfs-book;/general/git.html">git</ulink>
     86    </para></note>
    8587
    8688  <para condition="html" role="usernotes">User Notes:
    … …  
    375377
    376378    <para>There are actually two ways of installing this firmware. BLFS, in the
    377     'Kernel Configuration for additional firmware' section part of the <xref
    378     linkend="xorg-ati-driver"/> section  gives an example of compiling the
     379    'Kernel Configuration for additional firmware' section part of the <!--<xref
     380    linkend="xorg-ati-driver"/>--> section  gives an example of compiling the
    379381    firmware into the kernel - that is slightly faster to load, but uses more
    380382    kernel memory. Here we will use the alternative method of making the radeon
Note: See TracChangeset for help on using the changeset viewer.