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 billshooterofbul@pipedot.org on 2015-08-03 14:24 (#G9N7) When you have a large number of machines, the odds of you hitting the flaws inherent to sysv init and upstart become more frequent. systemd has a large number of "Proper" solutions to things that sysv and upstart work for 98% of the time. It also has a number of things that make administering systems easier, faster ( if you take the time to learn them instead of sticking your head in the sand and complaining about having to learn new things).
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 billshooterofbul@pipedot.org on 2015-08-03 14:24 (#G9N7) When you have a large number of machines, the odds of you hitting the flaws inherent to sysv init and upstart become more frequent. systemd has a large number of "Proper" solutions to things that sysv and upstart work for 98% of the time. It also has a number of things that make administering systems easier, faster ( if you take the time to learn them instead of sticking your head in the sand and complaining about having to learn new things).
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 billshooterofbul@pipedot.org on 2015-08-03 14:24 (#G9N7) When you have a large number of machines, the odds of you hitting the flaws inherent to sysv init and upstart become more frequent. systemd has a large number of "Proper" solutions to things that sysv and upstart work for 98% of the time. It also has a number of things that make administering systems easier, faster ( if you take the time to learn them instead of sticking your head in the sand and complaining about having to learn new things).
Re: Reading those paragraphs (Score: 1) by billshooterofbul@pipedot.org on 2015-08-03 14:24 (#G9N7) When you have a large number of machines, the odds of you hitting the flaws inherent to sysv init and upstart become more frequent. systemd has a large number of "Proper" solutions to things that sysv and upstart work for 98% of the time. It also has a number of things that make administering systems easier, faster ( if you take the time to learn them instead of sticking your head in the sand and complaining about having to learn new things).