Re: JHALFS build against BLFS: make-ca requires network access ?
| Newsgroups | gmane.linux.lfs.beyond.devel |
|---|---|
| Message-ID | <[email protected]> |
On 3/8/25 05:31, Xi Ruoyao ([email protected] via blfs-dev Mailing List) wrote: > On Sat, 2025-03-08 at 03:55 +0000, lfs wrote: > > /* snip */ > >> Should that command be rendering in a way that would see JHALFS try to >> execute it in the first place? >> >> >> The source (postlfs/security/make-ca.xml) has >> >> <screen role="root"><userinput>/usr/sbin/make-ca -g</userinput></screen> >> >> which is why it's getting dumped, but maybe it should be >> >> <screen role="nodump"><userinput>/usr/sbin/make-ca -g</userinput></screen> > No. We deliberately don't use nodump here. > > If we change it to nodump, packages "depending on" make-ca will fail to > build because in fact they depend on the certificate store to be set up, > not just make-ca. For some reason, I do not have the original message in the thread. But I agree with all the answers given here and in later messages. In the setting of blfs-tools after an initial build of lfs, care is taken to ensure network access in chroot, so that make-ca can get the certificates. Pierre -- http://lists.linuxfromscratch.org/sympa/info/blfs-dev Unsubscribe: See the above information page