On 10/29/2013 5:53 AM, Jan Engelhardt wrote:
The fact that the config files are no longer in a readable text, and need 680KB of man pages to explain them is part of the problem.
I don't need that for shell scripts.... i.e. you just made my point. :-)
You are just babbling nonsense as usual. The real sad part about it is, you do not even recognize it. But hey, systemd haters gonna hate.
What part of .6MB of needed documentation to begin to understand systemd don't you understand? I need no special documentation for the scripts that brought up the system in SysVinit. systemd uses it's only special syntax and language that needs well over a half a meg of specialized documentation that still doesn't make it's configuration easy or scriptable. That you think I hate systemd is your projection. Unlike you, I dislike having large alien bodies shoved down my throat. I'd have been ecstatic if it had been offered as a choice and likely would have dumped as many processes on it as possible. But needing specialized log formats that are in binary -- just like MS's logs shows me it's designed for keeping people from casually examining it and taking control away from end users. It's difficult to keep up on and examine the MS logs because their log format is binary and you have to write special tools to decode it. You can't use off-the-shelf text processing utils that have been available on *nix for 40+ years. Then you start bundling in device and power control into your service manager as well as it handling the logging -- and you are talking *monolithic*. That's poor design in the unix world where doing 1-2 things well and have them be inter-operable with other tools so you can have any format you want -- but ... inter-operable? What unix utils is systemd interoperable with? What pre-existing tools can we re-use to manage it, interpret the log files, etc. Then is the plain *bad practice*... in the unix world -- of using absolute, hard-coded paths. It can't use "PATH", or look where libraries are -- so all the binaries have to be moved to /usr/bin -- thus forcing /usr to be mounted before systemd ever starts. Again -- another weakness that suse works around by forcing initrd's on everyone... All this added complexity for dubious gain but mostly with complete incompatibility and lack of support for legacy usage. Yet these same people whine to high heaven about how a standard that's been around for near 20+ years, is "too new-fangled to be forced on users reading text"... The hypocrisy is ridiculous. You're just trying to wind me up... with such ridiculous nonsense. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org