I'm not convinced this is EEE, but it's hardly impossible: They start adding features that only make sense in a MS world (hyper-v drivers, secure boot improvements, package Linux as an "app" (WSL2)), then market their take on the stack to anyone using normal distros (leveraging buy-in to the MS ecosystem, low costs, and good support) to remove the contributors and money that would have supported the existing ecosystem (i.e. steal suse/Ubuntu/RH customers). As a result, fewer people build the things that would let Linux compete with MS, and anything without their backing bitrots. "Linux" remains, as a server OS (preferably on Azure) and as a compatibility layer in WSL2, but without drivers for new laptop/desktop hardware or GUI development it's just another component under NT.
Or, if you just don't believe a single company can control the ecosystem, go build a Linux system with no userland code from Red Hat and let us know how it goes.
> go build a Linux system with no userland code from Red Hat and let us know how it goes.
This is why I'm having trouble seeing the EEE connection. It's incredibly easy to do that. Anything Red Hat has, I could just fork and now it's "my" code under my control.
Okay, yes; if you ignore network effects and claim that forking code gives you meaningful control of it, then FOSS can never be controlled by any centralized entities. You will forgive my skepticism.
Ah yes, once Microsoft manages to erase every copy of the Linux source code with their new Github acquisition, they're well on their way to world domination and all that jazz.
> In 2002, Microsoft sued Lindows, Inc. claiming the name Lindows constituted an infringement of their Windows trademark. Microsoft's claims were rejected by the court, which asserted that Microsoft had used the term windows to describe graphical user interfaces before the Windows product was ever released, and that the windowing technique had already been implemented by Xerox and Apple Computer many years before.[7]
Makes sense, LfW 3.11 should be pretty usable. It could be like DOS+WfW, basically Linux kernel + Windows 10/11 GUI.
The best outcome would be achieving the dream of OS/2 -> Workplace OS, with a microkernel and OS-personalities, so running Linux, Windows, or other OS flavours co-existing on a single shared microkernel: one OS to rule them all.
this distro is for first-party usage, i.e. Microsoft's own services. I doubt we expect anyone from outside to use it, it's just on GitHub because there's no reason it shouldn't be.
> > it's just on GitHub because there's no reason it shouldn't be
> And the GPL
I don't follow? The GPL doesn't have anything to say about internal usage. The way it's written it only kicks in if you ship to third parties (ie distribute). This is what led to the AGPL - proprietary modifications to GPL code and users interacting remotely with the end product.
I would have assumed Ubuntu, given that they've partnered with them a few times, "deb" is the default Linux download for Edge/Linux, Ubuntu seems to be the default distro for WSL, etc. Surprised it's RedHat based.
Ubuntu is what users want (where "want" is a rather loaded term, it's just the most accessible version for most folks at the moment). Not what enterprise businesses want to resell.
Nah, the single biggest customer is the US Government, and the US Government buys Red Hat. I mean, Uncle Sam will forego machine learning optimizations that ship out of the box in Ubuntu and thus walk away from entire product lines simply because Red Hat has a better STIG. There was no way Microsoft was going to risk that.
This is a distro intended for 1P internal services. Azure heavily uses Ubuntu internally compared to RHEL. Personally I’m curious to see how adoption turns out, because I think you’re right and this would be more likely something customers pick up.
I don't suppose you could tell us what 1P stands for? Top Google hit for Azure 1P is.. this Github repo, followed by the Azure Pricing page then hundreds of sunglasses sales.
I always figured Microsoft partnered with Ubuntu because their saw Red Hat as their real competitor.
Kind of like how Walmart uses Azure instead of AWS.
> Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems
>What's the relationship between MS or CBL-Mariner and VMware?
None? Photon is an open source Linux distribution that’s based on fedora. Mariner pulls from photon, fedora, and others. It’s entirely developed by MS.
I’m aware, that doesn’t mean they have any direct input into mariner, they’re an upstream that mariner pulls a couple of things from, as well as fedora and others.
It also explains nothing about comment that “all doc is written by azure VMware”.
Azure is a cloud computing service. VMware is a software company owned by Dell. That would be like saying “all doc is written by AWS redhat”.
Regardless of the reasoning behind this move, it's pleasing to see them acknowledge all of the open source software that made this possible. Amazon could learn something from this.
I remember, many years ago, seeing some trade magazin publish an "announcement" of "Microsoft GNU/Linux" as an April fools' joke.
After the last couple of years, this is not as big a surprise as it would have been ten years ago, but back then the idea of Microsoft creating and making publically available their own GNU/Linux distro was really far out. I did not think I'd ever see the day. Next stop: flying pigs!
56 comments
[ 3.1 ms ] story [ 35.3 ms ] threadEdit: also https://news.ycombinator.com/item?id=27792366 from earlier.
Or, if you just don't believe a single company can control the ecosystem, go build a Linux system with no userland code from Red Hat and let us know how it goes.
This is why I'm having trouble seeing the EEE connection. It's incredibly easy to do that. Anything Red Hat has, I could just fork and now it's "my" code under my control.
Edit
https://en.wikipedia.org/wiki/Linspire
> In 2002, Microsoft sued Lindows, Inc. claiming the name Lindows constituted an infringement of their Windows trademark. Microsoft's claims were rejected by the court, which asserted that Microsoft had used the term windows to describe graphical user interfaces before the Windows product was ever released, and that the windowing technique had already been implemented by Xerox and Apple Computer many years before.[7]
Edit2
...is that the joke? whoosh
A worthy successor to IBM Linux/2
The best outcome would be achieving the dream of OS/2 -> Workplace OS, with a microkernel and OS-personalities, so running Linux, Windows, or other OS flavours co-existing on a single shared microkernel: one OS to rule them all.
OK, we got the decades old slogan out of the way, now can we talk about the actual distro?
> And the GPL
I don't follow? The GPL doesn't have anything to say about internal usage. The way it's written it only kicks in if you ship to third parties (ie distribute). This is what led to the AGPL - proprietary modifications to GPL code and users interacting remotely with the end product.
I should have added /s because clearly no one is understanding my post was slightly sarcastic.
(I work in Azure)
From 8 days ago.
https://news.ycombinator.com/item?id=27792366
> Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems
From https://www.winehq.org/about/
and all doc is written by Azure VMware.
What's the relationship between MS or CBL-Mariner and VMware?
I don’t follow what you mean.
>What's the relationship between MS or CBL-Mariner and VMware?
None? Photon is an open source Linux distribution that’s based on fedora. Mariner pulls from photon, fedora, and others. It’s entirely developed by MS.
https://github.com/vmware/photon
It also explains nothing about comment that “all doc is written by azure VMware”.
Azure is a cloud computing service. VMware is a software company owned by Dell. That would be like saying “all doc is written by AWS redhat”.
After the last couple of years, this is not as big a surprise as it would have been ten years ago, but back then the idea of Microsoft creating and making publically available their own GNU/Linux distro was really far out. I did not think I'd ever see the day. Next stop: flying pigs!