I can't believe people actually think it was "revenge". You don't get revenge on a company by attacking their customers and then not even leaving so much as a threatening note...
1) Yes, the same as/dev/random, the difference is that once it runs OUT of "cryptographically secure random numbers", it starts to REUSE the seed values. NOT GOOD.
2) Even if you can't predict which numbers are coming out, it will most likely make guesses more accurate.
3) "cryptographically secure" means NOTHING unless you can state the type (with parameters) of the cryptography. rot13 is technically "cryptography", albeit a weak one.
No, that is non-booting. Bricked means the phone is (pending an magical bolt of lightning from the almighty Zeus himself) is no longer any more valuable than a shiny brick.
There's another possibility. Look at the history (click on the actual score). There's a good chance they already had 2 negative mods and 2 +1 informative (thus showing 0). When you add +1 funny, they get a final score of +1 and "informative" has more votes than "funny" and so takes the lead.
It also depends if the 2 drugs are owned (through patents/etc) by the same company. If not, I doubt either one will help the other, even for their own profit.
actually, you should use/dev/random. when the entropy runs out (or gets too low),/dev/random will wait for it to go back up,/dev/urandom will REUSE it, seriously impacting the "randomness" of your results. urandom is fine for game data, graphics, etc but to NOT use it for anything important.
We are not expecting everyone to buy cars that cost $50,000 more. We are however hoping that SOME people do. The rich like features (we already have auto-parking), so let them buy them. After a while the price will come down (like auto-parking is) and eventually almost all cars will have it, including the one your drunk neighbour bought at the used car lot for $10,000
And rain, pot holes, oil slicks, ice, fading/missing road markings, flat tires, debris, fallen trees, mechanical issues, etc.
These days, making a car that drives itself down a standard road is almost trivial, getting it to deal with the unexpected is still VERY VERY difficult.
If everyone drove autonomous cars and, you had someone go on a bloody rampage with a "hacked" car every DAY, it would still not cause as many deaths as stupid drivers do today. In fact, with 17,000 dying from drunk driving every year in the US alone, each daily rampage would have to cause 46.5 deaths EACH just to match the DRUNKS. The you add the sleeping truckers, "what stopsign" idiots, speeders and other dumbasses that shouldn't be allowed to control a TRICYCLE and I'll take autonomous cars any day of the week!!!
I remember reading an article about glass windows that had very small (nearly invisible) wires in it to block the corporate network wireless from leaking outside of the building. You could probably put a light wire mesh over the window (like a window screen) to keep other networks *out*.
BULL. Making safe reflashable devices is TRIVIAL, companies simply don't bother. I have an n810 and not only does Nokia FULLY endorse reflashing it (and provide tools for windows/mac/linux to do so), but it was the recommended method of performing major updates until Diablo came out (which supported full updates without reflashing). All you need to do is have a very small ROM that handles the flashing, and nothing else. This ensures that no matter what happens during the flashing, it can still be reflashed.
It boggles my mind that companies (router manufacturers, I'm looking at you) put the reflashing code IN the firmware instead of somewhere safe such as a dedicated ROM. I highly doubt anyone is going to want/need to update that part of the code.
JavaScript has done more for making Linux viable on the desktop than C or Java ever has. So many apps these days can be written as web apps, and run on any OS and any hardware, as long as they have a decent web browser.
Most linux users I know actually use c/c++ apps instead of the "web apps". Thunderbird, pidgin, gwibber, etc all beat the pants off gmail, eBuddy, twitter, etc.
Slashdot Mirror
I can't believe people actually think it was "revenge". You don't get revenge on a company by attacking their customers and then not even leaving so much as a threatening note...
1) Yes, the same as /dev/random, the difference is that once it runs OUT of "cryptographically secure random numbers", it starts to REUSE the seed values. NOT GOOD.
2) Even if you can't predict which numbers are coming out, it will most likely make guesses more accurate.
3) "cryptographically secure" means NOTHING unless you can state the type (with parameters) of the cryptography. rot13 is technically "cryptography", albeit a weak one.
ah, well a mass-hack would be much different, I'll give you that.
No, that is non-booting. Bricked means the phone is (pending an magical bolt of lightning from the almighty Zeus himself) is no longer any more valuable than a shiny brick.
I'm not saying all ubuntu users use thunderbird/etc, just that SOME do. And btw, these users are anything BUT advanced...
as opposed to trinary bits...?
There's another possibility. Look at the history (click on the actual score). There's a good chance they already had 2 negative mods and 2 +1 informative (thus showing 0). When you add +1 funny, they get a final score of +1 and "informative" has more votes than "funny" and so takes the lead.
This just in, HatfulOfHollow has added limbs and finally become rich and famous!
It also depends if the 2 drugs are owned (through patents/etc) by the same company. If not, I doubt either one will help the other, even for their own profit.
actually, you should use /dev/random. when the entropy runs out (or gets too low), /dev/random will wait for it to go back up, /dev/urandom will REUSE it, seriously impacting the "randomness" of your results. urandom is fine for game data, graphics, etc but to NOT use it for anything important.
We are not expecting everyone to buy cars that cost $50,000 more. We are however hoping that SOME people do. The rich like features (we already have auto-parking), so let them buy them. After a while the price will come down (like auto-parking is) and eventually almost all cars will have it, including the one your drunk neighbour bought at the used car lot for $10,000
GOOD, and neither should a HUMAN driver!
And rain, pot holes, oil slicks, ice, fading/missing road markings, flat tires, debris, fallen trees, mechanical issues, etc.
These days, making a car that drives itself down a standard road is almost trivial, getting it to deal with the unexpected is still VERY VERY difficult.
If everyone drove autonomous cars and, you had someone go on a bloody rampage with a "hacked" car every DAY, it would still not cause as many deaths as stupid drivers do today. In fact, with 17,000 dying from drunk driving every year in the US alone, each daily rampage would have to cause 46.5 deaths EACH just to match the DRUNKS. The you add the sleeping truckers, "what stopsign" idiots, speeders and other dumbasses that shouldn't be allowed to control a TRICYCLE and I'll take autonomous cars any day of the week!!!
1. I'm genuinely curious as to what types (or brands) of devices cause such anomalies. 2. Don't use a crappy switch! 3. Don't use a crappy switch!
I remember reading an article about glass windows that had very small (nearly invisible) wires in it to block the corporate network wireless from leaking outside of the building. You could probably put a light wire mesh over the window (like a window screen) to keep other networks *out*.
Do you have a like to that Toshiba? I do not doubt you in the slightest, it just sounds like an awesome machine.
BULL. Making safe reflashable devices is TRIVIAL, companies simply don't bother. I have an n810 and not only does Nokia FULLY endorse reflashing it (and provide tools for windows/mac/linux to do so), but it was the recommended method of performing major updates until Diablo came out (which supported full updates without reflashing). All you need to do is have a very small ROM that handles the flashing, and nothing else. This ensures that no matter what happens during the flashing, it can still be reflashed.
It boggles my mind that companies (router manufacturers, I'm looking at you) put the reflashing code IN the firmware instead of somewhere safe such as a dedicated ROM. I highly doubt anyone is going to want/need to update that part of the code.
JavaScript has done more for making Linux viable on the desktop than C or Java ever has. So many apps these days can be written as web apps, and run on any OS and any hardware, as long as they have a decent web browser.
Most linux users I know actually use c/c++ apps instead of the "web apps". Thunderbird, pidgin, gwibber, etc all beat the pants off gmail, eBuddy, twitter, etc.
And the fact that there could possibly be a time when you would be better off using a hub over a switch...
So much for our road analogies when fighting Usage Based Billing :(
Might want to take Nokia off that list now that they have abandoned Meego (luckily Intel picked it up).
And how would a Windows or Apple (or anything else for that matter) computer have been any better in that situation?
Her backup in the next room over might...
Weird. I wonder what Canonical did to evolution to make it depend on Mono. It's not even an opt-depends in Arch...