Steve, You did not post the whole story to the list, but could it have to do with the fact that symlinks are protected by default in RHEL7?
# cat /proc/sys/fs/protected_symlinks 1 That means they can only be followed when outside a sticky world-writable directory, or when the uid of the symlink and follower match, or when the directory owner matches the symlink's owner. Regards, Benjamin Lefoul ________________________________________ From: owner-scientific-linux-us...@listserv.fnal.gov [owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Steve Gaarder [gaar...@math.cornell.edu] Sent: Friday, November 13, 2015 3:02 PM To: Nico Kadel-Garcia Cc: SCIENTIFIC-LINUX-USERS@FNAL.GOV Subject: Re: Filesystem package messes with /usr/local On Fri, 13 Nov 2015, Nico Kadel-Garcia wrote: > The /usr/local/ directories are part of the File System Hierarchy, at > http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY > > So, yes, it looks like upstream is following the File System > Hierarchy. To play nicely with it, you should ideally, replace the > subdirectories in /usr/local/ with individual symlinks. > They *are* symlinks, but symlinks to a read-only area in AFS space. Looking at the filesystem RPM, it assumes that it may be the first thing being installed in a new system, and (re)creates the basic file system structure. It seems ok with the symlink, but blows up when it can't chmod it. Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA gaar...@math.cornell.edu
