ottokiksmaler
commented
8 years ago Power notifiers are for kernel modules (drivers) and are not accessible from userspace (to use them we would need to change some driver to publish them through debugfs or similar, etc). Process is just frozen and unfrozen - there is no signal, etc, to it. That said, keyscan already does detect it has been frozen (it runs a test every second and measures time between measurements - if it's larger than 1s+small_delta it detects a sleep/wake event). Cold boot can be detected by creating a file on /tmp as it gets wiped on cold restart (it lives in RAM).
vasile-gh
ge0rg
KinoSeed
I will receive the burner some time this week - I hope - and am thinking about how to best achieve the subject. For the time being I feel that having working systemd hibernation/suspend wakeup services would be best because they would be inline with general GNU/Linux philosophy. BUT systemd says this is should be considered a hack, and we don't want that, do we? :-) and that there are nicer interfaces available. @ottokiksmaler Would you be able to change keyscan to take advantage of this? In fact I would propose splitting keyscan in two:
This way we could have (1) a very stable and small program to be integrated in the hibernation image (unlikely to require frequent changes, which is what we want because updating the hibernation image is still going to be comparatively a bit more dangerous), and (2) an easily update-able mod environment on /opt.
I would also suggest we stop supporting sdcard resident mods, and do a wholesale adoption of internal (/opt) mods.
Thoughts?