Oh, and please stop posting the same comment over and over again. Anybody reading this thread will have managed to get your point the first time around.
3 people took the time to tell me to RTFA I already read, so I returned the favor.
Ask Slashdots like this one, and succinct replies like this one make me wish there was an option to immediately archive a story with just one comment if enough people vote for it.:)
I had a Linksys ethernet switch that came with a small wall-wart that was obviously a switch-mode power supply, very light weight. The thing got so hot that the label turned brown.
I'm making the assumption these failed power supplies are SMPS, the article didn't say, but I bet it was.
Companies are looking to skimp on production and shipping costs by ditching old style linear transformer wall warts and going to switching power supplies, but a switch mode power supply is something that is not very tolerant to crappy design that cuts corners and overloads the supply.
If you overload a linear the voltage will just drop below the usable threshold. If you overload a switcher it'll seem to work for a while, overheat and fail, sometimes spectacularly.
It's biting them now, so hopefully they'll learn their lesson.
The main issue isn't complexity, at least not on an OS level. Systems like EROS and other Take-Grant type systems can be provably secure. The problem comes in the administration of multi-user system.
People have enough trouble managing simple systems like Unix-style permissions and Novell NDS permissions.
Most multiuser systems I've come across in actual use have pretty glaring security problems, just because of the complex nature of the way people want to use them.
At some point it becomes easier to just say "OK fine, we'll give this whole group of people this particular (overly broad) access... it's better than them having to come bug an admin every 10 minutes".
Another example, this one a particular problem for an internal app I had a big role in designing. Every user is given a password, and told not to give it away. A few months later it's exposed that many users know other user's passwords. Turns out when someone was on vacation or sick, someone had to be able to get access to the data normally reserved for that person only. This can usually be designed around, but it's the sort of thing that complicates these matters.
Daemons and programs are easier, they don't change roles or start working with different people unless it's a well defined change concurrent to an upgrade.
Exactly. Modern lower yield devices don't loft much dust into the stratosphere so it rains out quickly from the troposphere.
This makes the near field fallout zone that much hotter, but it also prevents any nuclear winter scenarios.
And for the fallout secondary effects there's the "rule of sevens"... for each 7 fold increase in time after 1 hour, radiation levels are reduced by a factor of 10. After 7 hours it's 10% of initial values, after 49 hours, 1%, etc.
Thanks for posting this. So many people seem to think that we have thousands of 50-100MT bombs just sitting around. Hardly anyone realizes that the entire modern aresenel is well under 1MT with very few exceptions.
The truth of the matter is, a complete nuclear engagement isn't the end of the world. It would just make a pretty good mess for a while.
The danger is that people seem to not even consider a post-nuke scenario, saying things like "Well I hope I'm at the center of the blast", etc. The vast majority of people will survive even a full scale drag out battle. How prepared are you?
There's just not a huge advantage to big yields. The power increases with the inverse cube law. A bomb that is twice as big doesn't do anywhere near twice as much damage.
If you short something to that angle iron it's going to fry lots of things. Not to mention zapping you pretty good if you touch a live wire at 120 volts while leaning on it.
Put a resistor in the ground line. At least a hundred kiloohm. Doesn't have to be high wattage, anything will do.
I think one of the major polarizing factors is a misunderstanding of what exactly a theory is.
A theory doen't have to be correct to be useful. Big bang is probably wrong. As long as it is useful we shouldn't discard it. If we start getting data that doesn't fit, we need to find a new theory or somehow explain how it fits in the old one.
I've run across supposed scientific minds that asserted the "laws" of physics as they stand today are "complete, immutable, and self-evident". So the ignorance isn't all on one side either. I'm no "free energy" kook, but science goes out the window when you close the door on contrary observations.
Slashdot Mirror
Last I checked, taking credit for someone else's work is called "plagiarism" and it is illegal
You shouldn't listen to your 6th grade english teacher so much. You can't copyright facts, and there's no "anti-plagarism" law.
Sleezy, yes, but incriminating?
If you make www.example.com/file1.html and I access file2.html, that's criminal now?
If they didn't want the data out, they shouldn't put it on the web.
Oh, and please stop posting the same comment over and over again. Anybody reading this thread will have managed to get your point the first time around.
3 people took the time to tell me to RTFA I already read, so I returned the favor.
I fucking hate that "RTFA" bullshit.
Jesus saved me from my past. He can save you as well.
I don't get it. What's the joke?
Not much software would ever be released if you want some sort of provable guarantee of being bug free.
If you'll read the whole fucking article, you'll see this is a bug in the Tivo software, not content protection being used.
Try reading more closely. This is a bug in the Tivo software, caused by a noisy signal, not actual content protection being used.
Maybe you should RTFA. This was a bug, no one is actually using said content protection yet.
It's still Slashdot whining, nothing has changed. It's just a bug someone found.
You can divx tivo content, but it's a little more roundabout process.
So when I come back a week later Tivo is gonna say "sorry you're schedule clashed with mine".
What? When you told it to record the game you can say "keep until I delete" in the recording options.
Next time try reading the prompts.
It's hard because it's hard
:)
Ask Slashdots like this one, and succinct replies like this one make me wish there was an option to immediately archive a story with just one comment if enough people vote for it.
I had a Linksys ethernet switch that came with a small wall-wart that was obviously a switch-mode power supply, very light weight. The thing got so hot that the label turned brown.
I'm making the assumption these failed power supplies are SMPS, the article didn't say, but I bet it was.
Companies are looking to skimp on production and shipping costs by ditching old style linear transformer wall warts and going to switching power supplies, but a switch mode power supply is something that is not very tolerant to crappy design that cuts corners and overloads the supply.
If you overload a linear the voltage will just drop below the usable threshold. If you overload a switcher it'll seem to work for a while, overheat and fail, sometimes spectacularly.
It's biting them now, so hopefully they'll learn their lesson.
What, it could happen.
Indeed. What SPEWS does is not so different from what you are proposing.
The main issue isn't complexity, at least not on an OS level. Systems like EROS and other Take-Grant type systems can be provably secure. The problem comes in the administration of multi-user system.
People have enough trouble managing simple systems like Unix-style permissions and Novell NDS permissions.
Most multiuser systems I've come across in actual use have pretty glaring security problems, just because of the complex nature of the way people want to use them.
At some point it becomes easier to just say "OK fine, we'll give this whole group of people this particular (overly broad) access... it's better than them having to come bug an admin every 10 minutes".
Another example, this one a particular problem for an internal app I had a big role in designing. Every user is given a password, and told not to give it away. A few months later it's exposed that many users know other user's passwords. Turns out when someone was on vacation or sick, someone had to be able to get access to the data normally reserved for that person only. This can usually be designed around, but it's the sort of thing that complicates these matters.
Daemons and programs are easier, they don't change roles or start working with different people unless it's a well defined change concurrent to an upgrade.
Yes,
The most thorough site I've found about nuclear bomb effects.
Exactly. Modern lower yield devices don't loft much dust into the stratosphere so it rains out quickly from the troposphere.
This makes the near field fallout zone that much hotter, but it also prevents any nuclear winter scenarios.
And for the fallout secondary effects there's the "rule of sevens"... for each 7 fold increase in time after 1 hour, radiation levels are reduced by a factor of 10. After 7 hours it's 10% of initial values, after 49 hours, 1%, etc.
Each bomblet has a blast radius of about 5 km (being very generous), that's 78 square km. Assuming your figures are right, 14,976 square km per boat.
That's a square 122 km wide per boat, assuming no overlap, and perfect flat terrain.
Yes, you could decimate a city with that, but it's not going to be the end of civililiation as we know it like so many movies make out.
Thanks for posting this. So many people seem to think that we have thousands of 50-100MT bombs just sitting around. Hardly anyone realizes that the entire modern aresenel is well under 1MT with very few exceptions.
The truth of the matter is, a complete nuclear engagement isn't the end of the world. It would just make a pretty good mess for a while.
The danger is that people seem to not even consider a post-nuke scenario, saying things like "Well I hope I'm at the center of the blast", etc. The vast majority of people will survive even a full scale drag out battle. How prepared are you?
And also the modern arsenel is submegaton.
There's just not a huge advantage to big yields. The power increases with the inverse cube law. A bomb that is twice as big doesn't do anywhere near twice as much damage.
If you short something to that angle iron it's going to fry lots of things. Not to mention zapping you pretty good if you touch a live wire at 120 volts while leaning on it.
Put a resistor in the ground line. At least a hundred kiloohm. Doesn't have to be high wattage, anything will do.
I think one of the major polarizing factors is a misunderstanding of what exactly a theory is.
A theory doen't have to be correct to be useful. Big bang is probably wrong. As long as it is useful we shouldn't discard it. If we start getting data that doesn't fit, we need to find a new theory or somehow explain how it fits in the old one.
I've run across supposed scientific minds that asserted the "laws" of physics as they stand today are "complete, immutable, and self-evident". So the ignorance isn't all on one side either. I'm no "free energy" kook, but science goes out the window when you close the door on contrary observations.
But at some point you have to decide whether paying them off so they don't riot is more costly than just letting them die.
It's going to take a lot of electricity.
World electrical production (OECD Countries): 9.3 petawatt-hours per year
US gasoline consumption: about 3.9 petawatt-hours per year
So unless you plan on increasing world electrical production a *lot*, we are going to have trouble.
US gas consumption = 320500000 gallons/day
121 megajoules per gallon, 1 megajoule= 1 megawatt second
The GPL was written for these purposes.
The entire purpose of the GPL is to preserve and protect freedom.
The GPL is about preserving the freedom to modify, use and distribute for future viewers/consumers/users of the code and applications.
Software patents and DRM remove the freedom to modify, use, and distribute.
It's nature for the GPL to clarify its stance on such matters.