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 |
|
---|
13 | <para>If you built your final system using the boot method, just run
|
---|
14 | <command>shutdown -r now</command> to reboot again, using your newly-built
|
---|
15 | kernel instead of the miminal one currently in use. If you chrooted,
|
---|
16 | there are a few more steps.</para>
|
---|
17 |
|
---|
18 | <para>The system you have created in this book is quite minimal, and most
|
---|
19 | likely will not have the functionality you would need to be able to
|
---|
20 | continue forward. By installing a few extra packages from CBLFS
|
---|
21 | while still in our current chroot environment, you can leave
|
---|
22 | yourself in a much better position to continue on once you reboot
|
---|
23 | into your new CLFS installation. Installing a text mode web browser,
|
---|
24 | such as Lynx, you can easily view the CBLFS website in one virtual terminal,
|
---|
25 | while building packages in another. The GPM package will also allow you
|
---|
26 | to perform copy/paste actions in your virtual terminals. Lastly, if you
|
---|
27 | are in a situation where static IP configuration does not meet your
|
---|
28 | networking requirements, installing packages such as Dhcpcd or PPP at
|
---|
29 | this point might also be useful.</para>
|
---|
30 |
|
---|
31 | <para>Now that we have said that, lets move on to booting our shiny
|
---|
32 | new CLFS installation for the first time! First exit from the chroot
|
---|
33 | environment:</para>
|
---|
34 |
|
---|
35 | <screen><userinput>logout</userinput></screen>
|
---|
36 |
|
---|
37 | <para>Then unmount the virtual file systems:</para>
|
---|
38 |
|
---|
39 | <screen><userinput>umount ${CLFS}/dev/pts
|
---|
40 |
|
---|
41 | if [ -h ${CLFS}/dev/shm ]; then
|
---|
42 | link=$(readlink ${CLFS}/dev/shm)
|
---|
43 | umount -v ${CLFS}/$link
|
---|
44 | unset link
|
---|
45 | else
|
---|
46 | umount -v ${CLFS}/dev/shm
|
---|
47 | fi
|
---|
48 |
|
---|
49 | umount ${CLFS}/dev
|
---|
50 | umount ${CLFS}/proc
|
---|
51 | umount ${CLFS}/sys</userinput></screen>
|
---|
52 |
|
---|
53 | <para>Unmount the CLFS file system itself:</para>
|
---|
54 |
|
---|
55 | <screen><userinput>umount ${CLFS}</userinput></screen>
|
---|
56 |
|
---|
57 | <para>If multiple partitions were created, unmount the other
|
---|
58 | partitions before unmounting the main one, like this:</para>
|
---|
59 |
|
---|
60 | <screen><userinput>umount ${CLFS}/usr
|
---|
61 | umount ${CLFS}/home
|
---|
62 | umount ${CLFS}</userinput></screen>
|
---|
63 |
|
---|
64 | <para>Now, reboot the system with:</para>
|
---|
65 |
|
---|
66 | <screen><userinput>shutdown -r now</userinput></screen>
|
---|
67 |
|
---|
68 | <para>Assuming the boot loader was set up as outlined earlier,
|
---|
69 | <emphasis>CLFS &version;</emphasis> will boot automatically.</para>
|
---|
70 |
|
---|
71 | <para>When the reboot is complete, the CLFS system is ready for use and
|
---|
72 | more software may be added to suit your needs.</para>
|
---|
73 |
|
---|
74 | </sect1>
|
---|