On 2/27/19 3:43 PM, Ken Moffat via lfs-dev wrote:
On Wed, Feb 27, 2019 at 10:27:02PM +0100, Pierre Labastie via lfs-dev wrote:
On 27/02/2019 18:05, Bruce Dubbs via lfs-dev wrote:
On 2/27/19 10:45 AM, Pierre Labastie via lfs-dev wrote:
On 27/02/2019 04:47, Bruce Dubbs via lfs-dev wrote:
We do mount a tmpfs as $LFS/run on the page "Preparing virtual kernel
systems." Then anything can be copied to it... It is not really a "virtual"
filesystem: rather a ramdisk.
I don't understand why we need network access in chroot. The user does have
the option of using network access from the host system outside of chroot and
putting a file into /mnt/lfs/<location>.
Well, that would make it easier to install jhalfs tools for blfs if network
could be accessed in chroot: make-ca needs to be run for installing wget, and
make-ca accesses the network. Make-ca cannot be run on the host. I agree It
may be the only use case...
I'm trying not to intervene in discussions I don't understand, but
that last paragraph sounds odd. I build make-ca in my pre-boot
script which I run in chroot. As far as I am aware, my only changes
from the book (apart from various switches in certain packages) are:
· Bind an nfs mount to /sources, and therefore I do not build in
/sources.
· Bind /home/logs to /logs until I've booted, so that I can write my
logs there.
And (after everyone'e help last weekend) make-ca works, as does wget
(and Thank You to you for noting that it should be built after the
certs so that it can use https:, I've now fixed that and confirmed
make-ca works like this on my laptop build.
Ken, It appears to be a systemd only issue.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
