| Newsgroups |
gmane.linux.lfs.automated |
| Message-ID |
<[email protected]> |
On 03/10/2022 19:11, Thomas Seeling ([email protected] via
alfs-discuss Mailing List) wrote:
> Hallo,
>
> I'm building LFS 11.2 with jhalfs, and this works fine (I'm running in
> KVM for the sake of learning KVM as well).
> However, I've ticked the box to build BLFS tools, and this does not work
> so fine.
> Most commands require root (like make-ca) but the blfs_tools build still
> runs as lfs user since it's just a continuation of the LFS build.
Normally, it runs using sudo when needed: does the user running jhalfs
(I understand it is naled "lfs") have sudo rights? ANd at the end of the
lfs build, the blfs tools are built in chroot, so at that point, all
permissions should be given. Presently, there is a problem with make-ca
on systemd, because the network is not set correctly in chroot. I have
to fix that.
>
> Basically it goes through the steps in the BLFS Makefile but there are
> lots of "permission denied" in the logfiles so it's highly likely that
> the build won't work.
>
> I then chose to run as root, invoking the Makefile in /blfs_tools/work
> standalone.
>
> PS: during configuration, in the panel for choosing BLFS tools, the box
> for git is unchecked, and the help text states for "stable" build you
> don't need to install git. This implies you only require git for
> checking out the development version of the books, but git is also used
> to checkout the stable book, so git is definitely required for all types
> of jhalfs build. Imho the checkbox should be ticked by default.
Thanks. I'll look into this... Obviously this is wrong, since we "git
clone" the repo before checking out the stable version.
Pierre
--
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page