From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What is the proper fstab line for shm memory (tmpfs)
Date: Fri, 26 Feb 2010 13:28:52 +0100 [thread overview]
Message-ID: <201002261328.52839.volkerarmin@googlemail.com> (raw)
In-Reply-To: <1267186392.8861.9.camel@rattus>
On Freitag 26 Februar 2010, William Kenworthy wrote:
> I have a number of systems with different shm lines in fstab - but which
> is correct? - I think they all work, but which is best (and why)? The
> main use I am concerned about is a PXE system with root over nfs where I
> am putting the portage tmp and some other stuff in tmpfs for speed.
>
> tmpfs /dev/shm tmpfs defaults 0 0
> shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
> none /dev/shm tmpfs defaults 0 0
>
> I suspect the middle line is correct.
>
> BillK
I have
shm /dev/shm tmpfs nodev,nosuid,noexec
0 0
for ages in fstab. If it is wrong, I am living a lie for years now.
next prev parent reply other threads:[~2010-02-26 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 12:13 [gentoo-user] What is the proper fstab line for shm memory (tmpfs) William Kenworthy
2010-02-26 12:28 ` Volker Armin Hemmann [this message]
2010-02-26 12:57 ` William Kenworthy
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=201002261328.52839.volkerarmin@googlemail.com \
--to=volkerarmin@googlemail.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