3 ms·
On the one hand, this seems wildly misguided; the Debian distribution for people who don't want to run systemd is still just Debian, and that'll remain the case
by JoshTriplett 12y ago
On the one hand, this seems wildly misguided; the Debian distribution for people who don't want to run systemd is still just Debian, and that'll remain the case through at least jessie, and for as long as people continue putting effort into keeping it working. So it's sad that the effort going into this fork doesn't instead go into maintaining the necessary infrastructure in Debian. I'm sure the maintainers of systemd-shim and cgmanager would welcome additional contributors.
On the other hand, perhaps this will provide a more useful outlet for the set of people who keep claiming they'd use a fork if available, so that they can actually go use one and stop griping on Debian mailing lists.
Nope, sorry, couldn't keep a straight face while saying that.
- marcosdumay 12y agoFrom the site, it looks they'll keep adding to systemd-shim and cgmanager.
- dredmorbius 12y agoThere are several arguments I can see in favor of a fork. 1. Ensure that there will be a systemd-free variant of debian even beyond jessie. 2. Provide a tangible metric of the interest in such a variant. 3. Provide a platform on which alternatives to systemd can be developed and promoted. After all, systemd it must be said, addresses some legitimate concerns, largely concerned with service tracking and a generally far more dynamic computing environment. The recent Future of FreeBSD presentation by Jordan Hubbard is actually one of the more eloquent arguments in this light (noting that FreeBSD is both Not Linux and Doesn't Have Systemd). The primary argument against forking is that it divides efforts. My counterargument is that forking makes the existing divide between views on a given approach tangible and explicitly visible. Free Software, particularly under the GNU GPL or equivalent copyleft, also explicitly preserves the right to merge projects which have forked, as has in fact been the case in several notable instances -- GCC/EGCS, the long-running TK For a specific study of the topic, see "A Comprehensive Study of Software Forks: Dates, Reasons and Outcomes" by Gregorio Robles and Jesuus M. Gonzalez-Barahona http://flosshub.org/sites/flosshub.org/files/paper_0.pdf http://flosshub.org/sites/flosshub.org/files/paper_0.pdf It cites: GCC/EGCS, xpdf/poppler, GNU Emac/Xemacs, the numerous OpenOffice forks, X.org/XFree, NetBSD/OpenBSD, Wireshark/Ethereal, Gerequi/Amarok, MySQL/Miriadb. In total the paper explores some 220 forks, analyzing them by software area (e.g., networking, web apps, development, etc.), year of initiation, and reason. "Technical" accounts for the most at 27%, "differences among technical team" is sixth at 7.3%. Resolution of forks is of particular interest: Successful branching: 43.6% Discontinuation of original: 29.8% Discontinuation of fork: 13.8% Discontinuation of both original and fork: 8.7% Re-merging of fork: 3.2% Other: 0.9% As a critic of systemd and proponent of the concepts of Free Software, including the Freedom to Fork, I'm in support of this and similar efforts.