Andres also patches things that are plain broken, e.g. "sound doesn't work any more". By the law Linus established above, those kind of patches are forbidden to go into 2.6.x.N.
by that hyperbola Dell Inspiron broken keyboard fix shouldn't have gone in, but it is in 2.6.11.1, and is fully covered with holy penguin pee.
Please, go fuck yourself senseless with you 'quality' windows drivers.
I've nothing but endless stream of problems with microsoft/windows drivers. Since switching totally to Linux (circa 1999), there've been no problems _that couldn't be solved_. Yeah, that involves contacting various developers and describing you problems with detail. But that's just something that isn't possible with windows.
If you only use things that have been tested first, but like recent software -- use testing.
No no no. testing doesn't get security updates whatsoever. If for whatever reason sec-update package is bugged, it will not propagate to testing. This will make the 2 week delay even longer, possibly putting sec update off for a very long time. It's stable or unstable, testing is just to have new stable in a few years.
Even then it's not exactly ATX, as upper-right corner of the board has some stuff that really shouldn't be there. So that part of ATX box is unusable (usually lowest of 5½" places and sometimes upper 3½" slot).
So yes, it fits ATX box, but no, it doesn't conform to it 100%. I do know that most people won't put it into smallest available case, but I put it into miditower, which is way bigger than my previous baby-AT case.
Well, for instance if somebody at indymedia would be suspected of active pedophilia, it really wouldn't be nice for anybody if they shouted aloud: 'Yeah, we caught this pedophile in indymedia'.
Especially if this (hypothetical) suspicion turned groundless.
Actually it's not one penny that is flipping, you have 'several pennies' as there are several teams, many sports (Why not basketball, squash or golf?). In that environment, one of thousands of pennies flipping 1 a bit too long wouldn't be that unexpectable.
Hmm. Well, if we consider that (imaginary) production yeld for a single layer is y=0.9, then for double layer it will be y^2*combination_yeld (again, imaginary 0.9). That alone would make it at 0.73.
I know jack about this, but I'd imagine they check at most optically disk surfaces before packaging them up. Not that they can record some test on them (apart from sampling the batch).
I think it would've made sense if scourging of shire were filmed and shown (rather lenghty anti-climax). As it is, it's claimed to have too long and slow ending (haven't seen it yet, waiting for extended).
Isn't this thing with DB's getting a little excessive? You're adding another layer and step to storing data which will in all likely hinder performance. I'm not sure the benefit out weight the cost.
Well, if it's only a name-translation thingy, then it shouldn't affect performance of file reading (when operating on sufficiently big files), only file opening/stat:ing.
I think you are missing the point. Not every user cares what is in their kernel, much the same was as Windows users don't. They just want stuff to work.
And you're missing the 'provider' point. If Linux kernel maintainer isn't willing to provide binary module hooks into kernel, then it's his right to refuse having them.
This module could walk around this rule by having same system as nVidia kernel driver, but no, they come to slashdot, bitch and moan.
For all of you who wonder what we mean when we say "zealots make it hard for businesses to take F/OSS seriously", this is what we mean.
Nope. This is eating own dogfood, having a stance and keeping it. Businesses can be sure that there's no fucking around rules of linux development. It's either playing by the rules or not playing at all.
well, for starters, there should be minimal amount of OS specific code in the game from the get go.
considering that they (iD) have released plenty of (multiplatform) this style games before, one could easily assume that they already have the OS specific code hammered out.
No, it's called dealing-with-sympotomes-instead-of-real-cause. Instead of curbing personal violence right in it's roots, they will have to deal later with that driver shooting people.
samizdat means 'selfpublishing', having nothing to do with communism. It was 'invented' in a communist country, but it's as well employed everywhere where an author can't get published.
Slashdot Mirror
Andres also patches things that are plain broken, e.g. "sound doesn't work any more". By the law Linus established above, those kind of patches are forbidden to go into 2.6.x.N.
by that hyperbola Dell Inspiron broken keyboard fix shouldn't have gone in, but it is in 2.6.11.1, and is fully covered with holy penguin pee.
Please, go fuck yourself senseless with you 'quality' windows drivers.
I've nothing but endless stream of problems with microsoft/windows drivers. Since switching totally to Linux (circa 1999), there've been no problems _that couldn't be solved_. Yeah, that involves contacting various developers and describing you problems with detail. But that's just something that isn't possible with windows.
Uh, and the risk would be what? That Mars would become uninhabitable?
Well, it could be something that isn't good for us AND isn't easily reversible. So Mars could be 'lost' for humanitys forcoming science.
This is good news for all of us waiting for decent free calendaring software.
You know, there's KOrganizer and loads of other that are free and actually useable..
If you only use things that have been tested first, but like recent software -- use testing.
No no no. testing doesn't get security updates whatsoever. If for whatever reason sec-update package is bugged, it will not propagate to testing. This will make the 2 week delay even longer, possibly putting sec update off for a very long time. It's stable or unstable, testing is just to have new stable in a few years.
Now think what'll happen when they put some of these babies into that beowulfish cluster.. (other than complication of computation).
Even then it's not exactly ATX, as upper-right corner of the board has some stuff that really shouldn't be there. So that part of ATX box is unusable (usually lowest of 5½" places and sometimes upper 3½" slot).
So yes, it fits ATX box, but no, it doesn't conform to it 100%. I do know that most people won't put it into smallest available case, but I put it into miditower, which is way bigger than my previous baby-AT case.
Fool. Ubuntu isn't a fork, it's a specialization.
A spiffy spysat would encrypt the images (triple 2048-bit ElGamal?) then beam them down to ground stations.
... and then magically disappearated in puff of sparkly smoke 5sec later.
Well, for instance if somebody at indymedia would be suspected of active pedophilia, it really wouldn't be nice for anybody if they shouted aloud: 'Yeah, we caught this pedophile in indymedia'.
Especially if this (hypothetical) suspicion turned groundless.
Actually it's not one penny that is flipping, you have 'several pennies' as there are several teams, many sports (Why not basketball, squash or golf?). In that environment, one of thousands of pennies flipping 1 a bit too long wouldn't be that unexpectable.
Hmm. Well, if we consider that (imaginary) production yeld for a single layer is y=0.9, then for double layer it will be y^2*combination_yeld (again, imaginary 0.9). That alone would make it at 0.73.
I know jack about this, but I'd imagine they check at most optically disk surfaces before packaging them up. Not that they can record some test on them (apart from sampling the batch).
I think it would've made sense if scourging of shire were filmed and shown (rather lenghty anti-climax). As it is, it's claimed to have too long and slow ending (haven't seen it yet, waiting for extended).
I doubt it's UP, most probably 2xSMP, so 312 nodes and about $1M. Which sounds reasonable for 12 years worth of computing in two weeks.
I think most serial codes have checksum, to validate data entry (as they tend to be quite badly human-repeatable), so that wouldn't be a problem.
Come on, the man who've kept packaging steaming pile of XFree86 for 11 debian architectures. While upstream supported only i386.
(Yup, I do know that he is sharp with his tongue)
Isn't this thing with DB's getting a little excessive? You're adding another layer and step to storing data which will in all likely hinder performance. I'm not sure the benefit out weight the cost.
Well, if it's only a name-translation thingy, then it shouldn't affect performance of file reading (when operating on sufficiently big files), only file opening/stat:ing.
The form submission is encrypted so no worries.
And what happens if someone injects something when you're loading the form itself?
I think you are missing the point. Not every user cares what is in their kernel, much the same was as Windows users don't. They just want stuff to work.
And you're missing the 'provider' point. If Linux kernel maintainer isn't willing to provide binary module hooks into kernel, then it's his right to refuse having them.
This module could walk around this rule by having same system as nVidia kernel driver, but no, they come to slashdot, bitch and moan.
For all of you who wonder what we mean when we say "zealots make it hard for businesses to take F/OSS seriously", this is what we mean.
Nope. This is eating own dogfood, having a stance and keeping it. Businesses can be sure that there's no fucking around rules of linux development. It's either playing by the rules or not playing at all.
I'd remind that any technical device sent there by man has very short estimation of uptime there..
well, for starters, there should be minimal amount of OS specific code in the game from the get go.
considering that they (iD) have released plenty of (multiplatform) this style games before, one could easily assume that they already have the OS specific code hammered out.
It's called prioritizing.
No, it's called dealing-with-sympotomes-instead-of-real-cause. Instead of curbing personal violence right in it's roots, they will have to deal later with that driver shooting people.
get lost, ignoramus.
samizdat means 'selfpublishing', having nothing to do with communism. It was 'invented' in a communist country, but it's as well employed everywhere where an author can't get published.
feh. ia64 assembly isn't necessarily hard. The hard thing is to keep all the pipelines full so that it's general slowness don't kill performance.
EPIC stands for explicitly parallel, not mind-numbingly-hard assembly.