Jeremy Henty wrote: > On Tue, Aug 04, 2009 at 03:18:59PM -0500, Bruce Dubbs wrote: >> Jeremy Henty wrote: >>> 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? >> If another user adds a file or expands a tarball, then the lfs user >> can't delete them because of the sticky bit. It could be worked >> around, but its just smoother if the lfs user owns everything. > > Good point. In that case I suggest adding "chown -R root:root > $LFS/sources" to the end of chapter 5 to ensure that everything in the > chroot is owned by a valid user in the chroot. Worth a ticket?
No. An LFS user should be able to figure out if he wants to do that on his own. After all, as root, using another user's files is not a problem. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
