On Mon, 2017-04-24 at 09:27 +0200, Bjørn Mork wrote:
> Ben Hutchings writes:
>
> > The change in version 0.128 to wait for the resume device to appear
> > uncovered a number of systems for which the resume device is not
> > properly configured. In fact, systems with swap
Ben Hutchings writes:
> The change in version 0.128 to wait for the resume device to appear
> uncovered a number of systems for which the resume device is not
> properly configured. In fact, systems with swap partitions that
> are never available at boot could not be
On Fri, 2017-04-21 at 11:02 +0200, Martin Steigerwald wrote:
[...]
> Currently I don´t have uswsusp installed, but pm-utils is
> still there. I am not sure whether systemd uses it or does it all by itself
> tough.
I think 'systemctl hibernate' invokes in-kernel swsusp by default. I
don't know
* Ben Hutchings [Fri Apr 21, 2017 at 04:33:09AM +0100]:
> The change in version 0.128 to wait for the resume device to appear
> uncovered a number of systems for which the resume device is not
> properly configured. In fact, systems with swap partitions that
> are never available at boot could
Dear Ben.
Ben Hutchings - 21.04.17, 04:33:
> The change in version 0.128 to wait for the resume device to appear
> uncovered a number of systems for which the resume device is not
> properly configured. In fact, systems with swap partitions that
> are never available at boot could not be
The change in version 0.128 to wait for the resume device to appear
uncovered a number of systems for which the resume device is not
properly configured. In fact, systems with swap partitions that
are never available at boot could not be configured correctly,
other than by adding 'noresume' to
6 matches
Mail list logo