From the article: Apparently IPv6 will solve all these problems, with a brand new standard that uses 64 bits.
...
Many, many applications work with IPv4 and assume that addresses will be 32 bit, not 64 bit (as IPv6 specifies).
That's a pretty glaring error, if we're talking about the same IPv6 spec.
I'm willing to bet that if they lose their case, they sink like a rock. Investors will evaporate, and their reputation will be utterly destroyed. Once they're bankrupt, it's pretty much a guarantee that you won't get your money back before a lot of other people (or corporations rather) get their money first. So you could probably sue them, but I'm thinking you would basically be redirecting your time/money to/dev/null.
IMO the extra pages are well worth the color they add to the plot and characters. I imagine his expansion of themes and ideas, and his illustrations of the complex history behind them are what is turning you off, but I think most geeks appreciate the thoroughness and multiple perspectives. Seems to me that most geeks pride themselves immensely on knowing even the most arcane details of a given subject (ideally, any given subject), and Stephenson is either a.) catering to this explicitly or b.) a geek himself, or both I suppose.
And while Snow Crash was almost non-stop hyperactivity (besides the occasional Sumerian culture educational interludes), I savored the action that much more in Diamond Age and Cryptonomicon. It didn't come across as indulgent, gratuitous action like it did in Snow Crash, it seemed to fit more into the story, which I found quite a bit more satisfying.
Maybe tonight when I'm in the outhouse staring at the wall it will suddenly become uproariously funny, but in the mean time I'm just going to have to assume that I was duped into reading a joke that just really wasn't funny.
I'm not sure web serving would ideally test this (I know it's a joke...I'm just wondering about this...). The article mentioned how the software would load balance the servers in the case of something happening like all of the players gathering in one corner of the map. Whereas in a typical system this might overload the server that was responsible for that portion of the map, the software would now spread out the load so that several of the servers would divide up the load for the one part of the map.
Seems to me that web serving would stay pretty balanced...no ONE server would suddenly have a spike over all the others, assuming the front-end load balancing was just cycling through the servers with each incoming request.
i don't agree with M$/BSA methods. but legally, they have the right, and there's not a real excuse to not follow the terms and conditions of a license if you are running a professional business.
You're right, and Mr. Ball wasn't disputing the fact that he wasn't in compliance. He was complaining about the way he was treated--armed marshalls knocking on the door and lots of negative publicity pushed by the BSA.
Nobody's arguing the fact that a license is a license, no matter how unfair it is. But as a business-to-business relationship, it would have been MUCH more beneficial for Microsoft to have first approached Ernie Ball outlining the problem and allowing them to correct it before showing up at their door with a warrant and pasting the raid all over the news. And that's all he's saying.
I know next-to-nothing about bluetooth, but what about security?
Would using bluetooth create a gaping security hole in your otherwise secure connection to your server? How easy would it be for somebody to monitor your keystrokes and snag your password from thin air?
what's to prevent me from simply removing the drive, placing it in another computer, and formatting it?
Maybe I'm missing something, but why would you want to do this? Wouldn't the point be to crack the encryption mechanism so that you could perform I/O on the system at will? What you're talking about sounds like paying $400 for a gaming console just so you can yank the hard-drive.
Re:Are you sure that is a good idea?
on
Real-World Hyperlinks
·
· Score: 2, Interesting
Good point, I'm sure every review will be "two thumbs up! WAYYYYY up!"
It would be a lot better if the product simply advertised what it is (instead of sending you somewhere). Then you could customize your cellphone/PDA with how to handle the incoming information. So assume they have a protocol where it reports what type of product it is (album, movie, whatever) along w/ info to specifically identify it, then you could set up your PDA to automatically visit your preferred movie review site(s), handing in the movie ID as a parameter.
But that might put way too much power in the hands of the consumer, and we want to avoid that if at all possible.
I still stand by my opinion that America's contribution was critical. Would the war have been won by the Allies anyhow? Maybe/probably/who knows, but by sending our men over there we either turned the tide or gave it more momentum, however you want to look at it. The American lives sacrificed were lives that other European nations didn't have to sacrifice.
And yeah, I didn't say our training was top dog, but I don't think we are trained to excel at friendly-fire. And the Fins, well...aren't they born with a rifle in one hand?
Of course, the British, Canadians and other had NOTHING to do with it. No sirree, there were only american troops fighting the Germans.
Granted it wasn't America alone, but it was America's contribution that was a critical turning point in WWII, and I don't think the half million soldiers who gave their lives should have their memories disrespected.
About the Marshall Plan, of course we didn't do it out of the kindness of our hearts. I'm not sure what kind of ideal world you live in where countries act out of pure kindness, but reality is that countries act in their own best interest. This shouldn't be suprising, and hardly seems to be worth mentioning.
The one thing you seem to excel at is shooting at your allies and own troops.
I would hardly say they "excel" at it, given the scope of the military operation executed, mistakes are going to happen. I would say we "excelled" at defeating those who opposed us (though this isn't my endorsement of it), and we have a lot of room for improvement on inter-/intra-military communication that will prevent future friendly-fire incidents. If our training is nothing to write home about, I'd be interested to know whose is.
The idea of "point of failure" is pretty scary, particularly given some of the issues the military already has had with some of it's standard issue gear. One would hope that a very prominent part of training would involve teaching the soldier to function without any computer-assistance--or possibly a worse case would be a malfunctioning computer (tourniquets tightening without injury, etc.).
At first the military would teach soldiers to be soldiers, and the gear would be supplementary, but it would most likely end up like every other technological advance. One day our soldiers are almost 100% reliant on the gadgets, at which point we are almost completely vulnerable to some sort of electronic attack that leaves us with a battlefield full of soldiers getting picked off like fish in a barrel because they have lost their technological crutch.
Yeah man, it was definitely a social event the night we caught it. If the people couldn't bring their friends or family with them, they sure as hell could have them call on their cell phone! I'm sure the caller was enjoying the movie vicariously through the movie-watcher, and I know we were all enjoying the incessant bleeps and burbles of cute little ring patterns.
And hey, don't let age be a factor in bringing that family. Got an infant!? Grab an extra diaper or two and bring 'em right in with you! After all, what infant wouldn't love special effects blasting at 1000 db with flashing explosions lighting up the room. They were absolutely screaming with joy!
Which is why Google is not eliminating them entirely, just moving them over to their own search.
It's a reasonable solution, I think. Is it worth tainting the vast majority of the search results with useless blog entries just so that the (very) few blogs with good information will still show up?
This solves their problem with bloggers manipulating search results, yet still keeps the information available to those who want it. Granted, you have to know to look for it, but it seems to me like a fair trade-off.
That argument only works assuming you have people in your company who actually have the skill to play with the source code. It seems that the longer I'm in this field, the more apparent it becomes that there are only a small number of people who actually know what's going on when they look at code, and maybe a smaller number who have actually have the skill to modify it to their needs.
but how much call will there be for a weapon that causes small, cauterized holes in people?
That was an interesting part of "Black Hawk Down" that didn't make it to the movie. One of the Delta guys was complaining about his Teflon-coated bullets against the "Sammies." They're made for penetrating armor, but when he was shooting human flesh they had a tendency to slip right in and right out, not causing the explosive damage you'd get with a more conventional bullet. He was commenting on how he could lay down a line of fire into a retreating group of people, and most of them would just keep moving, probably not even aware that they were getting punched full of holes as long as it didn't hit anything vital.
So that could well be a problem with lasers. A bullet fired accurately enough to hit the person can still cause a lot of damage upon penetration, but a laser might not do a whole lot unless it was an immediately fatal hit.
ChkRootKit will check for the known ones and some of the obvious signs for one.
Doesn't help much though if the user has developed something of their own that flies below the radar. Chkrootkit doesn't hurt for a bit of peace of mind.
Now there's an inspiring character. I remember reading those books as a pre-teen (usually in the "library") thinking, MAN, that guy hooks up with some HOT chicks! (or maybe they were rad back then, can't quite remember)
Seriously, that guy epitomized cool to me, I wanted to grow up and wear Ray-Bans everywhere and always be hooking up w/ big-breasted women. Fortunately, the 1st part isn't true. Regrettably, the 2nd hasn't happened.
Slashdot Mirror
Apparently IPv6 will solve all these problems, with a brand new standard that uses 64 bits.
Many, many applications work with IPv4 and assume that addresses will be 32 bit, not 64 bit (as IPv6 specifies).
That's a pretty glaring error, if we're talking about the same IPv6 spec.
You would need an enormous workforce to do that.
C'mon, give these guys some credit.
I'm willing to bet that if they lose their case, they sink like a rock. Investors will evaporate, and their reputation will be utterly destroyed. Once they're bankrupt, it's pretty much a guarantee that you won't get your money back before a lot of other people (or corporations rather) get their money first. So you could probably sue them, but I'm thinking you would basically be redirecting your time/money to /dev/null.
And while Snow Crash was almost non-stop hyperactivity (besides the occasional Sumerian culture educational interludes), I savored the action that much more in Diamond Age and Cryptonomicon. It didn't come across as indulgent, gratuitous action like it did in Snow Crash, it seemed to fit more into the story, which I found quite a bit more satisfying.
What's your point....are you saying the ISP should have sat on their arses until everyone had power again?
I re-read it. It still wasn't funny.
Maybe tonight when I'm in the outhouse staring at the wall it will suddenly become uproariously funny, but in the mean time I'm just going to have to assume that I was duped into reading a joke that just really wasn't funny.
What, "she" was a man?
Seems to me that web serving would stay pretty balanced...no ONE server would suddenly have a spike over all the others, assuming the front-end load balancing was just cycling through the servers with each incoming request.
You're right, and Mr. Ball wasn't disputing the fact that he wasn't in compliance. He was complaining about the way he was treated--armed marshalls knocking on the door and lots of negative publicity pushed by the BSA.
Nobody's arguing the fact that a license is a license, no matter how unfair it is. But as a business-to-business relationship, it would have been MUCH more beneficial for Microsoft to have first approached Ernie Ball outlining the problem and allowing them to correct it before showing up at their door with a warrant and pasting the raid all over the news. And that's all he's saying.
Would using bluetooth create a gaping security hole in your otherwise secure connection to your server? How easy would it be for somebody to monitor your keystrokes and snag your password from thin air?
Maybe I'm missing something, but why would you want to do this? Wouldn't the point be to crack the encryption mechanism so that you could perform I/O on the system at will? What you're talking about sounds like paying $400 for a gaming console just so you can yank the hard-drive.
It would be a lot better if the product simply advertised what it is (instead of sending you somewhere). Then you could customize your cellphone/PDA with how to handle the incoming information. So assume they have a protocol where it reports what type of product it is (album, movie, whatever) along w/ info to specifically identify it, then you could set up your PDA to automatically visit your preferred movie review site(s), handing in the movie ID as a parameter.
But that might put way too much power in the hands of the consumer, and we want to avoid that if at all possible.
And yeah, I didn't say our training was top dog, but I don't think we are trained to excel at friendly-fire. And the Fins, well...aren't they born with a rifle in one hand?
Granted it wasn't America alone, but it was America's contribution that was a critical turning point in WWII, and I don't think the half million soldiers who gave their lives should have their memories disrespected.
About the Marshall Plan, of course we didn't do it out of the kindness of our hearts. I'm not sure what kind of ideal world you live in where countries act out of pure kindness, but reality is that countries act in their own best interest. This shouldn't be suprising, and hardly seems to be worth mentioning.
The one thing you seem to excel at is shooting at your allies and own troops.
I would hardly say they "excel" at it, given the scope of the military operation executed, mistakes are going to happen. I would say we "excelled" at defeating those who opposed us (though this isn't my endorsement of it), and we have a lot of room for improvement on inter-/intra-military communication that will prevent future friendly-fire incidents. If our training is nothing to write home about, I'd be interested to know whose is.
At first the military would teach soldiers to be soldiers, and the gear would be supplementary, but it would most likely end up like every other technological advance. One day our soldiers are almost 100% reliant on the gadgets, at which point we are almost completely vulnerable to some sort of electronic attack that leaves us with a battlefield full of soldiers getting picked off like fish in a barrel because they have lost their technological crutch.
And hey, don't let age be a factor in bringing that family. Got an infant!? Grab an extra diaper or two and bring 'em right in with you! After all, what infant wouldn't love special effects blasting at 1000 db with flashing explosions lighting up the room. They were absolutely screaming with joy!
Well, on a positive note none of us would ever have the time to realize it had happened.
(reference)
It's a reasonable solution, I think. Is it worth tainting the vast majority of the search results with useless blog entries just so that the (very) few blogs with good information will still show up?
This solves their problem with bloggers manipulating search results, yet still keeps the information available to those who want it. Granted, you have to know to look for it, but it seems to me like a fair trade-off.
That argument only works assuming you have people in your company who actually have the skill to play with the source code. It seems that the longer I'm in this field, the more apparent it becomes that there are only a small number of people who actually know what's going on when they look at code, and maybe a smaller number who have actually have the skill to modify it to their needs.
Miss this ?
That was an interesting part of "Black Hawk Down" that didn't make it to the movie. One of the Delta guys was complaining about his Teflon-coated bullets against the "Sammies." They're made for penetrating armor, but when he was shooting human flesh they had a tendency to slip right in and right out, not causing the explosive damage you'd get with a more conventional bullet. He was commenting on how he could lay down a line of fire into a retreating group of people, and most of them would just keep moving, probably not even aware that they were getting punched full of holes as long as it didn't hit anything vital.
So that could well be a problem with lasers. A bullet fired accurately enough to hit the person can still cause a lot of damage upon penetration, but a laser might not do a whole lot unless it was an immediately fatal hit.
On reboot, it went through a traditional fsck routine, and rose like Lazarus.
Doesn't help much though if the user has developed something of their own that flies below the radar. Chkrootkit doesn't hurt for a bit of peace of mind.
Seriously, that guy epitomized cool to me, I wanted to grow up and wear Ray-Bans everywhere and always be hooking up w/ big-breasted women. Fortunately, the 1st part isn't true. Regrettably, the 2nd hasn't happened.