id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1073	/usr/local installs with the wrong permissions	matt@…	lfs-book@…	"strange bug.

I've seen it on the last 4 LFS builds I've done (I'll check in more detail when
I rebuild my laptop and now I know what I'm looking for.)

_something_ that is looking like a umask issue or install command bug is messing
up the permissions on my /usr/local directory

To offer an example 

root@alesi:/usr/local# ls -la
total 52
drwxr-sr-x  12 root root 4096 2005-04-22 06:12 .
drwxr-xr-x  10 root root 4096 2005-04-21 03:59 ..
drwxr-sr-x  12 root root 4096 2005-04-22 06:12 apache
drwxr-sr-x   2 root root 4096 2005-04-22 06:52 bin
lrwxr-xr-x   1 root root    9 2005-04-18 23:38 doc -> share/doc
drwxr-xr-x   2 root root 4096 2005-04-22 06:23 etc
drwxr-xr-x  10 root root 4096 2005-04-22 06:23 include
lrwxr-xr-x   1 root root   10 2005-04-18 23:38 info -> share/info
drwxrwxr-x   9 root root 4096 2005-04-10 17:28 j2sdk1.4.2_07
lrwxrwxrwx   1 root root   14 2005-04-21 06:32 java -> j2sdk1.4.2_07/
drwxr-xr-x   3 root root 4096 2005-04-22 06:23 lib
lrwxr-xr-x   1 root root    9 2005-04-18 23:38 man -> share/man
drwxr-xr-x   2 root root 4096 2005-04-22 00:03 sbin
drwxr-xr-x   9 root root 4096 2005-04-18 23:38 share
drwxrwxrwx  85 root root 8192 2005-04-22 06:51 src
drwxr-xr-x   9 root root 4096 2005-04-20 03:58 ssl

apache was only recently installed (last hour or so) and ssl was installed a day
earlier, so it does either appear to be a problem with the /usr/local/ directory
 and depending on how the products are installed inheriting the bad permissions,
or a problem with ""install"" setting the wrong permissions

this is on all my LFS 6 builds (I am not following blfs in detail) 

I have manually corrected this, but it would be interesting to see if others
have had this problem."	defect	closed	normal		Book	CVS	normal	invalid