<div>> Given that umask [077], wouldn't you expect everything to only be usable by you?</div> <div> </div> <div>Ah! You may have something there. <BR></div> <div>> Looking at the install scripts, I see that there are some </div> <div>> after-the-fact chmod's which add r permission to some trees, </div> <div>> but not x. So that's presumably why the result wasn't just rwx------, </div> <div>> as your umask would imply.</div> <div> </div> <div>But ... three of the directories DID have x permission. This is what I had immediately after installation: </div> <div> </div> <div> drwxr-xr-x 3 tex tex 4096 Jan 22 11:48 bin<BR> drwxr--r-- 19 tex tex 4096 Jan 22 12:42 texmf<BR> drwxr-xr-x 18 tex
tex 4096 Jan 22 12:42 texmf-dist<BR> drwxr-xr-x 5 tex tex 4096 Jan 22 11:49 texmf-doc<BR> drwxr--r-- 8 tex tex 4096 Jan 22 12:42 texmf-local<BR> drwxrw-rw- 8 tex tex 4096 Jan 22 12:42 texmf-var<BR><BR>> Since the installation scripts have been completely reimplemented </div> <div>> for the next release, and I don't think such special chmod's are done </div> <div>> any more, there's probably nothing to do here.<BR></div> <div>Well, if the installation scripts don't enforce the permissions that are necessary for a given setup scenario, it might be helpful to have a sentence in the installation notes that says something
like, "if you want TeX Live to be usable by everyone, you must set umask ... before you start", or "... ensure that you have these file permisions after installation: ...". </div> <div> </div><p> 
<hr size=1> Support the World Aids Awareness campaign this month with <a href="http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=51947/*http://uk.promotions.yahoo.com/forgood/">Yahoo! for Good</a>