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: 0) by Anonymous Coward on 2015-07-28 05:32 (#FN58) Binary logging is a myth. You can still read the logs with any test editor. You can also use jourald for some nice features, but it is not required; the logs are not binary. Re: Reading those paragraphs (Score: 2) by billshooterofbul@pipedot.org on 2015-07-28 19:01 (#FQGD) I love systemd, but I have to be honest, the logs are binary. There are tools for getting text out of them, which can then be piped into any cli text tool you want. you can also run syslog in parallel, if you'd like. But as I said earlier, binary isn't bad when the format is well documented. https://wiki.freedesktop.org/www/Software/systemd/journal-files/
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: 0) by Anonymous Coward on 2015-07-28 05:32 (#FN58) Binary logging is a myth. You can still read the logs with any test editor. You can also use jourald for some nice features, but it is not required; the logs are not binary. Re: Reading those paragraphs (Score: 2) by billshooterofbul@pipedot.org on 2015-07-28 19:01 (#FQGD) I love systemd, but I have to be honest, the logs are binary. There are tools for getting text out of them, which can then be piped into any cli text tool you want. you can also run syslog in parallel, if you'd like. But as I said earlier, binary isn't bad when the format is well documented. https://wiki.freedesktop.org/www/Software/systemd/journal-files/
Re: Reading those paragraphs (Score: 0) by Anonymous Coward on 2015-07-28 05:32 (#FN58) Binary logging is a myth. You can still read the logs with any test editor. You can also use jourald for some nice features, but it is not required; the logs are not binary. Re: Reading those paragraphs (Score: 2) by billshooterofbul@pipedot.org on 2015-07-28 19:01 (#FQGD) I love systemd, but I have to be honest, the logs are binary. There are tools for getting text out of them, which can then be piped into any cli text tool you want. you can also run syslog in parallel, if you'd like. But as I said earlier, binary isn't bad when the format is well documented. https://wiki.freedesktop.org/www/Software/systemd/journal-files/
Re: Reading those paragraphs (Score: 2) by billshooterofbul@pipedot.org on 2015-07-28 19:01 (#FQGD) I love systemd, but I have to be honest, the logs are binary. There are tools for getting text out of them, which can then be piped into any cli text tool you want. you can also run syslog in parallel, if you'd like. But as I said earlier, binary isn't bad when the format is well documented. https://wiki.freedesktop.org/www/Software/systemd/journal-files/