"A ton of commits were made involving kmod and it is quite clear that it is broken, so we remove it."
The commit above will add 100-150 entirely useless fork()/exec() to every bootup, and not have any other benefit. The same code, with the same dependencies will run, just with a forked binary. But hey, today's systems need only 150 PIDs to bring up the entire system, so who cares. :)
Suggestion: if you want a project to believe in, we all need that sometimes, look for something else, this boat will sink faster than it will learn to swim.
Actually I have nothing against a udev fork, if it looks useful to people go for it. I would even answer sensible questions, or whatever is needed. But that thing really just looks like a bad joke.
Cute, gentoo wants to make a second, different fork of udev because the first gentoo fork is apparently too hostile to other gentoo developers.
Gentoo-devel and debian-devel, the gifts that keep on giving on rainy saturdays.
As +Koen Kooi so aptly states, this is the perfect gift for a weekend's worth of entertainment.
It's sad to watch people delete code they don't understand.
Are you joking? Over the last year systemd has had commits from 118 contributors and from 27 in the last month. It's also developed by various companies like Intel, Ericpol Telecom(?) and ProFusion. Not to mention that two Arch Linux developers have done quite a bit of upstream systemd developement too. Oh and yes, there's quite a bit of a difference between fulltime developers and hobbyist.Quote:
Originally Posted by ryan
I had no idea this forum is filled with system admins who fiddle with init scrips all the time.
With that said, Volunteer developers are more than capable of competing with professional developers when there is an order of magnitude difference in code. The sheer amount of bloat in systemd is staggering and we are removing it from udev.
I hope this won't affect Gentoo's plans for systemd support? Right now it's not as easy as simply emerging it and having it just work.