From: Vincent Legoll <vincent.legoll@gmail.com>
To: ng0 <ng0@pragmatique.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: swap activation of guix system when swap is already active
Date: Tue, 16 May 2017 08:44:56 +0200 [thread overview]
Message-ID: <CAEwRq=r7GaL6yxu=RJCfRg5TOSDP93FT-=H+L+SbaVcNs9sZPA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.1705160003410.20926@ybpnyubfg>
> Shouldn't we 'swapoff' before 'swapon' so that the device can be 'swapon' in
> the system generation?
If you do that after checking that the swap device / file is already
on, you cloud also
just do nothing then, I'm not sure there's anything to be gained by
doing off+on...
WDYT ?
--
Vincent Legoll
prev parent reply other threads:[~2017-05-16 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 0:07 swap activation of guix system when swap is already active ng0
2017-05-16 6:44 ` Vincent Legoll [this message]
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='CAEwRq=r7GaL6yxu=RJCfRg5TOSDP93FT-=H+L+SbaVcNs9sZPA@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@pragmatique.xyz \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).