Changeset aa15d3e
- Timestamp:
- 05/29/2004 08:25:12 AM (20 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 6.0, 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/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/python-mods, qt5new, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 3b7081ba
- Parents:
- bb0d842b
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/bootscripts.xml
rbb0d842b raa15d3e 17 17 <para>The blfs-bootscripts package will be used throughout the <acronym>BLFS</acronym> 18 18 book for startup scripts. Unlike <acronym>LFS</acronym>, each init script 19 has a sep erate install target in the blfs-bootscripts package.19 has a separate install target in the blfs-bootscripts package. 20 20 It is recomended you keep the package 21 21 source directory around until completion of your -
introduction/important/patches.xml
rbb0d842b raa15d3e 14 14 </itemizedlist> 15 15 16 <para>In short, the book only includes patches that are either Required or17 Recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink>18 which hosts various patches (including the patches included in the books)16 <para>In short, the book only includes patches that are either required or 17 recommended. There is a <ulink url="http://www.linuxfromscratch.org/patches">Patches subproject</ulink> 18 which hosts various patches (including the patches referenced in the books) 19 19 to enable you to configure your <acronym>LFS</acronym> the way you like it.</para> 20 20 -
introduction/important/pkgmgt.xml
rbb0d842b raa15d3e 99 99 mentioned in <xref linkend="intro-important-beyond"/> need to be expanded to 100 100 include <filename>/usr/pkg/foo</filename>. For more than a few packages, 101 this scheme becomes unmanag able.</para>101 this scheme becomes unmanageable.</para> 102 102 103 103 </sect3> … … 111 111 to expand the environment variables. Though the symlinks can be created by the user, 112 112 to automate the creation, many package managers have been written on this approach. 113 Few of the popular ones are Stow, Epkg, Graft, and Depot.</para>113 A few of the popular ones are Stow, Epkg, Graft, and Depot.</para> 114 114 115 115 <para>The installation needs to be faked, so that the package thinks that it is 116 installed in <filename >/usr</filename> though in reality it is installed in117 <filename >/ust/pkg</filename> hierarchy. Installing in this manner is not usually a trivial116 installed in <filename class="directory">/usr</filename> though in reality it is installed in 117 <filename class="directory">/usr/pkg</filename> hierarchy. Installing in this manner is not usually a trivial 118 118 task. For example, consider that you are installing a package libfoo-1.1. The following 119 119 instructions may not install the package properly:</para> -
introduction/important/unpacking.xml
rbb0d842b raa15d3e 75 75 staring at the screen hoping to catch a particular error or warning. Log files 76 76 are also useful for debugging and keeping records. The following command 77 allows you to create a installation log. Replace <command> with the77 allows you to create an installation log. Replace <command> with the 78 78 command you intend to execute.</para> 79 79 … … 81 81 82 82 <para><parameter>2>&1</parameter> redirects error messages 83 to the same location as normaloutput. The <command>tee</command> command83 to the same location as standard output. The <command>tee</command> command 84 84 allows viewing of the output while logging the results to a file. The parentheses 85 85 around the command run the entire command in a subshell and finally the -
introduction/welcome/askhelp.xml
rbb0d842b raa15d3e 20 20 <itemizedlist> 21 21 <listitem><para>Is the hardware support compiled into the kernel or 22 available as a module to the kernel .If it is a module, is it configured23 properly in <filename>modules.conf</filename> and has it been loaded .You22 available as a module to the kernel? If it is a module, is it configured 23 properly in <filename>modules.conf</filename> and has it been loaded? You 24 24 should use <command>lsmod</command> as root to see if it's loaded. Check the 25 25 <filename>sys.log</filename> or run <command>modprobe <driver> … … 28 28 29 29 <listitem><para>Are your permissions properly set, especially for 30 devices .<acronym>LFS</acronym> uses groups to make these settings easier, but30 devices? <acronym>LFS</acronym> uses groups to make these settings easier, but 31 31 it also adds the step of adding users to groups to allow access. A simple 32 32 <command>moduser -G audio <user></command> may be all that's necessary 33 33 for that user to have access to the sound system. Any question that starts 34 out with "It works as root, but not as ..." should review permissions 35 thoroughly 36 prior to asking.</para></listitem> 34 out with "It works as root, but not as ..." requires a thorough review 35 of permissions prior to asking.</para></listitem> 37 36 38 37 <listitem><para><acronym>BLFS</acronym> liberally uses <filename> … … 40 39 need to expand your environment variables for each package placed there (e.g. 41 40 PATH=$PATH:/opt/kde/bin). In some cases, the package will walk you 42 through the changes, but some will not. <xref linkend="intro-important-beyond"/>43 is available to help you check.</para></listitem>41 through the changes, but some will not. The section called "<ulink 42 url="beyond.html">Going Beyond BLFS</ulink>" is available to help you check.</para></listitem> 44 43 </itemizedlist></sect2> 45 44 -
introduction/welcome/changelog.xml
rbb0d842b raa15d3e 11 11 12 12 <itemizedlist> 13 14 <listitem><para>May 29th, 2004 [igor]: Applied fixes for various 15 grammar and spelling errors, suggested by Randy 16 McMurchy.</para></listitem> 13 17 14 18 <listitem><para>May 29th, 2004 [igor]: Moved the samba maintainer -
introduction/welcome/conventions.xml
rbb0d842b raa15d3e 44 44 Therefore, this whole section is generally typed as seen.</para></blockquote> 45 45 46 <para><replaceable>[REPLACED TEXT]</replaceable></para> 47 48 <blockquote><para>This form of text is used to encapsulate text that is 49 not to be typed as seen or copy and pasted.</para></blockquote> 50 46 51 </sect1> 47 -
introduction/welcome/version.xml
rbb0d842b raa15d3e 4 4 5 5 <para>This is <acronym>BLFS</acronym>-BOOK version &version; dated &releasedate;. 6 If this version is older than a month a newer version is probably already6 If this version is older than a month, a newer version is probably already 7 7 available for download. Check one of the mirror sites below for updated 8 8 versions.</para> -
preface/foreword.xml
rbb0d842b raa15d3e 22 22 23 23 <para>Thanks as ever go to everyone in the <acronym>LFS</acronym>/<acronym>BLFS</acronym> 24 community especially those who have contributed instructions, written text,24 community; especially those who have contributed instructions, written text, 25 25 answered questions and generally shouted when things were wrong!</para> 26 26 -
preface/organization.xml
rbb0d842b raa15d3e 36 36 37 37 <sect2><title>Part VII - Content Serving</title> 38 <para>In this part we deal with databases and web server software 39 <!--(including php)-->.</para></sect2> 38 <para>In this part we deal with databases and web server software.</para></sect2> 40 39 41 40 <sect2><title>Part VIII - X + Window Managers</title> 42 41 <para>This part explains how to set up a basic 43 <application>XFree86</application>installation along42 X Window System installation along 44 43 with some generic <application>X</application> libraries and Window managers.</para></sect2> 45 44
Note:
See TracChangeset
for help on using the changeset viewer.