Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Tobias Hunger
Am 20.04.2016 06:47 schrieb "Chris Murphy" : > I kinda have to agree, if it can't be encrypted, then I think linux > hibernation is almost pointless, and maybe just give up. Intel Rapid > Start (firmware managed) hibernation with SSDs and the proper GPT > partition type GUID is faster and more reli

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Chris Murphy
On Tue, Apr 19, 2016 at 4:10 AM, Lennart Poettering wrote: > > So what precisely are you proposing? That we actively search for the > swap partition in the hibernate-resume generator? I think the main thing James is after, I know I'm in this camp, is understanding all the parts and how they inte

Re: [systemd-devel] service dependency on udev

2016-04-19 Thread Andrei Borzenkov
20.04.2016 04:27, Flavio Leitner пишет: > On Wed, Apr 20, 2016 at 05:34:49AM +0900, Greg KH wrote: >> On Tue, Apr 19, 2016 at 05:25:09PM -0300, Flavio Leitner wrote: >>> >>> Hello, >>> >>> I have a service that needs to start after all the devices (network >>> cards at least) have been properly pro

Re: [systemd-devel] service dependency on udev

2016-04-19 Thread Flavio Leitner
On Wed, Apr 20, 2016 at 05:34:49AM +0900, Greg KH wrote: > On Tue, Apr 19, 2016 at 05:25:09PM -0300, Flavio Leitner wrote: > > > > Hello, > > > > I have a service that needs to start after all the devices (network > > cards at least) have been properly processed by udev. Pretty much > > like the

Re: [systemd-devel] service dependency on udev

2016-04-19 Thread Greg KH
On Tue, Apr 19, 2016 at 05:25:09PM -0300, Flavio Leitner wrote: > > Hello, > > I have a service that needs to start after all the devices (network > cards at least) have been properly processed by udev. Pretty much > like the old 'network' sysv script. > > Any suggestion? How do you define "al

[systemd-devel] service dependency on udev

2016-04-19 Thread Flavio Leitner
Hello, I have a service that needs to start after all the devices (network cards at least) have been properly processed by udev. Pretty much like the old 'network' sysv script. Any suggestion? Thanks, -- fbl ___ systemd-devel mailing list systemd-d

Re: [systemd-devel] SELinux is preventing (ostnamed) from mounton access on the directory /home

2016-04-19 Thread Lennart Poettering
On Tue, 19.04.16 16:24, Samuel Rakitničan (samuel.rakitni...@gmail.com) wrote: > Hello, > > I have a system that is an upgrade from Fedora 23 to Fedora 24 Alpha. > Occasionally I get messages about selinux blocking systemd-hostnamed from > mounton access on /home. I can trigger this issue by runn

[systemd-devel] SELinux is preventing (ostnamed) from mounton access on the directory /home

2016-04-19 Thread Samuel Rakitničan
Hello, I have a system that is an upgrade from Fedora 23 to Fedora 24 Alpha. Occasionally I get messages about selinux blocking systemd-hostnamed from mounton access on /home. I can trigger this issue by running command hostnamectl. Is this supposed to happen? Is systemd-hostnamed supposed to do

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Harald Hoyer
Am 19.04.2016 um 12:10 schrieb Lennart Poettering: > On Mon, 18.04.16 23:19, James Hogarth (james.hoga...@gmail.com) wrote: > >> Hi all, >> >> There's been some discussion today about the impact of >> https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the problem >> actually lies. >> >>

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Lennart Poettering
On Tue, 19.04.16 08:45, James Hogarth (james.hoga...@gmail.com) wrote: > It could also be fixed by anaconda adding resume= to the grub configuration > like it already has to for the root device. The anaconda developers have > already pushed against this and it would only fix fresh installs anyway.

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Lennart Poettering
On Tue, 19.04.16 07:45, James Hogarth (james.hoga...@gmail.com) wrote: > The generator and the actual resume is already in systemd and the anaconda > folks on the bug did not think it should be with them and that adding > resume= would not be the correct fix (of course that additionally has the >

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Lennart Poettering
On Mon, 18.04.16 23:19, James Hogarth (james.hoga...@gmail.com) wrote: > Hi all, > > There's been some discussion today about the impact of > https://bugzilla.redhat.com/show_bug.cgi?id=1206936 and where the problem > actually lies. > > The issue lies specifically with hibernate and affects all

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread James Hogarth
On 19 Apr 2016 08:05, "Andrei Borzenkov" wrote: > > On Tue, Apr 19, 2016 at 9:45 AM, James Hogarth wrote: > > > > > Seeing as systemd decides the swap to hibernate to in the first place, can't > > No, it does not. Device to hibernate to is set by previous attempt to > resume from. This device mus

Re: [systemd-devel] systemd hibernator generator does not function on default Fedora install

2016-04-19 Thread Andrei Borzenkov
On Tue, Apr 19, 2016 at 9:45 AM, James Hogarth wrote: > > Seeing as systemd decides the swap to hibernate to in the first place, can't No, it does not. Device to hibernate to is set by previous attempt to resume from. This device must come from somewhere. Last device someone attempted to resume