| 1 |
On Wed, May 21, 2014 at 1:53 PM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 2 |
> Am 21.05.2014 15:31, schrieb Tom H: |
| 3 |
>> On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 4 |
>>> |
| 5 |
>>> Do I still need these lines .. especially with a modern |
| 6 |
>>> systemd/gnome3-environment? |
| 7 |
>>> |
| 8 |
>>> # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for |
| 9 |
>>> # POSIX shared memory (shm_open, shm_unlink). |
| 10 |
>>> # (tmpfs is a dynamically expandable/shrinkable ramdisk, and will |
| 11 |
>>> # use almost no memory if not populated with files) |
| 12 |
>>> tmpfs /dev/shm tmpfs |
| 13 |
>>> nodev,nosuid,noexec 0 0 |
| 14 |
>>> |
| 15 |
>>> |
| 16 |
>>> /dev/cdrw /media/cdrecorder auto |
| 17 |
>>> user,exec,noauto,managed 0 0 |
| 18 |
>> |
| 19 |
>> From "src/core/mount-setup.c": |
| 20 |
>> |
| 21 |
>> { "tmpfs", "/dev/shm", "tmpfs", |
| 22 |
>> "mode=1777", MS_NOSUID|MS_NODEV|MS_STRICTATIME, NULL, |
| 23 |
>> MNT_FATAL|MNT_IN_CONTAINER }, |
| 24 |
> |
| 25 |
> So the answer is "no" ? |
| 26 |
|
| 27 |
The answer is "no" unless you want to apply different perms to "/dev/shm". |
Archives