* On [22 Aug 2005 14:37 +0300] <[EMAIL PROTECTED]> wrote:
> Andrew Benton wrote:
> >Just as an experiment I've (or rather, root has) just run
> >
> >find /usr/lib -type d -exec chmod 755 {} \; &&
> >find /usr/lib -type f -exec chmod 644 {} \;
> >
> >This has set the permissions of every file in /usr/lib to 644. I've
> >rebooted and everything seems to be running OK...
>
> Spoke too soon. Gcc won't work if /usr/lib/gcc/i686-pc-linux-gnu/4.0.1/cc1
> isn't executable. There's probably a couple more things in /usr/lib that
> need to be executable. But the shared libraries seem to be OK set to 644
I think some of the sub directories of /usr/lib have files that need to
be executable--which by default are usually installed with the right
permissions--but most of the libraries in /usr/lib would probably be
fine with a 644 permission. I checked on a Debian box and almost none of
the libraries there are executable. I wonder why we would need a library
to be executable, in the first place.
--
"Life is a whim of several billion cells to be you for a while." -
Anonymous
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
