Maybe I'm missimg something but I don't see why we need to chown $LFS/sources. It's already world-writable (and sticky) so there's no problem with the lfs user unpacking stuff there. What will go wrong if do chapter 5 with $LFS/sources owned by root?
Not chown-ing $LFS/sources also resolves a tiny niggle at the end of chapter 5 - $LFS/sources is left chown-ed to lfs, so the chroot (and the final system if you decide not to clean up the sources) is left with one file with a bogus owner (since the lfs user does). It would be tidier to fix this. I hope I've not missed anything obvious - searching the site for "chown /sources" didn't turn up any prior discussion that I could see. Regards, Jeremy Henty -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
