Strange authorisation isuses:

"Dragan" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
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?

Dragan

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.