Cristian Rodríguez said the following on 01/22/2013 08:12 PM:
El 22/01/13 21:04, General Mail escribió:
From what I observe, in most cases, I've seen init scripts depending on /etc/sysconfig which seems reasonable to me.
Not really, no. see.. once upon a time.. ( :-) ) when systems had very limited processing power & storage, lacked of shared libraries and plug and play devices did not exist, programs could not afford any other way of getting startup parameters than the command line. That times are gone, now your cellphone has more computing power than NASA Apollo missions that sent people to the moon, yet for historical reasons some software still relies solely on this mechanism, that's one of the reasons sysconfig exists.
That's a non-sequitor. Configuration isn't about computing power. Take, for example, /etc/sysconfig/displaymanager. Its about DECISIONS. What display manager to run. Not how a specific display manager (kdm for example) is configured, what the wallpaper is, where the dialog box sits, colours, decoration, but DECISIONS as to *WHAT* to run. Elsewhere you'll find whether to include "." in the PATH. Nothing to do with command lines. And even so, when there are parameters for systemd, its about AUTOMATION rather than you having to type them[1]. And its about SYSTEM matters, not user-application matters. I still don't see you proposing an alternative for what the sysconfig files *are* doing. How about you stop making emotional statements and emotional terms like 'ugly' and talk in functional terms. Determine what it is that they are used - and what they are *not* being used for - for and why, and offer alternatives. As in "Put up or shut up". [1] Just as the values in many of my ~/dot files have settings that would be on the command line if I had to type them but don't. -- Events in complex systems are not susceptible to root cause analysis. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org