Opened 13 years ago
Closed 13 years ago
#2958 closed defect (invalid)
7.0 coreutils test needs o+x permission on tools dir
Reported by: | Sean | Owned by: | |
---|---|---|---|
Priority: | lowest | Milestone: | 7.1 |
Component: | Book | Version: | 7.0 |
Severity: | minor | Keywords: | |
Cc: |
Description
Hi. Very minor issue...
When running the coreutils test as 'nobody' in 6.23.1 it fails to start:
su-tools: /bin/bash: Permission denied
I had to chmod -R o+X $LFS/tools
The directions given in "5.35. Changing Ownership" tell you to chmod /tools to root:root
I can't readily find where the create mask is specified for the host root user when making the tools directory, or find any chmod of the tools directory. Maybe you should add an explicit chmod in 5.35, or mention chmod in 6.23.1
Change History (3)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
I just meant the tools directory itself. The files in it are fine. My umask on the host system was 0027 which is how I roll. I accept that it is my fault entirely.
Perhaps not a defect of the book, how about a mere suggestion to set permissions on the tools directory at the start, or set the umask of the host system. I think it would fit right into 4.2, 4.3 or 5.35 nicely. Umask is mentioned in 4.4 for the lfs user but after the tools directory has been created.
-Sean
comment:3 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
It is very unlikely that this is a problem with the book. All the executables in my reference build /tools/{bin,sbin} have o+x permissions.
The build test is automated before release. See http://www.linuxfromscratch.org/lfs/build-logs/7.0/core2duo/test-logs/086-coreutils
We need more precise information about what files had the wrong permissions in order to act on this ticket.