Language Selection

English French German Italian Portuguese Spanish

M$ Patent Deal - Who's Next?

Mandriva
40% (291 votes)
Red Hat
10% (74 votes)
Ubuntu
13% (97 votes)
Knoppix
2% (11 votes)
Mepis
4% (27 votes)
Gentoo
1% (8 votes)
Slackware
1% (8 votes)
PCLOS
7% (53 votes)
No one
21% (150 votes)
Total votes: 719

Re: Ubuntu forces you to add Microsoft codecs on your own time.

There is not no need for adding the MS win32codecs.
Xine ( without the win32codecs ) can play all formats proprietary and free apart from real media.
If you want real media support, you can always download the realplayer for Linux from realnetworks.

I think that the following

I think that the following are imposible to have a deal with M$:

Red Hat(they have already said no)
Ubuntu(the community is huge, that Ubuntu is 99.9% based in community)
Slackware(too old xD)

more on patents

How about - Oracle Unbreakable Linux?

//just kidding!

My votes on Mandriva, since there really is no sense going after non-commercial distro's

my vote went to mandriva as

my vote went to mandriva as well, there'd be no sense in going after something like knoppix or slack, which in my opinion is the best distro of all time, mandriva would prolly be the next to be attacked

Patents.

It is obvious that Slackware, Ubuntu , PCLinuxOS and Gentoo will never do this. In fact even MS will not agree to make a agreement with those distribution.

Redhat won't do this because of "principle" reasons.

Only big commercial distributions like Mandriva are likely to make an agreement with MS.

re: Patents.

Yep, I agree. Red Hat would never sign. Gentoo is almost a "specialty" system with a niche userbase... I don't think they'd be asked. Slackware might be asked, but I'm not sure they are "commercial" enough. But then on the other hand, Microsoft might need a Slackware or Debian to validate their claims - which will never happen. PCLOS is too small and not commercial - they'd never be asked. Mepis is a candidate, and hmmm, they'd might be tempted. I think Mandriva is the most likely candidate. Commercial and struggling financially and at one time, top of the game. And I bet if they were offered a big payday, they'd take it too.

EDIT: SJVN seems to think it will be Ubuntu, for some valid reasons. He just might be right. So, as of his story breaking, Mandriva stands at 33 and Ubuntu has 9. Let's see if his article turns the tide.

The microsoft way

This like to be the microsoft way to open source: to pay so Linux can use ms software without problem.
The ms quality in Linux?

More in Tux Machines

Samsung Leftovers

OSS Leftovers

  • FOSDEM 2018 Real-Time Communications Call for Participation
  • Top Bank, Legal and Software Industry Executives to Keynote at the Open Source Strategy Forum
  • Copyleft is Dead. Long live Copyleft!
    As you may have noticed, we recently re-licensed mgmt from the AGPL (Affero General Public License) to the regular GPL. This is a post explaining the decision and which hopefully includes some insights at the intersection of technology and legal issues.
  • Crowdsourcing the way to a more flexible strategic plan
    Trust the community. Opening a feedback platform to anyone on campus seems risky, but in hindsight I'd do it again in a heartbeat. The responses we received were very constructive; in fact, I rarely received negative and unproductive remarks. When people learned about our honest efforts at improving the community, they responded with kindness and support. By giving the community a voice—by really democratizing the effort—we achieved a surprising amount of campus-wide buy-in in a short period of time. Transparency is best. By keeping as many of our efforts as public as possible, we demonstrated that we were truly listening to our customers and understanding the effects of the outdated technology policies and decisions that were keeping them from doing their best work. I've always been a proponent of the idea that everyone is an agent of innovation; we just needed a tool that allowed everyone to make suggestions. Iterate, iterate, iterate. Crowdsourcing our first-year IT initiatives helped us create the most flexible and customer-centric plan we possibly could. The pressure to move quickly and lay down a comprehensive strategic plan is very real; however, by delaying that work and focusing on the evolving set of data flowing from our community, we were actually able to better demonstrate our commitment to our customers. That helped us build critical reputational capital, which paid off when we did eventually present a long-term strategic plan—because people already knew we could achieve results. It also helped us recruit strong allies and learn who we could trust to advance more complicated initiatives.
  • Reform is a DIY, modular, portable computer (work in progress)
    Want a fully functional laptop that works out of the box? There are plenty to choose from. Want a model that you can upgrade? That’s a bit tougher to find: some modern laptops don’t even let you replace the RAM. Then there’s the Reform. It’s a new DIY, modular laptop that’s designed to be easy to upgrade and modify. The CAD designs will even be available if you want to 3D print your own parts rather than buying a kit. You can’t buy a Reform computer yet. But developer Lukas Hartmann and designer Ana Dantes have developed a prototype and are soliciting feedback on the concept.
  • New neural network teaches itself Go, spanks the pros
    While artificial intelligence software has made huge strides recently, in many cases, it has only been automating things that humans already do well. If you want an AI to identify the Higgs boson in a spray of particles, for example, you have to train it on collisions that humans have already identified as containing a Higgs. If you want it to identify pictures of cats, you have to train it on a database of photos in which the cats have already been identified.

Ubuntu Leftovers

Server: MAAS, OPNFV, 'DevOps', and Docker

  • MAAS KVM Pods
    OpenStack is the dominant solution in the IaaS space, fueled by the need for reliable, scalable and interoperable private cloud infrastructure to accommodate cloud native applications. Through OpenStack’s open APIs, tenants can easily deploy elaborate virtual (overlay) networks, integrate with a variety of storage backends, even leverage modern hypervisor-like machine containers (LXD) for bare metal performance. Although the tooling allows a full fledged OpenStack deployment on just a single machine, the intrinsic efficiencies that OpenStack’s design promises, materialize at a certain scale — typically at least 12 servers.
  • DevOps for NFV: OPNFV Infrastructure and Continuous Integration
    In this article series, we have been discussing the Understanding OPNFV book. Previously, we provided an introduction to network functions virtualization (NFV), discussed the role of OPNFV in network transformation, and looked at how OPNFV integrates and enhances upstream projects. We continue our series with in-depth insight into the OPNFV DevOps toolchain, hardware labs, continuous integration (CI) pipeline, and deployment tools (installers) from chapters 6 and 7 of the book.  
  • A Chat with Chef about the DevOps Movement and Habitat Builder
    Last week at our annual user conference, Node.js Interactive, we announced several new members to the Node.js Foundation. One of the members that joined is Chef. Chef works with more than a thousand companies around the world to deliver their vision of digital transformation. We sat down with the team at Chef to talk about how Node.js fits within the DevOps movement, why they joined the Node.js Foundation, and also about a new offering from the group called Habitat Builder.
  • Why Use Docker with R? A DevOps Perspective
    There have been several blog posts going around about why one would use Docker with R. In this post I’ll try to add a DevOps point of view and explain how containerizing R is used in the context of the OpenCPU system for building and deploying R servers.
  • Docker on Docker at DockerCon EU 17
    Docker Inc. the company behind the open-source Docker container technology doesn't just build docker, it also used the same technology to power its own services.