Bill Gates: Windows Patched Faster than Linux 679
petard writes "In a very interesting interview published by the Register, Bill Gates made several interesting claims about Longhorn. Many of them have been extensively covered recently, including plans to force users to patch automatically. Surprisingly, everyone seems to have overlooked his statement that Microsoft fixes bugs faster than Linux developers do. 'We've gone from little over 40 hours on average to 24 hours. With Linux, that would be a couple of weeks on average.' Either he's lying or woefully misinformed; their recent performance seems to be more on the order of 3+ months, or over 2000 hours."
Maybe? (Score:3, Funny)
*I* think he's referring to... (Score:3, Funny)
YA *I* think he's referring to... (Score:2)
Re:YA *I* think he's referring to... (Score:4, Insightful)
Also, to be fair, I suspect that few users immediately apply kernel patches in the Linux world. They wait until RH's up2date or Debian's apt-get sucks down the latest and greatest. A fair comparison should might say "Microsoft does not attempt to supply a 'rapid-release' patch for technical users at all, unlike the Linux community. However, it's time-to-Joe-end-user-release is comparable to that of Red Hat." or something along those lines.
I certainly feel that, at least applying the immediately obvious and most useful criteria, Microsoft does *not* fix bugs (release patches) more quickly than the Linux community.
Re:YA *I* think he's referring to... (Score:3, Interesting)
IIRC, I got my Debian SSH and Sendmail patches same-day. I have NEVER seen Microsoft even respond to a bug submission that fast, let alone release a working patch.
Re:YA *I* think he's referring to... (Score:4, Insightful)
Example: Today's Windows bug. Microsoft announced it today and patched it today. That's less than 24 hours to "fix" it.
This type of logic makes perfect sense to the PR or marketing departments.
- Tony
Re:YA *I* think he's referring to... (Score:4, Interesting)
The problem is, the bug may be discovered independently by some knowledgable crackers and taken advantage of for months while stolid MS works at its own pace to 'fix' the problem. (Which, incidentally, often a) doesn't fix the whole problem, or b) introduces other problems.)
Worse yet, when the user community doesn't have knowledge of a problem and a cracker does, the user, who may have been able to obviate the problem through another means (blocking RPC at the firewall, or whatever), is now left defenseless until MS gets around to telling them about the problem.
So if MS can keep everybody's mouth shut about the problem until it's ready to release the patch, of course they're going to have an incredible record for getting patches out quickly.
Re:YA *I* think he's referring to... (Score:2)
That was exactly my first thought.
given that this is currently a senstive Microsoft weak point, I'd be expecting at least a bit of coloring of the truth.
I've come to the conclusion that corporations advertise according to their weaknesses; e.g. Hyundai advertising their "dependability" when they are in fact the most unreliable cars I've seen, or any kids
Re:Maybe? (Score:3, Funny)
HINT TO BILL: Maybe hardly EVER needing a patch is a GOOD THING.
Re:Maybe? (Score:3, Interesting)
'cause I still haven't found one.
A question of need (Score:2, Funny)
Patching Faster vs. Patching Easier (Score:3, Insightful)
The reality is that no one can produce, however we have tried, a perfectly bugless software.
And there is no way we can be certain that our softwares don't have any unintentional vulnerability either.
Nobody likes software patches, but it is a necessity if we want to make our softwares work better.
The question is not how fast one makes the patch - although it's very important - the keypoint in making patches is how EASY we can make our patch-delivery system works.
No doubt that the Linux patches, at least
Re:Patching Faster vs. Patching Easier (Score:4, Informative)
Lying or Misinformed? (Score:2)
Re:Lying or Misinformed? (Score:2)
I vote for "Managing the truth" (Score:3, Informative)
In comparison, I've seen Linux fixes come out in less than 30 minutes. Likely having Linux hackers spanning all time zones helps a lot to improve bug fixing time. Report bug at 6pm, patch available 8am.
Re:Lying or Misinformed? (Score:3, Interesting)
I have set up Linux and Windows workstations in production environments. Hell, most of the people who use my Linux terminals are oblivious to what's running underneath, save that it is windows. Is it a drop in replacement for Windows: hell no. Can it work on a large scale: hell yes. Do you realize that certain design assumptions bu
'Fast' Bug Fixing (Score:3, Funny)
I wouldn't be surprised if MS does make pages in under 24 hours. But I bet the process looks like this.
- Microsoft notified about a problem.
- Notification email sits in Exchange server for a week due to problems with a corrupted mailbox.
- Flunky reads email, decides it would never happen in real life, demotes to low priority.
- MS Updates their problem tracking database. Issue is lost in the db move.
- Another flunky goes through and re-adds all the issues from emails.
- Smarter employee upgrades importance, flags it as 'do now!'
- Issue languishes for another few weeks.
- Vulnerability 'approved for fix!'
- Programmers fix it in under 24 hours.
- Patch enters testing queue.
- Patch is tested in an inadequate number of systems that all include only MS software an no 'unusual' configurations like, say, not using IE as default browser.
- Patch is sent to deployment team.
- Wait another week.
- Deployment team packages fix, places it on wu.ms.c.
- Fix breaks on many systems, system admins tear out hair, MS pats themselves on backs for their fine bug fixing system.
Myrddin.
Re:'Fast' Bug Fixing (Score:2)
Re:'Fast' Bug Fixing (Score:2)
When was it illegal to..... (Score:2)
Or when did it become not illegal??
Re:When was it illegal to..... (Score:2)
It's an error.
His Watch Crashed (Score:2, Funny)
Jon Stewart quote: (Score:2)
He's making an assumption... (Score:2)
Hmmmm (Score:2)
Progress (Score:2)
He's broadening his outlook (so to speak). I can remember a time when he couldn't think of any reason why you'd need more than 640K.
Re:Progress (Score:2)
Re:Progress (Score:2)
forcing patches? (Score:2)
Most Windows admins know that patches should be installed only when they are really needed, because M$ has a bad history of releasing patches that break systems instead of fixing them, Windows XP SP 1 is an example.
This doesn't sound good to me, unless they are willing to test their patches extensively before forcing users to install them.
Re:forcing patches? (Score:2)
hmm (Score:2)
Heh, so, 20 years from now, will we laugh at that like we do with the old quote "640K ought to be enough for anybody"?
Here's hoping to yes =)
Lies, damn lies, etc. (Score:2)
Long story short, I think the "windows-vs-linux" thing is a lot like "cars-vs-SUV's". Someone call someone else a Nazi so we can move on.
Hogwash (Score:2)
Microsoft is indeed very quick at fixing things after their corrupted servers have DDOS'd the rest of the Internet. Congratulations Microsoft!
As far as patches and updates go... (Score:2, Insightful)
I mean, after I install an average workstation of redhat 9.0 I see a lot more patches downloaded from up2date than the 36 or so for a fresh XP Pro install. Of course I mean for all the apps, not just core kernel stuff.
Minor version numbers for *nix packages seem to increase faster, which is a good thing because that means more holes getting patched faster [than Windows].
I guess my comment is that we need to see mor
Re:As far as patches and updates go... (Score:2)
Only a limited number of those patches will be security related. If you really want to see how many security patches have been released for a microsoft product, simply go to technet's security bulletin page [microsoft.com].
-Lucas
Linux the kernel or Linux the system? (Score:3, Interesting)
I havent really heard anything about Linux, really.
I have heard about the SSH issues, ect, but never about Linux. SSH, OpenSSH,ect. are just parts of a Linux system, or BSD for that matter.
has there actually been a Linux KERNEL exploit in the last few years?
and besides, when there is a Linux KERNEL exploit its fixed in hours, or minutes! I think it would be impossible for M$ to match that.
this article qualifies for more M$ Fud.
Re:Linux the kernel or Linux the system? (Score:5, Insightful)
When is the last time a vulnerability in the windows kernel was found? To be fair, we will include vulnerabilities in the HAL, since in Linux the kernel contains that functionality as well.
OpenSSH is a part of Linux as much as RPC or Windows Messaging is a part of Windows.
If a linux kernel exploit is fixed in minutes, then it was a pretty dumb bug. Microsoft has been good lately about doing proactive security reviews, and they often find holes before anyone else does. Linux mostly seems to do reactive fixes, at least from where I'm sitting. Which is to say, at a Windows XP machine, but right next to a gentoo Linux system.
Re:Linux the kernel or Linux the system? (Score:3, Interesting)
Wow, you mean theres no way at all I could run a box without OpenSSH? You should tell that to my workstation I'm writing this on right this second.
Sure, you can turn off RPC after you install windows, but I had Debian installed without any servers at all. Do you think you could log in and shut off RPC fast enough to avoid picking up a worm or two while on a network (like, say, when you register XP over the internet)? J
Re:Linux the kernel or Linux the system? (Score:2)
There have been local root compromises and remote DoS issues this year. I'm not sure about remote root compromises. (I've just patched the systems without trying to understand every single detail in security advisories.)
Dream on.
Nothing is as fast as /.'er ....... (Score:2)
Forced Patches? (Score:2)
Re:Forced Patches? (Score:2)
Re:Forced Patches? (Score:2)
Yep (Score:2)
Not only that, but most linux vulns get patched within a few hours.
Most of the time, I hear about the patch before I hear that there was ever a vuln. Contrast this with the 30+ known IE vulnerabilities that haven't been patched in years.
Go figure.
Then Stop Misinforming /. Readers Please (Score:2)
This is quite an odd assertation, as the link only details one security flaw, and only mentions the date it was discovered, not the date it was patched. Besides, it would be utterly incompetent (and dare I say malicious?) to draw a conclusion from one datapoint.
Re:Then Stop Misinforming /. Readers Please (Score:2)
Bah! The suits at Microsoft are running scared (Score:5, Interesting)
And if we follow Mahatma Gandhi's approach, the best approach is to keep doing what we do while letting MS bash away. Eventually it will become quite evident as to which side is interested in doing good for their fellow man.
Then and now... (Score:2)
Desperation... (Score:2)
Secure By Default (Score:2)
Blasphemy. Pure unadulterated blasphemy. Note, he says it's going to be important. All this time, and secure by default is now going
Who Solves Security Problems Faster? (Score:5, Informative)
Crispin
----
Crispin Cowan, Ph.D.
Chief Scientist, Immunix Inc. [immunix.com]
Immunix: [immunix.com] Security Hardened Linux Distribution
He was misheard (Score:2)
(though, truth be told, they generate more bugs than a 5-month-long New York City garbageman strike)
Amazing Windows Vuln Hasn't Been posted (Score:2)
Re:Amazing Windows Vuln Hasn't Been posted (Score:2)
Saying that they "still haven't fix that rpc hole" is like saying that they "still haven't fixed that windows hole".
The bug you are referring to exploits a defect the SMB (windows filesharing) authentication code. The previous two patches covered different problems inside of DCOM (ie: one was not related to the other, aside from the fact it was exploitable).
What are his start/end times? (Score:4, Insightful)
I'd like to know what part of the process he is talking about? Is that the time between when the hole is made public and when the patch is released? That would explain things a bit... since MS typicaly can keep the news under wraps until they release the patch simultaneously.
Including a lot of "0 seconds between bug announcement and patch release" is bound to give you a much lower average. So, it would be possible for MS to receive 85 bug reports, surpress all but one for three months, release 85 patches and average just a bit better than 24 hours between public announcement and patch.
IE (Score:2)
Half the products Microsoft produces are not patched at all and when 2000/XP are found to be lost causes to Microsoft's multiple security initiatives over the past years, products are just decommisioned.
Yeah, they patched all the holes in Win98 permenantly this year because it is no longer supported and end of lifed.
I still have patches comming in for my Linux 2.0.xx kernel!!!
-Hack
PS: Bill your doin serious weed man, you should stop that.
Longhorn PR speech. (Score:2)
Here we go again... (Score:2)
Didn't he make a statement like that a few decades ago? And wasn't he wrong? I figure that UIs in the future are going to need a LOT of RAM. In fact, this one VERY good voice recognition software that a company I'm dealing with has, requires a mimimum of 1 Gig of RAM just for their app. This is what makes it poerate so well. I'm sure there will be plenty of apps (especially in the UI
Who cares? Really. (Score:2)
Two or three years ago, when Linux was still struggling for widespread adoption and everyone still thought Microsoft was the greatest thing going in computing, this would have been a big deal. The press used to treat anything Microsoft said as the gospel truth, and were hugely skeptical of Linux. A comment like this from Gates would have meant a lot.
But now Linux has made huge inroads into the server market and is already beginning to penetrate the desktop
reminds me of.... (Score:2, Funny)
"What Americans? There are no American troops on Iraqi soil"
Also good to note that Linux patches have been kicking more ass than Windows EVER will, from back in the day with the port 139 "bug" (Linux patch was out within hours, Windows, took ALOT longer for obvious reasons) to any in the unforeseen future.
Hell...I think Ol' Gatesy is mistaken; bugs that are intentionally placed in software in order to patch and call it an upgrade, well....they don't count.
he's probably not lying... (Score:5, Insightful)
Microsoft is a big company, and Windows is a very complex beast. My initial thought is that perhaps the security developers do indeed code and submit a patch within 24 hours.
But then the patch has to wend its way through the labyrinth of QA and regression testing. Because Windows is so highly integrated, even small changes can have big unforeseen consequences, so they can't rush patches out the door without breaking things. I believe Microsoft makes patches available via their support pages well before it hits Windows Update. What *we* are measuring is the time from bug report to being in Windows Update; what *they* are probably measuring is time to patch submittal or time to initial availability via support.
I really, really prefer the improved code separation in the Unix environment; if, say, BIND has a problem or exploit, it's highly unlikely that a patch it will break Postfix or Apache. Because things are better-separated, the developers understand their packages better and can more confidently push patches into their stable branches.
I worry a little about the way the Unix desktops are becoming increasingly interdependent, with lots of libraries and lots of integration... are we going to end up in the same place, eventually? Microsoft doesn't employ idiots, and considering the amount of trouble they've had scaling, well.... I just hope the free software developers are thinking about this.
Re:he's probably not lying... (Score:2)
Linux is different in that its developers add features
Re:he's probably not lying... (Score:5, Interesting)
It's certainly being mismeasured by the Linux community. While I haven't done a thorough study, I make note of a Konqueror patch that came out last year.
- Linux community touted it as proof patches were fast, because it was into the source tree in 90 minutes
- It took one month before KDE released a new binary compiled with the patch
- It took an additional month before Redhat incorporated this into a patch for their Linux distribution.
The issue also impacted IE, and it took Microsoft two weeks to release a binary patch on Windows Update.
The Linux community claimed 90 minutes, when it was really two months.
Microsoft counted it accurately as two weeks.
Just reporting good news to yourself doesn't make you better.
Re:he's probably not lying... (Score:4, Funny)
- Linux community touted it as proof patches were fast, because it was into the source tree in 90 minutes
- It took one month before KDE released a new binary compiled with the patch
- It took an additional month before Redhat incorporated this into a patch for their Linux distribution.
The Linux community claimed 90 minutes, when it was really two months.
Or overnight for those of us using Gentoo.
Phillip.
We invented personal computing (Score:2)
God what a lying idiot he is! Apple, TRS-80, S100-systems, ABC80 (in Sweden), PET, C64, Amiga, Sinclair, etc. Plus many other that I haven't mentioned. All predates the PC. They didn't invent jack shit, they are just a bunch of shoddy cloners!
More modern GUI systems? Xerox! Mac! Microsoft don't invent. They clone, embrace, extend and extinguish, leaving the ground deserted and barren where they have passed by.
Wow what a bad liar (Score:2)
Maybe he was just talking about Conectiva (Score:2)
Take, for instance, the most recent, CLA-2003:762 [insecure.org], released October 14 for a glibc bug from August 14 [mitre.org].
My all-time favorite, however, is CLA-2003:628 [insecure.org], released in April 2003 for a vulnerability in vixie cron announced in March 2001 [mitre.org]!
So, if you count Conectiva, Gates is probably right about it taking a couple of weeks on average, even if everyone else does it in 24 hours.
760 days for Conectiva + 1 day each for 50 other distributions is about 16 days
Lying (Score:2)
Microsoft invented personal computing? (Score:2)
Bwa-ha-ha!
ISTR that Gates and Allen started Microsoft to offer products for the personal computers already in existence. To quote from the Microsoft Museum "Microsoft History Trivia" document, the appearance of the MITS Altair 8800 inspired Gates and Allen to develop a BASIC language for it.
Microsoft can't even be trusted to get their revisionist history straight.
Everyone's talking, but... (Score:3, Insightful)
But of course (Score:2, Funny)
Angry (Score:2, Troll)
It wouldn't be so bad I guess, if it was from some lowly person like me saying it off the cuff, but to hear it from that totally rich bastard Bill Gates say it, really makes my blood boil. He's made all his money on lies, deception and hoodwinkery!
The sad thing is that many people believe him, because he's rich -- not because he is correct.
Microsoft's approach to solving bugs is this:
1.
He also said ... (Score:2)
and
also
And many more [quotesandsayings.com] ...
You guys... (Score:2)
Funny thing is, this story was posted as an Anti-MS troll, and a lot of people fell for it.
Crediting MS Trolling (Score:3, Interesting)
You're right. Microsoft has gotten better. Whether they've caught up is a point for debate. But at least they have generally improved their reaction speed. Let's give credit where its due.
Now - issues such as ignored bugs, fundimental design flaws, non-patches, destructive patches, so-called Respo
Well of course (Score:2)
Today's vulnerabilities (Score:2)
Learn from the best (Score:2)
The bigger, and more outrageous the lie - the less people will question it's veracity. As long as proving that it's a lie takes more than 5 minutes, or involves logic that a typical American High School graduate can't grasp, you can say anything - and it's as good as truth.
Marketing (Score:4, Informative)
I recently was in a Microsoft webinar regarding patch management. If you are interested, or a glutton for punishment, this [microsoft.com] was it. At one point they showed a histogram on the screen that was intended to show vulnerabilities in operating systems and how MS was beating everyone on the planet. Major Microsoft products were all broken down by release, e.g. Windows 20003, Windows XP, Windows 2000, Windows NT, etc.. Linux and BSD were categorized by distribution only, e.g. Redhat, Debian, BSD etc...
Windows 2003 appeared at the far left with only a few vulnerabilities. Windows 2003 was actually the "winner". It even "beat" BSD! Now think about that histogram for a minute. It created false divisions that did an apples to oranges comparison. The sum total of Debian vulnerabilites likely refer to all released versions of a Debian distribution with all possible packages installed while Win2003 likely refers to only a Win2003 retail box installed with the bare minimum options.
Marketing is a black art. I have some personal experience, but NDAs to bind me. It's an art of trying to create and/or shape ideas in the mind of your customers, critics and competitors. The most successful marketing is that which makes them believe they came to the ideas you wish them to hold of their own volition.
Two quotes (Score:3, Funny)
Gates also doesn't seem to have a lot of faith in 64 bit technologies in the consumer space. "64 bit is coming to desktops, there is no doubt about that," he said. "But apart from Photoshop, I can't think of desktop applications where you would need more than 4 gigabytes of physical memory, which is what you have to have in order to benefit from this technology. Right now, it is costly."
---------
This coming from the same person who said 640kb is more then enough for anyone?
and this one
---------------
Gates is optimistic about meeting the challenge of the new security threats, he told reporters. "We have to. We invented personal computing. It is the best tool of empowerment there has ever been. If there is anything that clouds that picture, we need to fix it."
---------------
I thought apple invented personal computing?
Re:hahah (Score:2)
good point.
Re:M$ is fast (Score:2)
Bill, is that you? So you'd rather rely on a company whose track record in bug fixing is poor at best or on a community of developers whose track record is on the whole good and for some projects bordering on fantasmigorical.
It's all well and good to say that you would rather rely on a company to respond quickly but this just hasn't been the case in the past with Microsoft
Re:M$ is fast (Score:2)
Re:M$ is fast (Score:2)
Microsoft is still behind. By the time you've heard about it it's already too late.
Re:Lots of patches lately (Score:4, Insightful)
RPC vulnerability returns. AGAIN!!! (Score:3, Interesting)
And none of those updates covered the RPC vulnerability, again! That's right the Microsoft RPC vulnerability that has already been patched twice is STILL vulnerable [securityfocus.com] and an exploit exists. Word is that Microsoft has been informed but, as usual, no word from Microsoft yet. The notification was sent 10 days ago.
So much for 24 hour patches. On the other hand, I must admit that I have no desire to reboot my servers every 24 hours so, it's just as well that Bill isn't as fast as
Re:Someone RAM Bill (Score:2, Informative)
I know everytime this quote is used, someone has to debunk it, but there's no reason to perpetuate a false quote by one of the geniuses of our time.
Re:Someone RAM Bill (Score:4, Interesting)
Re:Someone RAM Bill (Score:2)
Re:Someone RAM Bill (Score:2)
Re:Someone RAM Bill (Score:5, Insightful)
It's not like revisionist history is a new concept. In 1981, I could completely see, Bill Gates saying the 640K quote, and have it taken out of context. One of the Watson's (of founding IBM fame, I can't remember if it was Sr, or Jr. I'm guessing Sr), once said that worldwide we'd probably only need 5 computers ever. It's not like he's terrible stupid either.
If you really want to have fun and games, write down a particular fact that you can't remember a specific event ever happening in your childhood. Now, store that piece of paper someplace safe. Now everyday imagine that event happening. Picture in your mind how you would remember it if it happened. Over the course of time, you'll "remember" it as a fact that is just like all of your other memories from childhood. You'll know it's inaccurate, but to your mind you can't tell between a the old true memories, and the newly fabricated memories. It's a simple form of brainwashing. I've specific memories that I know for a fact never happened. I constructed a conversation I never had once for the purpose of trying this out. It's the old adage about a lie repeated often enough becomes true.
I'll willingly admit it's entirely possible Bill never said that, and he surely can't prove he never said it. However, I'll never trust Bill's memory about him not saying it. However, if you tracked down the original references to it and debunk that, now you have something. Somebody has to cite it. It's in the Usenet Archives, or in old papers and trade magazines. Find the originals and debunk them, don't cite Bill saying 15 years later that he didn't say it. That's not debunking.
Here, I'll prove it to you. "I've done some stupid things, and I've done some wrong things, but I was never born. Nobody in the human race would ever say they were born.". Does that "debunk" the fact that I was born or not? I'd say my sitting here, and typing into slashdot is pretty strong evidence I was born at some point in the past.
A number of statistics have been proven to be false, but are cited all the time in the past. If you follow all of the original citations back, you'll find they all start at one single reference. The original person who stated it, either lied, or had something wrong with the way they came to the conclusion. By the time anybody figures that out, it'll be a "fact". I know this happened on stuff reguarding sexual orientation (formely common cited stat that 10% of all men are gay), and I believe it's happened on several other occasions about other commonly cited stats.
Debunking involves getting reasonable close to the source and debunking it. Not asking somebody 20 years later, who has a vested interest in not looking like an idiot, if he said something that's blatantly stupid 20 years ago. Read up on what Bill has said about what he thought of the internet.
I believe it was Cringely who pointed out that Bill always proclaims he was a visionary about the net, and saw ahead of everyone how much that could change the world. Yet when you read his book from that time where he was spouting off about what he thought was the next big things in computers, just as the internet went mainstream he never mentioned it once. Bill's in a position where he can't afford to say, I missed that huge new technology. He's Bill Gate's, he thinks Microsoft single handedly invented the Personal Computer. Just read the end of the article.
Kirby
Re:Someone RAM Bill (Score:5, Insightful)
In 1981, NOBODY needed 640k on the desktop. IBM PCs shipped with a tenth [computercloset.org] that amount of memory. Even assuming memory growth is exponential in the same manner as Moore's Law, this meant that the average user probably wouldn't need 640k for five years or more. Even in 1987, I remember programs (such as WordPerfect 4.2) that could fit on a single 360k floppy -- so the 640k prediction held for several generations of machine. Not a bad prediction in the computer industry.
There were good reasons for making the 640k assumption. All I'm saying is, don't fault an engineer for making a design decision, even if you don't like him personally.
Having said that, you want a desktop application that takes up more than 4 GB of physical memory? Go download the OpenOffice source and add a line:
calloc(4294967296,sizeof(char));
Take THAT, Bill!
Re:Someone RAM Bill (Score:2)
Virtual memory space is very important. I have 512mb of memory, but I want to be able to mmap(2) files that are several gig in size. I don't care that it doesn't all fit into memory at the same time, thats why we have virtual memory after all. But when programs ending up taking over 90% of their code managing mmap(2)'ing in the right regions of memory to do stuff, it's rediculous. If I had a 64bit machine, I'd have 90% less code, and 90% less bugs.
Consider editing large uncompressed images (
Re:True... (Score:2)
now, linux security bug is reported (wait 3hrs), most people already have the patch.
Re:True... (Score:2)
I'm not that heavy into Linux, but I do recall that the talk of the town was when the 2.4 kernel would come out. IIRC, it was delayed and delayed, but whe
Re:No knee jerk responses needed (Score:2)
Re:MS has a track record of lies and FUD (Score:2)
I've got news for ya, Slashdot has a track record for FUD raised about most MS stories.
Re:MS has a track record of lies and FUD (Score:2)
This happens when the average background noise of the media and propoganda stream spreads more lies than truth while society still agrees that its important to listen to this nonsense. (I'm talking television, radio, magazines, and advertisements) Just look at CNN and Fox,
Re:Forced patches? (Score:3, Interesting)
I think the original post is misleading. Gates didn't say anything about forcing updates. He said that by default they would be installed automatically. There was no mention of forcing that.
From the article: