<p dir="ltr"><br>
On Jul 22, 2013 6:44 PM, "Lennart Poettering" <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>> wrote:<br>
><br>
> On Fri, 19.07.13 22:02, Dave Reisner (<a href="mailto:d@falconindy.com">d@falconindy.com</a>) wrote:<br>
><br>
> > Hi,<br>
> ><br>
> > With systemd 206 near release, I'd like to understand if commit<br>
> > c72aadd1851096ea is going to stand. This commit removes support for<br>
> > reading RD_TIMESTAMP in the initramfs, and thus makes systemd mandatory<br>
> > for measuring initramfs runtime.<br>
> ><br>
> > If this is the intended future, please help me to understand the<br>
> > rationale behind removing 25 lines of code for a useful feature -- one<br>
> > which has extremely low overhead and is self contained code-wise.<br>
> ><br>
> > I strongly object to the way this was done and would appreciate a more<br>
> > "official" explanation.<br>
><br>
> (I didn't remove the lines in question, but I am fine with it.)<br>
><br>
> So, we try to keep our code base clean. We delete stuff from time to<br>
> time if it it's obsolete and not important to keep for<br>
> compatibility. RD_TIMESTAMP is obsolete, we can do this much better now<br>
> (and more comprehensively) via serializing/deserializing systemd state<br>
> between inird and the host OS. And the stuff is not important for<br>
> compatibility, since this always has been one of those features that if<br>
> detected are used, but if they aren't it doesn't matter much. It's<br>
> nothing that prevents you to boot, causes services to fail, corrupts<br>
> anything. It's really just about whether "systemd-analyze" will you show<br>
> 3 boot time values split out instead of 2...<br>
><br>
> I do understand that you are currently not running systemd in the initrd<br>
> [1], so for you for now this is indeed a loss of functionality. I am<br>
> sorry for that, but please understand this as gentle push to maybe use<br>
> systemd in the initrd, or even better maybe just adopt dracut?</p>
<p dir="ltr">OK sure. Let's talk about getting rid of the compat crap for sysvinit which is peppering the code base.</p>
<p dir="ltr">Arch won't ever be adopting dracut. We've added systemd support to mkinitcpio.</p>
<p dir="ltr">><br>
> Lennart<br>
><br>
> [1] I remember Arch's Tom Gunderson working with Harald on improving the<br>
> mounting logic in darcut/systemd quite a bit at the last<br>
> hackfest. Because of Arch we now have much nicer mount code in<br>
> Dracut/systemd. It would be a pitty if that'd be lost to Arch itself,<br>
> where this came from...<br>
><br>
> --<br>
> Lennart Poettering - Red Hat, Inc.<br>
> _______________________________________________<br>
> systemd-devel mailing list<br>
> <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a><br>
</p>