SoylentNews is people
SoylentNews
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?
This discussion has been archived.
No new comments can be posted.
Debconf 2016 Welcomes... Microsoft!
|
Log In/Create an Account
| Top
| 54 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
To be a kind of moral Unix, he touched the hem of Nature's shift.
-- Shelley
(Score: 2) by rleigh on Saturday April 16 2016, @11:25PM
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
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