Re: Reading those paragraphs

Reading those paragraphs (Score: 1, Insightful)

by Anonymous Coward on 2015-07-27 02:15 (#FHBJ)

Makes me think there is something wrong with systemd. All the assertions that you make to try to defend it seem manipulative. It's like whoever wrote it actually knows there is something wrong with it.

Re: Reading those paragraphs (Score: 3, Interesting)

by Anonymous Coward on 2015-07-27 20:49 (#FM4C)

It's not clear that there is actually much wrong with systemd except the binary logging. But it's not clear that there isn't. And there were lots of horror stories about unrecoverable errors around a year ago. Perhaps they've addressed it since then.

OTOH, init was working perfectly fine in my use case, and I'd really rather not have switched. And systemd seems intent on swallowing so much stuff that nothing will work on both an init based system and a systemd based system. They aren't there yet, but...

So I don't trust the developers. And I'm upset at being coerced into using it. I *am* using it, but I'd really rather not be doing so. Systemd seems designed for administrators who administer a large number of servers/workstations/pcs. That's not me, and I'm unhappy at being coerced into using it. If Devuan ever gets its act together, I may well switch.

Re: Reading those paragraphs (Score: 1, Interesting)

by Anonymous Coward on 2015-07-28 15:32 (#FPT5)

Just out of curiosity, what is this talk about systemd being targetted at maintainers with lots of machines? Does it have some kind of remote management interface? I keep hearing about this but the systemd webpage isn't very helpful. Any quick comments?

Re: Reading those paragraphs (Score: 1)

by evilviper@pipedot.org on 2015-07-28 17:49 (#FQAG)

It can be configured to automatically restart services that exit, provides features that support configuration management engines like Puppet, automatically handles service dependencies, and more.

You can also see "A short list of other features:"
* http://0pointer.de/blog/projects/systemd.html

Re: Reading those paragraphs (Score: -1, Troll)

by Anonymous Coward on 2015-07-28 20:09 (#FQPX)

It looks like Puppet can handle anything you throw at it, if you throw it well, not just systemd. Are you talking about the d-bus interface?

I read most of that post, but I still don't understand who this is intended for. Fast booting doesn't make sense for servers. They are not booted frequently, it's fine if a server boots in 10 minutes instead of 2. What matters is that it boots consistent with its intended configuration. That post talks a lot about how starting services in parallel speeds up things, and most importantly lazy activation. Lazy activation is unacceptable, at least in our setup. We'd like to know of a failure (most often misconfiguation) as soon as possible at boot time, not when we actually need the service.

It doesn't make sense for workstations either. On workstations, there is often NO service running. We have the servers for that. Booting a workstation fast is a piece of cake, really. Mount your drives, get a network address, start up a couple daemons like the logger and the console and you're done. You don't need a complicated, hard to configure program to do that. Unless you redefine X11 display to be a service, the mouse driver to be a service etc. It doesn't make sense. Help me with this.

It very much looks like Lennart is bored with fucking up the audio system and is trying to fail at something new.

Time	Reason	Points	Voter
2015-07-28 20:31	Insightful	+1	genx@pipedot.org
2015-07-28 21:11	Overrated	-1	evilviper@pipedot.org
2015-07-28 21:48	Troll	-1	skarjak@pipedot.org

Story

Preview