At least Zod was *competent* at being evil. I just can't respect incompetent evil like W.
+
It took me a moment to realize that you weren't talking about W from Good Eats. W may be Alton's worst nemesis, but he can't help going back to her because, like it or not, she does know cooking utensils!
There is no air to create blast wave and thermal flash, so all you get is some hard radiation and hand-grenade level of blast from vaporized bomb casing. And that's it.
AIUI, you have to have the blast very close to the surface, if not actually on it. The radiation from the blast will be enough to vaporize some small amount of the asteroid. That vapor will leave the asteroid very quickly in the direction the blast came from and the rest of it will move in the other direction, although very slowly. I agree that it's not going to be as effective as it would be in atmosphere, but there will be some acceleration from it, and as I pointed out in another post, it doesn't take very much if you can give it enough time to work.
Not really. Let's say that the most we can do with a nuke is slow the asteroid down by 1 f/sec. Doesn't sound like much, does it? but if you do it 30 days before impact, that shifts the asteroid back almost 491 miles. If you have six months, it's over 2000 miles. Considering that the Earth is a moving target, that might be enough to ensure a miss. You're not trying to blow up the asteroid, you're just trying to nudge it into a slightly different orbit that doesn't impact the Earth, and if you have time, it doesn't take very much.
There are digital cameras that don't work with Linux, and probably never will. They're the keychain sized cameras that you can get at the drug store for $10 or so. They don't use a standard chipset, they don't have a standard interface and the very proprietary drivers are Windows only. I know, because I found out the hard way when I installed Linux as dual-boot and it couldn't see the cheapie camera I was using at the time. Now, I'm strictly Linux and I've broken down and shelled out the money for a decent camera. Works just fine, like you said.
The person who feels shafted here feels that their database had nothing to do with the problem. I don't know enough about the nature of his problem to venture a guess if this is true, so I'm going to assume it is for now.
I used to do Tier II support for a major ISP. Much of my day was devoted to taking calls after a junior tech had failed. I'd say that in at least a third of the cases, that tech had gone haring off in the wrong direction and wasted time playing with things that had nothing to do with the issue. It wasn't at all uncommon for me to look at the case notes and see that the first tech had spent the entire call playing with the network settings when the caller's modem didn't sync. Not knowing anything about the issue except for what's in the article, I'd give 4:3 odds that the contents of the database had nothing to do with the issue.
Yes, even the camera requires a driver to transfer pictures.
Unless she bought a toy digital camera with a non-standard chipset, it should have worked fine. Either digiKam or f-spot should have been able to find and download the photos. If not, the camera should have shown up on the desktop and you could have used copy/paste to get them onto the hard disk. Sounds like Granny was talked into buying a cheap camera instead of a good one.
he password policy should be made as strong and secure as possible
No. Not as strong as possible, as strong as practical. The security trainer was showing that it's possible to make your policy so strong it was impractical, and that's what weakened the passwords.
No, he wasn't an asshole. He had a very good point that has just gone over your head. To elucidate, if you add too many requirements to user's passwords they can't remember them and need to write them down. Once you get to that point, the passwords aren't strong any more and you've created a security hole by trying to avoid one. There's a limit on how much you can expect the average user to remember when it comes to passwords; go past that and their passwords get less, not more secure.
Where hardware does not conform to ACPI, but claims to do so...
I see. The BIOS needs to care about the OS because and only because the hardware isn't ACPI compliant but claims to be. The tables are a firmware kludge to compensate for the failure of the hardware designers to do their jobs properly. Thank you.
You seem to know what you're talking about, so maybe you can answer a question for me: why does the BIOS on the mobo need to know what OS is running? Shouldn't it just handle requests in a neutral manner? This seems to imply that Win2K expects different results from a BIOS call than XP or Linux or FreeBSD does, and that just doesn't seem to make sense!
Half the fun of wikipedia is looking up something, then wasting a couple hours wandering through topics till you get someplace you might not have gone otherwise.
And that, of course, is also the fun of looking up something in a dead-tree encyclopedia. As you look up the article you need, you run across other interesting articles and end up learning all sorts of unexpected things.
Several posters here have mentioned the possibility of these trolls suing Santa. Frankly, I hope they do! For years he was number 1 on the annual Forbes' list of the Fifteen Richest Fictional Characters because his wealth is clearly infinite. (They've removed him because of the number of complaints from children and the physical evidence (milk and cookies consumed, presents left)) However, if anybody has the resources to fight this and counter-sue those greedy bums into oblivion, it's Santa.
I'm from California too, and I have to say that you've fallen for a prank. Those are made up places for TV shows.
You may well be right, but as an Angelino, born and bred, I'm sure that Florida is a hoax made up by people to attack our orange industry. I've never understood why anybody would want to drink orange juice from some imaginary place like Florida when the best eating oranges in the world come from Southern California.
Bzzzzt! Wrong, but thank you for playing. Los Angeles has never had acid rain, and probably never will. That's only an issue in the Snow Belt, where people burn large quantities of high-sulphur coal in the Winter to keep from freezing their asses off.
That's all well and good, but as yu say, you're a programmer. I don't think I've written a line of code in over a decade; how long do you think it would take me to get up to speed again to chase a bug down? How about my sister? To her, source code would be gibberish; she's never coded, never wanted to. If she stumbled on a bug in an OSS program, about all she could do is file a report and hope somebody else fixed it. With a closed-source program, there's no assurance the people who own it even listen to bug reports from home users.
Most modern "viruses" (read: trojans) don't do anything which requires Local Admin privileges in Windows - and hence, Linux equivalents wouldn't need root access.
There are many trojans out there that try to "phone home" by sending email, or try to turn your computer into a spambot. They can't do that without binding to port 25, and in Linux, that takes root access.
+ It took me a moment to realize that you weren't talking about W from Good Eats. W may be Alton's worst nemesis, but he can't help going back to her because, like it or not, she does know cooking utensils!
AIUI, you have to have the blast very close to the surface, if not actually on it. The radiation from the blast will be enough to vaporize some small amount of the asteroid. That vapor will leave the asteroid very quickly in the direction the blast came from and the rest of it will move in the other direction, although very slowly. I agree that it's not going to be as effective as it would be in atmosphere, but there will be some acceleration from it, and as I pointed out in another post, it doesn't take very much if you can give it enough time to work.
Not really. Let's say that the most we can do with a nuke is slow the asteroid down by 1 f/sec. Doesn't sound like much, does it? but if you do it 30 days before impact, that shifts the asteroid back almost 491 miles. If you have six months, it's over 2000 miles. Considering that the Earth is a moving target, that might be enough to ensure a miss. You're not trying to blow up the asteroid, you're just trying to nudge it into a slightly different orbit that doesn't impact the Earth, and if you have time, it doesn't take very much.
While you're at it, don't forget Jerry's coauthor, Larry Niven!
There are digital cameras that don't work with Linux, and probably never will. They're the keychain sized cameras that you can get at the drug store for $10 or so. They don't use a standard chipset, they don't have a standard interface and the very proprietary drivers are Windows only. I know, because I found out the hard way when I installed Linux as dual-boot and it couldn't see the cheapie camera I was using at the time. Now, I'm strictly Linux and I've broken down and shelled out the money for a decent camera. Works just fine, like you said.
I used to do Tier II support for a major ISP. Much of my day was devoted to taking calls after a junior tech had failed. I'd say that in at least a third of the cases, that tech had gone haring off in the wrong direction and wasted time playing with things that had nothing to do with the issue. It wasn't at all uncommon for me to look at the case notes and see that the first tech had spent the entire call playing with the network settings when the caller's modem didn't sync. Not knowing anything about the issue except for what's in the article, I'd give 4:3 odds that the contents of the database had nothing to do with the issue.
At this point, I'm beginning to think that maybe the FSS wants everybody to be free to choose to do things the FSS way. And no other way.
Unless she bought a toy digital camera with a non-standard chipset, it should have worked fine. Either digiKam or f-spot should have been able to find and download the photos. If not, the camera should have shown up on the desktop and you could have used copy/paste to get them onto the hard disk. Sounds like Granny was talked into buying a cheap camera instead of a good one.
No. Not as strong as possible, as strong as practical. The security trainer was showing that it's possible to make your policy so strong it was impractical, and that's what weakened the passwords.
No, he wasn't an asshole. He had a very good point that has just gone over your head. To elucidate, if you add too many requirements to user's passwords they can't remember them and need to write them down. Once you get to that point, the passwords aren't strong any more and you've created a security hole by trying to avoid one. There's a limit on how much you can expect the average user to remember when it comes to passwords; go past that and their passwords get less, not more secure.
I see. The BIOS needs to care about the OS because and only because the hardware isn't ACPI compliant but claims to be. The tables are a firmware kludge to compensate for the failure of the hardware designers to do their jobs properly. Thank you.
You seem to know what you're talking about, so maybe you can answer a question for me: why does the BIOS on the mobo need to know what OS is running? Shouldn't it just handle requests in a neutral manner? This seems to imply that Win2K expects different results from a BIOS call than XP or Linux or FreeBSD does, and that just doesn't seem to make sense!
And that, of course, is also the fun of looking up something in a dead-tree encyclopedia. As you look up the article you need, you run across other interesting articles and end up learning all sorts of unexpected things.
Nice try, AC, but the url you gave doesn't point to anything.
Why not? it's not like they've never helped make lethal weapons. In case you didn't know, the M-16 was originally developed my Mattel.
Several posters here have mentioned the possibility of these trolls suing Santa. Frankly, I hope they do! For years he was number 1 on the annual Forbes' list of the Fifteen Richest Fictional Characters because his wealth is clearly infinite. (They've removed him because of the number of complaints from children and the physical evidence (milk and cookies consumed, presents left)) However, if anybody has the resources to fight this and counter-sue those greedy bums into oblivion, it's Santa.
So? If the Chicago River gets choked with algae, just set it on fire and burn it off!
You may well be right, but as an Angelino, born and bred, I'm sure that Florida is a hoax made up by people to attack our orange industry. I've never understood why anybody would want to drink orange juice from some imaginary place like Florida when the best eating oranges in the world come from Southern California.
I take it, then, you've never heard of something called "sulphuric acid," with a formula of H2SO4.
Bzzzzt! Wrong, but thank you for playing. Los Angeles has never had acid rain, and probably never will. That's only an issue in the Snow Belt, where people burn large quantities of high-sulphur coal in the Winter to keep from freezing their asses off.
That's all well and good, but as yu say, you're a programmer. I don't think I've written a line of code in over a decade; how long do you think it would take me to get up to speed again to chase a bug down? How about my sister? To her, source code would be gibberish; she's never coded, never wanted to. If she stumbled on a bug in an OSS program, about all she could do is file a report and hope somebody else fixed it. With a closed-source program, there's no assurance the people who own it even listen to bug reports from home users.
And that, of course, is the forum I was referring to in the first place. I'm glad to see we agree on this.
Did they give him a read T-shirt as a freebie?
Thank you, I sit corrected.
There are many trojans out there that try to "phone home" by sending email, or try to turn your computer into a spambot. They can't do that without binding to port 25, and in Linux, that takes root access.