Who is better qualified to write about things which the experts forget about? He's making good use of his ignorance, by providing details of his learning experience.
Fortunately he didn't remember the white doohikey and the static until after something died.
...and to top it off he Slashdotted the boss' computer.
Definition says nothing about requiring facts to be collected in some unbiased way, it just requires the movie to consist of material based on actual facts/documents which Farenheit does.
Google: Linux CPU cooler halt
Linux uses the CPU's HALT instruction when idle, which uses less power than the idle loop which some versions of DOS/MS-Windows uses.
It does reduce power usage during times of high prices. Just as many places offer cheaper electric rates if the power company can turn off things when demand is very high. Often that means that air conditioners turn off in an area for a while. No air conditioning for 20-60 minutes is OK when the house is already cool.
The hard part will be in avoiding the whole city turning everything on when the price drops to a certain point.
I mentioned a geothermal energy source, so I'm not ruling it out. But it's quite a leap to get from the known extremophile bacteria and geothermal vent ecology to something which could be oxygenating the water for ancient creatures.
Particularly awkward are the millions of elapsed years, during which geothermal heat might have shut off or wandered away.
Well, the way I'd keep the info private is to never store the data password in the servers.
User authentication requires the user supply something like a password. When the server has that, in addition to confirmation a separate DB access code can be built from it.
This DB access code could only be created using the password, and if that is not in the servers then the servers can't decrypt the data without the user.
The simple implementation would be to store it in the user's browser as a cookie. Of course there is risk of extraction of it from the user's machine. So instead do something like encrypt the newly recreated DB key, and store that decryption key in a user cookie. The data could only be accessed during each user transaction. A different encryption key can be used for the DB key for each session, so stored cookies become obsolete when a session ends.
That's a rather obvious solution given the problem definition, as keeping half a key is an old method of requiring cooperation. Maybe they're doing something similar but phrased in a way which obscures the split storage.
Slashdot Mirror
Fortunately he didn't remember the white doohikey and the static until after something died.
So when will spammers have to keep away from blue helicopters?
Thanks, Clippy!
And then everyone had to get out.
Ah. Then Rock, Paper, Saddam is a documentary.
Is the Individual Ready Reserve what John Kerry was in when he came back from Vietnam?
Does Moore own the film? Why didn't he put it in the public domain if he doesn't like copyright?
Now we don't know whether to laugh or cry.
The real story is "We had to wait for NVidia to let us use their hardware, and now we have some use of it. Temporarily."
There is more to a story than a URL. Did you use exactly the same wording, so it was judged the same way? Did the same person examine the submission?
So what are the SMS addresses of Chinese political leaders?
You didn't put "NO CATS ALLOWED" signs on your server room as soon as you saw the headline?
Is ACME the supplier?
Google: Linux CPU cooler halt
Linux uses the CPU's HALT instruction when idle, which uses less power than the idle loop which some versions of DOS/MS-Windows uses.
Obviously North Korea should be in charge of global certificates.
It took you four hours to install Linux?
What is the best brand of tinfoil for radar?
But please don't stock up on cars.
Humor like that is why I /.org
I read
However, from the phrasing it sounds like data loss would be permanent and irreversible. I think that answers my question.
This brings new meaning to "working within the system". I foresee a flurry of unusual requests from the public to assorted government agencies.
The hard part will be in avoiding the whole city turning everything on when the price drops to a certain point.
We don't all have such dedicated fans.
Particularly awkward are the millions of elapsed years, during which geothermal heat might have shut off or wandered away.
User authentication requires the user supply something like a password. When the server has that, in addition to confirmation a separate DB access code can be built from it.
This DB access code could only be created using the password, and if that is not in the servers then the servers can't decrypt the data without the user.
The simple implementation would be to store it in the user's browser as a cookie. Of course there is risk of extraction of it from the user's machine. So instead do something like encrypt the newly recreated DB key, and store that decryption key in a user cookie. The data could only be accessed during each user transaction. A different encryption key can be used for the DB key for each session, so stored cookies become obsolete when a session ends.
That's a rather obvious solution given the problem definition, as keeping half a key is an old method of requiring cooperation. Maybe they're doing something similar but phrased in a way which obscures the split storage.
What Space Shuttle program might NASA focus on? Are they building more?