Re: Strange authorisation isuses:

On Thu, 2022-06-16 at 14:17 +0200, Dragan wrote:
> Hi,
> 
> After I have build and successfully booted in current development 
> version of LFS I have tried jhalfs. I started boot build with all log 
> options and saved .config file for kernel from the latest build. In mean 
> time have Bruce committed new version! So the script has downloaded 
> updated sources files and started build. All was going as hoped for 
> until target 1002 : kernel!
> 
> I have killed build after more than 500 minutes.
> 
> Today I have chrooted in build and as usually run defconfig and 
> menuconfig and saved .config in my standard location. Then I have 
> cleaned up pulled jhalfs from git and trued to start build again only to 
> fail on Target 503- linux-headers because of authorization issues.
> 
> I have checked ownership of /lfs and preexisting source directory. Booth 
> were root:root. Clean up, also user lfs, and try again!
> 
> Same story. I've cleaned up leaving user lfs and started new clean build 
> up. Same story.
> 
> In both cases have script inherited sudo rights from previously executed 
> commands! Yesterday build have well asked for sudo password.
> 
> After remembering that I've cleaned the mess up us user lfs exited shell 
> and started new clean build and sudo pwd was necessary.  I have just 
> been asked to supply sudo pwd for second time after 617-ggc-pass2.
> 
> What, if anything, can be done to solve problem?

Remove everything in /mnt/lfs (or wherever your lfs system is residing), except
possibly lost+found, if it exists. If you want to keep the source tarballs, and
you have not yet done so, create a directory /sources on the host, and archive
the tarballs there first, before cleaning /mnt/lfs. Then pass /sources to
"Package Archive Directory" (you need to tick "Retrieve source files).

Pierre

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page