Ignore:
Timestamp:
02/11/2013 06:51:17 PM (11 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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:
8f83eeb
Parents:
a161de9
Message:

Removed extraneous spaces from blank lines and at the end of lines in the .xml

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

Location:
postlfs/filesystems
Files:
10 edited

Legend:

Unmodified
Added
Removed

  • postlfs/filesystems/aboutlvm.xml

    ra161de9 r0d7900a  
    1717
    1818  <para>LVM manages disk drives.  It allows multiple drives and partitions
    19   to be combined into larger <emphasis>volume groups</emphasis>, assists in 
    20   making backups through a <emphasis>snapshot</emphasis>, and allows for 
     19  to be combined into larger <emphasis>volume groups</emphasis>, assists in
     20  making backups through a <emphasis>snapshot</emphasis>, and allows for
    2121  dynamic volume resizing. It can also provide mirroring similar to
    2222  a RAID 1 array.</para>
    … …  
    2424  <para>A complete discussion of LVM is beyond the scope of this introduction,
    2525  but basic concepts are presented below.</para>
    26  
     26
    2727  <para>To run any of the commands presented here, the <xref linkend='lvm2'/>
    2828  package must be installed.  All commands must be run as the <systemitem
    … …  
    4343      <listitem><para>These are named groups of physical volumes that
    4444      can be manipulated by the administrator.  The number of physical
    45       volumes that make up a volume group is arbitrary.  Physical volumes 
    46       can be dynamically added or removed from a volume group. 
     45      volumes that make up a volume group is arbitrary.  Physical volumes
     46      can be dynamically added or removed from a volume group.
    4747      </para></listitem>
    4848    </varlistentry>
    … …  
    5656
    5757    </varlistentry>
    58   </variablelist> 
     58  </variablelist>
    5959
    6060  <para>To give a concrete example, suppose that you have two 2 TB disks.
    … …  
    6969/dev/sda4  LVM    remainder 8e (LVM)
    7070/dev/sdb1  swap     2GB     82 (Swap)
    71 /dev/sdb2  LVM    remainder 8e (LVM)</literal></screen> 
     71/dev/sdb2  LVM    remainder 8e (LVM)</literal></screen>
    7272
    7373  <para>First initialize the physical volumes:</para>
    … …  
    8989
    9090  <para>Finally the logical volumes can be formatted and mounted.  In this
    91   example, the jfs file system (<xref linkend='jfsutils'/>) is used for 
     91  example, the jfs file system (<xref linkend='jfsutils'/>) is used for
    9292  demonstration purposes.</para>
    9393
    … …  
    104104  <para>A LVM logical volume can host a root filesystem, but requires the use
    105105  of an initramfs (initial RAM file system) and is not discussed here.</para>
    106  
     106
    107107  <para>For a more information about LVM, see the <ulink
    108108  url="http://www.tldp.org/HOWTO/LVM-HOWTO/">LVM HOWTO</ulink> and

  • postlfs/filesystems/aboutraid.xml

    ra161de9 r0d7900a  
    1616  <title>About RAID</title>
    1717
    18   <para>The storage technology known as RAID (Redundant Array of 
     18  <para>The storage technology known as RAID (Redundant Array of
    1919  Independent Disks) combines multiple physical disks into a logical
    2020  unit.  The drives can generally be combined to provide data
    … …  
    2828  RAID Wiki</ulink>.</para>
    2929
    30   <para>Note that while RAID provides protection against disk 
     30  <para>Note that while RAID provides protection against disk
    3131  failures, it is not a substitute for backups.  A file deleted
    3232  is still deleted on all the disks of a RAID array.  Modern backups
    3333  are generally done via <xref linkend='rsync'/>.</para>
    3434
    35   <para>There are three major types of RAID implementation: 
     35  <para>There are three major types of RAID implementation:
    3636  Hardware RAID, BIOS-based RAID, and Software RAID.</para>
    3737
    3838  <sect2 id="hwraid">
    3939    <title>Hardware RAID</title>
    40     <para>Hardware based RAID provides capability through proprietary 
     40    <para>Hardware based RAID provides capability through proprietary
    4141    hardware and data layouts.  The control and configuration is generally
    4242    done via firmware in conjunction with executable programs made
    4343    available by the device manufacturer.  The capabilities are
    44     generally supplied via a PCI card, although there are some 
     44    generally supplied via a PCI card, although there are some
    4545    instances of RAID components integrated in to the motherboard.
    4646    Hardware RAID may also be available in a stand-alone enclosure.</para>
    … …  
    7676  <sect2 id="swraid">
    7777  <title>Software RAID</title>
    78     <para>Software based RAID is the most flexible form of RAID.  It is 
     78    <para>Software based RAID is the most flexible form of RAID.  It is
    7979    easy to install and update and provides full capability on all or
    80     part of any drives available to the system.  In BLFS, the RAID software 
     80    part of any drives available to the system.  In BLFS, the RAID software
    8181    is found in <xref linkend='mdadm'/>.</para>
    8282
    … …  
    8888
    8989    <para>The first step in creating a RAID array is to use partitioning software
    90     such as <userinput>fdisk</userinput> or <xref linkend='parted'/> to define the 
     90    such as <userinput>fdisk</userinput> or <xref linkend='parted'/> to define the
    9191    partitions needed for the array.  Usually, there will be one partition on
    9292    each drive participating in the RAID array, but that is not strictly necessary.
    … …  
    118118    both mirrored.  The third partition is a large (about 1TB) array for the
    119119    <filename class='directory'>/home</filename> directory.  This provides
    120     an ability to stripe data across multiple devices, improving speed for 
     120    an ability to stripe data across multiple devices, improving speed for
    121121    botih reading and writing large files.  Finally, a fourth array is created
    122122    that concatenates two partitions into a larger device.</para>
    … …  
    134134
    135135    <para>The devices created can be examined by device.  For example,
    136     to see the details of <filename>/dev/md1</filename>, use 
     136    to see the details of <filename>/dev/md1</filename>, use
    137137    <userinput>/sbin/mdadm --detail /dev/md1</userinput>:  </para>
    138138
    … …  
    170170
    171171   <note><para>The swap devices should be specified in the <filename>/etc/fstab</filename>
    172    file as normal.  The kernel normally stripes swap data across multiple swap 
     172   file as normal.  The kernel normally stripes swap data across multiple swap
    173173   files and should not be made part of a RAID array.</para></note>
    174174

  • postlfs/filesystems/fuse.xml

    ra161de9 r0d7900a  
    167167    <para>
    168168      <command>mv -v /usr/lib/libfuse.so.* /lib</command>: This moves the
    169       <application>FUSE</application> library to the root filesystem 
     169      <application>FUSE</application> library to the root filesystem
    170170      so that it is available early in the boot process in case
    171171      <filename class="directory">/usr</filename> is mounted on a separate

  • postlfs/filesystems/gptfdisk.xml

    ra161de9 r0d7900a  
    6969        <para>Recommended Patch: <ulink
    7070          url="&patch-root;/gptfdisk-&gptfdisk-version;-convenience-1.patch"/></para>
    71       </listitem> 
     71      </listitem>
    7272    </itemizedlist>
    7373
    … …  
    8989
    9090    <para>
    91       The <application>gptfdisk</application> package comes with a 
     91      The <application>gptfdisk</application> package comes with a
    9292      rudimentary <filename>Makefile</filename>.  First we update it
    9393      to provide a simple build and install interface.
    … …  
    112112
    113113    <para>
    114       <option>ICU=1</option>:  Adding this option to the <command>make</command> 
    115       command allows use of Unicode characters in partition names. 
     114      <option>ICU=1</option>:  Adding this option to the <command>make</command>
     115      command allows use of Unicode characters in partition names.
    116116    </para>
    117117
    118118    <para>
    119       <option>POPT=1</option>: Adding this option to the <command>make</command> 
     119      <option>POPT=1</option>: Adding this option to the <command>make</command>
    120120      command is required to build <command>sgdisk</command>. If used,
    121       this option needs to be on both the <command>make</command> and the 
     121      this option needs to be on both the <command>make</command> and the
    122122      <command>make install</command> line.
    123123    </para>
    … …  
    146146        <term><command>cgdisk</command></term>
    147147        <listitem>
    148           <para>is an is a curses-based text-mode tool for 
     148          <para>is an is a curses-based text-mode tool for
    149149          manipulating GPT partitions.</para>
    150150          <indexterm zone="gptfdisk cgdisk">
    … …  
    157157        <term><command>gdisk</command></term>
    158158        <listitem>
    159           <para>is an interactive text-mode tool 
     159          <para>is an interactive text-mode tool
    160160          for manipulating GPT partitions.</para>
    161161          <indexterm zone="gptfdisk gdisk">

  • postlfs/filesystems/initramfs.xml

    ra161de9 r0d7900a  
    4242    <title>Building an initramfs</title>
    4343
    44     <para>If you do decide to build an initramfs, the following scripts 
    45     will provide a basis to do it.  The scripts will allow specifying a 
    46     rootfs via partition UUID or partition LABEL or a rootfs on an 
     44    <para>If you do decide to build an initramfs, the following scripts
     45    will provide a basis to do it.  The scripts will allow specifying a
     46    rootfs via partition UUID or partition LABEL or a rootfs on an
    4747    LVM logical volume.  They do not support an encrypted root file system
    48     or mounting the rootfs over a network card.  For a more complete 
     48    or mounting the rootfs over a network card.  For a more complete
    4949    capability see <ulink url="http://www.linuxfromscratch.org/hints/read.html">
    5050    the LFS Hints</ulink> or <ulink url="http://fedoraproject.org/wiki/Dracut">
    … …  
    230230
    231231<command>chmod 0755 /sbin/mkinitramfs</command></userinput></screen>
    232  
     232
    233233    <screen role="root"><userinput>mkdir -p /usr/share/mkinitramfs &amp;&amp;
    234234cat &gt; /usr/share/mkinitramfs/init.in &lt;&lt; "EOF"
    … …  
    337337
    338338EOF</userinput></screen>
    339  
     339
    340340  </sect2>
    341341
    … …  
    371371    class='directory'>/boot</filename> directory.</para>
    372372
    373     <para>Now edit <filename>/boot/grub/grub.cfg</filename> and add a new 
     373    <para>Now edit <filename>/boot/grub/grub.cfg</filename> and add a new
    374374    menuentry.  Below are several examples.</para>
    375375
    376376     <screen><userinput># Generic initramfs and root fs identified by UUID
    377 menuentry "LFS Dev (LFS-7.0-Feb14) initrd, Linux 3.0.4" 
     377menuentry "LFS Dev (LFS-7.0-Feb14) initrd, Linux 3.0.4"
    378378{
    379379  linux  /vmlinuz-3.0.4-lfs-20120214 root=UUID=54b934a9-302d-415e-ac11-4988408eb0a8 ro
    … …  
    382382
    383383     <screen><userinput># Generic initramfs and root fs on LVM partition
    384 menuentry "LFS Dev (LFS-7.0-Feb18) initrd lvm, Linux 3.0.4" 
     384menuentry "LFS Dev (LFS-7.0-Feb18) initrd lvm, Linux 3.0.4"
    385385{
    386386  linux  /vmlinuz-3.0.4-lfs-20120218 root=/dev/mapper/myroot ro
    … …  
    389389
    390390     <screen><userinput># Specific initramfs and root fs identified by LABEL
    391 menuentry "LFS Dev (LFS-7.1-Feb20) initrd label, Linux 3.2.6" 
     391menuentry "LFS Dev (LFS-7.1-Feb20) initrd label, Linux 3.2.6"
    392392{
    393393  linux  /vmlinuz-3.2.6-lfs71-120220 root=LABEL=lfs71 ro

  • postlfs/filesystems/jfs.xml

    ra161de9 r0d7900a  
    103103
    104104      <seglistitem>
    105         <seg>fsck.jfs, jfs_debugfs, jfs_fsck, jfs_fscklog, 
     105        <seg>fsck.jfs, jfs_debugfs, jfs_fsck, jfs_fscklog,
    106106        jfs_logdump, jfs_mkfs, jfs_tune, mkfs.jfs </seg>
    107107        <seg>None</seg>
    … …  
    118118        <term><command>fsck.jfs</command></term>
    119119        <listitem>
    120           <para>is used to replay the JFS transaction log, check a 
     120          <para>is used to replay the JFS transaction log, check a
    121121          JFS formatted device for errors, and fix any errors found.</para>
    122122          <indexterm zone="jfsutils fsck.jfs">
    … …  
    159159        <term><command>jfs_debugfs</command></term>
    160160        <listitem>
    161           <para>is a program which can be used to perform various low-level 
     161          <para>is a program which can be used to perform various low-level
    162162          actions on a JFS formatted device.</para>
    163163          <indexterm zone="jfsutils jfs_debugfs">
    … …  
    170170        <term><command>jfs_fscklog</command></term>
    171171        <listitem>
    172           <para>extracts a JFS fsck service log into a file and/or formats and 
     172          <para>extracts a JFS fsck service log into a file and/or formats and
    173173          displays the extracted file.</para>
    174174          <indexterm zone="jfsutils jfs_fscklog">
    … …  
    181181        <term><command>jfs_logdump</command></term>
    182182        <listitem>
    183           <para>dumps the contents of the journal log from the specified 
     183          <para>dumps the contents of the journal log from the specified
    184184          JFS formatted device into output file ./jfslog.dmp.</para>
    185185          <indexterm zone="jfsutils jfs_logdump">

  • postlfs/filesystems/lvm2.xml

    ra161de9 r0d7900a  
    231231        <listitem>
    232232          <para>
    233             is a script that modifies the locking configuration in 
     233            is a script that modifies the locking configuration in
    234234            the <application>LVM2</application> configuration file.
    235235          </para>

  • postlfs/filesystems/mdadm.xml

    ra161de9 r0d7900a  
    7070
    7171<screen><literal>File Systems:
    72   Device Drivers: 
     72  Device Drivers:
    7373    Multiple devices driver support (RAID and LVM): Y
    7474      RAID support: Y or M

  • postlfs/filesystems/parted.xml

    ra161de9 r0d7900a  
    6464    <bridgehead renderas="sect4">Recommended</bridgehead>
    6565    <para role="recommended">
    66       <xref linkend="lvm2"/> (device-mapper, required if building 
     66      <xref linkend="lvm2"/> (device-mapper, required if building
    6767      <application>udisks</application>)
    6868    </para>

  • postlfs/filesystems/sshfs-fuse.xml

    ra161de9 r0d7900a  
    8080    <para role="required">
    8181      <xref linkend="fuse"/>,
    82       <xref linkend="glib2"/>, and 
     82      <xref linkend="glib2"/>, and
    8383      <xref linkend="openssh"/>.
    8484    </para>
Note: See TracChangeset for help on using the changeset viewer.