diff --git a/chapter11/afterlfs.xml b/chapter11/afterlfs.xml new file mode 100644 index 000000000..d2779b563 --- /dev/null +++ b/chapter11/afterlfs.xml @@ -0,0 +1,235 @@ + + + %general-entities; +]> + + + + + Getting Started After LFS + + + Deciding what to do next + + + Now that LFS is complete and you have a bootable system, what do you do? + The next step is to decide how to use it. Generally, there are two broad + categories to consider: workstation or server. Indeed, these categories + are not mutually exclusive. The applications needed for each category + can be combined onto a single system, but let's look at them separately + for now. + + + + A server is the simpler category. Generally this consists of a web + server such as the + Apache HTTP Server + and a database server such as + MariaDB. + However other services are possible. The operating system + embedded in a single use device falls into this category. + + + + On the other hand, a workstation is much more complex. It generally + requires a graphical user environment such as + LXDE, + XFCE, + KDE, or + Gnome + based on the + X Window graphical environment + and several graphical based applications such as the + Firefox web browser, + Thunderbird email client, + or + LibreOffice office suite. + These applications require many (several hundred depending on + desired capabilities) more packages of support applications and + libraries. + + + + In addition to the above, there is a set of applications that are + suitable for all systems for system management. These applications are + all in the full BLFS book. Not + all packages are needed in all environments. For example + dhcpcd, + is not appropriate for a server and + wireless_tools, + are normally only + useful for a laptop system. If you are not sure if a package presented + here is needed or not, it can either be installed now or later as the + need arises. + + + + + + Working in a partial BLFS environment + + + When you initially boot into LFS, you have all the internal tools to build + additional packages. Unfortunately, the user environment is quite sparse. + There are a couple of ways to improve this: + + + + Work from the LFS host in chroot + + + This method provides a complete graphical environment where a full + featured browser and copy/paste capabilites are available. This method + allows using applications like the host's version of wget to download + package sources to a location available when working in the chroot + envirnment. + + + + In order to properly build packages in chroot, you will also need to + remember to mount the virtual file systems if they are not already + mounted. One way to do this is to create a script on the + HOST system: + + +cat > ~/mount-virt.sh << "EOF" +#!/bin/bash + +function mountbind +{ + if ! mountpoint $LFS/$1 >/dev/null; then + $SUDO mount - -bind /$1 $LFS/$1 + echo $LFS/$1 mounted + else + echo $LFS/$1 already mounted + fi +} + +function mounttype +{ + if ! mountpoint $LFS/$1 >/dev/null; then + $SUDO mount -t $2 $3 $4 $5 $LFS/$1 + echo $LFS/$1 mounted + else + echo $LFS/$1 already mounted + fi +} + +if [ $EUID -ne 0 ]; then + SUDO=sudo +else + SUDO="" +fi + +if [ x$LFS == x ]; then + echo "LFS not set" + exit 1 +fi + +mountbind dev +mounttype dev/pts devpts devpts -o gid=5,mode=620 +mounttype proc proc proc +mounttype sys sysfs sysfs +mounttype run tmpfs run +mkdir $LFS/run/shm +#mountbind usr/src +#mountbind boot +#mountbind home +EOF + + + Note that the last three commands in the script are commented out. These + are useful if those directories are mounted as separate partitions on the + host system and will be mounted when booting the completed LFS/BLFS system. + + + + The script can be run with bash ~/mount-virt.sh as + either a regular user (recommended) or as root. If run as a regular + user, sudo is required on the host system. + + + + Another issue pointed out by the script is where to store downloaded + package files. This location is arbitrary. It can be in a regular + user's home directory such as ~/sources or in a global location like + /usr/src. Our recommendation is not to mix BLFS sources and LFS sources + in (from the chroot environment) /sources. In any case, the packages + must be accessible inside the chroot environment. + + + + A last convenience feature presented here is to streamline the process + of entering the chroot environment. This can be done with an alias + placed in a user's ~/.bashrc file on the host system: + + +alias lfs='sudo /usr/sbin/chroot /mnt/lfs /usr/bin/env -i HOME=/root TERM="$TERM" PS1="\u:\w\\\\$ " +PATH=/bin:/usr/bin:/sbin:/usr/sbin /bin/bash - -login' + + + This alias is a little tricky because of the quoting and levels of + backslash characters. It must be all on a single line. The above command + has been split in two for presentation purposes. + + + + + + Work remotely via ssh + + + This method also provides a full graphical environment, but first + requires installing + sshd and + wget + on the LFS system, usually in chroot. It also requires a second + computer. This method has the advantage of being simple by not requiring + the complexity of the chroot environment. It also uses your LFS built + kernel for all additional packages and still provides a complete system + for installing packages. + + + + + + Work from the LFS command line + + + This method requiures installing + make-ca, + wget, + gpm, and + links + in chroot and then rebooting into the new LFS system. At this + point the default system has six virtual consoles. Switching + consoles is as easy as using the Alt-Fn key combinations where Fn is + between F1 and F6. The Alt-LeftArrow and Alt-RightArrow key + combinations also will change the console. + + + + At this point you can log into two different virtual consoles and run + the links browser in one console and bash in the other. GPM then allows + copying commands from the browser with the left mouse button, switching + consoles, and pasting into the other console. + + + + + As a side note, switching of virtual consoles can also be done from + an X Window instance with the Ctrl-Alt-Fn key combination, but the + mouse copy operation does not work between the graphical interface + and a virtual console. You can return to the X Window display with + the Ctrl-Alt-Fn conbination where Fn is usually F7. + + + + + + + + + diff --git a/chapter11/chapter11.xml b/chapter11/chapter11.xml index 8b4c53a1d..9adb49473 100644 --- a/chapter11/chapter11.xml +++ b/chapter11/chapter11.xml @@ -15,5 +15,6 @@ + diff --git a/chapter11/reboot.xml b/chapter11/reboot.xml index b4413f1ce..70979a191 100644 --- a/chapter11/reboot.xml +++ b/chapter11/reboot.xml @@ -9,17 +9,22 @@ Rebooting the System + + Now that all of the software has been installed, it is time to reboot + your computer. However, there are still a few things to check. + Here are some suggestions: - 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 + + - + + + + Install any firmware needed if the + kernel driver for your hardware requires some firmware files to function + properly. + + - Install firmwares if the kernel - driver for your hardware require some firmware to function properly. - - - Finally, a review of the following configuration files - is also appropriate at this point. + + + Finally, a review of the following configuration files + is also appropriate at this point. + /etc/bashrc @@ -86,14 +98,11 @@ 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: + installation for the first time! First exit from the chroot + environment: logout - + Then unmount the virtual file systems: @@ -106,8 +115,7 @@ umount -v $LFS/sys If multiple partitions were created, unmount the other partitions before unmounting the main one, like this: -umount -v $LFS/usr -umount -v $LFS/home +umount -v $LFS/home umount -v $LFS Unmount the LFS file system itself: diff --git a/chapter11/whatnow.xml b/chapter11/whatnow.xml index 999926289..e477e21c8 100644 --- a/chapter11/whatnow.xml +++ b/chapter11/whatnow.xml @@ -8,7 +8,7 @@ - What Now? + Additional Resources Thank you for reading this LFS book. We hope that you have found this book helpful and have learned more about the system @@ -38,7 +38,8 @@ - Open Source Security Mailing List + Open Source Security + Mailing List This is a mailing list for discussion of security flaws, concepts, and practices in the Open Source community. @@ -46,7 +47,7 @@ - + LFS Hints