From: Mekeor Melire <mekeor@posteo.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Ivan Vilata i Balaguer <ivan@selidor.net>, guix-devel@gnu.org
Subject: Re: Status of hibernation (suspend to disk) in Guix
Date: Fri, 09 Dec 2022 20:52:00 +0000 [thread overview]
Message-ID: <87k030l2fa.fsf@posteo.de> (raw)
In-Reply-To: <87wn79wnfj.fsf@nckx>
2022-12-02 21:32 me@tobias.gr:
> Ivan Vilata i Balaguer 写道:
> > But then I wonder if I may have rushed to post the patch, as I don't
> > know whether hibernation is supposed to be more or less mature or
> > supported in Guix (we may not want to encourage people to use a
> > feature which may easily cause data loss)… Though it works quite
> > well for me!
>
> OTOH, I deliberately hadn't documented ‘resume=’ so far.
>
> OTOH, I have been hibernating multiple times a day for years now, only
> ever rebooting my laptop for kernel updates.
>
> So the feature is probably safe, and we should probably consider it
> supported at this point. Thanks for bringing it up!
>
> > So the TL;DR would be: Is it worth adding such documentation, given
> > the current state of hibernation support in Guix?
>
> I think documenting the current status quo in time for 1.4.0 is a good
> idea.
>
> The next step is to automate things so ‘resume=’ becomes optional.
> This should have landed already, but hasn't for personal reasons. The
> code is basically ready, but won't be in the release.
Thanks for making hibernation work and for bringing that up. I have two
questions:
1. Does hibernation work in case of swap-partition inside an
luks-encrypted device?
2. Does hibernation work in case of a swap-file inside a
root-partition inside a luks-encrypted device?
Also, I'm not sure if it makes sense to mark the hibernation-feature
stable and finished if the mentioned two cases are not supported.
next prev parent reply other threads:[~2022-12-09 20:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 20:12 Status of hibernation (suspend to disk) in Guix Ivan Vilata i Balaguer
2022-12-02 20:32 ` Tobias Geerinckx-Rice
2022-12-05 16:23 ` Ivan Vilata i Balaguer
2022-12-09 23:10 ` Mekeor Melire
2022-12-10 1:00 ` Mekeor Melire
2022-12-12 20:11 ` Ivan Vilata i Balaguer
2022-12-14 9:43 ` Ivan Vilata i Balaguer
2022-12-21 12:27 ` Ivan Vilata i Balaguer
2023-01-07 11:36 ` Ivan Vilata i Balaguer
2022-12-09 20:52 ` Mekeor Melire [this message]
2022-12-09 21:16 ` Jack Hill
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 6:55 Nathan Dehnel
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=87k030l2fa.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=guix-devel@gnu.org \
--cc=ivan@selidor.net \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.