- Timestamp:
- 09/18/2018 10:03:52 PM (6 years ago)
- Branches:
- basic
- Children:
- 57e3994
- Parents:
- 987384c1
- Location:
- postlfs
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/bootdisk.xml
r987384c1 re1100da 36 36 ways, it is equivalent to building an entire LFS system. 37 37 In addition, it would be a repetition of information already available. 38 For these reasons, the procedures for a rescue device image are not38 For these reasons, the procedures for creating a rescue device image are not 39 39 presented here.</para> 40 40 … … 65 65 longer capable of building an entire LFS/BLFS system, but is still a 66 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> 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> 69 70 70 71 <para>The instructions for using GRUB2 to make a custom rescue CD-ROM are … … 78 79 <title>Creating a Bootable USB Drive</title> 79 80 80 <para>A USB Pen drive, sometimes called a Thumb drive, is recognized by Linux as81 <para>A USB pen drive, sometimes called a thumb drive, is recognized by Linux as 81 82 a SCSI device. Using one of these devices as a rescue device has the advantage 82 83 that it is usually large enough to hold more than a minimal boot image. You … … 86 87 as well as the Linux kernel and supporting files.</para> 87 88 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 88 96 <para condition="html" role="usernotes">User Notes: 89 97 <ulink url='&blfs-wiki;/CreatingaCustomBootDevice'/></para> -
postlfs/config/config.xml
r987384c1 re1100da 40 40 <xref linkend="postlfs-config-vimrc"/>.</para> 41 41 42 <para> The remaining topics, <xref linkend="postlfs-config-logon"/>,42 <!-- <para> The remaining topics, <xref linkend="postlfs-config-logon"/>, 43 43 <phrase revision="sysv"><xref linkend="postlfs-config-random"/>,</phrase> 44 44 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> --> 46 46 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"/>--> 56 57 57 58 <!-- 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"/> 59 60 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"/>--> 61 62 62 63 </chapter> -
postlfs/config/console-fonts.xml
r987384c1 re1100da 22 22 <para> 23 23 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 25 27 console. Most, if not all, PCs boot with an 8x16 font - whatever the actual 26 28 screen size. There are a few things you can do to alter the display on the … … 53 55 <literal>root=/dev/sda2 video=1024x768 ro</literal> based on the 54 56 example in LFS section 8.4.4 : 55 < phrase revision="sysv">57 <!--<phrase revision="sysv"> 56 58 <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>.--> 59 63 </para> 60 64 … … 91 95 to 512 characters (in which case, the bright colours will not be 92 96 available). Clearly, these console fonts cannot be used to display CJK 93 text -that would need thousands of available glyphs.97 text — that would need thousands of available glyphs. 94 98 </para> 95 99 … … 154 158 When you find a font which to wish to use, as the 155 159 <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 <!-- 156 170 <phrase revision="sysv"> 157 <filename>/etc/sysconfig/console</filename> as described in158 171 LFS section 7.6.5 159 172 <ulink url="&lfs-root;/chapter07/usage.html"/>.</phrase> … … 162 175 LFS section 7.6 163 176 <ulink url="&lfs-rootd;/chapter07/console.html"/>.</phrase>. 177 --> 164 178 </para> 165 179 … … 218 232 By default <application>terminus-fonts</application> will try to create 219 233 several types of font, and it will fail if <command>bdftopcf</command> 220 from < xref linkend="xorg7-app"/> has not been installed. The configure234 from <!--<xref linkend="xorg7-app"/>--> has not been installed. The configure 221 235 script is only really useful if you go on to install 222 236 <emphasis>all</emphasis> the fonts (console and X11 bitmap) to the -
postlfs/config/devices.xml
r987384c1 re1100da 126 126 <note><para>The above line is used for descriptive purposes only. The 127 127 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> 129 130 130 131 </sect2> -
postlfs/config/firmware.xml
r987384c1 re1100da 80 80 firmware in order to load it into the system: 81 81 <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> 85 87 86 88 <para condition="html" role="usernotes">User Notes: … … 375 377 376 378 <para>There are actually two ways of installing this firmware. BLFS, in the 377 'Kernel Configuration for additional firmware' section part of the < xref378 linkend="xorg-ati-driver"/> section gives an example of compiling the379 'Kernel Configuration for additional firmware' section part of the <!--<xref 380 linkend="xorg-ati-driver"/>--> section gives an example of compiling the 379 381 firmware into the kernel - that is slightly faster to load, but uses more 380 382 kernel memory. Here we will use the alternative method of making the radeon -
postlfs/filesystems/parted.xml
r987384c1 re1100da 70 70 71 71 <bridgehead renderas="sect3">Parted Dependencies</bridgehead> 72 72 <!-- 73 73 <bridgehead renderas="sect4">Recommended</bridgehead> 74 74 <para role="recommended"> … … 82 82 <xref linkend="texlive"/> (or <xref linkend="tl-installer"/>) 83 83 </para> 84 84 --> 85 85 <para condition="html" role="usernotes"> 86 86 User Notes: <ulink url="&blfs-wiki;/parted"/> … … 111 111 makeinfo --plaintext -o doc/parted.txt doc/parted.texi</userinput></screen> 112 112 113 <!-- 113 114 <para>If you have <xref linkend="texlive"/> installed and wish to create 114 115 PDF and Postcript documentation issue the following commands:</para> 116 --> 115 117 116 118 <screen><userinput>texi2pdf -o doc/parted.pdf doc/parted.texi && -
postlfs/postlfs.xml
r987384c1 re1100da 11 11 --> 12 12 13 < part id="postlfs" xreflabel="Post LFS Configuration and Extra Software">13 <!--<part id="postlfs" xreflabel="Post LFS Configuration and Extra Software"> 14 14 <?dbhtml filename="postlfs.html" dir="postlfs"?> 15 15 16 <title>Post LFS Configuration and Extra Software</title> 16 <title>Post LFS Configuration and Extra Software</title>--> 17 17 18 18 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="config/config.xml"/> 19 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="security/security.xml"/>19 <!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="security/security.xml"/> 20 20 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="filesystems/filesystems.xml"/> 21 21 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="editors/editors.xml"/> 22 22 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="shells/shells.xml"/> 23 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="virtualization/virtualization.xml"/> 23 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="virtualization/virtualization.xml"/>--> 24 24 25 25 </part> -
postlfs/security/make-ca.xml
r987384c1 re1100da 75 75 76 76 <bridgehead renderas="sect3">make-ca Dependencies</bridgehead> 77 77 <!-- 78 78 <bridgehead renderas="sect4">Recommended</bridgehead> 79 79 <para role="recommended"><xref linkend="p11-kit"/> (required at runtime to … … 87 87 NSSDB) 88 88 </para> 89 89 --> 90 90 <para condition="html" role="usernotes">User Notes: 91 91 <ulink url='&blfs-wiki;/make-ca'/></para> … … 97 97 <para>The <application>make-ca</application> script will download and 98 98 process the certificates included in the <filename>certdata.txt</filename> 99 file for use as trust anchors for the < xref linkend="p11-kit"/>trust99 file for use as trust anchors for the <!-- <xref linkend="p11-kit"/> -->trust 100 100 module. Additionally, it will generate system certificate stores used by 101 101 BLFS applications (if the recommended and optional applications are present … … 146 146 147 147 <para>As the <systemitem class="username">root</systemitem> user, after 148 installing < xref linkend="p11-kit"/>, download the certificate source and148 installing <!--<xref linkend="p11-kit"/>-->, download the certificate source and 149 149 prepare for system use with the following command:</para> 150 150 … … 171 171 for use that might be preferred for one reason or another, including the 172 172 files shipped with Mozilla products in this book. RedHat and OpenSUSE, 173 for instance, use the version included in < xref linkend="nss"/>. Additional173 for instance, use the version included in <!--<xref linkend="nss"/>-->. Additional 174 174 upstream downloads are available at the links below.</para> 175 175 -
postlfs/security/openssh.xml
r987384c1 re1100da 93 93 <ulink url="http://www.libressl.org/">LibreSSL Portable</ulink></para> 94 94 --> 95 <!-- 95 96 <bridgehead renderas="sect4">Optional</bridgehead> 96 97 <para role="optional"> … … 110 111 <xref role="runtime" linkend="sysstat"/> 111 112 </para> 112 113 --> 113 114 <para condition="html" role="usernotes"> 114 115 User Notes: <ulink url="&blfs-wiki;/OpenSSH"/> -
postlfs/security/p11-kit.xml
r987384c1 re1100da 81 81 <para role="optional"> 82 82 <xref linkend="make-ca"/> (runtime), 83 <xref linkend="nss"/> (runtime),83 <!-- <xref linkend="nss"/> (runtime), 84 84 <xref linkend="gtk-doc"/> and 85 <xref linkend="libxslt"/> 85 <xref linkend="libxslt"/>--> 86 86 </para> 87 87 … … 133 133 <para> 134 134 <option>--enable-doc</option>: Use this switch if you have installed 135 <xref linkend="gtk-doc"/> and <xref linkend="libxslt"/>and wish to135 <!-- <xref linkend="gtk-doc"/> and <xref linkend="libxslt"/> -->and wish to 136 136 rebuild the documentation and generate manual pages. 137 137 </para> -
postlfs/security/sudo.xml
r987384c1 re1100da 75 75 76 76 <bridgehead renderas="sect3">Sudo Dependencies</bridgehead> 77 77 <!-- 78 78 <bridgehead renderas="sect4">Optional</bridgehead> 79 79 <para role="optional"> … … 86 86 <ulink url="http://www.fwtk.org/">FWTK</ulink>, and 87 87 <ulink url="&sourceforge-dl;/opie/">Opie</ulink> 88 <!-- <ulink url="http://www.rsa.com/node.aspx?id=1156">SecurID</ulink>-->89 </para>88 </para> 89 --> 90 90 91 91 <para condition="html" role="usernotes">User Notes:
Note:
See TracChangeset
for help on using the changeset viewer.