You'd probably have more luck starting a campaign to get S3 to do it. Nvidia and ATI are pretty comfortable with their respective very large market shares and their managers probably won't open up things for worry about their competitors seeing what they are doing (wheather those fears are justified or not).
S3, having such a small market share, might be much more eager to capture a niche market (non-windows) and not be as worried about the 'big boys' stealing their IP.
Off topic: I've linked to the Encyclopedia Britannica above because the article about Planck's constant is very short. The article in Wikipedia is long. I've frequently seen the Encyclopedia Britannica be misleading because of the severe limitation placed on size of the articles due to paper costs. Wikipedia does not have that problem.
I've frequently seen Wikipedia be misleading because some 10 year old has seen fit to erase stuff written by Ph.D.'s, and replace it with his own misunderstanding ramblings on the subject matter. Britannica does not have that problem.
Radiation has been shown to act in a cumulative manner. So exposing someone to 100 units in a second is the same as exposing them to 1 unit over 100 seconds.
Um, no. Cells have a DNA repair proteins which can often fix damaged strands of DNA. When cells are exposed to a large dose of radiation, those repair mechanisms can be overwhelmed, and the errors won't be corrected. In this case, the cells can suffer much more damage than would occur if the exposure were spread out over more time.
For one thing, pf is a lot easier on the eyes than iptables. Look through some iptables config files you find on the net. Then go look at some pf.conf files. I think you'll see it's much easier to look at the pf files and instantly see what's going on.
For another, please point me to the linux equivalent of CARP ( an incredibly easy to set up redundant firewall ). If you are in charge of running a firewall for a company, redundant hardware at the firewall is nice.
I think I'll stick with what the designers called it. A Microkernal. I think they'd know better than anyone else. If you'd care to site a real reference rather than one a 10-year old can change at a whim, I might check it out.
If they are bothering to go to your external website rather than just looking on Monster.com, etc, then they almost certainly did a Google search for your name... your website is right there in the google cache.
I Hit submit too soon on the least one... If you want any decent range to do a real race, you are going to need a lot of batteries. Batteries mean weight. Weight means worse handling. The handling if that thing will get worse than an Atom's real quick if you add more weight to it than an Atom normally has.
For how long? What's the range? How many loops can you get around a road course before the batteries are drained and you need a recharge? If it's just a few, I'll take the Elise, thanks.
The handling will be like the Atom as long as they don't use many battery packs (which means it will burn through them quick and have very limited range). Batteries are heavy, and weight is anathema to what the Ariel Atom stands for.
It's not just not as revolutionary as the article writer things. It's not revolutionary AT ALL. Electric motors generate peak torque at 0 RPM. Yes, they can accellerate like mad, but they use a ton of juice to do it. Then they are spent. Anyone could do this at any time. It's not news.
So it can do a quarter mile fast. Ask anyone who does open wheel racing (formula 1, etc), and they will tell you, "drag racing is for pussies". Anyone can slam down their foot and go a short distance in a straight line. No skill is involved. Only a question of money you want to spend to shave off time.
OpenBSD fixes 'security holes' all the time, without even knowing it. If code looks 'dirty' (hard to read), they will often rewrite it so that it's easier to audit for bugs in the future. Most of the time when they fix a 'hole', they never actually spotted the hole. They were just cleaning up messy looking code. A few years later (like in this case) it will often turn out that there was a security hole hidden in the mess.
FYI, they do often send the cleaned version back to the codes maintainers, but they can't force them to use the re-arranged code, or port it to other systems. Sorry.
Lots of companies use OpenSSH but don't distribute it. Lots of companies redistribute the vanilla version, with no changes made. In either of those cases, there's no 'giving something back'. And they aren't going to toss money at it just because it's GPL.
Making it GPL would do nothing for the funding, it mearly would add more restrictions to the license, which the OpenBSD folks are totally against.
I don't see how the experts will be made to look like fools. Idiots have been buying into Bigfoot, etc, for a long long time. The experts always come out against it. Who looks like fools? The idiots who believe in it.
If the guy wants to reshape a hill and take money from suckers, well, as the old saying goes, "There's a Sucker Born Every Minute". The fools are the ones who give him money to reshape the hill, or tour his 'pyramid', not the experts.
They *claim* they found cut and polished stone blocks.
Someone who thinks it would be possible to build a pyramid in the timeframe that he claims could very very easily mistake broken rock for rock that had been cut by humans.
Sorry, until I hear about a few legitimate archeologists claiming this has some merit, it's just a load of crap.
What the hell kind of crappy MBA program did you go to? Intel did *NOT* handle it well. I had one of those CPUs. Intel tried to tell me (a scientific researcher) that my computations didn't need that level of FPU accuracy, and that they wouldn't replace it. It was only after we, the users, screamed bloody murder and brought lawsuits that they decided to back down and replace them all.
The PR nightmare was *caused* specifically by the way Intel handled the discovery. They thought that they had the right to decide which users did or didn't 'need' accurate FPU computations.
I have been an 'AMD fanboy' from that day forward, specifically because of Intel's totally botched handling of an engineering glitch.
No. Not true, even in English. For example, "c" does not make a sound distinctly different from all other characters.
Yes it does, but only when followed by an h. The "ch" sound is distinctly different from sounds produced by any other letters. If it weren't for "ch", yes, 'c' would be a rudendent letter.
Slashdot Mirror
In addition to real security, documentation of it would likely eventually lead to drivers that worked for the other OS's. ;)
It's a blob.
S3, having such a small market share, might be much more eager to capture a niche market (non-windows) and not be as worried about the 'big boys' stealing their IP.
Um. No. *You* may want patent laws revoked, but some of us like them. We don't 'need' to try to get them revoked.
I can see as many bad uses coming from these as good.
I've frequently seen Wikipedia be misleading because some 10 year old has seen fit to erase stuff written by Ph.D.'s, and replace it with his own misunderstanding ramblings on the subject matter. Britannica does not have that problem.
Um, no. Cells have a DNA repair proteins which can often fix damaged strands of DNA. When cells are exposed to a large dose of radiation, those repair mechanisms can be overwhelmed, and the errors won't be corrected. In this case, the cells can suffer much more damage than would occur if the exposure were spread out over more time.
Air conditioning would be used throughout the building. The tumors were in only those on the top floor. Radon is an unlikely cause in this case.
For another, please point me to the linux equivalent of CARP ( an incredibly easy to set up redundant firewall ). If you are in charge of running a firewall for a company, redundant hardware at the firewall is nice.
Making one that exploits a hole in a common video player would be no more difficult.
I think I'll stick with what the designers called it. A Microkernal. I think they'd know better than anyone else. If you'd care to site a real reference rather than one a 10-year old can change at a whim, I might check it out.
And that's a good thing?
A quote from Theo de Raadt:
PAM is completely and utterly broken and cannot be fixed.
BeOS didn't seem slow to me. No matter what I threw at it.
If they are bothering to go to your external website rather than just looking on Monster.com, etc, then they almost certainly did a Google search for your name... your website is right there in the google cache.
I Hit submit too soon on the least one... If you want any decent range to do a real race, you are going to need a lot of batteries. Batteries mean weight. Weight means worse handling. The handling if that thing will get worse than an Atom's real quick if you add more weight to it than an Atom normally has.
For how long? What's the range? How many loops can you get around a road course before the batteries are drained and you need a recharge? If it's just a few, I'll take the Elise, thanks.
The handling will be like the Atom as long as they don't use many battery packs (which means it will burn through them quick and have very limited range). Batteries are heavy, and weight is anathema to what the Ariel Atom stands for.
It's not just not as revolutionary as the article writer things. It's not revolutionary AT ALL.
Electric motors generate peak torque at 0 RPM. Yes, they can accellerate like mad, but they use a ton of juice to do it. Then they are spent. Anyone could do this at any time. It's not news.
So it can do a quarter mile fast. Ask anyone who does open wheel racing (formula 1, etc), and they will tell you, "drag racing is for pussies". Anyone can slam down their foot and go a short distance in a straight line. No skill is involved. Only a question of money you want to spend to shave off time.
OpenBSD fixes 'security holes' all the time, without even knowing it. If code looks 'dirty' (hard to read), they will often rewrite it so that it's easier to audit for bugs in the future. Most of the time when they fix a 'hole', they never actually spotted the hole. They were just cleaning up messy looking code. A few years later (like in this case) it will often turn out that there was a security hole hidden in the mess.
FYI, they do often send the cleaned version back to the codes maintainers, but they can't force them to use the re-arranged code, or port it to other systems. Sorry.
Making it GPL would do nothing for the funding, it mearly would add more restrictions to the license, which the OpenBSD folks are totally against.
If the guy wants to reshape a hill and take money from suckers, well, as the old saying goes, "There's a Sucker Born Every Minute". The fools are the ones who give him money to reshape the hill, or tour his 'pyramid', not the experts.
They *claim* they found cut and polished stone blocks.
Someone who thinks it would be possible to build a pyramid in the timeframe that he claims could very very easily mistake broken rock for rock that had been cut by humans.
Sorry, until I hear about a few legitimate archeologists claiming this has some merit, it's just a load of crap.
Why are you wasting time in IE doing MS updates? That's what WSUS is for.
Most of my OpenBSD boxes are IP-less firewalls, so usually I don't really worry about patching them until the next release comes out.
The PR nightmare was *caused* specifically by the way Intel handled the discovery. They thought that they had the right to decide which users did or didn't 'need' accurate FPU computations.
I have been an 'AMD fanboy' from that day forward, specifically because of Intel's totally botched handling of an engineering glitch.
Yes it does, but only when followed by an h. The "ch" sound is distinctly different from sounds produced by any other letters. If it weren't for "ch", yes, 'c' would be a rudendent letter.