source: chapter11/reboot.xml

trunk
Last change on this file was bde421e, checked in by Xi Ruoyao <xry111@…>, 4 months ago

reboot: fix /dev/shm unmounting command

/dev/shm may be a mount point, or a symlink.

  • Property mode set to 100644
File size: 5.5 KB
Line 
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-finish-reboot">
9 <?dbhtml filename="reboot.html"?>
10
11 <title>Rebooting the System</title>
12 <para>
13 Now that all of the software has been installed, it is time to reboot
14 your computer. However, there are still a few things to check.
15 Here are some suggestions:</para>
16
17
18<!--
19 The system you
20 have created in this book is quite minimal, and most likely will not have
21 the functionality you would need to be able to continue forward. By installing
22 a few extra packages from the BLFS book while still in our current chroot
23 environment, you can leave yourself in a much better position to continue on
24 once you reboot into your new LFS installation. Here are some suggestions:</para>
25-->
26 <itemizedlist>
27<!--
28 <listitem><para>A text mode browser such as <ulink
29 url='&blfs-book;basicnet/lynx.html'>Lynx</ulink>
30 will allow you to easily view the BLFS book in one virtual terminal, while
31 building packages in another.</para></listitem>
32
33 <listitem><para>The <ulink
34 url='&blfs-book;postlfs/make-ca.html'>make-ca</ulink> package
35 will allow you to set up local trusted anchor certificates, allowing
36 the system to verify SSL certificates provided by remote servers (for
37 example, a website using HTTPS).</para></listitem>
38
39 <listitem><para>The <ulink
40 url='&blfs-book;general/gpm.html'>GPM</ulink> package will allow
41 you to perform copy/paste actions in your virtual
42 terminals.</para></listitem>
43
44 <listitem revision="sysv"><para>
45 If you are in a situation where static IP configuration
46 does not meet your networking requirements, installing a package
47 such as <ulink url='&blfs-book;basicnet/dhcpcd.html'>dhcpcd</ulink>
48 or the client portion of <ulink
49 url='&blfs-book;basicnet/dhcp.html'>dhcp</ulink> may be
50 useful.</para></listitem>
51
52 <listitem><para>Installing <ulink
53 url='&blfs-book;postlfs/sudo.html'>sudo</ulink> may be useful for
54 building packages as a non-&root; user and easily installing the
55 resulting packages in your new system.</para></listitem>
56
57 <listitem><para>If you want to access your new system from a remote system
58 within a comfortable GUI environment, install <ulink
59 url='&blfs-book;postlfs/openssh.html'>openssh</ulink>.</para></listitem>
60
61 <listitem><para>To make fetching files over the internet easier, install
62 <ulink url='&blfs-book;basicnet/wget.html'>wget</ulink>.</para></listitem>
63
64 <listitem><para>To connect to a wireless access point for networking,
65 install <ulink
66 url='&blfs-book;basicnet/wpa_supplicant.html'>wpa_supplicant</ulink>.
67 </para></listitem>
68-->
69 <listitem>
70 <para>
71 Install any <ulink
72 url='&blfs-book;postlfs/firmware.html'>firmware</ulink> needed if the
73 kernel driver for your hardware requires some firmware files to function
74 properly.
75 </para>
76 </listitem>
77
78 <listitem>
79 <para>
80 A review of the following configuration files
81 is also appropriate at this point.
82 </para>
83
84 <itemizedlist>
85 <listitem><para>/etc/bashrc </para></listitem>
86 <listitem><para>/etc/dircolors </para></listitem>
87 <listitem><para>/etc/fstab </para></listitem>
88 <listitem><para>/etc/hosts </para></listitem>
89 <listitem><para>/etc/inputrc </para></listitem>
90 <listitem><para>/etc/profile </para></listitem>
91 <listitem><para>/etc/resolv.conf </para></listitem>
92 <listitem><para>/etc/vimrc </para></listitem>
93 <listitem><para>/root/.bash_profile </para></listitem>
94 <listitem><para>/root/.bashrc </para></listitem>
95 <listitem revision="sysv"><para>/etc/sysconfig/ifconfig.eth0 </para></listitem>
96 </itemizedlist>
97 </listitem>
98 </itemizedlist>
99
100 <para>Now that we have said that, let's move on to booting our shiny new LFS
101 installation for the first time! <emphasis>First exit from the chroot
102 environment</emphasis>:</para>
103
104<screen><userinput>logout</userinput></screen>
105<!-- We need to show the user the details...-->
106
107 <para>Then unmount the virtual file systems:</para>
108
109<screen><userinput>umount -v $LFS/dev/pts
110mountpoint -q $LFS/dev/shm &amp;&amp; umount $LFS/dev/shm
111umount -v $LFS/dev
112umount -v $LFS/run
113umount -v $LFS/proc
114umount -v $LFS/sys</userinput></screen>
115
116 <para>If multiple partitions were created, unmount the other
117 partitions before unmounting the main one, like this:</para>
118
119<screen role="nodump"><userinput>umount -v $LFS/home
120umount -v $LFS</userinput></screen>
121
122 <para>Unmount the LFS file system itself:</para>
123
124<screen role="nodump"><userinput>umount -v $LFS</userinput></screen>
125
126 <para>Now, reboot the system.</para>
127
128<!-- Commented out because we don't have a host system requirement on
129 its init, and different init system may recommend different commands
130 for reboot. -->
131<!--<screen role="nodump"><userinput>shutdown -r now</userinput></screen>-->
132
133 <para>Assuming the GRUB boot loader was set up as outlined earlier, the menu
134 is set to boot <emphasis>LFS &version;</emphasis> automatically.</para>
135
136 <para>When the reboot is complete, the LFS system is ready for use and
137 more software may be added to suit your needs.</para>
138
139</sect1>
Note: See TracBrowser for help on using the repository browser.