On 06/04/2014 07:17 PM, Linda Walsh wrote:
Anton Aylward wrote:
On 06/04/2014 08:26 AM, Carlos E. R. wrote:
[ Big Snip ]
What Carlos is saying, what I'm saying, is that this is Linux and its configurable. Its as configurable to the degree that you want to put the effort in to make it so.
---- Considerable effort is being thrown away with a large amount of that configurability being thrown away as well as Systemd absorbs functions and disables configuration options.
I see the opposite. I see systemd being 'table driven' (aka 'units') and the configuration being extended. I can do things with systemd like proper multi-seat that I couldn't do before. Perhaps you would like to give an example of options you've lost and those of us who are happy with systemd can think about if that is so or if the option exists elsewhere.
Or... can it give me run levels and previous functionality?
Like the functionality that existed before Bells UNIX System Group introduced sysvinit? And what do you mean by 'run level' As far as I can see the only run levels in sysvinit that did anything were 1, 2, 5 and 6, and their functionality exists with systemd. Heck, it you're that pressured you can still run "init" with those parameters. Systemd also offers the ability to enter 'rescue mode' and 'emergency mode' and to alter the way syslog is done at run time. If systemd didn't have to maintain backward compatibility it would be a lot simpler. I'm puzzled as to why you as that last question since its a RTFM issue. "man 1 init" gives the answer <quote> For compatibility with SysV, if systemd is called as init and a PID that is not 1, it will execute telinit and pass all command line arguments unmodified. That means init and telinit are mostly equivalent when invoked from normal login sessions. See telinit(8) for more information. </quote> -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org