Originally posted by Chaz
View Post
Announcement
Collapse
No announcement yet.
Debian Init System Coupling Vote Results
Collapse
X
-
Originally posted by Chaz View Post*As was discussed once before I am writing "System D" in the way in which proper nouns have been written in English for the last few hundred years, and not the way that the System D creators do it, because I think their way is stupid. Moving on!
Comment
-
Originally posted by Chaz View PostI never totally understood that thread but I think this whole affair WAS the rearguard battle. The original battle was System D* versus Upstart. Ian lost but he is not willing to accept total defeat. In his eyes total defeat is System D taking over Debian and exterminating all other init systems and therefore ruining Debian, and he believes that will happen if tight coupling with System D is allowed. So after he lost his primary objective of Upstart (and tight coupling of Upstart), he retreated toward the position of loose coupling. But others on the Committee were not satisfied with this and wanted tight coupling, so Ian fought a "rearguard action" (a battle you fight to defend yourself against a pursuing enemy while you are retreating) to stave them off. He lost that too when the Committee did not adopt loose coupling, so Ian fought another rearguard battle with the referendum. So he has been defeated in the original battle and also in his attempt to retreat to his Plan B position, so to complete the analogy we could say that Ian has now been not just defeated but annihilated.
*As was discussed once before I am writing "System D" in the way in which proper nouns have been written in English for the last few hundred years, and not the way that the System D creators do it, because I think their way is stupid. Moving on!
Comment
-
There is nothing 'nonsensical' about it. Dissent and difference of opinion is supposed to be healthy but there seems to be a concerted effort to cast dissent as 'troublemaking' and demonize Ian Jackson as some sort of a villian which is a bit sad coming from a Linux community.
If you do not want dissent or difference of opinion then the Debian constitution should be amended without the possibility of raising GRs. There is no need to demonize other points of view. Presumably these structures exist so that these discussions can happen, and now that the discussion has happened and a democratic choice has been made, it shows everything is working as intended, healthily. What's not to like or dislike?
It's clear now the majority within the Debian community that can make the decision have made it in favour of systemd. While before there may have been the slightest doubt because it was a split vote 4:4 with the chairman's vote deciding, its now clear where the community stands, and continued efforts to change this will have little impact beyond bitterness and anger.
Redhat and derivatives and Debian and derivatives are firmly in the systemd bandwagon. This effectively makes systemd the defacto init for 99% of Linux systems. Even if you fork Debian a lot of future linux developments will presumably be made with systemd in mind, meaning compatibility will become a continuously growing effort. A lot of developers will target systems that have systemd, and you will have to request devs to support non systemd versions and they may not have the time or inclination to do that. So maintaining an up to date fork will be a time consuming affair.
Yesterday I had suggested Alpine linux as a project with potential for a lot of Debian server users since the main point of anger was about lack of choice and Alpine linux uses openrc and is focussed on networking, security and hosting VMs and containers. But this potential is in the context that a lot of future Linux developments will be made with systemd. Instead of arguments of a political nature discussion should be on if it's possible or feasible to have any sustainable engineering alternative to systemd that can be maintained for servers at least, and since these discussions can be had outside the heated theatre of pro and anti, they can be more productive.Last edited by raulb; 19 November 2014, 03:55 AM.
Comment
-
Originally posted by raulb View PostThere is nothing 'nonsensical' about it. Dissent and difference of opinion is supposed to be healthy but there seems to be a concerted effort to cast dissent as 'troublemaking' and demonize Ian Jackson as some sort of a villian which is a bit sad coming from a Linux community.
If you do not want dissent or difference of opinion then the Debian constitution should be amended without the possibility of raising GRs. There is no need to demonize other points of view. Presumably these structures exist so that these discussions can happen, and now that the discussion has happened and a democratic choice has been made, it shows everything is working as intended, healthily. What's not to like or dislike?
It's clear now the majority within the Debian community that can make the decision have made it in favour of systemd. While before there may have been the slightest doubt because it was a split vote 4:4 with the chairman's vote deciding, its now clear where the community stands, and continued efforts to change this will have little impact beyond bitterness and anger.
Redhat and derivatives and Debian and derivatives are firmly in the systemd bandwagon. This effectively makes systemd the defacto init for 99% of Linux systems. Even if you fork Debian a lot of future linux developments will presumably be made with systemd in mind, meaning compatibility will become a continuously growing effort. A lot of developers will target systems that have systemd, and you will have to request devs to support non systemd versions and they may not have the time or inclination to do that. So maintaining an up to date fork will be a time consuming affair.
Yesterday I had suggested Alpine linux as a project with potential for a lot of Debian server users since the main point of anger was about lack of choice and Alpine linux uses openrc and is focussed on networking, security and hosting VMs and containers. But this potential is in the context that a lot of future Linux developments will be made with systemd. Instead of arguments of a political nature discussion should be on if it's possible or feasible to have any sustainable engineering alternative to systemd that can be maintained for servers at least, and since these discussions can be had outside the heated theatre of pro and anti, they can be more productive.
Comment
-
Originally posted by raulb View PostInstead of arguments of a political nature discussion should be on if it's possible or feasible to have any sustainable engineering alternative to systemd that can be maintained for servers at least, and since these discussions can be had outside the heated theatre of pro and anti, they can be more productive.
Comment
Comment