Compare commits

..

No commits in common. "b9dc511954b080d8b05a44f1758be6dbb4078852" and "6878c02245b49987749e73a12003fcf07bf173ca" have entirely different histories.

2 changed files with 4 additions and 12 deletions

View File

@ -27,11 +27,11 @@ BuildPackages=
docbook-xsl docbook-xsl
elfutils elfutils
gcc gcc
gettext
git git
gnu-efi-libs gnu-efi-libs
gnutls gnutls
gperf gperf
inetutils
iptables iptables
kmod kmod
libcap libcap

14
TODO
View File

@ -17,17 +17,6 @@ Janitorial Clean-ups:
* rework mount.c and swap.c to follow proper state enumeration/deserialization * rework mount.c and swap.c to follow proper state enumeration/deserialization
semantics, like we do for device.c now semantics, like we do for device.c now
Before v244:
* revisit SystemdOptions EFI variable. Find a better, systematic name and use
it for the env var, the bootctl verb and the EFI variable itself, clear up
semantics.
* Figure out a better name for the global per-unit-type drop-in dirs, it's
confusing when it comes to -.mount.d/ (is it a drop-in-dir for all mount
units, or one for the root mount?). Also, OOM handling in
service_unit_name_is_valid() is borked.
Features: Features:
* coredump: maybe when coredumping read a new xattr from /proc/$PID/exe that * coredump: maybe when coredumping read a new xattr from /proc/$PID/exe that
@ -268,6 +257,9 @@ Features:
* bypass SIGTERM state in unit files if KillSignal is SIGKILL * bypass SIGTERM state in unit files if KillSignal is SIGKILL
* tree-wide: ensure we always block the signals we hook into with
sd_event_add_signal() first
* add proper dbus APIs for the various sd_notify() commands, such as MAINPID=1 * add proper dbus APIs for the various sd_notify() commands, such as MAINPID=1
and so on, which would mean we could report errors and such. and so on, which would mean we could report errors and such.