1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="ch-tools-chroot">
|
---|
9 | <?dbhtml filename="env.html"?>
|
---|
10 |
|
---|
11 | <title>Setting up the Environment</title>
|
---|
12 |
|
---|
13 | <para>The current shell is also the <command>init</command> process,
|
---|
14 | so exiting from it will cause kernel panic. Prevent exiting from the
|
---|
15 | shell accidentally:</para>
|
---|
16 |
|
---|
17 | <screen role="nodump"><userinput>enable -n exit
|
---|
18 | readonly IGNOREEOF=1000</userinput></screen>
|
---|
19 |
|
---|
20 | <para>The standard I/O streams of the initial shell process is connected
|
---|
21 | with <filename>/dev/console</filename>. However, the testsuite of some
|
---|
22 | packages may expect the standard I/O streams to be connected with a
|
---|
23 | <quote>real</quote> TTY device node. Spawn a new shell process on the
|
---|
24 | TTY device with <command>agetty</command>:</para>
|
---|
25 |
|
---|
26 | <screen role="nodump"><userinput>agetty -n -l /bin/bash <replaceable>tty0</replaceable></userinput></screen>
|
---|
27 |
|
---|
28 | <para>If you are working via a serial console, replace
|
---|
29 | <replaceable>tty0</replaceable> with the name of the serial console
|
---|
30 | device node, for example <literal>ttyS0</literal>.</para>
|
---|
31 |
|
---|
32 | <para>The command above spawns a new shell process on the TTY device
|
---|
33 | specified in the command, and the initial shell process will run in
|
---|
34 | background as an init process with very limited functions. The new shell
|
---|
35 | process will output:</para>
|
---|
36 |
|
---|
37 | <screen role="nodump"><computeroutput>bash: cannot set terminal process group (-1): Inappropriate ioctl for device
|
---|
38 | bash: no job control in this shell</computeroutput></screen>
|
---|
39 |
|
---|
40 | <para>This is normal because the shell is not assigned with a
|
---|
41 | controlling terminal yet. Now set up controlling terminal and
|
---|
42 | environment variables:</para>
|
---|
43 |
|
---|
44 | <screen><userinput>exec setsid -c /usr/bin/env -i \
|
---|
45 | HOME=/root \
|
---|
46 | TERM="$TERM" \
|
---|
47 | PS1='(lfs) \u:\w\$ ' \
|
---|
48 | PATH=/usr/bin:/usr/sbin \
|
---|
49 | /bin/bash --login</userinput></screen>
|
---|
50 |
|
---|
51 | <para>The command replace the current shell process with a new shell
|
---|
52 | process, with controlling terminal set up.</para>
|
---|
53 |
|
---|
54 | <para>The <parameter>-i</parameter> option given to the <command>env</command>
|
---|
55 | command will clear all the variables in the environment. After that, only
|
---|
56 | the <envar>HOME</envar>, <envar>TERM</envar>, <envar>PS1</envar>, and
|
---|
57 | <envar>PATH</envar> variables are set again. The
|
---|
58 | <parameter>TERM=$TERM</parameter> construct will set the <envar>TERM</envar>
|
---|
59 | variable to the default value specified by <command>agetty</command>. This variable is
|
---|
60 | needed so programs like <command>vim</command> and <command>less</command>
|
---|
61 | can operate properly. If other variables are desired, such as
|
---|
62 | <envar>CFLAGS</envar> or <envar>CXXFLAGS</envar>, this is a good place to set
|
---|
63 | them.</para>
|
---|
64 |
|
---|
65 | <para>Notice that <filename class="directory">/tools/bin</filename> is not
|
---|
66 | in the <envar>PATH</envar>. This means that the cross toolchain will no longer be
|
---|
67 | used.</para>
|
---|
68 |
|
---|
69 | <para>Note that the <command>bash</command> prompt will say
|
---|
70 | <computeroutput>I have no name!</computeroutput> This is normal because the
|
---|
71 | <filename>/etc/passwd</filename> file has not been created yet.</para>
|
---|
72 |
|
---|
73 | <para>Now set up a temporary hostname, which is required by test suite of
|
---|
74 | some packages:</para>
|
---|
75 |
|
---|
76 | <screen><userinput>hostname lfs</userinput></screen>
|
---|
77 |
|
---|
78 | <note>
|
---|
79 | <para>It is important that all the commands throughout the remainder of this
|
---|
80 | chapter and the following chapters are run from within the environment
|
---|
81 | we've set. If you leave this environment for any reason (rebooting for
|
---|
82 | example), ensure that the virtual kernel filesystems are mounted as
|
---|
83 | explained in <xref linkend="ch-tools-kernfsmount"/> and
|
---|
84 | <xref linkend="ch-tools-devadjust"/> and set up the environment again before
|
---|
85 | continuing with the installation.</para>
|
---|
86 | </note>
|
---|
87 |
|
---|
88 | </sect1>
|
---|