On Tuesday 26 August 2014 at 17:42:54, Dave Reisner wrote: > On Wed, Aug 27, 2014 at 12:47:10AM +0400, Ivan Shapovalov wrote: > > This depends on the systemd hook. It adds [email protected] > > and systemd-hibernate-resume-generator which perform userspace parsing of > > resume= kernel parameter, allowing to specify the resume device by its > > persistent path ("resume=/dev/disk/by-foo/bar") or fstab-like specifier > > ("resume=FOO=bar"), just like the root= parameter. > > --- > > > > Given that relevant functionality has just landed in systemd git, it makes > > sense to pipeline things a bit (even if actual applying will be delayed > > until > > systemd-217). > > > > Also, does this need to be a separate hook or can be merged into 'systemd' > > hook itself? > > This belongs in mkinitcpio proper, along with the systemd hooks > currently residing in the core/systemd package. You can blame me for the > latter not yet happening. Given that, we should probably add this to the > systemd package for now, as to not give people the idea that sd-resume > can be used without the systemd hook. > > Thanks so much for pushing this work upstream!
I'm confused a bit. Do you say that the 'systemd' hook currently in core/systemd shall be eventually moved to core/mkinitcpio? Either way, there are 'sd-vconsole' and 'sd-shutdown' already in core/mkinitcpio. I think that if 'sd-resume' will be a separate hook, then either it should be placed here, or all three sd-* hooks should be moved to core/systemd. (The global alternative -- viability unknown -- is not to make 'sd-resume' a separate hook but to add all this directly from 'systemd' hook.) -- Ivan Shapovalov / intelfx /
signature.asc
Description: This is a digitally signed message part.
