Slashdot Mirror


Devuan Progress Report Published

zdzichu writes: The group of anonymous Italians behind the recent Debian fork have published their first progress report. It covers a wide range of topics: the 4.5k€ of donations received so far, moving distro infrastructure from GitHub to GitLab, progress on LoginKit (which replaces systemd's logind), fraud accusations, logo discussions, and few more important points.

73 of 184 comments (clear)

  1. Nice progress! by Anonymous Coward · · Score: 3, Insightful

    Totally beyond my previously (already good) expectations :)
    They will have a future much more promising than those who are afraid of choice would say.

  2. Re: Their comments on trolls/trolling by Anonymous Coward · · Score: 1

    OTOH logind is -- according to the #debianfork channel on IRC -- useless and it is better and more secure to run x.org as root than to have systemd running.

    Which seems reasonable. Look how many recent security bugs are related to systemd vs x.org.
    It's very prudent to defer systemd deployment until it gets mature (in case it has the possibility to get mature :).

  3. SOAP vs Rest by Tailhook · · Score: 1, Interesting

    This reminds me of the early days of "web services." The "enterprise" folks were jetting around writing gobs of XML and SOAP specifications, making speeches at conferences and whatnot. Meanwhile, some thoughtful people pointed out that the combination of existing HTTP verbs and the natural namespace provided by URLs satisfied the same use cases without the mountains of esoteric specifications and staggering protocol overhead. One memory I have from that time has persisted; some SOAP standards body muckity-muck was asked about REST during some function that happened around the time of the SOAP 1.0 specification release and he said (paraphrased); "Those REST folks aren't the kind of people the get things done!"

    Today, SOAP gives people nausea almost universally and REST is the first choice of green-field work, with all sorts of API's proliferating everywhere. New languages and tools target REST first and SOAP eventually. Maybe. And if not then, meh, whatever.

    Now we have the Debian fork. And what is said of the people behind it by those advocating systemd bloatware? Well they're just malcontents. They don't understand the problem systemd is trying to solve. They made a crummy web site and didn't even put their names on it. They'll never accomplish anything!

    I have the feeling Poettering et. al are going to lose this one. If so then at least we can credit systemd with providing the motivation to progress, and reaffirming some of those cherished (if possibly mythical) UNIX principles.

    (Incidentally, if anyone knows who was responsible for that statement about REST I mentioned please chime in .... I'm 99% sure it appeared on Slashdot.)

    --
    Maw! Fire up the karma burner!
    1. Re:SOAP vs Rest by igloo-x · · Score: 1, Funny

      Your little SOAP vs. REST story is only memorable because it almost never happens. Debian has a tendency to eat it's children and I've yet to read a single compelling technical reason on Slashdot why systemd is a bad idea. Most anti-systemd people heard about it then decided they hate it because of its feng-shui or whatever, then retroactively invent bullshit technical reasons for it which are either ignorance or lies.

    2. Re:SOAP vs Rest by DrXym · · Score: 1
      I don't see many parallels. Working with systemd isn't exactly rocket science for admins or end users. Instead of typing one command to start or stop a service you type another. Systems even provide aliases or links to support the old notation, e.g. shutdown in FC21 is a link to systemctl which infers what to do from argv[0].

      Tenuous comparison aside, probably the main reason SOAP dropped out of sight was it wasn't suitable for the eventual problem domain. SOAP was fine for computer to computer (B2B) communication where it's rather important to have schemas with validation, XML signatures, bindings like Axis that generate some nice stub classes for you and all that stuff. But it's a pain in the ass when you're a bit of JS in a browser trying to process some text you just got from a server and it's too much effort to produce schemas for the sake of some snippets of data. Of course JSON has taken off so much that suddenly having a schema for validation purposes is quite important again. I bet anyone who has used JSON in a server or wherever has had to handroll validators to ensure what they're getting is correct (e.g. that a field exists or contains a number etc.). There are drafts to produce a JSON schema spec and I expect in time tools will appear that spew out stubs and validators from a schema in a manner not wholly dissimilar from SOAP. So things will turn full circle in time. Doubtless someone will proclaim that JSON is too much effort at that point and suddenly we'll all supposed to be using YAML.

    3. Re:SOAP vs Rest by Hognoxious · · Score: 1

      It is what it is because a bunch of people got talking about problems they were having with their Linux set-ups and decided that the best way to solve their problems was to re-implement a few system components under the umbrella of one project.

      It may be the best way to solve their problems. But if I'm suffering from these problems, I haven't noticed yet. So I'll take the status quo over a half-assed solution that's been in existence for a shorter period than some people's uptimes, thanks all the same.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    4. Re:SOAP vs Rest by Barsteward · · Score: 1

      "Which does not explain systemd's exceptionally bad design (or did they design at all?) and implementation."

      that is just your opinion because you don't like it (which is a normal reaction to "i don't like it so i'll trash it") - so why not do an in-depth analysis on its "exceptionally bad design and implementation" and publish it so we can all see what you are talking about and check your points of reference and justification for your opinion. I'm sure if your analysis has any good points, they'll be stupid not to implement them.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  4. Re:For a bunch of people who hate Debian by Anonymous Coward · · Score: 1

    Nice propaganda, except they do not hate Debian :)
    What they might hate is the people flooding Debian that are afraid (look, I do not use "hate" :) of choices.
    Devuan is embracing the original spirits of Debian, so no wonder it reuses elements from the Debian logo.

  5. Wait a minute... by wonkey_monkey · · Score: 1

    It covers a wide range of topics: the 4.5k€ of donations received so far, moving distro infrastructure from GitHub to GitLab, progress on LoginKit (which replaces systemd's logind), fraud accusations, logo discussions, and few more important points.

    Was someone trying to sneak that one through in the middle of a dull-news sandwich?

    --
    systemd is Roko's Basilisk.
    1. Re:Wait a minute... by Peter+H.S. · · Score: 1, Informative

      It covers a wide range of topics: the 4.5k€ of donations received so far, moving distro infrastructure from GitHub to GitLab, progress on LoginKit (which replaces systemd's logind), fraud accusations, logo discussions, and few more important points.

      Was someone trying to sneak that one through in the middle of a dull-news sandwich?

      The problem is that all money donated to Devuan doesn't go directly into Devuan, but into a rather dubious organization, with no public oversight and no accountability.
      Here is a link to the org and their pre-Devuan Linux distro:
      http://www.dynebolic.org/
      Take a look around, and notice how a "donate" button never is far way from any project or web page.

      The foundation has a chairman called Denis Roio, AKA "Jaromil", and according to themselves, the foundation "helps them pay taxes", in other words, they pay themselves from the org whatever they like.

      There is a certain smell of "scam" around the Devuan project, not so much its contributors as a whole, but about the small group of shady figures centered around the "dyne org".

    2. Re:Wait a minute... by jaromil · · Score: 1

      Thanks Peter! you are so kind! Hey wait a minute! the scammers are also on slashdot!! quick quick, close your wallet!

    3. Re:Wait a minute... by Peter+H.S. · · Score: 1, Interesting

      Thanks Peter! you are so kind!

      Hey wait a minute! the scammers are also on slashdot!!

      quick quick, close your wallet!

      Well, I am right ain't I. You funnel the donated Devuan money into dyne org, and as CEO/Chairman of that small org with self elected people, with no public oversight of the money, you also pull money out of dyne org into your own pocket to "pay for taxes". Dress it all up as a non-profit org too.

      Make Devuan a proper org that directly receive the donated money you are begging for all the time, and have a proper elected committee with public oversight over the donated money and what they are spend on, and then maybe the smell of scam will evaporate.

    4. Re:Wait a minute... by marcello_dl · · Score: 2

      If dyne is a foundation, I don't see why there must be another entity for Devuan, since the objectives are the same. It's like 300â down the drain yearly for mere bureaucracy. If a bunch of devuan devs got elected to "lead" the distro and dyne.org staff did not respect their decisions, dyne would be a hindrance, but I'd wait for this to happen and or provide some substance to your fraud accusation. AFAIK, a foundation would need accounting tricks or no funds appropriation can take place.

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
  6. Forked the Debian? or the Debian? by ThePhilips · · Score: 1

    The larger question is: what Devuan is really forking?

    Do they fork a distro?

    Or do they fork an organization?

    With some work, one can fork a distro. But to fork the organization, one need to win over the people. I doubt that they will win over many (Debian) people without actually changing something in the forked organization.

    Though many see the "systemd vs world" as the dividing force, in reality there is IMO problem with Debian organization. I have followed the debate for some time, and IMO, the problem is that there is too much democracy in the Debian. Public debate is a good thing. But too much of it simply prevents the organization from doing its work. That is IMO what has happened during the Debian's init system selection process.

    --
    All hope abandon ye who enter here.
    1. Re:Forked the Debian? or the Debian? by ruir · · Score: 2

      The problem with Debian is that for whatever reason they ignored the power of linux, choice. At least in Debian 8, it is still trivial to make it use sysvinitrc instead of system. Why not let people choose, instead of forcing it upon new upgrades, and worse insult yet, make current systems upgrade to systemd by default?

    2. Re:Forked the Debian? or the Debian? by kthreadd · · Score: 4, Insightful

      Choice is not a matter of just pressing a button and have it magically appear. Someone has to actually maintain it. The Devuan developers think that they can do that. If so then that's great. It's sad that they don't think that they can do the same thing within Debian though I understand their reasoning. It takes a lot of time and effort to get into Debian and they want to be more pragmatic.

    3. Re:Forked the Debian? or the Debian? by Cley+Faye · · Score: 1

      The proposition to have multiple init system in Debian was promptly rejected with arguments ranging from infeasible to "who is going to make all these packages compatible with sysv init" (although they were compatible a few month ago).
      I don't think doing it anyway in Debian was a good choice in that ambience.

    4. Re:Forked the Debian? or the Debian? by kthreadd · · Score: 1

      "who is going to make all these packages compatible with sysv init"

      Exactly. Did someone step up within Debian to do it?

    5. Re:Forked the Debian? or the Debian? by ThePhilips · · Score: 1

      I do not know the answer for the Debian, but if you did RTFA, you would notice that it is precisely what the Devuan is doing: creating and packaging software which provide the interface of systemd services without the systemd itself.

      The (retorical) question which I have already asked on difference occasions here is whether the Debian is a good place to do such development.

      One strong undertone from the CTTE's init system selection debate was that Debian doesn't want to do the development and wants to maximize the reuse of the code from the other distros. This turned into a weird attitude when systemd vs. upstart was evaluated. The upstart devs and maintainers have committed themselves to implement whatever Debian needs. The systemd devs and maintainers committed to literally to nothing, basically saying "if it is good for Fedora is should do the job for Debian too; no Debian specific patches are going to be accepted even into the Debian systemd package". And that was later respun by a couple of CTTE members as "upstart still needs development while systemd doesn't".

      That is also why I raise the question about changes to the Debian organization in Devuan: How could Devuan be more software developer friendlier? At the moment the barrier to entry is very high, leaving developers at mercy of the respective Debian packager. Or leaving the developer basically out if it has something to do with the low-level stuff like init system.

      --
      All hope abandon ye who enter here.
    6. Re:Forked the Debian? or the Debian? by kthreadd · · Score: 2

      I do not know the answer for the Debian, but if you did RTFA, you would notice that it is precisely what the Devuan is doing: creating and packaging software which provide the interface of systemd services without the systemd itself.

      Yes, that's what they are doing.

      The (retorical) question which I have already asked on difference occasions here is whether the Debian is a good place to do such development.

      One strong undertone from the CTTE's init system selection debate was that Debian doesn't want to do the development and wants to maximize the reuse of the code from the other distros. This turned into a weird attitude when systemd vs. upstart was evaluated. The upstart devs and maintainers have committed themselves to implement whatever Debian needs. The systemd devs and maintainers committed to literally to nothing, basically saying "if it is good for Fedora is should do the job for Debian too; no Debian specific patches are going to be accepted even into the Debian systemd package". And that was later respun by a couple of CTTE members as "upstart still needs development while systemd doesn't".

      That is also why I raise the question about changes to the Debian organization in Devuan: How could Devuan be more software developer friendlier? At the moment the barrier to entry is very high, leaving developers at mercy of the respective Debian packager. Or leaving the developer basically out if it has something to do with the low-level stuff like init system.

      You're talking about Debian and Devuan like it's two monolithic organizations. It's not. It's people. And and if you want "Debian" to do something then real human Debian developers will have to do the job. It doesn't matter what any committee decides if no one is interested in actually doing the work.

      The Devuan developers are obviously up for the task. That's great. They do what they want to do. It's just too bad that they for whatever reason couldn't do it in Debian. I don't blame them. It takes an arm and a leg to get into Debian nowdays, so if it's easier for them to create a fork then maybe that says something about the Debian project too.

    7. Re:Forked the Debian? or the Debian? by Peter+H.S. · · Score: 1, Interesting

      The problem with Debian is that for whatever reason they ignored the power of linux, choice. At least in Debian 8, it is still trivial to make it use sysvinitrc instead of system. Why not let people choose, instead of forcing it upon new upgrades, and worse insult yet, make current systems upgrade to systemd by default?

      Every choice has a cost and a consequences. In this case, supporting multiple init-systems dramatically increase the maintenance complexity. Every Debian Developer would need to run both a stable and unstable/testing version of both init systems, and some packages would have to be maintained in two different versions (talk about dependency hell).

      But that isn't even the most problematic part; that is the fact that all non-systemd development have more or less collapsed the last couple of years; "ConsoleKit" bit-rotted for years, meaning DE developers couldn't justify developing against it, "SysVinit" is hopelessly understaffed (don't even have a build test) and haven't made a release for 5 years (RH/SUSE was the defacto maintainers), there is no development taking place on real alternatives to systemd's "udev" (the "eudev" is mainly a shadow fork by AFAIK, one person), "cgroups" development like "CGManager" will cease when systemd provides functionality to support LXC, and so on.

      In short, there is a huge stack of development needed now and in the future in order to run a non-systemd Linux distro, and fewer and fewer developers to do the job.

      When FreeBSD changes to a modern init-system (they will probably clone systemd), they won't support old legacy style init-scripts daemons permanently either. It is simply too much work with too little gain.

    8. Re:Forked the Debian? or the Debian? by Peter+H.S. · · Score: 1

      .... The systemd devs and maintainers committed to literally to nothing, basically saying "if it is good for Fedora is should do the job for Debian too; no Debian specific patches are going to be accepted even into the Debian systemd package".

      That is simply wrong. Please notice that several long time systemd developers with commit access to the systemd git tree, are in fact Debian Developers. So there is a lot of "Debianism's" in where files placed etc.

      Sure, the main branch of systemd wants to have as few distro specific patches as possible, but they do accept them if there is no other solution.

      Here is a Debian specific patch that predates Debians adoption of systemd as default init-system:
      http://cgit.freedesktop.org/sy...

    9. Re:Forked the Debian? or the Debian? by ThePhilips · · Score: 1

      You're talking about Debian and Devuan like it's two monolithic organizations. It's not. It's people. And and if you want "Debian" to do something then real human Debian developers will have to do the job. It doesn't matter what any committee decides if no one is interested in actually doing the work.

      Hu?

      This very topic was laundered during the init system selection on the debian-ctte for very long time: it makes no sense to invest time into developing systemd if upstart is picked, and vice versa.

      There might be people willing to do the work - but there is little more demotivational than a project declaring that they are taking a different path.

      But the most demotivational is when people are told that they can't even have an alternative systemd implementation/fork - of which there are already couple - because GNOME demands the systemd, not just any systemd.

      For motivation to spend your free time on something, this is as good as hitting a brick wall at full speed.

      The Devuan developers are obviously up for the task. That's great. They do what they want to do. It's just too bad that they for whatever reason couldn't do it in Debian. I don't blame them. It takes an arm and a leg to get into Debian nowdays, so if it's easier for them to create a fork then maybe that says something about the Debian project too.

      To me the most interesting part whether the whole fork would even take off.

      Technical aspects of init system replacement are very easy - compared to the establishment of an organizational structure of the Debian.

      --
      All hope abandon ye who enter here.
    10. Re:Forked the Debian? or the Debian? by ThePhilips · · Score: 1

      Sure, the main branch of systemd wants to have as few distro specific patches as possible, but they do accept them if there is no other solution.

      I was just quoting the (ex-)maintainer of the systemd, from his e-mails from the CTTE discussion.

      Debian feedback would be submitted to mainline - but if it is rejected, he wouldn't even carry a custom Debian patch for it, because he doesn't want to deviate from the mainline. And he, as the maintainer of the systemd, would not consider it a bug. As such somebody else would have to fix somewhere else.

      If you are willing to grep through the 1K emails - you would definitely find that being repeated several time.

      Here is a Debian specific patch that predates Debians adoption of systemd as default init-system: http://cgit.freedesktop.org/sy...

      It's obviously not Debian specific.

      It is very obviously a distro specific part of systemd: Debian was added to the list where Fedora and Arch were already present.

      --
      All hope abandon ye who enter here.
    11. Re:Forked the Debian? or the Debian? by Peter+H.S. · · Score: 2, Insightful

      I was just quoting the (ex-)maintainer of the systemd, from his e-mails from the CTTE discussion.

      Without source or citation. I think your representation of what was said is rather biased.

      Debian feedback would be submitted to mainline - but if it is rejected, he wouldn't even carry a custom Debian patch for it, because he doesn't want to deviate from the mainline. And he, as the maintainer of the systemd, would not consider it a bug. As such somebody else would have to fix somewhere else.

      If it isn't a bug, why patch it? Sure, some people have tried to drop some turd patches into systemd, eg. ripping out security features in order to support some obscure glibc variant. The right thing of course is to patch the glibc variant to support the proper security functions, not patching systemd.

      No package maintainer wants to support non-trivial, non-mainline patches without very good reasons. The whole point of open source software, that as many people as possible can share and enjoy improvements, so patches should go upstream as fast as possible. Maintaining non-trivial, non-upstream patches can also be a real problem when backporting security fixes, and may introduce patch specific bugs too.

      If you are willing to grep through the 1K emails - you would definitely find that being repeated several time.

      I have actually read most of them at the time, and I still think you are misrepresenting the systemd maintainers.

      Here is a Debian specific patch that predates Debians adoption of systemd as default init-system:
      http://cgit.freedesktop.org/sy...

      It's obviously not Debian specific.

      It is very obviously a distro specific part of systemd: Debian was added to the list where Fedora and Arch were already present.

      Huh? The main point is that systemd mainline accepts Debian (and distro) specific patches if it is unavoidable. Despite the many claims to the contrary, the systemd developers do care about feedback and have many different distro developers with commit access. If you got a good user case, chances are good that a distro specific patch will be accepted. And having the patch going into the upstream repo is much better than carrying it as a separate distro patch.

      In short, Debian developers where taking part in creating systemd long before Debian discussed making systemd the default init system. So they knew what they where doing when selecting systemd over Upstart (the CLA was enough to discount it), and the latest GR have confirmed that the vast majority of Debian developers firmly backs systemd as the default init-system.

    12. Re:Forked the Debian? or the Debian? by Damouze · · Score: 1

      But the most demotivational is when people are told that they can't even have an alternative systemd implementation/fork - of which there are already couple - because GNOME demands the systemd, not just any systemd.

      Anyone remember AARD?

      --
      And on the Eighth Day, Man created God.
    13. Re:Forked the Debian? or the Debian? by Eunuchswear · · Score: 1

      The proposition to have multiple init system in Debian was promptly rejected

      No it wasn't.

      What was rejected was the proposition that packages that didn't support all init systems should be removed from Debian, violating the Debian constitution:

      2.1.1 Nothing in this constitution imposes an obligation on anyone to do work for the Project. A person who does not want to do a task which has been delegated or assigned to them does not need to do it. However, they must not actively work against these rules and decisions properly made under them.

      Deboian does have multiple init systems, and if people want it to continue to have multiple init systems then it is up to those people to do the work, not to try to force other developpers to do the work for them.

      --
      Watch this Heartland Institute video
    14. Re:Forked the Debian? or the Debian? by Eunuchswear · · Score: 2

      GNOME demands the systemd, not just any systemd.

      No. Gnome demands libpam-systemd or consolekit. libpam-systemd demands either systemd or systemd-shim.

      So either work on consolekit/consolekit2 or work on systemd-shim.

      --
      Watch this Heartland Institute video
    15. Re:Forked the Debian? or the Debian? by ThePhilips · · Score: 2

      If it isn't a bug, why patch it?

      And this is a clear systemd bias (and GNOME attitude).

      If systemd says it is not a bug, then it is not. And if something doesn't work - well, somebody opened a ticket about something NOT working - then something does NOT work. And if the systemd refused to fix it - who's going to?

      The whole position of systemd implementors in Debian was and probably still is: we change how the whole system works, but we are totally not responsible if something breaks, because it is, duh, mainline systemd.

      The whole problem of the hairy rcS scripts was ability to workaround pretty much any software or hardware problem on spot. Here, systemd insists that they are always in right - it is the rest of the world who are wrong. The problem is that a blank statement about wrongness of the world (it never was right to begin with) doesn't solve the immediate problem users are having.

      I have actually read most of them at the time, and I still think you are misrepresenting the systemd maintainers.

      Frankly I do not remember. It could have been one of the adjacent tickets about the systemd breaking the systems on autoupdate.

      Tollef Fog Heen was pretty clear that he is not going to do anything special for Debian. (He is (or was at the time) a Fedora user already anyway.)

      Huh?

      If you can't tell what the hell the trivial commit does, then you are obviously not a software developer.

      That was a great PR move on part of the systemd developers: to flood the mail lists with the buzz words. Users have no idea what they mean - but they sure sound cool - so systemd must be cool too.

      --
      All hope abandon ye who enter here.
    16. Re:Forked the Debian? or the Debian? by ThePhilips · · Score: 1

      GNOME demands the systemd, not just any systemd.

      No. Gnome demands libpam-systemd or consolekit. libpam-systemd demands either systemd or systemd-shim.

      So either work on consolekit/consolekit2 or work on systemd-shim.

      I was basically quoting Debian's GNOME maintainer, from the times of the Debian's CTTE debate.

      At least at the time, Debian's GNOME package had a hardcoded dependency on the systemd package, not a feature/virtual package which provides the services. And GNOME DDs were refusing to change that, because they didn't like the systemd-shim.

      --
      All hope abandon ye who enter here.
    17. Re:Forked the Debian? or the Debian? by Eunuchswear · · Score: 2

      At least at the time, Debian's GNOME package had a hardcoded dependency on the systemd package, not a feature/virtual package which provides the services. And GNOME DDs were refusing to change that, because they didn't like the systemd-shim.

      Whether that was the case then it isn't now.

      gdm3 depends on libpam-systemd.

      libpam-systemd depends on systemd-sysv | systemd-shim.

      There is exactly one package in current Jessie or Sid that depends on systemd -- gummiboot.

      --
      Watch this Heartland Institute video
    18. Re:Forked the Debian? or the Debian? by blind+biker · · Score: 1

      I had the impression your post had an agenda, and then I read, at the end, you confirmed it:

      When FreeBSD changes to a modern init-system (they will probably clone systemd)

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    19. Re:Forked the Debian? or the Debian? by Peter+H.S. · · Score: 1

      If it isn't a bug, why patch it?

      And this is a clear systemd bias (and GNOME attitude).

      If systemd says it is not a bug, then it is not. And if something doesn't work - well, somebody opened a ticket about something NOT working - then something does NOT work. And if the systemd refused to fix it - who's going to?

      Not every bug filed is an actual bug, even though the submitter feels it is. Saying no to bad patches and closing non-bugs with a "not-a-bug" is the daily grind of developers and package maintainers.

      The "Heartbleed" bug is a prime example on how bad things can go when you accept patches that circumvent security measures in order to support obscure user cases.

      Really, systemd developers accept a huge amount of patches from hundreds of different non-systemd developers each year, suggesting that they won't accept patches is simply contrary to reality. I have yet to see a reasonable patch being rejected on the systemd-mailing list.

      The whole position of systemd implementors in Debian was and probably still is: we change how the whole system works, but we are totally not responsible if something breaks, because it is, duh, mainline systemd.

      I really don't see the Debian systemd maintainers that way at all. They seem to be hard working and serious to me. I have yet to see a example of them accepting breakage because mainline systemd. As I said, there are Debian developers with commit access to the systemd git tree, so they obviously have a lot of influence on systemd as a upstream project.

      Tollef Fog Heen was pretty clear that he is not going to do anything special for Debian. (He is (or was at the time) a Fedora user already anyway.)

      I have seen no examples or evidence of this. Really, what specific non-trivial patches could Debian need that couldn't go into mainline systemd? Can't think of any, nor have I ever seen it on the mailing list.

      Huh?

      If you can't tell what the hell the trivial commit does, then you are obviously not a software developer.

      It is trivial, but it is Debian distro specific and in upstream systemd. There are a lot more examples in the git tree, and also of Debian influence in the general design of systemd. You assertion that systemd developers doesn't care or won't accommodate the Debian distro is therefore unfounded.

      That systemd actually accepts trivial distro specific patches, shows that they are accommodating their users. Since it is trivial, it could have been carried by the distro maintainer.

      That was a great PR move on part of the systemd developers: to flood the mail lists with the buzz words. Users have no idea what they mean - but they sure sound cool - so systemd must be cool too.

      Really, trying to pass off systemd as a "fad" that Debian accepted because of "buzzwords" on a mailing list is outright pathetic; systemd is real improvement over SysVinit in every aspect, and the Debian CTTE choose it because of its technical merit. That the Debian developers agree with this, was demonstrated at the latest Debian GR.

    20. Re:Forked the Debian? or the Debian? by Peter+H.S. · · Score: 1

      I had the impression your post had an agenda, and then I read, at the end, you confirmed it:

      When FreeBSD changes to a modern init-system (they will probably clone systemd)

      Sure, my agenda is to show that supporting multiple init systems is very difficult.

      That FreeBSD (and other BSD's) will change to a systemd-like init system is a given thing too. Even the founder of FreeBSD has publicly said it is in the future for FreeBSD.

      The fact is that the way people uses computers have changed dramatically the last decade; virtualization, OS containers, instantiated services, mobile devices etc. SysVinit and similar legacy style script based init systems simply aren't up to working with all this.

      So when FreebSD change their init system (and they will), they won't support a free choice between the new init system and old legacy script based init systems either.

    21. Re:Forked the Debian? or the Debian? by linuxrocks123 · · Score: 1

      Technical aspects of init system replacement are very easy - compared to the establishment of an organizational structure of the Debian.

      Ha ha ha ha ha. The best way to kill the project would be to set up the "organizational structure of Debian". Once you remove from Debian the ftp-masters political intrigues, the bureaucratic red-tape "freeze" phases, the militant feminist lobbying group, and the unnecessary and technically incompetent divergences from upstream (see "Debian openssl"), there's not much "organizational structure" to Debian left.

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    22. Re:Forked the Debian? or the Debian? by Barsteward · · Score: 1

      who let you out of kindergarten?

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    23. Re:Forked the Debian? or the Debian? by Eunuchswear · · Score: 1

      A weird attitude for a project that previously have forked such things as Firefox over a licensing issue.

      Debian didn't fork Firefox. Mozilla told Debian that if Debian didn't build exactly the code that Mozilla released then Debian weren't allowed to use any Mozilla trademarks -- the name, the logo and so on.

      Since Debian stable doesn't change versions (that's what stable means) that would have meant no bug fixes for Firefox (and Thunderbird) for a whole Debian stable release, which was unacceptable. So Debian made a version of Firefox with no Mozilla trademarks, Iceweasel. It's not a fork, Debian writes no code for it, it's just Firefox with a new name, logo, and whatever security patches are needed.

      --
      Watch this Heartland Institute video
  7. Why to develop anything? by short · · Score: 1

    Linux worked better - or rather it really worked - before systemd. Why to develop anything? Just keep the old proven and _working_ daemons.

    1. Re:Why to develop anything? by short · · Score: 2

      upstart is event based, it has replaced sysvinit in RHEL-6 and RHEL-6 still worked, I have noticed it has replaced init only after some time using it. systemd's scope is needlessly large for the even based parallelization, systemd replaces everything what worked and nobody complained before.

    2. Re:Why to develop anything? by Anonymous Coward · · Score: 1

      Fast. Reliable.Simple. Pick two.

      False assertation. daemontools, runit, s6 all do that successfully with simplicity and elegance.
      systemd? a init spaghetti monster, even worse than sysvrc (in case you do not know sysvinit and sysvrc are two things).

    3. Re:Why to develop anything? by thegarbz · · Score: 1

      Systemd's scope is as large as it needs to be for what it is trying to achieve, complete system level management. It was never about simply replacing the init system. In many ways it hasn't done anything to init systems that hasn't been done before by many of the init replacements.

      But the thing about nobody complaining is that it just plain isn't true. People don't magically create software where there isn't a gap to fill (fucking about user interfaces excepted of course). There are people who think the idea of unified system management able to handle all aspects of process control in one package is great. There are plenty of detractors (especially vocal on slashdot) who will say that this should be managed by a set of 40 different projects, but it appears enough people think otherwise that it has not only been created but it has also been adopted.

    4. Re:Why to develop anything? by Spazmania · · Score: 2

      I picked my two: reliable and simple. That's why I picked Debian. If my priority was "fast" I'd have picked Gentoo and suffered.

      See init get complicated in the name of a faster boot gives me heartburn.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    5. Re:Why to develop anything? by short · · Score: 1

      Maybe there is some need for extension (although I have never found it) but in that case - systemd is still too buggy to be deployed in a real OS. After any upgrade/update I am dealing with daemons refusing to start, system upgrade takes _whole_night_ because systemd crashed on an assert - on each host upgraded etc. etc.
      It is similar to pulseaudio, since that time I had to learn all the options of audio software how to deal with silent audio which always worked before pulseaudio deployment.

    6. Re:Why to develop anything? by Windowser · · Score: 3, Insightful

      I picked my two: reliable and simple. That's why I picked Debian.

      I use Debian for the same reason

      See init get complicated in the name of a faster boot gives me heartburn.

      You need a system that boot fast when you reboot often. I don't care if my Linux system takes a couple seconds more to boot since I almost never reboot it.

      --
      Avoid the MS tax, always buy I.B.M. PC's (I Built-it Myself)
    7. Re:Why to develop anything? by IMightB · · Score: 2

      Faster boot seems to be the one small feature that systemd haters pick up on. In reality, systemd provides many many more things than just a faster boot.

    8. Re:Why to develop anything? by Spazmania · · Score: 1

      I think of it like passing programs between processes like bash now does in the environment variables.

      DO. NOT. WANT.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    9. Re:Why to develop anything? by bucky0 · · Score: 2

      People don't magically create software where there isn't a gap to fill (fucking about user interfaces excepted of course).

      Everything systemd aside, that's not true. The NIH-syndrome is alive and well. Instead of working on and improving existing software, a LOT of people want to start from scratch just so they can have their braces in the place they like to see them. For instance, I was poking around with protobuf earlier and saw that there are five javascript bindings.

      --

      -Bucky
    10. Re:Why to develop anything? by Barsteward · · Score: 1

      "complaints" against something doesn't mean they are true, it can just mean they are they don't like "new". people will complain about something even if its faultless.

      again, the logging is overblown because you can still have text logging so its used as a stick to beat systemd even though text logging still works.

      again, that DNS component is optional. i'm sure they'll fix it at some point as they are discussing it now so until then use what you use now.

      i didn't see anything in the blog post that says "sacrifices security (susceptible to ARP attacks) in favor of speed" but it does say they are pretty much the same speed as all other implementations so does that mean all other implementations are also sacrificing security in faour of speed?

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    11. Re:Why to develop anything? by thegarbz · · Score: 1

      See init get complicated in the name of a faster boot gives me heartburn.

      If you think the goal of systemd was faster booting then you have some reading to do. Like a lot of reading.

    12. Re:Why to develop anything? by Barsteward · · Score: 1

      Obviously Redhat don't suffer your unjustified prejudice against technical people that are far smarter than you could ever be.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    13. Re:Why to develop anything? by Barsteward · · Score: 1

      I think i'd rather take Redhat, Suse etc stance over systemd than an AC who "proclaims" to "understand the guts" as I am sure they would rather not have a system given to clients that would be a problem. Fortunately your unsupported opinions don't carry any weight with likes of Redhat etc, fully supported opinions with evidence probably would be looked at.

      --
      "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
    14. Re:Why to develop anything? by Spazmania · · Score: 1

      Red Hat uses upstart. It's as nasty if not nastier than systemd.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    15. Re:Why to develop anything? by Spazmania · · Score: 1

      Well, if it's goal was improved reliability or making the sysadmin's life easier it missed by quite a bit. If it's goal was something else, then it's moving in a direction other than the reason I wanted Debian for.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  8. Re:make it easy! by Anonymous Coward · · Score: 1

    That is the reason why systemd becomes entrenched: Developers like it and start to depend on it since it makes their live easier.

    Which is very debatable, if not just laughable.

  9. Re:make it easy! by Anonymous Coward · · Score: 2

    That is the reason why systemd becomes entrenched: Developers like it and start to depend on it since it makes their live easier.

    Which is very debatable, if not just laughable.

    Systemd is Microsoft Event Viewer and data store for GNU/Linux. We do not want binary logs. If an operating system requires more than a text editor to view log files, there is a problem with the operating system and/or the log files. As an GNU/Linux since 1992 when SLS was "the distribution of choice" the current trend with the Debian GNU/Linux Project baffles my mind. What happened to the vision Deborah and Ian conceived so many year ago?

  10. Re: Their comments on trolls/trolling by t_hunger · · Score: 2

    The absense of CVEs can mean the absense of people looking, and with the x11 being a quagmire of protocols, often contradicting each other as new stuff gets added over the decades, there are very few people that can even understand the code. One guy started to look last a while back and he is finding appalling bugs, check the recent CVEs and his presentation at last years chaos communication congress (30C3).

    Making this swamp a bit dryer by not having it have root priviledgea is something that was work in progress ever since xfree started to run on Linux.

    Now you come here and tell me that this sour spot for the last thirty years is better to keep around than having a much smaller, much cleaner codebase where almost all parts run in their own security context -- usually with privileges way lower than those you have as a user. Right.

    --
    Regards, Tobias
  11. Re: make it easy! by t_hunger · · Score: 1

    That consultation mongering in that link is indeed laughable.

    --
    Regards, Tobias
  12. Re: Their comments on trolls/trolling by Spazmania · · Score: 1

    Thing is, I've been using it to build sheds and I'd like to keep using it to build sheds. Don't insist I use bridge-building techniques to build a shed.

    --
    Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
  13. Re:Their comments on trolls/trolling by 0100010001010011 · · Score: 2

    I wish they would had put their efforts into Debian's kFreeBSD. It can't move to systemd and they downgraded it from an 'official' Jessie release.

    Personally it's a bit of the best of FreeBSD and the best of Debian (apt-get) in a nice package. There's no problem with ZFS being 'in' the kernel. The latest versions of FreeNAS and FreeBSD both have ZFS booting.

    Plus it still has all the debian server admin tools.

  14. Re: Their comments on trolls/trolling by Anonymous Coward · · Score: 1

    Even you own numbers show that xorg-sever is way bigger than systemd. Not that compressed archive sizes are a meaningful metric, nor is the contents of the archives remotely comparable.

    I was able to follow the systemd codebase rather easily, it is not to horrible in my opinion. I won't comment on xorg for lack of first hand experience.

    Check http://www.x.org/wiki/Development/Security/ yourself: The last batch from Dec. alone was 12 CVEs. Compared to those the issues you listed in systemd are rather tame. And yes, there will be more issues discovered in systemd (as there will be more in x11).

    But all that is completely besides the point: We have a way to run xorg non-root now, and you do not like that way. Please suggest an alternative then, that gets the same results but which is more robust. So far I hear "running xorg as root is secure" and the argument for that is "we always did it that way".

    I am hoping the devuan people will come up with ideas to solve long-standing problems, but do far I have not seen much interest:-(

  15. Re: make it easy! by t_hunger · · Score: 1

    That person is bitching that everybody and their dog start to depends on systemd. That is your evidence right there.

    Of course you have to do the dating assumption that devs do whatever they like... It kind of crumples if you assume that there are systemd hitmen traveling the world, forcing developers to depend on systemd.

    --
    Regards, Tobias
  16. Re: Their comments on trolls/trolling by t_hunger · · Score: 1

    What got vdev/udev to do with running xorg as non-root? Yes, that does initial setup of device nodes, but all the rest is handled by systemd-logind.

    You are brandishing the wing stick:-)

    --
    Regards, Tobias
  17. Re: make it easy! by t_hunger · · Score: 1

    There is no way to refute conspiration theorists. It is a self-contained believe system, that functions outside of the real world. I won't bother to argue with that.

    --
    Regards, Tobias
  18. Re: Their comments on trolls/trolling by t_hunger · · Score: 1

    It was not possible with consolekit, great that there was progress with consolekit2.

    --
    Regards, Tobias
  19. Re:Their comments on trolls/trolling by davydagger · · Score: 1
    No one is scared of anyone, I am just sick of hearing bitching and complaining from the anti-poettering, and anti-systemd crowd about trolls. They are the trolls, and have gone as far as to issue poettering death threats. Once we fought back, like a typical reactionary bully, they cried of being oppressed. Fuck them

    Its good to see a few of them are actually putting their money where their mouth is. The beauty of open source is that it gives the loudmouth enough rope to hang himself. He doesn't get to bitch that anything was forced on him, or he had no choices.

    But you see how this ends, if they were any bit good a system design, or even system administrator, they wouldn't be bitching about systemd or poettering in the first place, because if they were any good, they'd understand there are other options, and installing something else isn't hard. If you're a decent sysadmin that is. But if they had the skills to run a diffrent init system, they wouldn't be bitching.

    No one is forcing anything on these people, its simply the more technically competant people who work for distros are more technically competant. So, after years of bitching they finally did something, and do you know what is going to happen to Devuan? Nothing. Its going to fizzle because maintaining a distro isn't as hard as making death threats and bitching, and if they actually had the skill and dedication to learn something new, most likely they'd be systemd fanbois

  20. Re: Their comments on trolls/trolling by Eunuchswear · · Score: 1

    Hooray! The anti-systemd paedophiles have turned up again! Now the gang's all here.

    --
    Watch this Heartland Institute video
  21. Re: Their comments on trolls/trolling by Peter+H.S. · · Score: 1

    The rest is fully achievable using ConsoleKit2. You realize you don't understand it, which is good ;-)

    Link please. AFAIK, it isn't possible to run Xorg as non-root in a safe manner using either CK or ConsoleKit2.

    And BTW, the difficulty in running xorg as non-root in a safe manner is caused by the way the Linux kernel handles devices, not Xorg. That is why you need user session management from systemd-logind in order to secure that attached devices can't be abused to compromise security.

  22. i want to see an ISO to burn & install by FudRucker · · Score: 1

    then i will see how much i like Devuan

    --
    Politics is Treachery, Religion is Brainwashing
  23. Re:good job Dev Juan by TechyImmigrant · · Score: 1

    and appreciate systemd's implicit mandate for backup suffixes that won't fill your hd undetected as an exercise.

    So implicit that it wasn't explicit.

    --
    I should use this sig to advertise my book ISBN-13 : 978-1501515132.
  24. Modular Debian by trek00 · · Score: 1

    I see another good project starting, Modular Debian, that aims to integrate the pid 1 freedom in the main distribution, without forking https://www.freelists.org/arch...

  25. Re:make it easy! by Barsteward · · Score: 1

    its not superfluous, its more comprehensive than rsyslog, it starts logging earlier than rsyslog can, it logs after rsyslog has stopped. but if you don't want the binary log info, you can discard it. If that alternative was elegant, why wasn't it adopted across all distros?

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)
  26. Re: Their comments on trolls/trolling by Hognoxious · · Score: 1

    Forcing is probably too strong.

    But you'd be surprised how much shit a charismatic person in the wrong place at the wrong time can cause.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  27. Re: Their comments on trolls/trolling by Barsteward · · Score: 1

    Its up to you to define and explain your version of "bloatware", just throwing words around with nothing to back them up is pretty damning for your argument.

    --
    "The hands that help are better far than lips that pray." - Robert Ingersoll (1833-1899)