On Tue, 26.08.14 15:49, Ivan Shapovalov (intelfx...@gmail.com) wrote:
Hmm, the fact that the kernel cmdline option is named resume is
probably a strong indication we should stick to that nomenclature, after
all that's UI already in away...
But maybe call it
On Mon, 25.08.14 02:16, Ivan Shapovalov (intelfx...@gmail.com) wrote:
+
+static const char *arg_dest = /tmp;
+static char *arg_resume_dev = NULL;
+
+static int parse_proc_cmdline_item(const char *key, const char *value) {
+if (streq(key, resume) value) {
+
On Monday 25 August 2014 at 19:58:52, Lennart Poettering wrote:
[...]
One more question though, regarding the terminology. So far we used the
following terms:
suspend → means suspend-to-ram
hibernate → means suspend-to-disk
hybrid-sleep → means both STR + STD combined
On Mon, 25.08.14 22:27, Ivan Shapovalov (intelfx...@gmail.com) wrote:
On Monday 25 August 2014 at 19:58:52, Lennart Poettering wrote:
[...]
One more question though, regarding the terminology. So far we used the
following terms:
suspend → means suspend-to-ram
resume-generator understands resume= kernel command line parameter and
instantiates the systemd-resume@.service accordingly if it is passed.
This enables resume from hibernation using device specified on the kernel
command line, where the device path may point to an arbitrary udev-created
