01.18.09

Microsoft’s Jim Allchin: “I am Scared [of GNU/Linux]” (Analysts Cartel Part II)

Posted in Deception, FUD, GNU/Linux, Microsoft, Windows at 11:21 am by Dr. Roy Schestowitz

In Part III: How Microsoft Manufactures Statistics with Gartner|IDC

THIS IS the second part of a short series that began here. It reveals the ways in which IDC and Gartner interact with Microsoft [1, 2, 3, 4, 5, 6, 7].

Comes vs. Microsoft Exhibit PX07168 [PDF] from September 2002 shows why a ‘study’ against GNU/Linux is being manufactured.

Microsoft’s Jim Allchin, for example, states in this debrief that “we are not on a path to win against Linux” where he mentions (in point 6) the absolute necessity to “get a study done”. To quote in context, “We MUST get a TOC study done. Cost is a first thing on everyone’s mind right now given the economy and pressure on cost reduction. I am not sure what the final decision was on the IDC study. We REALLY need some here. I think billv/bob own this. If the IDC report won’t cut it, then we get another one done.”

Among those involved in this correspondence we find Paul Flessner, who wrote about Dell’s GNU/Linux dealings: “We should whack them, we should make sure they understand our value.” Brian Valentine is there too and so is Bill Veghte of the anti-GNU/Linux initiatives [1, 2, 3].

The subject of this discussion is — as plainly put in the subject line — “Linux”.

Jim Allchin on Novell

The quote above is very real by the way. Allchin is chanting about “Facts”, repeatedly (as in “Get the Facts”). Here is how it starts:

My conclusion: We are not on a path to win against Linux We must change some things and we must do it immediately. The current white papers, etc. are too high level and they are not going to cut it. Here are specific actions that I have concluded that we must take.

1. bill’s team must get a couple more hot resources assigned to it immediately who can do a tear down of Linux.

Jeff Jones (of Microsoft) has just had the IDC/IDG-owned magazines [1, 2] publish his security FUD. That was yesterday (an attack on Firefox) and here in this letter we find Allchin writing about the very same lies-based methodology that’s so often criticised (counting and aggregating all packages that are peripheral to the operating system):

3. We need a comparison of the security issues published from some place like CERT for Linux vs Windows 2000 or Windows XP. We need to be sure to count all the component pieces of Linux (e.g., apache, samba, navigator, etc.).

Then come more FUD about having to recompile applications in GNU/Linux:

4. We need the technical resource / strategy resource to look for fundamental issues about Linux that customers might not know. One that I thought of while on the trip that I used dealt with the fact you need to recompile your apps, etc when a new release of Linux comes out. I don’t think anyone wants to recompile their apps when they are running them in production, etc. I am sure if we put serious IQ to the situation we can think of many issues.

Check this patent FUD out:

5. We need someone to tear down the indemnification offered from RedHat and IBM to customers. We need to understand exactly the risk a customer is under if a patent lawsuit happens and Linux is challenged. I’d like Dan to own this. There MUST be risks to customers that are being passed on. I want this understood precisely. We need to get the license from IBM given to customers and investigate.

Here is an important bit:

6. We MUST get a TOC study done. Cost is a first thing on everyone’s mind right now given the economy and pressure on cost reduction. I am not sure what the final decision was on the IDC study. We REALLY need some here. I think billv/bob own this. If the IDC report won’t cut it, then we get another one done. Some customers know that Linux isn’t really free, but we need to help the other customers see this.

According to Allchin, “Customers are very disappointed (outright angry!) in how our apps interfere with each other.” They need to dig some dirt on GNU/Linux, so someone is assigned for the job.

8. We need a paper explaining how we do scale up. Linux is getting in some places based on the fact that customers are trying to scale up and they can’t run applications independently/safely on Windows. I will be writing mail about this separately. The paper would explain how to do it on Windows. Customers are very smart about the problems (eg., registry issues, lack of support from 3rd parties if more than a single app is running on the system (even though it works), etc.). We need a story here. I think this has to be someone as smart as davidds, I am not sure who should own this. It is possible that someone Iike blaing should do this. Maybe someone in Paulfle’s team can do it. We must address MSFT server products in this (e.g, sql, exchange, etc.). Customers are very disappointed (outright angry!) in how our apps interfere with each other.

Microsoft needs to manufacture some “quick facts” because, according to Allchin, “The paper [against GNU/Linux that] we have today as I said was laughed at in one place.”

10.. We need to put together a single short paper (just a couple of pages – maybe a single sheet) for a leave behind for customers of the 10 questions that they should consider before adopting Linux This should be based on the learnings we get from some of the items above and well as others that we find. These should be as hard hitting as we can be, BUT they need to be factual based, We should be thinking about howto put things like Red Hat’s server price In it to show where it’s going, etc, The paper we have today as I said was laughed at in one place. (I am not sure what one they had seen,) I think Billy needs to figure out who should own this I think someone like vlcg would be great.

Jim Allchin then admits that he is scared when he says under the subject line “Linux”:

I am scared.

The third and last part of this series will give most of the ‘beef’ of this story. The correspondence, in full, is below.


Appendix: Comes vs. Microsoft – exhibit px07168, as text


From: Jim Allchin
Sent: Friday, September 27, 2002 10:20 PM
To: Brian Valentine, Paul Flessner; Bill Veghte, Bob Kefly; Eric Rudder, Dan Neault
Cc: Michele Freed
Subject: Linux

I am travelling as you know. I have had many VAP round tables (both partner and not), met with many enterprise customers, had many roundtables with the field – both sales roundtable and technical roundtables. I also met with the US seminar group I have seen a tot of customers this week.

My conclusion: We are not on a path to win against Linux We must change some things and we must do it immediately. The current white papers, etc. are too high level and they are not going to cut it. Here are specific actions that I have concluded that we must take.

1. bill’s team must get a couple more hot resources assigned to it immediately who can do a tear down of Linux. This resources must help do the items I outline below together with other teams. I am not sure who might be best to assign here. Michele and I have been brainstorming and we don’t have a long list. One person that I think we could consider recruiting to help would be vicg. Another person might be brian hall. These guys aren’t super technical, but they are both good at distilling the essence and packaging stuff. Vic would be better than brian, but I wanted to throw both names out. I would only pick one of them. Just as importantly we need a kynl type of person – someone very technical. I insist that we find someone within a week and assign them on this for the next 2 months. I am not sure who to pick on the technical side. Once you read below I would like some suggestions. I think can be done in 2 months.

2. We need a paper which outlines technically how our system (kernel, web service, file server) is better. I think we have Mark R signed up to write this (robs was supposed to engage him on this). This paper needs to cover things like the facts that we have a preemptive kernel, asychronous I/O, etc Facts… that go to the core of why windows is different and Linux is old unix. Facts. I would have the technical person help with this. There was a technical wrlteup a few years ago by Mark in Windows NT Magazine. We need more on this.

3. We need a comparison of the security issues published from some place like CERT for Linux vs Windows 2000 or Windows XP. We need to be sure to count all the component pieces of Linux (e.g., apache, samba, navigator, etc.). This needs to be fact based. It should be short and sweet. A table would be great. I think Mikenash owns this.

4. We need the technical resource / strategy resource to look for fundamental issues about Linux that customers might not know. One that I thought of while on the trip that I used dealt with the fact you need to recompile your apps, etc when a new release of Linux comes out. I don’t think anyone wants to recompile their apps when they are running them in production, etc. I am sure if we put serious IQ to the situation we can think of many issues.

5. We need someone to tear down the indemnification offered from RedHat and IBM to customers. We need to understand exactly the risk a customer is under if a patent lawsuit happens and Linux is challenged. I’d like Dan to own this. There MUST be risks to customers that are being passed on. I want this understood precisely. We need to get the license from IBM given to customers and investigate.

6. We MUST get a TOC study done. Cost is a first thing on everyone’s mind right now given the economy and pressure on cost reduction. I am not sure what the final decision was on the IDC study. We REALLY need some here. I think billv/bob own this. If the IDC report won’t cut it, then we get another one done. Some customers know that Linux isn’t really free, but we need to help the other customers see this.

7. We need a paper (which we may already have) on the productively gains possible on with .NET development over php and j2ee. This must have examples of how productive development is, performance, and operational capability. Eric owns getting this down if it isn’t already.

MS-CC-RN 000001039342
HIGHLY CONFIDENTIAL


8. We need a paper explaining how we do scale up. Linux is getting in some places based on the fact that customers are trying to scale up and they can’t run applications independently/safely on Windows. I will be writing mail about this separately. The paper would explain how to do it on Windows. Customers are very smart about the problems (eg., registry issues, lack of support from 3rd parties if more than a single app is running on the system (even though it works), etc.). We need a story here. I think this has to be someone as smart as davidds, I am not sure who should own this. It is possible that someone like blaing should do this. Maybe someone in Paulfle’s team can do it. We must address MSFT server products in this (e.g, sql, exchange, etc.). Customers are very disappointed (outright angry!) in how our apps interfere with each other.

9. I think we need a paper on SFU and interop. Customers believe that unix systems are more compatible with each other and more interoperable, I was stunned at the number of customers who had no idea about what SFU could do, We must promote this much more. Billv owns ensuring this is done.

10.. We need to put together a single short paper (just a couple of pages – maybe a single sheet) for a leave behind for customers of the 10 questions that they should consider before adopting Linux This should be based on the learnings we get from some of the items above and well as others that we find. These should be as hard hitting as we can be, BUT they need to be factual based, We should be thinking about howto put things like Red Hat’s server price In it to show where it’s going, etc, The paper we have today as I said was laughed at in one place. (I am not sure what one they had seen,) I think Billy needs to figure out who should own this I think someone like vlcg would be great.

_________

I know there is a lot in this email, I am sorry. It is serious guys, The field does not feel supported by us. We are not giving them what they need to win

Bill/Paul: I need to ask you to take ownership of driving this ahead What I want to see is a package including ALL of these items that we can provide to the field within 2 months (MAX). I am scared. Again.. I want the two people assigned within a week. I want to know who the people are. Eric please help thinking about who the right people are. Please remember NO marketing. Facts. No anger toward Linux. Just facts. Please understand this isn’t up for discussion. I want some solid people assigned ASAP.

I would like a review in 1 month on the progress on this.

thanks,

jim

5/6/2005

MS-CC-RN 000001039343
HIGHLY CONFIDENTIAL


Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

This post is also available in Gemini over at:

gemini://gemini.techrights.org/2009/01/18/allchin-scared-of-gnu-linux/

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

5 Comments

  1. Paul Gaskin said,

    January 19, 2009 at 7:44 pm

    Gravatar

    That’s hilarious.

  2. paul (the unverified) said,

    January 20, 2009 at 10:02 am

    Gravatar

    Jim is really up on his “management speak.”

    This impresses me as though he has compiled a nice list of m$’s weakest points and all of their misinterpretations/misrepresentations re GNU/Linux.

    I do have to give him credit for one of his closing comments. “Please remember NO marketing. Facts. No anger toward Linux. Just facts.” I wonder if m$ really knows how to communicate like that though. I think that they’ve been pitching FUD for so long that nothing else can come out of their mouths. I imagine first they’ll mix up a new batch of kool-aid and then I guess we’ll see.

  3. Roy Schestowitz said,

    January 20, 2009 at 10:10 am

    Gravatar

    There’s more coming from Allchin in parts 4 and 5.

  4. Shane Coyle said,

    January 20, 2009 at 10:23 am

    Gravatar

    I love all of this stuff.

    We need a paper which outlines technically how our system (kernel, web service, file server) is better. I think we have Mark R signed up to write this (robs was supposed to engage him on this). This paper needs to cover things like the facts that we have a preemptive kernel, asychronous I/O, etc Facts… that go to the core of why windows is different and Linux is old unix. Facts. I would have the technical person help with this. There was a technical wrlteup a few years ago by Mark in Windows NT Magazine. We need more on this.

    Mark R? Russinovich? as in sysinternals that was bought up by MS and he was named a fellow or something a few years later?

  5. Roy Schestowitz said,

    January 20, 2009 at 10:26 am

    Gravatar

    Yeah! I thought exactly that when I read it.

What Else is New


  1. IRC Proceedings: Friday, March 05, 2021

    IRC logs for Friday, March 05, 2021



  2. Links 5/3/2021: Qubes OS 4.0.4 Release and Wine's Project Leader is Open to Wayland

    Links for the day



  3. How To Deal With Your Raspberry Spy -- Part II: Introduction

    Following Part I, published a few hours ago, let's examine what happened from a technical perspective and what can be done about it technically



  4. How To Deal With Your Raspberry Spy -- Part I: Acknowledgements

    March 2, 2021 blog post series from a guest author; for some background, see blog posts from Microsoft in the official blog of Raspberry Pi and our response to these



  5. German Decision on Unitary Patent/UPC Will Take Years (and It Doesn't Matter Because the Whole Thing is Dead Already)

    Kluwer Patent Blog's Dr. Bausch explains why the UPC is pretty much doomed, as it cannot be ratified any time soon and probably will never be ratified either (for a multitude of reasons, including Brexit)



  6. Techrights in Australia (IPFS and Gemini)

    Allies in Australia will help Techrights serve material from another server; we're still bettering ourselves for an era of oppressive World Wide Web



  7. Professional Troll Matthew Garrett Spreads Libel, Defamation and Slander About the Free Software Community to Entertain Microsoft and Friends

    After months of parking in our IRC channels to provoke and troll people (and try to collect 'dirt' from responses) the professional troll Matthew Garrett has been for many years shows his true colours again



  8. Links 5/3/2021: Linux 5.12-rc2 Imminent, Linux Lite 5.4 RC1 in Review

    Links for the day



  9. IRC Proceedings: Thursday, March 04, 2021

    IRC logs for Thursday, March 04, 2021



  10. Links 4/3/2021: LibreOffice 7.1.1, Cockpit 239, Many Stable Kernel Releases

    Links for the day



  11. Links 4/3/2021: Pardus 19.5 is Out and Free Software Foundation Gets Consulting Grant

    Links for the day



  12. IRC Proceedings: Wednesday, March 03, 2021

    IRC logs for Wednesday, March 03, 2021



  13. The Free Software Foundation Should Re-add Richard Stallman to the Board

    Dr. Richard Stallman is missed by many who perceive him to have been wrongly treated; putting Stallman back in the Board (at the very least) would help the image of the Free Software Foundation more than the newly-announced work with Community Consulting Teams of Boston



  14. Free Software Calling

    Fewer people are willing to "put up with the shit" given by so-called 'Big Tech', seeing that it's mostly about social control rather than enablement or emancipation



  15. Meme: EPO Management Totally Gets 'Tehc'

    The bestest patent office in the whole wide world is besting the “hey hi” (AI) cutting edge; don't worry about exam and certification integrity



  16. The EPO's Software Blunders Are Inevitable Outcome of Technically Clueless Management Which Grants Illegal Patents on Software

    The "clusterfuck" which the EPO has become is negatively affecting not only EPO staff but also stakeholders, who sink into depression and sometimes anger, even fury, at great expense to their health; this is how institutions die (for a quick but short money grab, a culmination of corruption which piggybacks half a century of goodwill gestures)



  17. Links 3/3/2021: OpenSUSE Leap 15.3 Beta, GNU Denemo 2.5, and NomadBSD 1.4

    Links for the day



  18. What Free Software Organisations Can Learn From Australia's Rape Crisis

    Reprinted with permission from Daniel Pocock



  19. Microsoft Weaponises (and Further Spreads) Racism to Distract From Its Own Incompetence (and 'Five Eyes' Collusion for Back Door Access)

    Racist Microsoft is at it again; we're meant to think that China is evil for doing exactly what the United States has been doing but more importantly we're told not to blame Microsoft for shoddy code and back doors (classic blame-shifting tactics and overt distortion of facts, as we saw in the wake of SolarWinds backdoors)



  20. GNU/Linux News Sites Need to Promote Software Freedom, Not Binary and Proprietary Blobs Merely Compiled for GNU/Linux

    There has been lots of proprietary fluff in GNU/Linux 'news' sites so far this week; it merits an explanation or clarification, e.g. why we should generally reject proprietary stuff and instead promote Free/libre alternatives



  21. Links 3/3/2021: OpenSSH 8.5 and Absolute64 20210302 Released

    Links for the day



  22. IRC Proceedings: Tuesday, March 02, 2021

    IRC logs for Tuesday, March 02, 2021



  23. Links 3/3/2021: IPFire 2.25 Core Update 154, Red Hat Satellite 6.8.4, Kiwi TCMS 10.0

    Links for the day



  24. Links 2/3/2021: KDE Plasma 5.21.2, Qt 6.1 Beta, Refund of Pre-installed Windows

    Links for the day



  25. 'GatoKeeper'/IP Kat (AstraZeneca) Still Suppressing and Censoring the Public Views or Internal EPO Talks About EPO Corruption

    The suppression of comments critical of the EPO‘s administration (especially corruption scandals surrounding António Campinos and Benoît Battistelli) is a real problem; those ought not be a taboo subject in comments (where bloggers used to speak about those issues openly and regularly)



  26. Pocock on Removing Cognitive Bias Around Consent

    Reprinted with permission from Daniel Pocock



  27. IRC Proceedings: Monday, March 01, 2021

    IRC logs for Monday, March 01, 2021



  28. Links 2/3/2021: Maui 1.2.1, RSS Guard 3.9.0

    Links for the day



  29. ZDNet Really Hates Golang (Maybe Because Microsoft Does)

    The Golang programming language seems to be the target of intense FUD campaigns from sites connected to Microsoft, so it’s likely a bit of a Nemesis/endgame to Microsoft monoculture (unlike Rust, which Microsoft has already pocketed and is actively besieging to promote Microsoft monopoly and hardware monoculture)



  30. Links 1/3/2021: KStars 3.5.2, ET: Legacy 2.77, Flameshot 0.9

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts