On Fri, Oct 3, 2014 at 11:42 PM, Joseph <[email protected]> wrote: > On 10/03/14 23:00, Mike Gilbert wrote: >> >> On Fri, Oct 3, 2014 at 10:22 PM, Joseph <[email protected]> wrote: >>> >>> I'm getting an error message during emerge: >>> * configure has detected that the sem_open function is broken. >>> * Please ensure that /dev/shm is mounted as a tmpfs with mode 1777. >>> * ERROR: dev-lang/python-3.3.5-r1::gentoo failed (configure phase): >>> >>> my /dev/shm is mounted as drwxr-xr-x 17 root root 4020 Oct 3 >>> 08:57 >>> shm >>> >>> and it should be: >>> drwxrwxrwt 2 root root 100 Sep 29 09:25 shm >>> >>> I've already change in fstab: >>> from: >>> shm /dev/shm devtmpfs >>> nodev,nosuid,noexec >>> 0 0 >>> >>> to: >>> shm /dev/shm tmpfs >>> defaults,nodev,nosuid,mode=1777 0 0 >>> >>> Is it OK to run: >>> umount shm >>> mount shm >>> >>> This is a remount system, so I want to make sure I'm not making a >>> mistake. >>> >> >> Yes, that should be fairly safe to run. The only risk is if you have >> some application running which has files open on it; but umount should >> give you an error in that case. >> >> Also, you can/should remove that fstab entry entirely once you have >> remounted it; both openrc and systemd will automatically mount >> /dev/shm with proper permissions if it is missing from fstab. > > > Will it? > In my kernel confg I have: > > grep CONFIG_DEVTMPFS /usr/src/linux/.config CONFIG_DEVTMPFS=y > # CONFIG_DEVTMPFS_MOUNT is not set > > should I set "CONFIG_DEVTMPFS_MOUNT=y" >
It has nothing to do with that kernel option.
