Announcement

Collapse
No announcement yet.

Users/Developers Threatening Fork Of Debian GNU/Linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #41
    Originally posted by birdie View Post
    Yes, because for an init system this is f*cking unacceptable: systemd segfaults, crashes and freezes.
    That's demagogy and fear mongering.

    Your links aren't valid proof of anything and you know it, these are just google searches for "systemd segfault" etc and none of the top results I cared to look at yield a valid complaint or problem or a non-fixed issue.

    It's like saying Obama is a communist by providing such a link as proof.

    Comment


    • #42
      Lennart Sucks

      Lennart produces garbage. Look how long it took for him to fix his PulseAudio

      Comment


      • #43
        I only think that systemd was choosed in an democracy way following Debian rules.

        And I should consider debianfork.org is against democracy as they dont accept the elected option. Debian just can go back in this... so fuck Canonical...

        Comment


        • #44
          "If systemd will be substituting sysvinit in Debian, we will fork the project and create a new distro. We hope this won't be necessary, but we are well prepared for it."

          Is this a kind of terrorist threat?

          Comment


          • #45
            Of course, the core of the argument is not whether or not there should be coupling between DE's and systemd but whether this GR will make freeze plans fail. If Ian's GR is accepted, next Debian will most likely be significantly postponed

            Comment


            • #46
              Originally posted by AndrewGray View Post
              Lennart produces garbage. Look how long it took for him to fix his PulseAudio
              Apple produces garbage, look how long it took them to get to only 8% market share, while window$ still has 90%.
              Microsoft produces garbage, after 30 years their kernel still crashes.
              Assholes like you produce garbage, look at how much hate you yield without any valid point.

              Comment


              • #47
                Originally posted by birdie View Post
                Yes, because for an init system this is f*cking unacceptable: systemd segfaults, crashes and freezes.

                Oh, maybe because Linux developers have lost their minds completely.

                People and ISVs beg them for a stable platform, they make it even more unstable.
                This is not why Linux devs have lost their minds. This is list why you should be banned globally as a troll.

                Comment


                • #48
                  Originally posted by erendorn View Post
                  Managing user sessions is simply not easy. Check what both KDE and Gnome maintainers say on the subject.
                  Consolekit does it, but is unmaintained, and apparently already starting to break.
                  logind does it, is maintained, does it securely, and easily.
                  It is perfectly understandable for a DE to depend on such tools to launch and manage user sessions. Any fallback would probably be either mono user, or just displaying a poput saying "sorry, no user session without logind".
                  And it is perfectly fine to provide a monouser fallback or a fallback with a non-functional lock screen or some other reduced functionality under this proposal. There would still be a bug asking to add such functionality, but that would be either a "wishlist" or "normal" severity bug - not blocking the package from entering the next release. And such bug will be the focal point for people to give support, for example, with patches. All as intended.

                  Originally posted by nanonyme View Post
                  Of course, the core of the argument is not whether or not there should be coupling between DE's and systemd but whether this GR will make freeze plans fail. If Ian's GR is accepted, next Debian will most likely be significantly postponed
                  Everyone involved in the discussion is already in agreement that whatever the resolution of this GR it will *not* have any impact on the jessie release. Currently all such bugs in jessie are fixed and it is unlikely that new cases will be introduced before the release. However, this would impact the next release and also, if any cases were found in jessie, this would allow much easier back-porting of fixes for such issues into jessie even after the release.

                  Comment


                  • #49
                    Those guys are funny: "Hey, we don't have the time to get involved with Debian,but if they don't do what we want we will just fork this 30,000+ packages distribution, pull the 1,000+ developers needed to maintain a distro of this scale out of nowhere and then manage all these people in our spare time!"

                    It should be pretty obvious that this is just another anti-systemd hate campaign that will change nothing at all. Seems to me that some people are really desperate.

                    Comment


                    • #50
                      Originally posted by saulo View Post
                      I only think that systemd was choosed in an democracy way following Debian rules.
                      To be completely fair, what Debian has decided is what init system will be the *default* init system in Debian. Debian has always shipped more than one init system and all software so far has worked with them all (more or less). There was never a vote that Debian should abandon all other init systems. Until such vote all init systems should be kept working for all software as before.

                      Oh and by the way - anyone is welcome to fork Debian at any time: Debian has over 150 derivative distributions and we are very proud of that fact! Anyone wishing to make a "noSystemdAllowed" Debian derivative is welcome to do so.

                      Comment

                      Working...
                      X