On Tue, Oct 24, 2017 at 03:30:10PM -0700, Paul Rogers wrote:
>
(trimming to one point)
> So, once LFS is finished, then there may be some "essentials" one needs
> immediately, e.g. preferred editor, environment, iptables firewall,
> etc., but soon after that one needs to get networking running, boot and
> run in the new system. Yes, the LFS system is so Spartan it's
> unpleasant to use, but there's no good reason to put off booting too
> long. It's better done before there are too many added complications.
>
> >
> > Paul, why do you say that about perl modules ? I have been known to
> > build a few in chroot.
>
> Many can be, but testing in those that involve any networking or
> internet stuff will try to access the network interfaces, and even
> internet.
>
So ? I agree that if you screwed up the network interface itself
(misnamed, or missing kernel driver) then networking will not work
*after* you have booted until you fix that, and also I am well-known
for not running testsuites in my own builds (for many desktop
packages I regard the tests as only useful for the maintainer), but
for perl distributions ('perl modules' in BLFS terminology) I almost
always run the tests.
For my server, running 8.1, I built and tested NetAddr-IP, Net-DNS,
Net-HTTP before booting the new system. No problems with the tests,
they correctly remarked that certain optional deps were not present
and did not run those tests.
And if somebody wants to download via the host system there is
always the possibility of booting bare LFS, fixing any errors, going
back to chroot, building through to e.g. Xorg (or Wayland, I
suppose), booting the now-BLFS system to check that things work, and
then going back to chroot until the preferred browser etc have been
built (I do that fairly often on builds where I have updated a lot
of packages, gurgling[¹] for fixes in 'links -g' or lynx is not very
productive).
For *your* distro (building the basics on an i7, distributing the
LFS system to older machines, each of which will be used for a
different purpose) I can understand why you do things your way - but
it is by no means the only way to successfully bring up a new system.
My purpose is to not put people off by saying "you shouldn't do that"
when maybe they can.
ĸen
1. I think it was tglx (a kernel maintainer) who first used that
phrase, I like it.
--
Truth, in front of her huge walk-in wardrobe, selected black leather
boots with stiletto heels for such a barefaced truth.
- Unseen Academicals
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
