These benchmarks were performed on relatively old hardware, with a slow cpu and a disk only running UDMA2. And, as others have already pointed out, the data are statistically not really reliable.
Myself, I'd be much more interested in seeing numbers made on a setup more like my own.
Static benchmarks are never good for deciding "which is best".
Being Norwegian, I know we are not a member of the EU. Irrelevant, all the time Norway has signed a treaty (called EØS in Norway) , that basically forces us to follow EU directives anyway.
Only Denmark and one other EU country has. So, under current interpretation, DeCSS is legal in Norway, as long as it is used for legal purposes. Using it for piracy is not.
Seriously, the more people running the latest kernel, the better - how long would it have taken for this bug to be found if there weren't thousands of people testing it as soon as 2.4.15 was released?
As for production use, most people are smart enough to not run the most recent kernel releases on critical systems.
Slashdot Mirror
These benchmarks were performed on relatively old hardware, with a slow cpu and a disk only running UDMA2. And, as others have already pointed out, the data are statistically not really reliable.
Myself, I'd be much more interested in seeing numbers made on a setup more like my own.
Static benchmarks are never good for deciding "which is best".
This is not my experience with this phone. Then again, I live in Oslo, with very good signal conditions.
Being Norwegian, I know we are not a member of the EU. Irrelevant, all the time Norway has signed a treaty (called EØS in Norway) , that basically forces us to follow EU directives anyway.
No, but, having made a treaty of economic cooperation with the EU, Norway is obligated to implement most EU laws, including EUCD.
Only Denmark and one other EU country has. So, under current interpretation, DeCSS is legal in Norway, as long as it is used for legal purposes. Using it for piracy is not.
Apart from the fact that it's *fun*, you mean?
Seriously, the more people running the latest kernel, the better - how long would it have taken for this bug to be found if there weren't thousands of people testing it as soon as 2.4.15 was released?
As for production use, most people are smart enough to not run the most recent kernel releases on critical systems.
Thought about it, but then I realized that I would have to go *back* to 2.4.16 to keep on the stable side. So I'll just stick with 2.4.15 for now ;)