[NTLUG:Discuss] Debian ditching sysvinit

[Leroy Tennison]

On 10/28/2013 02:22 PM, Chris Cox wrote:
> Since this topic came up briefly at the last meeting:
>
> http://www.phoronix.com/scan.php?page=news_item&px=MTQ5NzQ
>
> (Note: if Debian switches, for example, to systemd, then Ubuntu would very
> likely also switch, noting that most say Debian's decision is "ruled" by
> Ubuntu folks, so most think Debian will switch to upstart)
>
> Red Hat and SUSE, the two enterprise distros, are committed to systemd
> (and as I mentioned, systemd reaches into more than just "init" things...
> so it's hard to say "no" to).
>
> However, Debian's decision, because of it's wide use (non-Ubuntu) around
> the world.... well, it might cause some interesting "problems" for the two
> well known enterprise distros if they go with upstart.  We'll see.
>
>
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
Am I just mistaken and paranoid or is Linux getting "Microsoft-itis" in 
that the direction everything seems to be headed is:

 1. Hide how things are done (wrap a GUI around it, don't even document
    configuration files and entries)
 2. Take control away from the user and give it to the programmer-priests

Examples:

 1. GRUB2, "DO NOT EDIT THIS FILE" (quote from grub.cfg)
 2. SAX(2) - don't even try to configure a monitor or other things
    without it.
 3. KDE4- need to know what file controls something?  God help you -
    you're going to need it!  Documentation seems to be dismal.
 4. Network Manager - enough said
 5. I haven't kept up with systemd but what I seem to recall about
    upstart is that things are moving out of scripts into some less
    accessible place