The tin-foil-hat crowd would probably also know how to disable any auto-patching. However, for the vast majority of Windows users, this would be a really, really good thing to have. To most of them, the computer is no different than a toaster or the cable box -- it just has to work. If that means little green guys inside the computer update it when needed, that's sufficient for most.
The reduction in spam and viruses alone would be worth the effort.
Re:can always get your /.
on
WiFi Gone Wild
·
· Score: 3, Funny
...stop off at mr. porclyn and/.
Well, that would explain some of the shitty moderation going on here lately...
(ObDisclaimer: No, I can't possibly go through the proof, even with my college education including what amounts to nearly a minor in Mathematics. Then again, I'm too far out of that loop and like many others, that which isn't used is doomed to atrophy. Truth be told, I do know that this is a breakthrough, but I haven't 1/100th of the knowledge remaining, nor 1/1000th of the time (aren't kids fun?) to go through it myself.)
Having 2 or more CPU's will only help you if your application has the ability to use them. If it's a single-threaded app, then you'll just be heating up your system case more than necessary for no gain.
OR Solaris x86. The fact that Sun has never actively marketed that offering (until recently with their new Sun Fire V60x/V65x/V20z servers) is one of the reasons that people don't seriously consider Solaris x86 as a viable platform -- Sun keeps wavering on their support of it. It looks like they're back on the bandwagon again now, but given their track record, who knows?
This is what they're up to. I've been pondering what it was that they've been doing over the past year or so with all these settlements of lawsuits, and now we see all these patents being granted -- they're going to bombard the USPTO in patent applications hoping that given the sad state of affairs there that a fair amount like this will be granted, regardless of any prior art.
Then, once a critical mass of patents have been built, they'll bury the US legal system and competitors in so much paperwork for patent infringement that neither the courts nor the defendant parties will be able to react. With patents in hand (legit or not), there's little that the courts can do to them for bringing frivolous lawsuits, and the people being sued won't be able to keep up with the sheer amount of litigation in either time or cost.
Then, once a sufficient amount of patent lawsuit success is obtained and precedents are set, they launch the blitzkrieg against IBM. What better way to fight a patent war than to have your own arsenal of battle-tested patents.
And while all this is going on, they'll be able to do just about whatever the heck they want, a la the bully days of the 90's. Gobble up companies, steal ideas, squelch OSS innovation due to FUD over whether or not a given product is free of proprietary code....it all makes sense....
Damn....it's just one of those things that is so obvious and so simple, yet so well hidden. It may be worth doing a lookup of pending patents with the USPTO to see what's coming up -- I'm guessing the backlog from Redmond is substantial.
This is so not true. My WRT54G has had an enable/disable toggle for SSID broadcasting included in the firmware since the day I purchased it about 18 months ago. Perhaps you're referring to an old version of firmware, but most anything purchased from Linksys since the WAP boom began has had this option.
Yes, this is only moderately critical because (a) the overwhelming majority of owners of these devices have them either directly or indirectly behind a NAT'ing cable modem or DSL connection, and (b) the "exploit" (if it can even be called that) is a known entity that any owner of one of these devices (myself included) should have realized the possibility of from day 1 and changed that password immediately, possibly before even connecting it to the cable modem.
This doesn't rate a critical or severe like the script kiddies' worms that keep coming out because short of installing a custom firmware version, there's not much that can be done with the device once owned other than to screw with its owner's networking.
You're absolutely right, and yet it will never happen. Why? It's the difference between a new Hummer H2 every six months and having to stick with the same 2004 model Land Rover purchased in September 2003 for another 3 months. I mean come on, think of the strain you're putting on these guys! To think that they wouldn't be able to afford the 4th beach house is just unspeakable! And what will people say when they show up at the yacht club with the same old 45' skiff they had two years ago! Blasphemous! Surely you wouldn't force them to use last years Callaway clubs when they are hobnobbing with Tiger at the AT&T Pro-Am...
And what's a home without the latest gear from Levinson, some Snell amps and pre-amps, and a great set of Wilson Watt Puppy speakers to play the......oh, um nevermind. Guess you'd actually have to enjoy listening to music to make that worthwhile....
Perhaps you didn't read that far into yesterday's thread where it was more or less said that the hardware will be indirectly sold via service and support contracts, much like your cellphone itself is free but the cost is recouped (several times over) in the form of your multi-year contract.
And now you know why Cisco bought out Linksys. Providing a $70 product that has the majority of the functionality of products that cost a minimum of 9x as much is cause for the big fish to get really worried about the saleability of their products.
My guess is that Linksys products will blink out of existence within the next couple of years.
The fact that ice hockey is being played at all in places like Tampa, Miami, and Phoenix, is definitely an indication that the apocalypse is coming. I mean, fer crissake, it's going to be 90 degrees in Tampa today and they're playing ice hockey there tonight!!!!
But the key is that there's no legal record of them being told they were wrong, nor any admittance of guilt. In essence, this protects them from setting precedent that can be used against them in a subsequent case for much larger damages.
It doesn't matter to the court whether the public opinion thinks they're guilty or not. And the only weapon the public has against actions like this is to not use the company's products, and we don't see that happening at all now, do we?
Actually, it's been said before, but they're not getting beat down here....they're settling all their open litigation. I'm not sure to what end this is progressing towards, but something tells me that Microsoft themselves is trying to clear all open cases against them so that they can gear up for something big.
I just can't put my finger on what they're up to...
Once again, the critical problem here is that you're all trying to solve a non-technical problem with a technical solution. There is usually only one effective way to remedy a social problem, which is to provide a social solution. This is the dividing line between what technology can accomplish (providing strong framework) and what management has to do in order to get people to follow their policies (positive/negative reinforcement).
It goes along the lines of the old corrupt cop routine...
Officer: Your headlight is broken. That's a $100 fine. Motorist: No it's not! It's working perfectly fine! [Officer smashes the left headlight] Officer: Want to make it a $200 fine?
Now couple that with stories of cops pinning drugs on undesirables, police brutality, sending innocent people to jail for crimes they didn't commit, politicians serving their own interests, corrupt judges, etc, etc, etc.....yes, we have an inate distrust of government, why do you ask?
This may be overly idealistic, but there is a simple solution to the problem -- vote them out. This country (contrary to popular/. opinion) is not a dictatorship.
The problem wasn't that the CSS settings didn't play well between the different browsers, but instead, Microsoft intentionally sent a set of broken CSS settings to browsers that identified themselves as Opera.
The author proved this by using wget with the user-agent strings set to emulate Opera, MSIE, and Netscape, and saved the output from the www.msn.com page for each user-agent. Content was indeed different for each user-agent, but the kicker was that the page returned for Opera contained a setting that forced it to display characters off the viewable page.
He further proved that it wasn't a bug in Opera by being able to both successfully display the msn.com pages retrieved for IE in the Opera browser, as well as to display the munged output retrieved for Opera in IE. In other words, the Opera-retrieved page for msn.com needed no tweaking other than what the IE-retrieved page received.
Given these results, I have a hard time believing that this is an honest mistake.
Space aliens implanted Linux into Linus as a trojan horse against humanity. After Linux becomes ubiquitous, our intergalactic "friends" will return to harvest our bodies for food.
Slashdot Mirror
The tin-foil-hat crowd would probably also know how to disable any auto-patching. However, for the vast majority of Windows users, this would be a really, really good thing to have. To most of them, the computer is no different than a toaster or the cable box -- it just has to work. If that means little green guys inside the computer update it when needed, that's sufficient for most.
The reduction in spam and viruses alone would be worth the effort.
...stop off at mr. porclyn and /.
Well, that would explain some of the shitty moderation going on here lately...
(ObDisclaimer: No, I can't possibly go through the proof, even with my college education including what amounts to nearly a minor in Mathematics. Then again, I'm too far out of that loop and like many others, that which isn't used is doomed to atrophy. Truth be told, I do know that this is a breakthrough, but I haven't 1/100th of the knowledge remaining, nor 1/1000th of the time (aren't kids fun?) to go through it myself.)
Having 2 or more CPU's will only help you if your application has the ability to use them. If it's a single-threaded app, then you'll just be heating up your system case more than necessary for no gain.
The PC can run Windows OR Linux
OR Solaris x86. The fact that Sun has never actively marketed that offering (until recently with their new Sun Fire V60x/V65x/V20z servers) is one of the reasons that people don't seriously consider Solaris x86 as a viable platform -- Sun keeps wavering on their support of it. It looks like they're back on the bandwagon again now, but given their track record, who knows?
I forsee http://patents.groklaw.net/ coming soon to a web browser near you....
No, not quite.....
3. Sue everyone else.
This is what they're up to. I've been pondering what it was that they've been doing over the past year or so with all these settlements of lawsuits, and now we see all these patents being granted -- they're going to bombard the USPTO in patent applications hoping that given the sad state of affairs there that a fair amount like this will be granted, regardless of any prior art.
Then, once a critical mass of patents have been built, they'll bury the US legal system and competitors in so much paperwork for patent infringement that neither the courts nor the defendant parties will be able to react. With patents in hand (legit or not), there's little that the courts can do to them for bringing frivolous lawsuits, and the people being sued won't be able to keep up with the sheer amount of litigation in either time or cost.
Then, once a sufficient amount of patent lawsuit success is obtained and precedents are set, they launch the blitzkrieg against IBM. What better way to fight a patent war than to have your own arsenal of battle-tested patents.
And while all this is going on, they'll be able to do just about whatever the heck they want, a la the bully days of the 90's. Gobble up companies, steal ideas, squelch OSS innovation due to FUD over whether or not a given product is free of proprietary code....it all makes sense....
Damn....it's just one of those things that is so obvious and so simple, yet so well hidden. It may be worth doing a lookup of pending patents with the USPTO to see what's coming up -- I'm guessing the backlog from Redmond is substantial.
This is so not true. My WRT54G has had an enable/disable toggle for SSID broadcasting included in the firmware since the day I purchased it about 18 months ago. Perhaps you're referring to an old version of firmware, but most anything purchased from Linksys since the WAP boom began has had this option.
Yes, this is only moderately critical because (a) the overwhelming majority of owners of these devices have them either directly or indirectly behind a NAT'ing cable modem or DSL connection, and (b) the "exploit" (if it can even be called that) is a known entity that any owner of one of these devices (myself included) should have realized the possibility of from day 1 and changed that password immediately, possibly before even connecting it to the cable modem.
This doesn't rate a critical or severe like the script kiddies' worms that keep coming out because short of installing a custom firmware version, there's not much that can be done with the device once owned other than to screw with its owner's networking.
You're absolutely right, and yet it will never happen. Why? It's the difference between a new Hummer H2 every six months and having to stick with the same 2004 model Land Rover purchased in September 2003 for another 3 months. I mean come on, think of the strain you're putting on these guys! To think that they wouldn't be able to afford the 4th beach house is just unspeakable! And what will people say when they show up at the yacht club with the same old 45' skiff they had two years ago! Blasphemous! Surely you wouldn't force them to use last years Callaway clubs when they are hobnobbing with Tiger at the AT&T Pro-Am...
And what's a home without the latest gear from Levinson, some Snell amps and pre-amps, and a great set of Wilson Watt Puppy speakers to play the......oh, um nevermind. Guess you'd actually have to enjoy listening to music to make that worthwhile....
Perhaps you didn't read that far into yesterday's thread where it was more or less said that the hardware will be indirectly sold via service and support contracts, much like your cellphone itself is free but the cost is recouped (several times over) in the form of your multi-year contract.
And now you know why Cisco bought out Linksys. Providing a $70 product that has the majority of the functionality of products that cost a minimum of 9x as much is cause for the big fish to get really worried about the saleability of their products.
My guess is that Linksys products will blink out of existence within the next couple of years.
The fact that ice hockey is being played at all in places like Tampa, Miami, and Phoenix, is definitely an indication that the apocalypse is coming. I mean, fer crissake, it's going to be 90 degrees in Tampa today and they're playing ice hockey there tonight!!!!
With the way things are going around my city lately, I think we'll see "Teach yourself English: Columbus Brookhaven High School" before long....
Yeah...they're called supermarket customer cards around here....
5,997,000 to go. Or thereabouts....
Quick math tells us that the last user will be sued in January 3335.
But the key is that there's no legal record of them being told they were wrong, nor any admittance of guilt. In essence, this protects them from setting precedent that can be used against them in a subsequent case for much larger damages.
It doesn't matter to the court whether the public opinion thinks they're guilty or not. And the only weapon the public has against actions like this is to not use the company's products, and we don't see that happening at all now, do we?
Actually, it's been said before, but they're not getting beat down here....they're settling all their open litigation. I'm not sure to what end this is progressing towards, but something tells me that Microsoft themselves is trying to clear all open cases against them so that they can gear up for something big.
I just can't put my finger on what they're up to...
Obligatory Wikipedia Fusion Power link.
Once again, the critical problem here is that you're all trying to solve a non-technical problem with a technical solution. There is usually only one effective way to remedy a social problem, which is to provide a social solution. This is the dividing line between what technology can accomplish (providing strong framework) and what management has to do in order to get people to follow their policies (positive/negative reinforcement).
Bomb, gas, crash, Afghanistan, airplane, fire, biowarfare, sarin, nuclear, Muqtada Al-Sadr, barbarism, CIA, Al-Qaida, terrorist, seize, drugs, fertilizer, kill, plot, chemical, RPG, bin Laden, canister, Iraq, plague, sniper, sleeper cell, C4, guerilla, Barbara Streisand
Now couple that with stories of cops pinning drugs on undesirables, police brutality, sending innocent people to jail for crimes they didn't commit, politicians serving their own interests, corrupt judges, etc, etc, etc.....yes, we have an inate distrust of government, why do you ask?
This may be overly idealistic, but there is a simple solution to the problem -- vote them out. This country (contrary to popular /. opinion) is not a dictatorship.
The problem wasn't that the CSS settings didn't play well between the different browsers, but instead, Microsoft intentionally sent a set of broken CSS settings to browsers that identified themselves as Opera.
The author proved this by using wget with the user-agent strings set to emulate Opera, MSIE, and Netscape, and saved the output from the www.msn.com page for each user-agent. Content was indeed different for each user-agent, but the kicker was that the page returned for Opera contained a setting that forced it to display characters off the viewable page.
He further proved that it wasn't a bug in Opera by being able to both successfully display the msn.com pages retrieved for IE in the Opera browser, as well as to display the munged output retrieved for Opera in IE. In other words, the Opera-retrieved page for msn.com needed no tweaking other than what the IE-retrieved page received.
Given these results, I have a hard time believing that this is an honest mistake.
Space aliens implanted Linux into Linus as a trojan horse against humanity. After Linux becomes ubiquitous, our intergalactic "friends" will return to harvest our bodies for food.
Cthulhu will not be pleased.