Summary: | Incorrect permissions set on fixdep (=sys-kernel/gentoo-sources-2.6.30-r7) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Roger <rogerx.oss> |
Component: | New packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Roger
2009-10-22 05:30:59 UTC
Can you please post your emerge --info This is not a gentoo-sources issue as this file and it's permissions are created during kernel compilation. Think I found it. I have umask set for user 0077 within .bashrc When su'ing over to root, the umask settings are preserved at 0077 instead of switching to the default within /etc/profile. I'm guessing, if a user is going to use umask for a user, they should also set the defaults (listed within /etc/profile as 0022) within the root's .bashrc as well. I'm also finding I have to do a chmod -R a+X /usr/src/linux to get the kernel sources readable by rsync on the remote hosts. I'll find out within the next week as I'm currently upgrading GCC and re-emerging system/world if this, in fact, is the culprit. If so, I suggest adding an additional note within /etc/profile (top of file is where umask is set) concerning possible file permission errors if changing the default or root's umask -- hence, the user designated to use emerge. (Also, I'm using =sys-apps/portage-2.2_rc46 -- for which might be a culprit further down the line if profile's umask is irrelevant.) |