|
@@ -16,14 +16,51 @@
|
|
|
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. Installing a text mode web
|
|
|
- browser, such as Lynx, you can easily view the BLFS book in one virtual
|
|
|
- terminal, while building packages in another. The GPM package will also allow
|
|
|
- you to perform copy/paste actions in your virtual terminals. Lastly, if you
|
|
|
- are in a situation where static IP configuration does not meet your networking
|
|
|
- requirements, installing packages such as Dhcpcd or PPP at this point might
|
|
|
- also be useful.</para>
|
|
|
-
|
|
|
+ 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-root;/view/svn/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-root;/view/svn/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-root;/view/svn/basicnet/dhcpcd.html'>dhcpcd</ulink>
|
|
|
+ or the client portion of <ulink
|
|
|
+ url='&blfs-root;/view/svn/basicnet/dhcp.html'>dhcp</ulink> may be
|
|
|
+ useful.</para></listitem>
|
|
|
+
|
|
|
+ <listitem><para>Installing <ulink
|
|
|
+ url='&blfs-root;/view/svn/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-root;/view/svn/postlfs/openssh.html'>openssh</ulink> and it's
|
|
|
+ prerequsite, <ulink
|
|
|
+ url='&blfs-root;/view/svn/postlfs/openssl.html'>openssl</ulink>.
|
|
|
+ </para></listitem>
|
|
|
+
|
|
|
+ <listitem><para>If one or more of your disk drives have a GUID partition
|
|
|
+ table (GPT), either <ulink
|
|
|
+ url='&blfs-root;/view/svn/postlfs/gptfdisk.html'>gptfdisk</ulink> or <ulink
|
|
|
+ url='&blfs-root;/view/svn/postlfs/parted.html'>parted</ulink> will be useful.
|
|
|
+ </para></listitem>
|
|
|
+
|
|
|
+ <listitem><para>Finally, a review of configuration files such as
|
|
|
+ /etc/vimrc, /etc/dircolors, /etc/profile, /etc/bashrc, /etc/hosts,
|
|
|
+ /etc/inputrc, /etc/resolv.conf, /root/.bash_profile, and /root/.bashrc is
|
|
|
+ also appropriate at this point. </para></listitem>
|
|
|
+
|
|
|
+ </itemizedlist>
|
|
|
|
|
|
<para>Now that we have said that, lets move on to booting our shiny new LFS
|
|
|
installation for the first time! First exit from the chroot environment:</para>
|