I can't touch type yet everyone using a Linux kernel uses code I typed. I can't write the way it was required to in schools a hudred years ago yet I can write a letter manually and it's readable. Forcing everyone to learn touch typing is wrong, just learn people how to type and let them optionally improve their skills.
Who cares how you tie your shoelaces if you don't fall flat on your face every three steps?
Yet we are sending thousands to their deaths in Iraq, and other places in the world the USA is colonizing. Apparently it's OK to send people to their deaths if it's for a war.
you're wrong. the 'performance' governor can easily run on top of a 'tickless' kernel and perform just as good as a non-tickless kernel.
There is no need to disable tickless *ever*
As a matter of fact, the tickless kernel actually uses less CPU to schedule processes in since it doesn't need to interrupt your 100% cpu load program 1000x per second (just for the tick!), and so, the tickless kernel beats your non-tickless kernel.
Hell, you can even run tickless WITHOUT any governor at all, and have it run at full speed (the default) at all times. Maximum performance with the least system overhead! Tickless wins again! yay!
nonsense, tickless kernels are used nowadays in EVERY environment, including servers. It not only saves power, but also CPU cycles, which means that CPU intensive tasks actually get more time on the processor if they need.
Would you not expect the manufacturer of -say- your refrigerator (especially the largest manufacturer in the world of refrigerators) to make sure each and ever component in said fridges is optimum?
If there was -nothing- wrong with the linux kernel as is, yes, by all means canonical can sit and sell ubuntu. But the problem is that there is much wrong in the kernel and much more to be fixed. And the kernel needs -the biggest vendor- of desktop linux to help out by telling the kernel developers what is wrong, and not just point at it, but actually reach out and make the communication work both ways.
You're arguing that the manufacturer of -say- engine parts shouldn't worry about how the users like their car's driving experience... that's not right. This isn't some closed and proprietary component. It works because almost everyone in the chain gets involved.
That's not the point. By dismissing a major component of what makes your product 'tick' as 'insignificant', you're effectively pissing off everyone who works on it. Canonical will fire most of their desktop developers too if they think that desktop development is no longer needed.
You can only tidy up an installer so much. Even Microsoft knows that you have to also improve the kernel, and so, they are now ahead of Canonical when it comes to significant additions to the linux kernel.
That is sad by all standards, and the label 'shamefull' in totally appropriate IMHO.
surprised? well, they haven't exactly sent any patches... gee, I wonder if they are really genuinely interested in making linux better, or just run away with it and try to make money out of it.
given that the kernel is one of the largest parts, with probably the most dramatic changes going on, you'd think that it would be wise for anyone so dependent on it to contribute directly.
Canonical is not only not caring, they are also passing on a strategical opportunity to help out where it matters a lot.
the list is made yearly, I doubt SCO had time this year to write something. The top list comprises only kernels 2.6.24 and above. Microsoft's code has not been accepted yet and so also not counts.
Please, this is a _local_ privilege escalation. It's not like code red infecting your box remotely. A sledgehammer is also a local privilege escalation.
Those are non-reinforced structures, IOW Gravity is the main force on the rock. Extension forces are much harder for rocks, and require reinforcement. As one of the posters below points out, having strength alter (in any way) can severely increase the risk of failure for reinforced structures.
Just because Bath didn't fall over, doesn't mean it isn't safe for everyone.
If a material absorbs so much CO2 over it's lifespan, it significantly alters the chemical composition and therefore strength.
I doubt any builder will use this material unless it's been proven that the new material is sufficiently stable.
Example: as a geology student, I ran into an area in central spain with lots of Gypsum sediments (Ca|MG.SO4). Putting limestone and concrete buildings on this sediment wasn't done until the 20th century, but all the buildings built in that area are long gone, even though in nearby towns they still stand tall. Reason? The Gypsym in the soil chemically eats the mortar and limestone (CaCO3) out of the structure on top of it, making it crumble within a few decades. The Gypsum areas are largely a wasteland where only very few buildings remain.
Now, Mg.Ca-CO3 (dolomite limestone) is largely as stable or more stable than pure limestone, and certainly harder, but any new formula for the glue in concrete will have to pass the test of time before it will be widely adopted, especially in e.g. bridges and skyscrapers...
Perhaps we can start with the interstates, nobody would notice if they started to crumble early;)
Slashdot Mirror
This is a terrorist action, our government is being subverted by evil voices to create more high-grade plutonium! Flee! Flee!
Dropping support for Windows and Mac will significantly lower the overall cost of attending college, however.
Those questions, however, would have not been worthy of asking on Slashdot.
and within 5 years I had recognized that the single most important course I took was a half-semester of typing
seriously, your school must have sucked.
exactly
I can't touch type yet everyone using a Linux kernel uses code I typed. I can't write the way it was required to in schools a hudred years ago yet I can write a letter manually and it's readable. Forcing everyone to learn touch typing is wrong, just learn people how to type and let them optionally improve their skills.
Who cares how you tie your shoelaces if you don't fall flat on your face every three steps?
We can't even let terminal patients die
Yet we are sending thousands to their deaths in Iraq, and other places in the world the USA is colonizing. Apparently it's OK to send people to their deaths if it's for a war.
so, let's declare war on Mars!
give us more efficient hardware documentation, so we can do just that...
I'll be a sport and tell you when it's a bad idea to use tickless:
- when your hardware doesn't support tickless (e.g. PPC Macs?), or
- when your hardware clocks are not precise enough (e.g. HPET broken)
in both these cases, you're most likely to get better performance from upgrading your hardware, not from disabling tickless.
you're wrong. the 'performance' governor can easily run on top of a 'tickless' kernel and perform just as good as a non-tickless kernel.
There is no need to disable tickless *ever*
As a matter of fact, the tickless kernel actually uses less CPU to schedule processes in since it doesn't need to interrupt your 100% cpu load program 1000x per second (just for the tick!), and so, the tickless kernel beats your non-tickless kernel.
Hell, you can even run tickless WITHOUT any governor at all, and have it run at full speed (the default) at all times. Maximum performance with the least system overhead! Tickless wins again! yay!
nonsense, tickless kernels are used nowadays in EVERY environment, including servers. It not only saves power, but also CPU cycles, which means that CPU intensive tasks actually get more time on the processor if they need.
tickless should be enabled for EVERY x86 machine.
Would you not expect the manufacturer of -say- your refrigerator (especially the largest manufacturer in the world of refrigerators) to make sure each and ever component in said fridges is optimum?
If there was -nothing- wrong with the linux kernel as is, yes, by all means canonical can sit and sell ubuntu. But the problem is that there is much wrong in the kernel and much more to be fixed. And the kernel needs -the biggest vendor- of desktop linux to help out by telling the kernel developers what is wrong, and not just point at it, but actually reach out and make the communication work both ways.
You're arguing that the manufacturer of -say- engine parts shouldn't worry about how the users like their car's driving experience... that's not right. This isn't some closed and proprietary component. It works because almost everyone in the chain gets involved.
because they're the biggest desktop linux provider.
That's not the point. By dismissing a major component of what makes your product 'tick' as 'insignificant', you're effectively pissing off everyone who works on it. Canonical will fire most of their desktop developers too if they think that desktop development is no longer needed.
You can only tidy up an installer so much. Even Microsoft knows that you have to also improve the kernel, and so, they are now ahead of Canonical when it comes to significant additions to the linux kernel.
That is sad by all standards, and the label 'shamefull' in totally appropriate IMHO.
surprised? well, they haven't exactly sent any patches ... gee, I wonder if they are really genuinely interested in making linux better, or just run away with it and try to make money out of it.
given that the kernel is one of the largest parts, with probably the most dramatic changes going on, you'd think that it would be wise for anyone so dependent on it to contribute directly.
Canonical is not only not caring, they are also passing on a strategical opportunity to help out where it matters a lot.
the list is made yearly, I doubt SCO had time this year to write something. The top list comprises only kernels 2.6.24 and above. Microsoft's code has not been accepted yet and so also not counts.
canonical doesn't contribute back at all - only debian does, and even debian is not a big kernel contributor
seriously, you didn't run away screaming from that credit union?
stop labelling security vulnerabilities as denial of service attacks!
most (if not any) remote attackers don't even bother to become root, they happily run their zombie / bots as an unprivileged user.
sudo
Please, this is a _local_ privilege escalation. It's not like code red infecting your box remotely. A sledgehammer is also a local privilege escalation.
Those are non-reinforced structures, IOW Gravity is the main force on the rock. Extension forces are much harder for rocks, and require reinforcement. As one of the posters below points out, having strength alter (in any way) can severely increase the risk of failure for reinforced structures.
Just because Bath didn't fall over, doesn't mean it isn't safe for everyone.
Ca|Mg.SO4 is another way to write Gypsum. It is not nearly as strange as some area names in Spain :)
This sounds like a concrete nightmare:
If a material absorbs so much CO2 over it's lifespan, it significantly alters the chemical composition and therefore strength.
I doubt any builder will use this material unless it's been proven that the new material is sufficiently stable.
Example: as a geology student, I ran into an area in central spain with lots of Gypsum sediments (Ca|MG.SO4). Putting limestone and concrete buildings on this sediment wasn't done until the 20th century, but all the buildings built in that area are long gone, even though in nearby towns they still stand tall. Reason? The Gypsym in the soil chemically eats the mortar and limestone (CaCO3) out of the structure on top of it, making it crumble within a few decades. The Gypsum areas are largely a wasteland where only very few buildings remain.
Now, Mg.Ca-CO3 (dolomite limestone) is largely as stable or more stable than pure limestone, and certainly harder, but any new formula for the glue in concrete will have to pass the test of time before it will be widely adopted, especially in e.g. bridges and skyscrapers...
Perhaps we can start with the interstates, nobody would notice if they started to crumble early ;)
Unless nVidia will license that same technology to ATI, it sounds like it freezes ATI out of the multi-GPU-on-Intel-chipsets market.
s/ATI/AMD/g
why would AMD promote SLI when they can sell crossover? It seems they would cannibalize their own GPU market by supporting SLI on their chipsets.