Am 21.05.2014 21:44, schrieb Tom H:
> The answer is "no" unless you want to apply different perms to "/dev/shm".
I don't have an idea why I should want to do that so I removed the line
for now. Thanks.
Stefan
On Wednesday 21 May 2014 20:44:04 Tom H wrote:
> On Wed, May 21, 2014 at 1:53 PM, Stefan G. Weichinger
wrote:
> > Am 21.05.2014 15:31, schrieb Tom H:
> >> On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger
wrote:
> >>> Do I still need these lines .. especially with a modern
> >>> systemd/gno
On Wed, May 21, 2014 at 1:53 PM, Stefan G. Weichinger wrote:
> Am 21.05.2014 15:31, schrieb Tom H:
>> On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger wrote:
>>>
>>> Do I still need these lines .. especially with a modern
>>> systemd/gnome3-environment?
>>>
>>> # glibc 2.2 and above expects
Am 21.05.2014 15:31, schrieb Tom H:
> On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger wrote:
>>
>> Do I still need these lines .. especially with a modern
>> systemd/gnome3-environment?
>>
>> # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
>> # POSIX shared memory (shm_open
On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger wrote:
>
> Do I still need these lines .. especially with a modern
> systemd/gnome3-environment?
>
> # glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
> # POSIX shared memory (shm_open, shm_unlink).
> # (tmpfs is a dynamically e
Do I still need these lines .. especially with a modern
systemd/gnome3-environment?
->
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not
6 matches
Mail list logo
