From an email from Linus Torvalds to GKH
"Greg just for your information, I will *not* be merging any code from Kay [Sievers] into the kernel until this constant pattern is fixed.
This has been going on for *years*, and doesn't seem to be getting any better. This is relevant to you because I have seen you talk about the kdbus patches, and this is a heads-up that you need to keep them separate from other work. Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers.
But I'm not willing to merge something where the maintainer is known to not care about bugs and regressions and then forces people in other projects to fix their project. Because I am *not* willing to take patches from people who don't clean up after their problems, and don't admit that it's their problem to fix."
(Score: 2) by zocalo on Friday April 04 2014, @11:39PM
On the plus side, they've driven so many people to BSD that Netcraft is *still* getting it wrong.
UNIX? They're not even circumcised! Savages!
(Score: 2) by frojack on Saturday April 05 2014, @03:05AM
Not to mention tmp not being tmp anymore, and you aren't safe in cleaning tmp between boots.
Systemd might be needed, because initd has become somewhat unworkable in larger machines, but it goes way too far and messes up way too much of the existing system.
No, you are mistaken. I've always had this sig.
(Score: 2) by neagix on Saturday April 05 2014, @09:07AM
Wait aaaa minute since when this is not allowed anymore? and what do you mean specifically?
(Score: 2) by zocalo on Saturday April 05 2014, @09:49AM
And yes, there's a lot more of the "not our fault!" attitude, and although that write up is by the SystemD team and Udev caused the breakage, there's such a heavy overlap between the members of the two teams it doesn't really make much difference.
UNIX? They're not even circumcised! Savages!
(Score: 2) by neagix on Monday April 07 2014, @06:32AM
Yeah, I heard about this. I was wondering about the possibility to delete /tmp across reboots.
In general, it's like hearing the loud screech of the chains of legacy...not saying that everything should have been left untouched, but that not all the problems have been addressed with the new solutions.
Is this the chance for a new init project (Epoch?) or maturity will be reached afterwards?
Disclaimer: I would have forbidden the author to access any PC just because of PulseAudio already
(Score: 2) by TheRaven on Saturday April 05 2014, @11:38AM
sudo mod me up
(Score: 1) by GeminiDomino on Saturday April 05 2014, @07:02PM
As someone who's been out of the FreeBSD arena for a (long) while:
Do you still have to compile from scratch to do a package/system update?
I used to love FreeBSD, but having a couple of dozen heterogenous hardware servers to keep current, that's a lot of downtime.
"We've been attacked by the intelligent, educated segment of our culture"
(Score: 1) by David_W on Sunday April 06 2014, @01:35AM
Not really, no. Binary system updates can be done with freebsd-update [freebsd.org], and the new pkg (pkgng) [freebsd.org] stuff is more focused around binary packages. I still build my stuff from source, so I can't vouch for how good these tools are at their jobs, but they definitely exist. As always, the Handbook [freebsd.org] has much more info.