Recent Features
| |||||||||||||
LCE: Systemd two years onLCE: Systemd two years onPosted Nov 8, 2012 3:11 UTC (Thu) by kenmoffat (subscriber, #4807)Parent article: LCE: Systemd two years on
This is the first time I've been disappointed by an lwn article! It reads like pure propaganda, as if systemd is th only convceivable future. Personally, I'm happy to run /bin/bash init scripts on LFS - no. my boot is nothing tlike as quick as was suggested (15 seconds from pushing the on/off switch until getting to grub, on this amd64 machine, and then about another 15 seconds to boot), but I still haven't seen any reason to abjure shell scripts for init.
(Log in to post comments)
LCE: Systemd two years on Posted Nov 8, 2012 3:33 UTC (Thu) by mattdm (subscriber, #18) [Link]
The tone does come off as a little partisan. LWN editorials often do show strong opinions, but almost always in a self-aware way. Comments like "The problem with shell scripts, of course...", on the other hand, seem a little off.
LCE: Systemd two years on Posted Nov 8, 2012 3:47 UTC (Thu) by bjencks (subscriber, #80303) [Link]
I think it's pretty typical for a conference report -- he's reporting on what was said, and since Lennart was the one speaking it would obviously be partisan.
LCE: Systemd two years on Posted Nov 8, 2012 6:51 UTC (Thu) by eyal (subscriber, #949) [Link]
This article is not an overview of init systems, but a coverage of a talk about systemd given by systemd's creator and lead developer.
As such, it is a(nother) fine article from LWN.
Eyal.
LCE: Systemd two years on Posted Nov 8, 2012 10:00 UTC (Thu) by BradReed (subscriber, #5917) [Link]
I am also unsure with what the major problem is with system logs being in plain text. A failure in being able to read the last 10 messages of a particular service? I guess grep and tail are too old fashioned for modern linux users.
LCE: Systemd two years on Posted Nov 8, 2012 11:15 UTC (Thu) by dan_a (subscriber, #5325) [Link]
Grep and tail are fine for users (or for advanced users.) They are less fine for automated log parsing.
I'm a bit worried, though, about how divergent the platforms for server and desktop Linux might end up becoming by going down the path of Journal vs. Syslog - server admins don't always have the same needs as desktop users, but it can't be helpful if the tools they use diverge too much.
LCE: Systemd two years on Posted Nov 8, 2012 14:38 UTC (Thu) by cmorgan (guest, #71980) [Link]
Nothing prevents journald from maintaining backwards compatibility:
From http://www.freedesktop.org/software/systemd/man/systemd-j...
"
A few configuration parameters from journald.conf may be overridden on the kernel command line:
systemd.journald.forward_to_syslog=, systemd.journald.forward_to_kmsg=, systemd.journald.forward_to_console=
LCE: Systemd two years on Posted Nov 15, 2012 13:45 UTC (Thu) by engla (guest, #47454) [Link]
Isn't it sad that this topic has to devolve into tribal groupings? For or against? Partisan? We need to make this a bit less like Lord of the Flies.
In debian circles, you can read stuff like "I'll GR against systemd if I have to", which reminds me only of the Republicans of 2011; "if I'm not getting what I want, then we all go down together".
Maybe if everyone made an effort to see what the other side sees as positive in their preferred solution, we could solve this more smoothly.
|
|||||||||||||