README.md

@@ -1,7 +1,7 @@
-![systemd logo](http://brand.systemd.io/assets/page-logo.png)
-
 # systemd - System and Service Manager
 
+![systemd logo](https://avatars0.githubusercontent.com/u/1918868?s=200&v=4)
+
 <a href="https://in.waw.pl/systemd-github-state/systemd-systemd-issues.svg"><img align="right" src="https://in.waw.pl/systemd-github-state/systemd-systemd-issues-small.svg" alt="Count of open issues over time"></a>
 <a href="https://in.waw.pl/systemd-github-state/systemd-systemd-pull-requests.svg"><img align="right" src="https://in.waw.pl/systemd-github-state/systemd-systemd-pull-requests-small.svg" alt="Count of open pull requests over time"></a>
 [![Semaphore CI Build Status](https://semaphoreci.com/api/v1/projects/28a5a3ca-3c56-4078-8b5e-7ed6ef912e14/443470/shields_badge.svg)](https://semaphoreci.com/systemd/systemd)<br/>

TODO

@@ -28,33 +28,6 @@ Features:
 * socket units: allow creating a udev monitor socket with ListenDevices= or so,
   with matches, then actviate app thorugh that passing socket oveer
 
-* move discoverable partitions spec into markdown and our tree
-
-* sd-event: add native support for P_ALL waitid() watching, then move PID 1 to
-  it fo reaping assigned but unknown children. This needs to some special care
-  to operate somewhat sensibly in light of priorities: P_ALL will return
-  arbitrary processes, regardless of the priority we want to watch them with,
-  hence on each event loop iteration check all processes which we shall watch
-  with higher prio explicitly, and then watch the entire rest with P_ALL.
-
-* tweak sd-event's child watching: keep a prioq of children to watch and use
-  waitid() only on the children with the highest priority until one is waitable
-  and ignore all lower-prio ones from that point on
-
-* sd-event: drop stack allocated epoll_event buffer in sd_event_wait()
-
-* maybe introduce xattrs that can be set on the root dir of the root fs
-  partition that declare the volatility mode to use the image in. Previously I
-  thought marking this via GPT partition flags but that's not ideal since
-  that's outside of the LUKS encryption/verity verification, and we probably
-  shouldn't operate in a volatile mode unless we got told so from a trusted
-  source.
-
-* look for /var/tmp automatically via gpt auto discovery
-
-* figure out automatic partition discovery when combining writable root dir
-  with immutable /usr
-
 * coredump: maybe when coredumping read a new xattr from /proc/$PID/exe that
   may be used to mark a whole binary as non-coredumpable. Would fix:
   https://bugs.freedesktop.org/show_bug.cgi?id=69447