Since my distro is based on Archlinux I might go for the initrd-way.
Currently I'm testing the shutdown-script way ...
Am 15.09.2012 10:24, schrieb Philip Müller:
Yes it is the root-disk. I managed it by overwritting all messages
with attached script.
No issues at all. It displays my message and reacts as wanted. No
hangups etc.
Am 14.09.2012 19:20, schrieb Lennart Poettering:
On Fri, 14.09.12 00:14, Philip Müller ([email protected]) wrote:
So, seems to work. I attached my current scripts and two picutes
with error messages.
Also I added now *read -t 30* and fixed hanging by pressing the
Enter-key. Is there any way
to hide those error messages (seems the system still tries to read
from CD after it got ejected),
so my message gets displayed clean? Maybe there is a way to get it
cleaner.
You are ejecting the root disk? Well, that's difficult to get right.
You could transition back into an initrd of some kind and print the
message there:
http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface
Or you could print this message from a script in
/usr/lib/systemd/system-shutdown and hope for the best. (And turn off
console printk output via /proc/sys/kernel/printk first). Since the
systemd-shutdown binary (which runs at the very end) locks itself into
memory you might be able to get away with that. That said, the initrd
thing is the only fix that would really get this right.
Lennart
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
