- Timestamp:
- 01/01/2013 10:17:51 PM (11 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 49144a2
- Parents:
- 0f344dd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter09/reboot.xml
r0f344dd reec1ca9 17 17 a few extra packages from the BLFS book while still in our current chroot 18 18 environment, you can leave yourself in a much better position to continue on 19 once you reboot into your new LFS installation. Installing a text mode web 20 browser, such as Lynx, you can easily view the BLFS book in one virtual 21 terminal, while building packages in another. The GPM package will also allow 22 you to perform copy/paste actions in your virtual terminals. Lastly, if you 23 are in a situation where static IP configuration does not meet your networking 24 requirements, installing packages such as Dhcpcd or PPP at this point might 25 also be useful.</para> 19 once you reboot into your new LFS installation. Here are some suggestions:</para> 20 21 <itemizedlist> 26 22 23 <listitem><para>A text mode browser such as <ulink 24 url='&blfs-root;/view/svn/basicnet/lynx.html'>Lynx</ulink> 25 will allow you to easily view the BLFS book in one virtual terminal, while 26 building packages in another.</para></listitem> 27 28 <listitem><para>The <ulink 29 url='&blfs-root;/view/svn/general/gpm.html'>GPM</ulink> package will allow 30 you to perform copy/paste actions in your virtual 31 terminals.</para></listitem> 32 33 <listitem><para>If you are in a situation where static IP configuration 34 does not meet your networking requirements, installing a package 35 such as <ulink url='&blfs-root;/view/svn/basicnet/dhcpcd.html'>dhcpcd</ulink> 36 or the client portion of <ulink 37 url='&blfs-root;/view/svn/basicnet/dhcp.html'>dhcp</ulink> may be 38 useful.</para></listitem> 39 40 <listitem><para>Installing <ulink 41 url='&blfs-root;/view/svn/postlfs/sudo.html'>sudo</ulink> may be useful for 42 building packages as a non-root user and easily installing the resulting 43 packages in your new system. </para></listitem> 44 45 <listitem><para>If you want to access your new system from a remote system 46 within a comfortable GUI environment, install <ulink 47 url='&blfs-root;/view/svn/postlfs/openssh.html'>openssh</ulink> and it's 48 prerequsite, <ulink 49 url='&blfs-root;/view/svn/postlfs/openssl.html'>openssl</ulink>. 50 </para></listitem> 51 52 <listitem><para>If one or more of your disk drives have a GUID partition 53 table (GPT), either <ulink 54 url='&blfs-root;/view/svn/postlfs/gptfdisk.html'>gptfdisk</ulink> or <ulink 55 url='&blfs-root;/view/svn/postlfs/parted.html'>parted</ulink> will be useful. 56 </para></listitem> 57 58 <listitem><para>Finally, a review of configuration files such as 59 /etc/vimrc, /etc/dircolors, /etc/profile, /etc/bashrc, /etc/hosts, 60 /etc/inputrc, /etc/resolv.conf, /root/.bash_profile, and /root/.bashrc is 61 also appropriate at this point. </para></listitem> 62 63 </itemizedlist> 27 64 28 65 <para>Now that we have said that, lets move on to booting our shiny new LFS
Note:
See TracChangeset
for help on using the changeset viewer.