Having non-text log files is moronic and there's no excuse for it. There is the reality, though, that the computing world today is vastly different than the simple servers that Unix was originally designed to run on 50 years ago and some things just don't work the same. It's true that systemd goes against the "do one thing and do it well" philosophy, but at the same time the "do one thing and do it well" philosophy sometimes goes against reality.
There are places where the old way of doing things doesn't work well or leads to terrible kludges, such as with plug & play devices. The idea that you would add a piece of hardware to a running system would have seemed odd 50 years ago. I think there are better ways to handle such, and there's certainly no reason to scrap init scripts for the vast majority of software packages out there. But systemd is really here to stay and it'll be nearly impossible to replace unless something incredible comes along to replace it. Don't hold your breath. -- Michael Darrin Chaney, Sr. [email protected] http://www.michaelchaney.com/ -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAAtfUtGw%2BQwzenKNmeRcUYi9UJhsxuGi8TFDZDs55Fa4neBeqw%40mail.gmail.com.
