Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Friday April 15 2016, @04:56AM   Printer-friendly
from the speechless dept.

The annual Debian developers conference, debconf 16, is taking place July 2-9 in Cape Town, South Africa, featuring for the first time ever Microsoft as a silver sponsor.

This seems consistent with the strategy, that pessimists may define EEE (embrace, extend, extinguish), of seeking close integration with the GNU/Linux system.

The move, from a traditionally hostile company that recently started showing enthusiasm towards open source software, is causing a mixture of derision and opposition in the community. As the grey beards in the IT community might recall, most of Microsoft partners, from IBM to the humble dev, tend to end up screwed in the long term. Will GNU/Linux be the exception?


Original Submission

 
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: 1, Insightful) by Anonymous Coward on Friday April 15 2016, @10:28AM

    by Anonymous Coward on Friday April 15 2016, @10:28AM (#332156)

    When they picked up systemd as the only option, they turned into Debhat. The writing is already on the wall, burned in with an industrial laser. What was Debian sold out to Redhat.

    Starting Score:    0  points
    Moderation   +1  
       Troll=1, Insightful=2, Total=3
    Extra 'Insightful' Modifier   0  

    Total Score:   1  
  • (Score: 2, Informative) by dmbasso on Friday April 15 2016, @04:15PM

    by dmbasso (3237) on Friday April 15 2016, @04:15PM (#332270)

    When they picked up systemd as the only option

    Wtf are you talking about?

    apt-cache show sysvinit-core
    Package: sysvinit-core
    Source: sysvinit
    Version: 2.88dsf-59.3
    Installed-Size: 220
    Maintainer: Debian sysvinit maintainers <pkg-sysvinit-devel@lists.alioth.debian.org>
    Architecture: amd64
    Replaces: systemd-sysv, sysvinit (<< 2.88dsf-44~), upstart
    Depends: initscripts (>= 2.88dsf-13.3), sysv-rc | file-rc, sysvinit-utils (>= 2.86.ds1-66), libc6 (>= 2.15), libselinux1 (>= 1.32), libsepol1 (>= 1.14), debconf (>= 0.5) | debconf-2.0, debianutils (>= 4)
    Conflicts: systemd-sysv, upstart
    Description-en: System-V-like init utilities
      This package contains programs required for booting
      a Debian system and doing basic process management.
      .
      The most important program in the package is /sbin/init.
      It is the first process started on boot and continues
      to run as process number 1 until the system halts. All
      other processes are descended from it.

    --
    `echo $[0x853204FA81]|tr 0-9 ionbsdeaml`@gmail.com
    • (Score: 2) by rleigh on Saturday April 16 2016, @11:25PM

      by rleigh (4887) on Saturday April 16 2016, @11:25PM (#332997) Homepage

      Take a look at http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/log/ [debian.org] and you'll see that it's no longer maintained particularly actively. Being present in the archive doesn't tell the whole story. How many packages, particularly gnome-related ones, deliberately removed and broke sysvinit support? Running sysvinit is certainly *possible*, but that doesn't mean everything will work with it. The playing field hasn't been level for some time.

      (And wow, time flies. Two years and three months since my last commit.)

      • (Score: 2) by dmbasso on Sunday April 17 2016, @03:02AM

        by dmbasso (3237) on Sunday April 17 2016, @03:02AM (#333085)

        Take a look at http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/log/ [debian.org] and you'll see that it's no longer maintained particularly actively.

        Looks like a healthy stable mature package to me.

        How many packages, particularly gnome-related ones, deliberately removed and broke sysvinit support?

        That's not Debian's fault.

        Running sysvinit is certainly *possible*, but that doesn't mean everything will work with it.

        Just as you can't easily put a V8 engine in a Tesla car. You can, however, continue to use your Mustang with all its compatible pieces.

        The sysvinit-core package works as intended, so you can't say systemd is the only option. Unless you don't mind being intellectually dishonest, as the GGP (and whoever modded my previous comment overrated).

        --
        `echo $[0x853204FA81]|tr 0-9 ionbsdeaml`@gmail.com