Changeset 02974d8


Ignore:
Timestamp:
03/14/2004 09:53:12 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
caa08b6
Parents:
5b7293a
Message:

Re-adding HOME to the chroot command, and a few textual shuffles.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3291 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
1 deleted
7 edited

Legend:

Unmodified
Added
Removed

  • chapter01/askforhelp.xml

    r5b7293a r02974d8  
    11<sect1 id="prepare-askforhelp">
    22<title>How to ask for help</title>
    3 <?dbhtml filename="askforhelp.html" dir="chapter02"?>
     3<?dbhtml filename="askforhelp.html" dir="chapter01"?>
    44
    5 <para>If you encounter a problem while using this book, and your problem
    6 is not listed in the FAQ (<ulink url="&faq-root;"/>), you will find that
    7 most of the people on Internet Relay Chat (IRC) and on the mailing lists
    8 are willing to help you (see <xref linkend="ch-scatter-administrativa"/>.
    9 To assist us in diagnosing and solving your problem, include as much relevant
    10 information as possible in your request for help.</para>
     5<para>If you run into a problem while working through this book, you should
     6first check the FAQ at <ulink url="&faq-root;"/> -- most likely your question
     7is already answered there. If it is not, you should try to find the source of
     8the problem. The following hint might give you some ideas for your
     9troubleshooting: <ulink url="&hints-root;errors.txt"/>.</para>
     10
     11<para>If all that fails, you will find that most people on IRC and the mailing
     12lists (see <xref linkend="ch-scatter-administrativa"/>) are willing to help
     13you. But to assist them in diagnosing and solving your problem, please include
     14all relevant information in your request for help.</para>
    1115
    1216<sect2>

  • chapter01/changelog.xml

    r5b7293a r02974d8  
    3737</listitem>
    3838
    39 <listitem><para>March 9th, 2004 [alex]: Chapter 6 - Removed HOME and --login
    40 from the chroot commands.</para></listitem>
     39<listitem><para>March 9th, 2004 [alex]: Chapter 6 - Removed --login from the
     40chroot commands.</para></listitem>
    4141
    4242<listitem><para>March 6th, 2004 [alex]: Rotated the contents of chapters 2, 3

  • chapter05/patch.xml

    r5b7293a r02974d8  
    1414<title>Installation of Patch</title>
    1515
    16 <para>Prepare Patch for compilation (the preprocessor flag
     16<para>Prepare Patch for compilation (setting the preprocessor flags to
    1717<emphasis>-D_GNU_SOURCE</emphasis> is only needed on the PowerPC platform, on
    1818other architectures you can leave it out):</para>

  • chapter06/chapter06.xml

    r5b7293a r02974d8  
    130130
    131131<screen><userinput>chroot $LFS /tools/bin/env -i \
    132 &nbsp;&nbsp;&nbsp;&nbsp;TERM=$TERM  PS1='\u:\w\$ ' \
     132&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root  TERM=$TERM  PS1='\u:\w\$ ' \
    133133&nbsp;&nbsp;&nbsp;&nbsp;PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
    134134&nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash +h</userinput></screen>
    135135
    136 <para>The <emphasis>-i</emphasis> option given to the
    137 <command>env</command> command will clear all variables of the chroot
    138 environment. After that, only the TERM, PS1 and PATH variables are
    139 set again. The TERM=$TERM construct will set the TERM variable inside chroot
    140 to the same value as outside chroot; this variable is needed for programs
    141 like <command>less</command> and <command>vim</command> to operate
    142 properly. If you need other variables present, such as CFLAGS, CXXFLAGS or
    143 HOME, this is a good place to set them.</para>
     136<para>The <emphasis>-i</emphasis> option passed to the <command>env</command>
     137command will clear all variables of the chroot environment. After that, only
     138the HOME, TERM, PS1 and PATH variables are set again. The HOME variable is set
     139mainly to prevent several small warnings during the configure runs of
     140Diffutils, Grep and Grub. The TERM variable is set to make programs such as
     141<command>less</command> and <command>vim</command>, that make use of the
     142Ncurses package, operate properly -- the TERM=$TERM construct sets the TERM
     143variable inside chroot to the same value as outside chroot. The main prompt
     144(PS1) is set to "username:working-dir# " (since the "\$" becomes "#" for root).
     145If you need other variables present, such as CFLAGS, CXXFLAGS or LDFLAGS, this
     146is a good place to set them.</para>
    144147
    145148<para>From this point on there's no need to use the LFS variable anymore,
    … …  
    403406problem here. The above command takes care of this also.</para>
    404407
    405 <para>You can now remove the Binutils source and build directories.</para>
     408<para>You must now remove the Binutils source and build directories. (This is
     409important, as you should start the next section with a fresh untarring of the
     410package.)</para>
    406411
    407412<para>The next thing to do is to amend our GCC specs file so that it points
    … …  
    581586
    582587<screen><userinput>chroot $LFS /tools/bin/env -i \
    583 &nbsp;&nbsp;&nbsp;&nbsp;TERM=$TERM  PS1='\u:\w\$ ' \
     588&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root  TERM=$TERM  PS1='\u:\w\$ ' \
    584589&nbsp;&nbsp;&nbsp;&nbsp;PATH=/bin:/usr/bin:/sbin:/usr/sbin \
    585590&nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash</userinput></screen>
    … …  
    611616
    612617<screen><userinput>chroot $LFS /usr/bin/env -i \
    613 &nbsp;&nbsp;&nbsp;&nbsp;TERM=$TERM  PS1='\u:\w\$ ' \
     618&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root  TERM=$TERM  PS1='\u:\w\$ ' \
    614619&nbsp;&nbsp;&nbsp;&nbsp;PATH=/bin:/usr/bin:/sbin:/usr/sbin \
    615620&nbsp;&nbsp;&nbsp;&nbsp;/bin/bash</userinput></screen>

  • chapter06/patch.xml

    r5b7293a r02974d8  
    1616<title>Installation of Patch</title>
    1717
    18 <para>Prepare Patch for compilation (the preprocessor flag
     18<para>Prepare Patch for compilation (setting the preprocessor flags to
    1919<emphasis>-D_GNU_SOURCE</emphasis> is only needed on PowerPCs, on other
    2020machines you can leave it out):</para>

  • chapter09/whatnow.xml

    r5b7293a r02974d8  
    33<?dbhtml filename="whatnow.html" dir="chapter09"?>
    44
    5 <para>We thank you for reading the LFS Book and hope that you've found this
    6 book useful and worth your time.</para>
     5<para>Thank you for reading the LFS Book. We hope that you've found this book
     6useful and worth your time.</para>
    77
    88<para>Now that you have finished installing your LFS system, you may be
    9 wondering "What now?". In order to answer that question, we have composed a
    10 list of resources for you.</para>
     9wondering what to do next. As an answer to that question we have composed a
     10short list of resources:</para>
    1111
    1212<itemizedlist>
    1313<listitem><para>Beyond Linux From Scratch</para>
    1414
    15 <para>The Beyond Linux From Scratch book covers installation procedures
    16 for a wide range of software beyond the scope of the LFS Book. The BLFS
    17 project can be found at <ulink url="&blfs-root;"/>.</para></listitem>
     15<para>If you want extra utilities for your LFS system, there is the Beyond
     16Linux From Scratch book for you. It covers the installation procedures of many
     17different packages beyond the scope of the LFS book. Among them are
     18general libraries, programming languages, graphical desktops, multimedia,
     19networking and printing. The BLFS project can be found at
     20<ulink url="&blfs-root;"/>.</para></listitem>
    1821
    1922<listitem><para>LFS Hints</para>
    2023
    21 <para>The LFS Hints are a collection of small, educational documents
    22 submitted by volunteers in the LFS community. The Hints are available at
    23 <ulink url="&hints-index;"/>.</para></listitem>
     24<para>The LFS Hints are a collection of educational documents, often small,
     25submitted by volunteers in the LFS community. They cover subjects ranging from
     26dependencies to UTF-8 locales, from optimization to uGlibc, and from cloning to
     27TZ. The Hints are available at <ulink url="&hints-index;"/>.</para></listitem>
    2428
    2529<listitem><para>Mailing lists</para>
    2630
    27 <para>There are several LFS mailing lists you may subscribe to if you are
    28 in need of help. See <xref linkend="ch-scatter-maillists"/> for more
     31<para>There are several LFS mailing lists you may subscribe to if you want to
     32help develop the book further, assist others to build their systems, or are in
     33need of help yourself. See <ulink url="&lfs-root;mail.html"/> for more
    2934information.</para></listitem>
    3035
    … …  
    3338<para>The goal of the Linux Documentation Project is to collaborate in
    3439all of the issues of Linux documentation. The LDP features a large collection
    35 of HOWTOs, Guides and man pages; it may be found at
     40of HOWTOs, Guides and man pages, and can be found at
    3641<ulink url="&tldp-root;"/>.</para></listitem>
    3742

  • index.xml

    r5b7293a r02974d8  
    33                        "/usr/share/docbook/docbookx.dtd" [
    44
    5 <!ENTITY version "CVS-2004-03-05">
    6 <!ENTITY releasedate "March 5th, 2004">
     5<!ENTITY version "CVS-2004-03-14">
     6<!ENTITY releasedate "March 14th, 2004">
    77<!ENTITY milestone "5.2">
    88<!ENTITY nbsp " ">
Note: See TracChangeset for help on using the changeset viewer.