Tuesday, 21 January 2014 13:25

Red Hat must be rejoicing as Debian tilts towards systemd Featured


The Debian GNU/Linux Project's technical committee appears to be split down the middle on the question of the default init system for the next release.

But the panel is tilting towards a compromise on systemd as the default. It means that the future direction of Linux development will be determined by Red Hat, the company that is behind systemd, and the biggest commercial entity in the Linux game.

Two more Debian technical panel members - Don Armstrong and Andreas Barth - have now declared their choices, with statements indicating which system they would support.

Armstrong has said he prefers systemd, while Barth has indicated he would like upstart.

The panel was tasked with selecting the default init system for its next release, Jessie, back in November.

Four others in the committee have indicated their choices: Ian Jackson (upstart), Russ Allberry (systemd), Bdale Garbee (systemd) and Keith Packard (systemd). Garbee, as head of the panel, is said to have a casting vote.

The two remaining members of the technical committee - Colin Watson and Steve Langasek - are both employees of Canonical which created the upstart init system.

Langasek is also the upstart maintainer for Debian. It is thus reasonable to assume that they will both support upstart as the default system.

Of course, there could be a recommendation that there be multiple init systems supported. This would, however, be a considerable impost in terms of developer time, the scarcest resource of any free or open source software project.

Given that Debian is a community project that has close to 1000 developers involved, there is still scope for the technical committee to come down on one side, and the project, through a General Resolution, to vote an entirely different way. That would not be a good look.

The panel's decision is likely to be known soon, given that three-fourths of its members have openly tilted one way or the other.

Jackson has suggested wording to be included in the decision to make systemd the default.

He wrote: "We are very concerned about the systemd upstream's history of claiming control of wide areas of functionality. We are also worried by the vigorous adoption campaign one of whose key strategies appears to be making systemd mandatory for various other software, even where the benefits of such tight coupling are minimal or alternative approaches such as operation with reduced functionality would be entirely feasible.

"In this context the systemd project's apparent lack of prioritisation of the legitimate divergence of wishes and goals on the part of its downstreams is especially worrying.

"Our selection of systemd as default is made despite these worries.  We reiterate Debian's commitment to diversity of approaches and to the freedom of our downstreams and users to make their own choices."

As Jackson pointed out, his last paragraph makes sense if the project then passes a resolution to support multiple init systems for the foreseeable future.

But his is not the last word on the subject; one thing Debian is never short of is opinions on any, and every, issue.

Jackson's draft contains mostly wishful thinking. Red Hat will take the systemd project in any direction it wishes, and create any number of dependencies that it deems will serve its interests.

The debate over upstart v systemd is a proxy war for Canonical v Red Hat, one the pretender, the other the 800-kg gorilla. Red Hat has not become a billion-dollar company by being the nice kid on the block.

Somewhere in Berlin, Lennart Poettering, the chief systemd developer, must be pouring himself a nice, cool drink and laughing out loud.

Read 12065 times

Please join our community here and become a VIP.

Subscribe to ITWIRE UPDATE Newsletter here
JOIN our iTWireTV our YouTube Community here


The past year has seen a meteoric rise in ransomware incidents worldwide.

Over the past 12 months, SonicWall Capture Labs threat researchers have diligently tracked the meteoric rise in cyberattacks, as well as trends and activity across all threat vectors, including:

Encrypted threats
IoT malware
Zero-day attacks and more

These exclusive findings are now available via the 2022 SonicWall Cyber Threat Report, which ensures SMBs, government agencies, enterprises and other organizations have the actionable threat intelligence needed to combat the rising tide of cybercrime.

Click the button below to get the report.



It's all about Webinars.

Marketing budgets are now focused on Webinars combined with Lead Generation.

If you wish to promote a Webinar we recommend at least a 3 to 4 week campaign prior to your event.

The iTWire campaign will include extensive adverts on our News Site itwire.com and prominent Newsletter promotion https://itwire.com/itwire-update.html and Promotional News & Editorial. Plus a video interview of the key speaker on iTWire TV https://www.youtube.com/c/iTWireTV/videos which will be used in Promotional Posts on the iTWire Home Page.

Now we are coming out of Lockdown iTWire will be focussed to assisting with your webinars and campaigns and assistance via part payments and extended terms, a Webinar Business Booster Pack and other supportive programs. We can also create your adverts and written content plus coordinate your video interview.

We look forward to discussing your campaign goals with you. Please click the button below.


Sam Varghese

Sam Varghese has been writing for iTWire since 2006, a year after the site came into existence. For nearly a decade thereafter, he wrote mostly about free and open source software, based on his own use of this genre of software. Since May 2016, he has been writing across many areas of technology. He has been a journalist for nearly 40 years in India (Indian Express and Deccan Herald), the UAE (Khaleej Times) and Australia (Daily Commercial News (now defunct) and The Age). His personal blog is titled Irregular Expression.

Share News tips for the iTWire Journalists? Your tip will be anonymous