1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % general-entities SYSTEM "../general.ent">
%general-entities;
]>
<sect1 id="ch-finish-reboot">
<?dbhtml filename="reboot.html"?>
<title>Rebooting the System</title>
<para>Now that all of the software has been installed, it is time to reboot
your computer. However, you should be aware of a few things. The system you
have created in this book is quite minimal, and most likely will not have
the functionality you would need to be able to continue forward. By installing
a few extra packages from the BLFS book while still in our current chroot
environment, you can leave yourself in a much better position to continue on
once you reboot into your new LFS installation. Here are some suggestions:</para>
<itemizedlist>
<listitem><para>A text mode browser such as <ulink
url='&blfs-book;basicnet/lynx.html'>Lynx</ulink>
will allow you to easily view the BLFS book in one virtual terminal, while
building packages in another.</para></listitem>
<listitem><para>The
<ulink url='&blfs-book;postlfs/make-ca.html'>make-ca</ulink> package
will allow you to set up local trusted anchor certificates, allowing
the system to verify SSL certificates provided by remote servers (for
example, a website using HTTPS).</para></listitem>
<listitem><para>The <ulink
url='&blfs-book;general/gpm.html'>GPM</ulink> package will allow
you to perform copy/paste actions in your virtual
terminals.</para></listitem>
<listitem><para>If you are in a situation where static IP configuration
does not meet your networking requirements, installing a package
such as <ulink url='&blfs-book;basicnet/dhcpcd.html'>dhcpcd</ulink>
or the client portion of <ulink
url='&blfs-book;basicnet/dhcp.html'>dhcp</ulink> may be
useful.</para></listitem>
<listitem><para>Installing <ulink
url='&blfs-book;postlfs/sudo.html'>sudo</ulink> may be useful for
building packages as a non-root user and easily installing the resulting
packages in your new system. </para></listitem>
<listitem><para>If you want to access your new system from a remote system
within a comfortable GUI environment, install <ulink
url='&blfs-book;postlfs/openssh.html'>openssh</ulink>.
</para></listitem>
<listitem><para>To make fetching files over the internet easier, install
<ulink url='&blfs-book;basicnet/wget.html'>wget</ulink>.
</para></listitem>
<listitem><para>Finally, a review of the following configuration files
is also appropriate at this point. </para>
<itemizedlist>
<listitem><para>/etc/bashrc </para></listitem>
<listitem><para>/etc/dircolors </para></listitem>
<listitem><para>/etc/fstab </para></listitem>
<listitem><para>/etc/hosts </para></listitem>
<listitem><para>/etc/inputrc </para></listitem>
<listitem><para>/etc/profile </para></listitem>
<listitem><para>/etc/resolv.conf </para></listitem>
<listitem><para>/etc/vimrc </para></listitem>
<listitem><para>/root/.bash_profile </para></listitem>
<listitem><para>/root/.bashrc </para></listitem>
<listitem revision="sysv"><para>/etc/sysconfig/ifconfig.eth0 </para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>Now that we have said that, let's move on to booting our shiny new LFS
installation for the first time! First exit from the chroot environment:</para>
<screen><userinput>logout</userinput></screen>
<para>Unmount the LFS file system hierarchy:</para>
<screen><userinput>umount -Rv $LFS</userinput></screen>
<para>Now, reboot the system with:</para>
<screen role="nodump"><userinput>shutdown -r now</userinput></screen>
<para>Assuming the GRUB boot loader was set up as outlined earlier, the menu
is set to boot <emphasis>LFS &version;</emphasis> automatically.</para>
<para>When the reboot is complete, the LFS system is ready for use and
more software may be added to suit your needs.</para>
</sect1>
|
