On Thu, Oct 29, 2015 at 7:17 PM, Steve Gaarder <gaar...@math.cornell.edu> wrote: > > I always thought that /usr/local was defined to be an area left alone by the > operating system. For many years, we have made it a symlink to a read-only > directory in AFS space. This has worked fine - until now. When I tried to > update the "filesystem" package, it failed because it tried to do chmods on > (at least) /usr/local/bin and /usr/local/etc. Why is it doing this? Is > /usr/local no longer truly local?
It's normal that "filesystem" ensures that "/usr/local/" has a default mode applicable to a standard use-case. (Untested) Perhaps you could leverage the "/etc/tmpfiles.d/" system to ensure that you keep it read-only: http://www.freedesktop.org/software/systemd/man/tmpfiles.d.html
