This has been implemented a while back, see
405e116f57b1cf33d4ca0294ab045a9f709bbc96
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1354306
Title:
gpio shutdown trigger
This has been implemented a while back, see
405e116f57b1cf33d4ca0294ab045a9f709bbc96
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1347776
Title:
shutdown trigger on
OK, if this is not a bytes value, parse_size() is probably not a good
idea. (that said, I think it's a pretty poor choice to expose this as
512byte block value...)
Anyway, looks good. Please push!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Also, please add the initialization of .offset and .skip into the
declaration of the params variable, as initializer. i.e.:
struct crypt_params_plain params = {
.offset = arg_offset,
.skip = arg_skip,
};
Also, please document the new switches in crypttab(5).
--
You received
Hmm, please use parse_bytes() for parsing byte values.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/953875
Title:
Encrypted swap no longer mounted at bootup
Status in
(In reply to Lennart Poettering from comment #6)
Hmm, please use parse_bytes() for parsing byte values.
Sorry, I meant parse_size() of course.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https
(In reply to Martin Pitt from comment #13)
(In reply to Lennart Poettering from comment #12)
The best way is to fix the few services that really need dbus
unconditionally to be around to add After=dbus.service. And all is good.
If we go with that approach, then it would IMHO be cleaner
Please do not apply that ExecStop= thing. You really shouldn't block
that. Think about people who boot their system with emergency on the
kernel cmdline, and thus get a PID 1 plus a shell and nothing else, they
should be able to start dbus and stop it as they wish...
If at all, use
I think the proper way to fix this is by waiting for this kernel patch
to be applied:
http://www.spinics.net/lists/linux-input/msg33007.html
With that in place we can then update logind to make use of it, and then
simply add the udev tag to all keyboards that are discovered, which
would then
I think the proper way to fix this is by waiting for this kernel patch
to be applied:
http://www.spinics.net/lists/linux-input/msg33007.html
With that in place we can then update logind to make use of it, and then
simply add the udev tag to all keyboards that are discovered, which
would then
10 matches
Mail list logo
