On Thu, Oct 9, 2014 at 8:02 AM, Valeri Galtsev galtsev@kicp.uchicago.edu wrote:
was - the requirements at that time were nearly/completely different. We have different scenarios right now.
Really? What application could you not start with sysv init syntax? What CPU has become too slow to start things serially? What feature do you need that could not have been added without breaking other existing work?
<irony> The feature of advantage is fast boot. As Linux like Windows needs reboot often, it is awfully important. And all of you, dinosaurs (who saw years long uptime of Linux machines) who don't care that boot takes 60 seconds now instead of 4 minutes should just shut up. </irony>
Let me second what you said. I also would add: In my opinion it is not clever to keep settings that are expressed by plain ASCII text being marked up, "dressed into junk", XML. For human to read them you need "undress" them (you GUI guys may forget that your GUI does that - not literally of course), and to pass them to systemd itself one has strip the junk (XML markup). The same goes about firewalld.
But what am I doing. The World passed that point...
I guess debugging the GUIs that make the config files accessible will be job security for the young guys that replace us...