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 "systemd-hibernate-resume@.service" and
> > systemd-hibernate-resume-generator or so?
> > 
> > Longer to type but more precise, and I figure nobody has to type this
> > ever anyway...
> 
> That's what will be reflected in manpages. I'd argue that "systemd-resume"
> is how one expects this feature to be named -- support from "systemd" side
> for the kernel feature called "resume".

Well, I am mostly thinking about somebody who wonders what that service
is about if he doesn't know that the kernel details and the kernel
cmdline option yet.

I think systemd-hibernate-resume has the benefit that both folks who
already know the kernel side of things, and people who don't know
anything about this at all yet, have both a chance to grok what this is
about.

If I don#t now the kernel side of things, then I would always have
assume that "systemd-resume" is something that is involved with STR, not
STD... "systemd-hibernate-resume.service" otoh makes this very clear, and also
pairs this up nicely to the existing "systemd-hibernate.service".

Lennart

-- 
Lennart Poettering, Red Hat
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to