Stories
Slash Boxes
Comments

SoylentNews is people

posted by LaminatorX on Wednesday October 08 2014, @01:33AM   Printer-friendly
from the needs-a-systemd-port dept.

According to an email sent to the Debian debian-devel-announce mailing list by Adam D. Barratt, the Debian GNU/kFreeBSD port is in grave danger of being dropped from the upcoming Debian 8 "Jessie" release. Debian GNU/kFreeBSD runs the GNU userland tools, the GNU C library and the Debian package set on top of the FreeBSD kernel.

Barratt states:

We remain gravely concerned about the viability of this port. Despite the reduced scope, we feel that the port is not currently of sufficient quality to feature as a fully supported release architecture in Jessie.

We therefore advise the kFreeBSD porters that the port is in danger of being dropped from Jessie, and invite any porters who are able to commit to working on the port in the long term to make themselves known *now*.

We will assess the viability of kFreeBSD in Jessie on or after 1st November, and a yes/no decision will be taken at that time.

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by Marand on Wednesday October 08 2014, @02:03AM

    by Marand (1081) on Wednesday October 08 2014, @02:03AM (#103412) Journal

    The kFreeBSD port has always been a niche thing with fewer people and resources, so this isn't particularly surprising. During the "technical committee" farce that decided to replace sysv-init with systemd for Jessie, when the kFreeBSD port was mentioned as a roadblock to switching, the argument (and port) were summarily dismissed as irrelevant.

    Once systemd "won" and became the upcoming default init, what options were left? Maintain two official inits, one specifically for a single port; port systemd to non-linux; or drop kFreeBSD port. GNOME and systemd devs have made it clear in the past that the Linux kernel is the only one that matters and they want to create the One True OS that provides the entire stack, so porting isn't likely. Maintaining a second official init is a lot of work that many will see as a waste of time, especially for a niche port.

    No, the most likely solution is to put the port that doesn't play nice with systemd on the chopping block. Even if it makes it into Jessie somehow, its days are likely numbered. I had some hope that the kFreeBSD port would help retain some non-systemd sanity in Debian, but it's not looking good.

    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Underrated=1, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 1, Informative) by Anonymous Coward on Wednesday October 08 2014, @02:57AM

    by Anonymous Coward on Wednesday October 08 2014, @02:57AM (#103425)

    Systemd is like leprosy. It infects the host, Debian in this case, and slow eats away and irreparably damages it. First Debian's community is disrupted. Then its governance is corrupted. Then its ports, like kFreeBSD, are killed off, one by one. Soon enough Debian's quality and reliability are failing. This drives away the few remaining users. Finally, Debian is nothing but a corpse; a rotting carcass.

    • (Score: 0) by Anonymous Coward on Wednesday October 08 2014, @08:18AM

      by Anonymous Coward on Wednesday October 08 2014, @08:18AM (#103479)

      I have mod points, but there is no option to mod the parent "poetical" :(

  • (Score: 0) by Anonymous Coward on Wednesday October 08 2014, @04:21PM

    by Anonymous Coward on Wednesday October 08 2014, @04:21PM (#103647)

    they want to create the One True OS that provides the entire stack

    One OS to rule them all, One OS to find them,
    One OS to bring them all and in the darkness bind them
    in the land of SystemD where the shadows lie.