Hi Benda, on Gentoo:RAP user install Gentoo into a PREFIXed path under his/her own privileges. Other users can use the installation as well but some files are not readable by others. I do not know what needs to be tweaked but assume something in portage eclasses could ensure files are readable by everybody and dirs have rx bit set for everybody too? Some examples as of now: $ ls -latr /apps/gentoo_uv/etc/portage/make.conf; ls -latr /apps/gentoo/etc/{timezone,shadow} -rw------- 1 mmokrejs mmokrejs 2685 Apr 14 09:56 /apps/gentoo_uv/etc/portage/make.conf -rw-r----- 1 mmokrejs mmokrejs 259 Sep 1 2016 /apps/gentoo/etc/shadow -rw------- 1 mmokrejs mmokrejs 14 Jan 27 13:04 /apps/gentoo/etc/timezone $ It is more a problem that "emerge -s foo" and "gcc-config -l" cannot be run by another user. Could anything be done about it?
Just wondering, in Prefix we don't do any umask stuff, does RAP set umask? or do you have umask in your shell init?
Hi Fabian, actually at the moment I have umask 077 in my .bash_profile but I cannot what settings I had when I installed RAP. However, most other files are world readable. I admit that especially passwd and shadow files cpould have mangled permission bits because I was testing some stuff for benda whether the "Username becomes invalid inside RAP" section in https://wiki.gentoo.org/wiki/Prefix/libc was correct. I admit I forget about this possibility my shell umask settings were at the fault. How can I get all files and dirs from find(1) utility having no "group or other" bits set? Other users can execute startprefix of the RAP install I have installed, but not even 'gcc-config -l' works for them. I already discussed with Benda in the past that e.g. 'eselect python set 3' cannot be executed by users other then the one who made the installation. All in all, I would be happy if this thread helps to ensure the read bits are enabled for everybody, probably bootstrap*.sh would ask user to override his/her umask setting and making the permission more opened.
find $EPREFIX -exec chmod g+rX,o+rX '{}' \+ or something Closing this bug, as there's not much we can do here apart from post-fixups.
