Forgot your password?
typodupeerror
Open Source Linux

Gentoo Developers Fork udev 152

Posted by Unknown Lamer
from the lennart-vows-revenge dept.
In October, Linus Torvalds expressed concerns that udev was making "...changes that were known to be problematic, and are pure and utter stupidity." Several Gentoo developers were also concerned about the removal of features and uncooperative nature of udev maintained by the systemd developers, so they've announced a fork: "After speaking with several other Gentoo developers that share Linus' concerns, I have decided to form a team to fork udev. Our plan is to eliminate the separate /usr requirement from our fork, among other things. We will announce the project later this week." The project name (for now) is udev-ng, and you can grab the code from Github. Update: 11/16 21:29 GMT by U L : One of the developers commented that this isn't yet an official Gentoo project (but hopefully it will be!). There's also an informative flamewar about the fork on debian-devel.
This discussion has been archived. No new comments can be posted.

Gentoo Developers Fork udev

Comments Filter:
  • Yea! (Score:4, Interesting)

    by Anonymous Coward on Friday November 16, 2012 @05:36PM (#42006257)

    Well, at least there's one distro that's tired of letting Red Hat developers dictate the course of linux component development and marginalize the whole independent distro model. Hello Debian? Ubuntu? SuSE? Are you guys beginning to see a pattern here?

  • by Anonymous Coward on Friday November 16, 2012 @06:00PM (#42006603)

    Those idiots are still giving us all grief. Can't we just kick these guys and they're half-assed project to the curb? Systemd was a good idea, but shit implementation and zero admin love. Hell, they are actively admin hostile! Now they plan to Fuck up udev? great.

    They didn't just plan it, they DID it.

    Linus was on a roll. Read the whole thread [lkml.org]:

    Stop this crazy. FIX UDEV ALREADY, DAMMIT.

    Who maintains udev these days? Is it Lennart/Kai, as part of systemd?

    Lennart/Kai, fix the udev regression already. Lennart was the one who
    brought up kernel ABI regressions at some conference, and if you now
    you have the *gall* to break udev in an incompatible manner that
    requires basically impossible kernel changes for the kernel to "fix"
    the udev interface, I don't know what to say.

    "Two-faced lying weasel" would be the most polite thing I could say.
    But it almost certainly will involve a lot of cursing.

    ...

    The fact is, udev made new - and insane - rules that are simply
    *invalid*. Modern udev is broken, and needs to be fixed.

    Stop this idiocy.

    The kernel doesn't have a lockup problem. udev does.

    Yeah, that bugzilla shows the problem with Kay as a maintainer too,
    not willing to own up to problems he caused.

    and

    So now, after you've dismissed the patch that did the equivalent fix
    in udev (Ming Lei's patch basically disabled your idiotic and wrong
    sequence number test for firmware loading), you say it's ok to bypass
    udev entirely, because that is "more robust".

    Kay, you are so full of sh*t that it's not funny. You're refusing to
    acknowledge your bugs, you refuse to fix them even when a patch is
    sent to you, and then you make excuses for the fact that we have to
    work around *your* bugs, and say that we should have done so from the
    very beginning.

    Is Kay Sievers really that dumb?

  • Re:Append NG (Score:5, Interesting)

    by Paradigm_Complex (968558) on Friday November 16, 2012 @06:17PM (#42006811)
    In this projects IRC channel, someone proposed appending a -pg to it, since the point of this fork is to revert udev to what it was before it went insane. I find this prospect quite amusing and hope it picks up.
  • by knorthern knight (513660) on Friday November 16, 2012 @06:42PM (#42007137)

    A full-of-themselves group of developers pissed off enough people to get a viable fork going. Hopefully systemd-udev gets kicked to the curb by udev-ng.

    BTW, Poettering and Sievers are the same characters who wanted a binary syslog with an undocumented format http://linux.slashdot.org/story/11/11/23/1733236/secure-syslog-replacement-proposed [slashdot.org] The Slashdot summary noted "This is being done as an extension to systemd". Sound familiar? Give them enough time, and those guys will end up rolling the linux kernel into the systemd tarball.

  • by Chirs (87576) on Friday November 16, 2012 @07:37PM (#42007851)

    Is Kay Sievers really that dumb?

    Yes and no.

    What the udev guys are suggesting is that in the "module init" stage (where modules are loaded into the kernel) the module should not block waiting for firmware (because there may not be a filesystem yet, especially if the module is actually compiled into the kernel rather than loaded later). Rather the firmware should be loaded at "device open" time.

    This is actually a reasonable position to take.

    Unfortunately it breaks a number of (arguably misbehaving) modules, and among most linux kernel developers it is a BIG DEAL to break existing code.

  • by Anonymous Coward on Friday November 16, 2012 @07:53PM (#42008041)

    There's plenty of us here watching from afar with large grins on our face.

    Hello from FreeBSD, NetBSD, DragonflyBSD, and OpenBSD.

  • This is why... (Score:5, Interesting)

    by A bsd fool (2667567) on Friday November 16, 2012 @08:41PM (#42008479)

    ...I'm a (Free)BSD fanboy/fool. There is occasional stupidity (witness the recent replacement of sysinstall with some half-assed, half-baked, incomplete alternative), but usually the core team is sane, and the flamewars don't have two people both arguing from flawed foundations. The obviously *right* thing to do with this whole mess is simple: toss it.

    Create a standard place for firmware files, allow it to be configured and overridden easily, make judicious use of symlinks/union mounts. Then, let the drivers do the right thing: Load up, determine if a firmware needs to be squirted in, load it if so, and continue. This idea of some entire subsystem tied to a userland daemon being responsible for loading device firmware is plain absurd. Drivers know how to load their own firmware, and with an extremely simple knob (rc.conf, linux equiv to loader.conf, sysctl, whatever) they will know where to look for it as well.

    Somebody, somewhere, smoked some serious shit to come up with this udev/systemd fiasco to begin with.

  • Re:Append NG (Score:4, Interesting)

    by Anonymous Coward on Friday November 16, 2012 @10:33PM (#42009307)

    I'm surprised nobody has suggested the -og suffix.

  • by KiloByte (825081) on Friday November 16, 2012 @10:34PM (#42009309)

    Don't forget Avahi -- a network-facing daemon included in the default GUI install that has a remote security hole at least once a year. And what it's for? So you can have a link-local chat (compatible only with itself) and some autodetection of rare Apple's printers.

Those who do things in a noble spirit of self-sacrifice are to be avoided at all costs. -- N. Alexander.

Working...