Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Wednesday September 24 2014, @06:01AM   Printer-friendly
from the better-together dept.

Debian Jesse is going to have Gnome3 as the default desktop.

The desktop re-qualification page, used to help choose which desktop will be default, has in the Jesse version a weight for systemd integration, and of course only Gnome3 does it (at least for now). This will surely make the systemd/gnome3 fanbase happy, but possibly will make others unhappy, as it [may] be seen as another step towards mono-culture, until we soon end up with all distros being redhat clones.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by gallondr00nk on Wednesday September 24 2014, @12:42PM

    by gallondr00nk (392) on Wednesday September 24 2014, @12:42PM (#97623)

    I'd really like to know what happened to keeping the init system separate from the desktop environment. What was the harm in it?

    What's missing from the Systemd debate is what Linux as a whole actually gets out of it. I havn't seen this quantified in any meaningful way. Is it faster boot times? Better stability? A more user friendly or elegant init system? More features?

    I mostly use the BSDs, and so don't follow Linux user groups or mailing lists that closely. Are people communicating with the community at large about what all this disruption is in aid of?

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2, Insightful) by Anonymous Coward on Wednesday September 24 2014, @01:12PM

    by Anonymous Coward on Wednesday September 24 2014, @01:12PM (#97634)

    Are people communicating with the community at large about what all this disruption is in aid of?

    Spurious technical non-arguments are presented as indisputable fact in response to even the most balanced criticisms. So while there is often some form of "communication", the systemd camp have been incapable of responding with anything more than a dictatorial "because fuck you". Add resentment over the pushiness and dubious politics taking place and it seems the schism isn't going to be resolved amicably. The "fuck you" attitude having become mutual across both camps.

    • (Score: 0) by Anonymous Coward on Wednesday September 24 2014, @03:43PM

      by Anonymous Coward on Wednesday September 24 2014, @03:43PM (#97722)

      why haven't there been any physical beat downs. These fucks took over everything and banned anyone opposed. They need to be hurt.

  • (Score: 2) by metamonkey on Wednesday September 24 2014, @03:18PM

    by metamonkey (3174) on Wednesday September 24 2014, @03:18PM (#97701)

    The primary thing systemd has going for it is faster boot times because you skip all the script interpretation overhead and the ability to fork off services that are not interdependent.

    The problems depend on who you ask. The main one that annoys me is, well, I liked having scripts for services. It makes it very easy to see exactly what's going on when a process starts or stops, and it's very easy to modify and create new custom services. You just need to know basic shell scripting. It's also easy to backtrack. Want to know how a certain service is being started? Just grep through /etc/init.d. You'll find it. On systemd they're all started in the same way. You just have a config file that tells systemd what options you want, but you can't just add to the start up process for a service. It's also very, very poorly documented. So we went from easy to understand and modify scripts to poorly designed and poorly documented inflexible config files. Oh, and then instead of just logging all the output to text files, it uses a freaking binary log that has to be read with another systemd program, journald. So now you can't just grep through your logs, or have a daemon that just sits watching the tail of a log file for certain events.

    You combine all of that shit and it's just not very "UNIX-y." "The UNIX way" is for programs to do one (or few) things and do them very well, and output text. Then you can string together small, simple programs to accomplish complex tasks. Systemd, on the other hand, is monolithic and obfuscated.

    I use it (I run Debian 7.6 Wheezy), and it's "fine." I'm not on a holy war against it. But to be honest I'd be happier with init.

    --
    Okay 3, 2, 1, let's jam.
    • (Score: 0) by Anonymous Coward on Wednesday September 24 2014, @06:00PM

      by Anonymous Coward on Wednesday September 24 2014, @06:00PM (#97799)

      Wheezy is sysv

      • (Score: 2) by metamonkey on Wednesday September 24 2014, @06:35PM

        by metamonkey (3174) on Wednesday September 24 2014, @06:35PM (#97821)

        Oh. Then I must have been thinking of my other box that runs fedora.

        --
        Okay 3, 2, 1, let's jam.