10.25.07

Microsoft and Novell Work in Isolation to Weed Out Common Threat (Free Linux)

Posted in Boycott Novell, Europe, GNU/Linux, Intellectual Monopoly, Interoperability, Microsoft, Novell, Patents, Protocol, Red Hat, Servers, Virtualisation at 8:48 pm by Dr. Roy Schestowitz

Not much is new under the sun. Microsoft has a plan and Novell plays along happily, so long as it is rewarded financially and offered exclusive rights, at the expense of all other Linux distributions.

Here is what Novell had to say about Microsoft’s latest attempt to pretend to have ‘opened up’.

“The majority of our customers have mixed-source environments, and they want their platform vendors to make things work together,” said Roger Levy, senior vice president and general manager, Open Platform Solutions at Novell. “That’s why we entered into a technical collaboration agreement with Microsoft. As a result, Novell is the first vendor to develop and ship technology that will allow a paravirtualized Windows Server 2008 to be hosted as a guest on the Xen hypervisor. Microsoft’s decision to put the hypercall API under their Open Specifications Promise will make it even easier for Novell, our customers and partners, and the entire open source community to develop high-quality virtualization solutions that deliver true interoperability between Windows and Linux.”

Did you spot that bit about “hypercall API” and “Open Specifications”? Guess what? As usual, it contains anti-GPL poison. It is the old trick that involved licensing, which is part of the plan to block those that do not comply with Microsoft’s rules and assimilate.

This one particular issue was not entirely overlooked by Joe Wilcox over at Microsoft Watch.

Microsoft’s decision to license the hypercall API is the right call, although some pundits and competitors might balk at the licensing scheme.

If you think it’s just this hypercall, then think again. Reuters has just published a detailed list of Microsoft patented protocols, which brings back to mind the terms of the agreement in Europe [1, 2].

Microsoft will release interconnection information — called protocols — which rival servers need in order to work smoothly with Microsoft Windows desktops.

It is worth repeating the key argument that Microsoft wants to charge money for standard protocols which is deliberately ‘extended’ with the sole intention of breaking compatibility. It wishes to be rewarded for abuse of standards and sabotage of intercommunication among servers.

Red Hat, which is watching this type of worrisome developments from afar, responds with understandable concern.

While Red Hat welcomed Microsoft’s recent decision to comply with the European Court of First Instance’s antitrust ruling, Michael Cunningham, general counsel for Red Hat, stated that the company was still concerned about Microsoft’s patent model.

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

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

8 Comments

  1. Yuhong Bao said,

    December 15, 2007 at 10:44 pm

    Gravatar

    So, should Red Hat try to implement the spec? Probably not yet, but what if Windows Server Virtualization become common?

  2. Roy Schestowitz said,

    December 15, 2007 at 10:56 pm

    Gravatar

    This contains ‘GPL poison’, so it’s merely a tool (bait) to make Linux companies fall for patent deals.

  3. Yuhong Bao said,

    December 15, 2007 at 10:58 pm

    Gravatar

    What GPL poison? and if Windows Server Virtualization become common, should Red Hat still try to implement it?

  4. Yuhong Bao said,

    December 15, 2007 at 10:59 pm

    Gravatar

    In other words, how severe is the GPL poison?

  5. Yuhong Bao said,

    December 15, 2007 at 11:01 pm

    Gravatar

    I wonder what if every Linux vendor assimulated?

  6. Roy Schestowitz said,

    December 15, 2007 at 11:48 pm

    Gravatar

    What GPL poison?

    “GPL poison” usually refers to a case where Microsoft deliberately makes its licence/software incompatible with the GNU GPL licence.

    and if Windows Server Virtualization become common, should Red Hat still try to implement it?

    For hypercalls to be implemented, money needs to be paid. Again, you can probably see a separator between free and commercial. There is no good reason to do this, other than to betray Free software and ensure that only companies can deliver a particular solution.

    Companies can be crushed, unlike communities. A year or two ago, Steve Ballmer made a statement that suggests he wants to ‘encapsulate’ GNU/Linux in a company such as Novell, which he can then crush (along with GNU/Linux).

    In other words, how severe is the GPL poison?

    It’s severe enough to make a Free Linux secondary and incomparable with ‘commercial-grade Linux’ (not free). It’s establishing a different situation for TCO comparisons.

    I wonder what if every Linux vendor assimulated?

    That won’t happen any time soon. Red Hat controls a majority of the server market. Novell got together with Microsoft only because it was desperate to get a dent in Red Hat’s dominant position and dethrone it. Novell failed.

    On the desktop, Ubuntu variants seem to have become very popular. Ubuntu’s founder has openly described Microsoft’s action as ‘mafia techniques’ and ‘racketeering’. Needless to say, he is not willing to fall for this whole patent scam. The same goes for Mandriva.

  7. Yuhong Bao said,

    December 15, 2007 at 11:51 pm

    Gravatar

    But what specific poison are you talking about? And indeed I hoped that full assimation would not happen, I was just wondering what if it did happen.

  8. Roy Schestowitz said,

    December 16, 2007 at 12:17 am

    Gravatar

    Oh, I apologise for missing the actual question you had in mind. Here is an item that speaks about the licensing route (think Samba/CIFS).

    Licensing may be a sticky point for some third parties interested in licensing the hypercall API. Microsoft will release the API, at no cost, under its Open Specification Promise, which makes a pledge not to sue anyone using hypercall. Promise not to sue isn’t exactly a feel-good licensing term for perceived or real Microsoft competitors. Microsoft’s focus is customers and loyal partners, anyway.

    At a second glance, there’s no cost involved, but there ought to be concerns about the pledge which is similar to OOXML’s pledge that isn’t sufficient to calm one’s mind. Also mind an item where we explained this further. Paula’s item explains why Red Hat might suffer and I haven’t much hope for distributions like Debian in that regard. The notion of API licensing, patents, and promises not to sue should raise flags.

What Else is New


  1. Links 22/1/2021: pfSense Plus, Endless OS Foundation, and Many Laptops With GNU/Linux

    Links for the day



  2. The Linux Foundation is Trying to Obscure Racism Using Microsoft-Inspired Tactics (Vouchers Disguised as Actual Money)

    The Linux Foundation and its PR stunts don’t help combat racism; one might argue that the Foundation is leveraging racism, which prevails in the US, to paint itself as benevolent and caring (offering immaterial things and self-serving press releases)



  3. InteLeaks – Part XXVII: 'Pulling a Nokia' on Intel (Outsourcing to Microsoft)

    The recommendation of an Intel marriage with Microsoft (even in units that deal mostly with Linux) is an insulting slap across the face of developers employed there; we take a look at recommendations made to IoTG (Intel) by a firm with Microsoft orientation



  4. IRC Proceedings: Thursday, January 21, 2021

    IRC logs for Thursday, January 21, 2021



  5. InteLeaks – Part XXVI: Harbor Research is Horrible 'Research', Lacking Actual Technical Background

    Having looked at the members of staff of Harbor Research (individually), it seems clearer now why they have an affinity for Microsoft and why they're directing Intel to liaise with Microsoft and become a prisoner of Microsoft (even in areas where Microsoft is increasingly irrelevant)



  6. Links 21/1/2021: Raspberry Pi Pico, Ubuntu 21.04 Picks GNOME 3.38, KDE Plasma 5.21 Beta

    Links for the day



  7. How a Newly Inaugurated President Biden Can Advance Software Freedom (If He Actually Wishes to Do So)

    Techrights has 'Four Suggestions' to President Biden, the 46th 'front end' of American plutocracy



  8. InteLeaks – Part XXV: Intel's Brain Drain Leads to Unusual Measures

    As the company once known as 'chipzilla' loses its relevance and dominance in the market it's reaching out to retired people, trying to get them back onboard



  9. Hey Hi (AI) is Just a Trojan Horse for Illegal Software Patents, According to EPO Management and Litigation Firms It's in Bed With

    The longtime pushers or the lobby of patent profiteers just carry on pushing for software patents, nowadays latching onto the inane and unwarranted media hype around Hey Hi (AI) — a hype wave that was co-opted by EPO management to grant unlawful patents



  10. The Central Staff Representatives (CSC) of the EPO Are Petitioning to End the Assault on EPO Staff

    The EPO, just one month after the staff went on strike, is about to receive a compelling petition to stop the assault on EPO staff



  11. InteLeaks – Part XXIV: Love for Microsoft, Not for Free Software or Whatever Replaces Microsoft

    Intel is basing its big decisions on buzzwords and firms that master buzzwords; it's sad that instead of listening to Intel's own (in-house) engineers it's relying on a bunch of clowns who push 'Clown Computing' and 'apps' and 'UX'...



  12. IRC Proceedings: Wednesday, January 20, 2021

    IRC logs for Wednesday, January 20, 2021



  13. Links 21/1/2021: Google Tightens the Screws on Chromium, VideoLAN VLC 3.0.12

    Links for the day



  14. IBM Panics and Resorts to 'Customer Retention' Tactics With Red Hat Enterprise Linux (RHEL)

    IBM 'frees' RHEL but with limitations that can restrict growth of small companies (or subject them to financial barriers, originally unforeseen)



  15. Recent Techrights Articles About President Joe Biden

    Instead of writing yet more stuff about the latest US president, let's look back at what we wrote in recent weeks/months



  16. Links 20/1/2021: LibreOffice 7.1 RC2 and the RHEL Contingency

    Links for the day



  17. InteLeaks – Part XXIII: Intel Paying for Bogus 'Research' 'Insights' Which Merely Seek to Justify Outsourcing to Microsoft and Imposing Microsoft's Proprietary Software on Free Software Developers

    Intel's preference for Microsoft monopoly (an imposed/top-down decision) was seemingly certified by so-called 'consultants' and 'analysts' from the outside rather than the inside, basically manufacturing a false perception of consent after managers had already made up their minds



  18. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part V: How FSF Secrecy Ended Up Insulting People, Alienating Trans Developers

    Having just uploaded this introductory video, we delve into the backstory or the real reason the FSF sank into somewhat of a crisis with the trans community almost half a decade ago



  19. InteLeaks – Part XXII: Bubbles and Buzzwords, No Substance at Intel's Internet of Things (IoT) Group (IOTG)

    The video above is continuation of the previous part about a document full of superficial buzzwords (not technical jargon anywhere), in effect recommending to managers that they blindly follow trends and cargo cults (such as Clown Computing) and not what’s most suitable for technical excellence



  20. IRC Proceedings: Tuesday, January 19, 2021

    IRC logs for Tuesday, January 19, 2021



  21. Links 20/1/2021: WireGuard for pfSense and New US President

    Links for the day



  22. Links 19/1/2021: Krita 4.4.2 Released and JingOS Hype

    Links for the day



  23. Team UPC Keeps Pretending That UPCA Can Still be Resurrected (Even Without the UK, Which is Strictly a Requirement)

    The latest distortion of facts regarding the Unified Patent Court (UPC) Agreement (UPCA) as seen from the lens of people who seek to profit from such distortion



  24. 'Ethical Source' is Not Ethical and Not a Movement But a Misguided Self-Serving PR Stunt

    Something which is neither enforceable nor ethical is being promoted by profoundly unethical media in the pockets of large corporations



  25. InteLeaks – Part XXI: Intel Seeking Advice From a Bunch of Clowns (Harbor 'Research')

    A firm called Harbor 'Research' is making dubious recommendations to Intel; as shown in the above video, there's also an obsession with buzzwords (typically suggestive of a lack of technical grasp/understanding)



  26. IRC Proceedings: Monday, January 18, 2021

    IRC logs for Monday, January 18, 2021



  27. The US Election Was Not Rigged, But the Nomination Process Was (Undermined to Maintain Control by Oligarchy)

    Cheating/driving the left out of the Democratic Party seems like a longstanding tradition and we know who stands to gain from it; moreover, problems remain in the voting process because it's controlled by secret code of companies like Microsoft (in spite of the openwashing)



  28. InteLeaks – Part XX: Redacted (for Names Only) Release of Intel File About Developer eXperience (DX) Meddling in GNU/Linux

    Today (or tonight) we release the first 'phase' of InteLeaks in a sensibly redacted form; coming up next is a surprise from Team Microsoft



  29. Sites in Bed With the EPO and UPC 'Covering' the 'News' Without Mentioning Any of the Overt Abuses

    It is rather sad that blogs like IP Kat have turned into proponents of abusive EPO management and Team UPC increasingly resorts to lying using pseudonyms (to avert criticism and accountability); much of the rebuttal or response that’s hinged on reality/facts can only be found in comments, which are still subjected to a face-saving moderation process (conducted by Team UPC)



  30. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part IV: Stories From the Depths of the Free Software Foundation (FSF)

    To reduce or alleviate suspicions and a potential of mistrust the FSF needs to become more transparent and liberate information (such as the real reason Bradley Kuhn left, as noted in the previous part)


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