On Sat, Mar 23, 2019 at 05:54:42AM -0400, Ryan Marsaw via blfs-dev wrote:
>
> However, I read Ken's response to your query and he uses the chroot
> environment too, so I'm curious if you've done anything differently in
> your setup, Ken?
>
Yes - when I have built enough packages for the system to be usable
for me (but after Python2) I reboot to check it boots without
obvious problems (e.g. fcron jobs run and send mail to my server,
nfs is accessible). After that I then re-measure the SBU for the
new system by getting it to build a new pass-1 binutils.
Only after that do I go back to chroot. But I have to admit that I
mostly do native (not-chroot) builds of desktop systems.
I don't think I do anything which affects this issue, but my scripts
for entering chroot are a bit different from the book and I do quite
a bit before entering chroot - test if $LFS/dev/{console,null} exist,
or mknod them (I guess that can probably come out now, but no harm -
it's from the days when udev needed them to be able to boot), check
if things are mounted or else mount them, mount #LFS/dev/shm || true
('already mounted').
> For what it's worth, I wrote about this issue here:
>
> http://lists.linuxfromscratch.org/pipermail/blfs-dev/2017-December/033789.html
>
> Cheers,
>
> -- Ryan
Heh, you think we can remember further back than last week ? ;-)
ĸen
--
It is said that there are two great unsolved problems in computer
science: naming, cache invalidation, and off-by-one errors.
-- Ben Bullock
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
