[mdlug] Systemd and all of it's nonsensical BS

Michael Corral micorral at comcast.net
Mon Feb 23 18:40:23 EST 2015


2015-02-23, Monsieur Garry Stahl a ecrit:
> On 02/23/2015 01:25 PM, Adam Tauno Williams wrote:
>>  On Mon, 2015-02-23 at 13:09 -0500, David Lee Lambert wrote:
>> >  Well, depends what you mean by "consumed". Not in Debian Stable yet, it 
>> >  is
>> >  in Debian Testing but in theory there are alternatives.  And, in my 
>> >  testing
>> >  of Testing so far, on two fresh-installed VMs, no issues with it.
>>  Running openSUSE - systemd  - on my laptop(s).  Use them all day every
>>  day.  No systemd related issues.
>> 
> Likewise.  openSUSE on all computers,m no issues.

I've been running systemd on Fedora for almost 4 years, when
Fedora 15 became the first distro to make systemd the default
init system. What problems am I supposed to be having? Because
I've never had any, even on production servers running Apache,
Tomcat, and PostgreSQL (yes, servers running Fedora - scary!:).

At first, I didn't like systemd because it was unfamiliar to me.
But once I learned how to use it, I liked it and now think it's
a big improvement over the old SysV init system. In Fedora, having
systemd logs forwarded to syslog is the default (it's a setting in
/etc/systemd/journald.conf), so you can still have the old-style
logging if you prefer that.

I do think that a lot of the complaints about systemd are simply due
to ignorance, though there are some crusty curmudgeons stuck in 1991
who just don't want to learn anything new (or took the fictional
"UNIX philosophy" about "do one thing, blah blah blah ..." a bit
too seriously:).

Michael


More information about the mdlug mailing list