public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] fstab cleanup
Date: Wed, 21 May 2014 15:44:04 -0400	[thread overview]
Message-ID: <CAOdo=SwS51DasjNjvvHEPs3Bgss-xi+wyp+7+nJxmderG14ULA@mail.gmail.com> (raw)
In-Reply-To: <537CE803.5040007@xunil.at>

On Wed, May 21, 2014 at 1:53 PM, Stefan G. Weichinger <lists@xunil.at> wrote:
> Am 21.05.2014 15:31, schrieb Tom H:
>> On Wed, May 21, 2014 at 6:32 AM, Stefan G. Weichinger <lists@xunil.at> 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 expandable/shrinkable ramdisk, and will
>>> #  use almost no memory if not populated with files)
>>> tmpfs                   /dev/shm        tmpfs
>>> nodev,nosuid,noexec     0 0
>>>
>>>
>>> /dev/cdrw               /media/cdrecorder       auto
>>> user,exec,noauto,managed 0 0
>>
>> From "src/core/mount-setup.c":
>>
>> { "tmpfs",      "/dev/shm",                  "tmpfs",
>> "mode=1777", MS_NOSUID|MS_NODEV|MS_STRICTATIME, NULL,
>> MNT_FATAL|MNT_IN_CONTAINER },
>
> So the answer is "no" ?

The answer is "no" unless you want to apply different perms to "/dev/shm".


  reply	other threads:[~2014-05-21 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 10:32 [gentoo-user] fstab cleanup Stefan G. Weichinger
2014-05-21 13:31 ` Tom H
2014-05-21 17:53   ` Stefan G. Weichinger
2014-05-21 19:44     ` Tom H [this message]
2014-05-21 20:15       ` Mick
2014-05-21 20:40       ` Stefan G. Weichinger
2014-05-26  4:47 ` [gentoo-user] " Nikos Chantziaras
2014-05-26  6:27   ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOdo=SwS51DasjNjvvHEPs3Bgss-xi+wyp+7+nJxmderG14ULA@mail.gmail.com' \
    --to=tomh0665@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox