Users/Developers Threatening Fork Of Debian GNU/Linux
In light of Debian's outlook for using systemd by default, a group of users/developers/administrators are talking about forking Debian GNU/Linux.
No fork has happened as of yet but this group is threatening to do so if Debian will be bound to using systemd rather than other options like SysVinit or Upstart. In potentially avoiding the fork, the DebianFork.org camp is encouraging stakeholders to support Ian Jackson's recent request about preserving freedom of choice for init systems. This general resolution isn't about getting rid of systemd by default but ensuring that Debian packages won't become dependent on any single init system, i.e. systemd.
DebianFork.org says, "We don't want to be forced to use systemd in substitution to the traditional UNIX sysvinit init, because systemd betrays the UNIX philosophy. We contemplate adopting more recent alternatives to sysvinit, but not those undermining the basic design principles of 'do one thing and do it well' with a complex collection of dozens of tightly coupled binaries and opaque logs. Are there better solutions than forking?" DebianFork.org is ideally hoping beyond Jackson's proposal being approved that SysVinit will remain the default for a while longer.
Those wishing to learn more about this new initiative can visit DebianFork.org.
No fork has happened as of yet but this group is threatening to do so if Debian will be bound to using systemd rather than other options like SysVinit or Upstart. In potentially avoiding the fork, the DebianFork.org camp is encouraging stakeholders to support Ian Jackson's recent request about preserving freedom of choice for init systems. This general resolution isn't about getting rid of systemd by default but ensuring that Debian packages won't become dependent on any single init system, i.e. systemd.
DebianFork.org says, "We don't want to be forced to use systemd in substitution to the traditional UNIX sysvinit init, because systemd betrays the UNIX philosophy. We contemplate adopting more recent alternatives to sysvinit, but not those undermining the basic design principles of 'do one thing and do it well' with a complex collection of dozens of tightly coupled binaries and opaque logs. Are there better solutions than forking?" DebianFork.org is ideally hoping beyond Jackson's proposal being approved that SysVinit will remain the default for a while longer.
Those wishing to learn more about this new initiative can visit DebianFork.org.
178 Comments