From: "Clément Lassieur" <clement@lassieur.org>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Mount /tmp as tmpfs?
Date: Thu, 17 May 2018 20:21:13 +0200 [thread overview]
Message-ID: <87d0xuqh2e.fsf@lassieur.org> (raw)
In-Reply-To: <87y3gigqp8.fsf@gmail.com>
Pierre Neidhardt <ambrevar@gmail.com> writes:
> I was wondering if it's commendable to mount /tmp as tmpfs with GuixSD.
> I think it could be useful to speed up Guix builds.
>
> What would be the best way to do so?
> Can't test now, but what about
>
> (file-system
> (mount-point "/tmp")
> (device "tmpfs")
> (type "tmpfs")
> (flags '(no-dev no-suid))
>
> ?
I use:
(file-system
(mount-point "/tmp")
(device "none")
(title 'device)
(type "tmpfs")
(check? #f))
And it works perfectly.
next prev parent reply other threads:[~2018-05-17 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 17:03 Mount /tmp as tmpfs? Pierre Neidhardt
2018-05-17 18:21 ` Clément Lassieur [this message]
2018-05-17 18:26 ` Pierre Neidhardt
2018-05-18 10:53 ` Nils Gillmann
2018-05-18 11:20 ` Clément Lassieur
2018-05-18 11:22 ` Pierre Neidhardt
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0xuqh2e.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).