On 1/15/20 9:08 AM, Alan Feuerbacher via blfs-support wrote:
On 1/15/2020 5:18 AM, Scott Andrews via blfs-support wrote:
On 1/14/20 10:18 PM, Alan Feuerbacher via blfs-support wrote:
Now that I've got my shiny new LFS system up and running, and I've
installed a pile of BLFS software in chroot, but don't have X
running, I'd like some hints on streamlining the process of
installing software via Lynx.
Unfortunately, my hard drive that contained a lot of helpful hints
from when I last played with LFS 2 1/2 years ago went belly up a
couple of years ago, and I've forgotten many of the hints that were
on that drive. Here's what I remember:
In the Linux console I believe there is a way to switch between two
or more independent windows, so that you can have a program running
in each. This facilitates, say, looking at the BLFS book in Lynx in
one window, and installing the software in another. How do you
switch windows?
I know that on startup Linux records some log files, including what
is output to the console. Where can I find them?
A couple of days ago Bruce Dubbs gave me a link to some hints on
transitioning from LFS to BLSF. Good stuff!
Any other helpful hints?
Thanks in advance!
Alan
Use a package manager. Build packages in a clean chroot. I use the
kernel overlayfs to do that even when building the base system. It
protects the host from damage, when you are building and installing
LFS and BLFS. It also provides a mechanism to catch errors that you
don't know are happening.
Sorry, but I don't know what any of that means. Can you expand on it?
Alan
Have a look at : https://github.com/baho-utot/Overlay for how to setup
and
https://wiki.archlinux.org/index.php/Overlay_filesystem
https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt
https://www.datalight.com/blog/2016/01/27/explaining-overlayfs-%E2%80%93-what-it-does-and-how-it-works
https://en.wikipedia.org/wiki/OverlayFS
What the kernel overlayfs does is to create a unionfs type of
filesystem. It needs three directories to work ie lower, upper, work and
a direct as a mount point. I place a clone of the host system in the
lower directory, the upper and work directories are empty then mount the
overlay using the mount point directory. Chroot to the mount point and
then setup and build LFS. Then lower directory containing the "host
system" is read only, all the changes go to the upper directory. Than
completly protects your host from any errors you might make. after you
exit the chroot the you can look at the upper directory to see what has
been added or modified.
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
