The Linux Weather Forecast
kwabbles writes "The Linux Foundation launched the Linux Weather Forecast yesterday. It features 'current conditions' for kernel development, a 'short-term forecast,' and a 'long-term forecast.' Now developers and organizations that want to see when certain implementations/fixes are planned can find answers at this informative and handy site."
Although I cannot predict day to day fluctuations, I can say with a high degree of certainty that in 1000 years, Linux usage among the population will be around 62% with a 73 percentage point uncertainty. My models are never wrong.
See my journal for slashdot ID's by year. Mine created in 2005. http://slashdot.org/journal/289875/slashdot-ids-by-year
Partly cloudy with a slight chance of kernel panics.
What the hell is Karma and why is mine always "Bad"
I was looking forward to reading reports of stormy weather ahead, or even of bright skies. But this seems be be more of a roadmap, not really a forecast. If someone can read this more deeply and see the analogy, then please enlighten me!
Phoenix, Boston, Little Rock, see a pattern?
The Linux forecast for tonight is ... dark.
sigs, as if you care.
Wow. Just wow. This is a fantastic development. This is an excellent complement to FUSE (userspace filesystems), libUSB (userspace USB drivers), X11 (many graphics drivers), sound mixing, and all the other random stuff farmed out to userspace where possible.
Having develpoed in both user and kernel space, I know that userspace development is vastly easier: a crash is now only a segfault, debugging can be done easily and the most suitable language for the task can be used. This makes it faster and easier to develop both robust and efficient code.
But, come on and look at Linux: it's slowly becoming a microkernel: everything that can be in userspace is slowly moving there. And that is a good thing.
SJW n. One who posts facts.
we will see some segmentation faults and a 30% possibility of a new error called kernel disintegration. Also in international news the war on errors seems pretty grim.
Also, the xml feed is has a slight syntax error:
Hope is the currency of fools
The kernel is nothing like a car, with or without a banana in its radiator or anywhere else. I'm sorry, but that just doesn't describe the situation at all.
Imagine, if you will, a perfect state machine with N inputs and G(N) outputs, where each output is a Thorgen-Zeta function of all the inputs bounded by the radial square root of each of its eigenvalues. Clearly, the scope is integrable under N, which is probably what led you to your assumption. But where your car-fruit analogy falls down is in assuming that complete T-Z continuity with respect to time.
So a better analogy would be a car with a fish in its tailpipe, dripping maggots along the highway in the rain. Some of the maggots survive to become features, but some are squashed by schoolbuses full of sweaty cheerleaders.
sigs, as if you care.
Cool.... now we can all shelter whenever there is a SEVERE LINUS WARNING.
Not flaming, if they provide a good resource more power to them.
I can see that now. Yes, I had failed to account for the natural tachyon output of properly seated bananas (and the lower but significant output of properly seated plantains, as well). But we may be drifting slightly off-topic.
The OP is correct: the Linux Weather Forecast is like a car with a banana (properly seated) in the radiator.
sigs, as if you care.
Something that drives me particularly nuts about Linux is the number of regressions that happen. Don't get me wrong - I love Linux. But it feels like, in their haste to get things done better than ever, they sometimes reintroduce old flaws.
:)
Case-in-point: Firewire, and more precisely, multi-LUN support. Sounds esoteric, but it's actually not too uncommon to find hardware that needs it these days. When 2.6 came out, 1394 (as a whole) was just plain broken. They finally got it fixed in 2.6.12 or so, but then, in 2.6.22, they introduced a new Firewire stack - which promptly broke multi-LUN support. Maybe not everyone needs this, but I'm heavily dependent on it. I'm now in a position where I can't do any kernel upgrades until I've confirmed the fix has made it into 2.6.23 final.
I know it's something of a petty gripe, but I'd appreciate it if Linus could do a better job of making sure regressions like that didn't slip back in. I don't need a repeat of the bad weather that we've already had.
Plausible conjecture should not be misrepresented as proof positive.
The seating must be in the Complex domain, and for the output to generate the necessary synchrotron tachyon, the banana must be entangled with the fish in the tailpipe, as postulated by Minsky space.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)