Oil slicks have been implicated in algae die-offs. QED
Remember that you need to not only show evidence that oil slicks kill algae but that oil slicks kill so much algae, globally, that global populations of algae are decreasing "rapidly". References would be helpful.
Quod erat demonstrandum means you have proved the point you originally set out to prove. It is not Latin for "I win."
Oceanic algae produces something like 85% of the world's oxygen and is dying off rapidly due to pollution and climate change.
we're not talking about CO2... We're talking about things like oil slicks
It's one thing to say that oil slicks can kill algae (no disagreement there). It's quite another to say that a reason for global algae die-off is man-made pollution. Many (dare I say most?) types of pollution cause algal bloom.
The right strain of algae. Not just any strain, the right strain.
You need the right strain to make it grow quickly and give decent biodiesel yields. But just about any algae will grow in a high-CO2, high water, high sunlight environment.
Carbon fiber is extremely strong, but it is also stiff and brittle (and expensive). Fiberglass is also strong, but very, very flexible - Voyager's wingtips could have bent until they touched each other before breaking. Of course, in a crash, you want the structure ahead of you to break or crumple in a controlled manner (to increase the amount of time you decelerate) and not rebound.
If you live in the US, consider writing your state Attorneys General instead of the BBB. What they are doing is against the law. You can treat the CD as a gift with no strings attached.
I'm not sure if most people understand how hard it is to say get 40-60 Gig of bandwidth to the middle of nowhere. It takes months, if not years, to put in the right infrastructure. If you think I'm lying, call up say, Sprint and ask them for a 10GE pipe to the middle of Iowa
Right-of-way is more important than existing infrastructure.
Just to use a company that's familiar to you as an example, ask the Southern Pacific Railroad Integration.
Hmmm... Let me know when someone finds a "carrier-grade" carrier. I have yet to find any carrier with 5 minutes or less of downtime per year.
Telcos feel they need 99.999% uptime from their equipment in order to provide you with a much lower level of service - typically 99.9% for a T1 or an analog voice line, occasionally 99.99% for a set of redundant circuits.
Our current carrier is at approximately 24 hours of downtime per quarter-year.
That's roughly 99%. If this is a T1, you should be able to do ten times better. Your SLA should provide a clause to escape your contract if it's really that bad. However, find out what the downtime is caused by - if it's local loop issues, then it's not the CLEC's fault, it's the ILEC's fault and you're still stuck with their wiring no matter who you choose. The best thing to do in that circumstance may be to demand a different physical circuit from your existing CLEC.
You can put a harmonic on the loop, but it needs to be in phase with the wavelength of the loop, which limits you to integer harmonics, and there are practical upper limits to the harmonics you can cheaply use. I don't think they'd ship a chip that had, say, a 500MHz loop and use a 20x harmonic to get 10GHz, so that as a user, you could select 21x or 22x instead. I think it'd be more likely that for the 10GHz example, they'd give you a CPU with a 3.3GHz loop. You'd get the rated 10GHz frequency, and 3.3GHz and 6.6GHz power-saving frequencies, and no option to clock it at 13.3GHz.
Varying the breadth of the pulse doesn't clock you any faster or slower.
You can't readily adjust the amount of time it takes electricity to make its way around a fixed-size loop. If this is what is actually clocking the chip, it'll have an official frequency (or two, perhaps, for low-power usage) and you'll be stuck with that. The manufacturer would have to throw out, rather than derate, any parts that don't work at that frequency.
making signs that people will understand even 1,000 years from now
If there are people living around Yucca one thousand years from now, and they aren't capable of understanding English, recognizing the "nuclear" icon, or using a geiger counter, then how are they going to know to blame us?
My computer started rebooting randomly a week or so ago
See the other post on rebooting being the blue screen of death.
I've seen a Windows XP system do this with a dying hard disk. By the time I got to it, even though Windows couldn't find any problem with the disk, it wasn't able to be fully backed up (all of C: and System State) with ntbackup - it'd blue-screen every time at the same point.
No problems since replacing the hard drive (which, granted, necessitated a fresh Windows XP installation). The failing hard drive, if you're curious, was a Western Digital 120GB IDE drive. In my case it was likely Google Desktop's reindexer, not a virus scanner, that was causing the disk activity that triggered the crash.
I haven't done the math for relative signal strength, but the numbers are there, if you want to do it, for cell phones.
Then please post them. Specifically, some numbers for cell phone stray power transmissions for +/- 12MHz centered at 1227.6 MHz and 1575.42 MHz, and for avionic GPS receiver selectivity.
Also keep in mind that GPS is a very wideband, low bitrate signal that normally operates with a signal to noise ratio of less than 1 (look at the signal figures).
I seem to rember in Apollo 13 the center 2nd stage engine, a J-2, went out early.
Dangerously strong pogo oscillations, which could have ripped the engine off the rocket, happened to trip a pressure sensor which caused the computer to shut down the engine.
Pogo was reduced to tolerable levels by the end of the Apollo series, and later engines such as the SSME were designed to eliminate it entirely.
For applications that require admin for some part of their execution, we are providing guidance to the ISVs on how to re-factor their applications so that the components that the end sees don't need the privilege and the ones that do need to can be isolated and componentized so that most users don't encounter the escalation.
Many admins, including myself, are currently supporting third-party software they know to be designed incorrectly in this aspect, and have had no luck applying the little political leverage they have to the ISV to get it fixed.
In my example the people who coded the application in question did not know about the difference between HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER, or between %TEMP% and Program Files. There have been several major version upgrades since we first noticed this, none of which have addressed the problem.
you run the risk of putting 120-volts on the chassis or shorting the outlet through the o-scope.
Also note that oscilliscopes typically have very high-impedance inputs, that will work perfectly well with some megaohm resistors in series with the test leads. Worst case, it may show a lower amplitude wave, but the waveform will be preserved. At 377V (peak to peak voltage for 120V RMS), the most current you can pump through a 1 megaohm resistor is 377 microamps, which should be safe.
And of course, make sure your oscilliscope is rated for at least 400V peak to peak voltage.
Slashdot Mirror
Maybe there's something on their own land that they don't want their own citizens to know about.
Remember that you need to not only show evidence that oil slicks kill algae but that oil slicks kill so much algae, globally, that global populations of algae are decreasing "rapidly". References would be helpful.
Quod erat demonstrandum means you have proved the point you originally set out to prove. It is not Latin for "I win."
It's one thing to say that oil slicks can kill algae (no disagreement there). It's quite another to say that a reason for global algae die-off is man-made pollution. Many (dare I say most?) types of pollution cause algal bloom.
You need the right strain to make it grow quickly and give decent biodiesel yields. But just about any algae will grow in a high-CO2, high water, high sunlight environment.
If pollution kills algae, how the heck does this work?
Err, which plane?
Carbon fiber is extremely strong, but it is also stiff and brittle (and expensive). Fiberglass is also strong, but very, very flexible - Voyager's wingtips could have bent until they touched each other before breaking. Of course, in a crash, you want the structure ahead of you to break or crumple in a controlled manner (to increase the amount of time you decelerate) and not rebound.
*does double take*
A what?
I wish the Seattle Times made online archives that easy to get to.
If you live in the US, consider writing your state Attorneys General instead of the BBB. What they are doing is against the law. You can treat the CD as a gift with no strings attached.
As initially envisioned, the laptops sported a hand crank on the side to generate power, but Negroponte has scrapped that idea because the twisting forces that would be bad for the machine. Instead, some form of power generation device, likely a pedal, will be attached to the AC power adapter, he said.
Right-of-way is more important than existing infrastructure.
Just to use a company that's familiar to you as an example, ask the Southern Pacific Railroad Integration.
Telcos feel they need 99.999% uptime from their equipment in order to provide you with a much lower level of service - typically 99.9% for a T1 or an analog voice line, occasionally 99.99% for a set of redundant circuits.
Our current carrier is at approximately 24 hours of downtime per quarter-year.
That's roughly 99%. If this is a T1, you should be able to do ten times better. Your SLA should provide a clause to escape your contract if it's really that bad. However, find out what the downtime is caused by - if it's local loop issues, then it's not the CLEC's fault, it's the ILEC's fault and you're still stuck with their wiring no matter who you choose. The best thing to do in that circumstance may be to demand a different physical circuit from your existing CLEC.
The symbol on the left is not a letter, sir?"
Correct.
Varying the breadth of the pulse doesn't clock you any faster or slower.
You can't readily adjust the amount of time it takes electricity to make its way around a fixed-size loop. If this is what is actually clocking the chip, it'll have an official frequency (or two, perhaps, for low-power usage) and you'll be stuck with that. The manufacturer would have to throw out, rather than derate, any parts that don't work at that frequency.
If there are people living around Yucca one thousand years from now, and they aren't capable of understanding English, recognizing the "nuclear" icon, or using a geiger counter, then how are they going to know to blame us?
See the other post on rebooting being the blue screen of death.
I've seen a Windows XP system do this with a dying hard disk. By the time I got to it, even though Windows couldn't find any problem with the disk, it wasn't able to be fully backed up (all of C: and System State) with ntbackup - it'd blue-screen every time at the same point.
No problems since replacing the hard drive (which, granted, necessitated a fresh Windows XP installation). The failing hard drive, if you're curious, was a Western Digital 120GB IDE drive. In my case it was likely Google Desktop's reindexer, not a virus scanner, that was causing the disk activity that triggered the crash.
Then please post them. Specifically, some numbers for cell phone stray power transmissions for +/- 12MHz centered at 1227.6 MHz and 1575.42 MHz, and for avionic GPS receiver selectivity.
Also keep in mind that GPS is a very wideband, low bitrate signal that normally operates with a signal to noise ratio of less than 1 (look at the signal figures).
Dangerously strong pogo oscillations, which could have ripped the engine off the rocket, happened to trip a pressure sensor which caused the computer to shut down the engine.
Pogo was reduced to tolerable levels by the end of the Apollo series, and later engines such as the SSME were designed to eliminate it entirely.
Many admins, including myself, are currently supporting third-party software they know to be designed incorrectly in this aspect, and have had no luck applying the little political leverage they have to the ISV to get it fixed.
In my example the people who coded the application in question did not know about the difference between HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER, or between %TEMP% and Program Files. There have been several major version upgrades since we first noticed this, none of which have addressed the problem.
How can we help Microsoft help the ISV help us?
Err, I mean no. Sorry about that.
Yes.
Also note that oscilliscopes typically have very high-impedance inputs, that will work perfectly well with some megaohm resistors in series with the test leads. Worst case, it may show a lower amplitude wave, but the waveform will be preserved. At 377V (peak to peak voltage for 120V RMS), the most current you can pump through a 1 megaohm resistor is 377 microamps, which should be safe.
And of course, make sure your oscilliscope is rated for at least 400V peak to peak voltage.
...zero-day
SETABORTPROC Escape
Linux geeks are not afraid.
IDS, thanks for playin'
Unofficial patch burn
World serves its own needs
Dummy serve your own needs.
Feed the news from ISC,
Go insane
The blogs all start to clatter
With fear fight down height.
Wire is on fire
On a new years' holiday
And the mafia for hire
At a pharma site.
Tuesday now it's coming in
A hurry with the worries
breathing down your neck.
Team by team the coders baffled,
trumped, tethered cropped.
Feature? That's insane!
Fine, then. Uh oh,
A week 'till it's released to you
But it'll do
Unregister a DLL
World serves its own needs,
Patch this at your own speed
Crummy packet capture
And it's never quite
Right, right.
Admin now an alcoholic
Can't take bright light
Feeling pretty tired.
It's the end of the world as we know it.
It's the end of the world as we know it.
It's the end of the world as we know it and I feel fine.