Q: why chown $LFS/sources?
Jeremy Henty
onepoint at starurchin.org
Wed Aug 5 00:52:31 MDT 2009
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?
Regards,
Jeremy Henty
More information about the lfs-dev
mailing list