Interesting article on Linux and Microsoft
-
@scottalanmiller said in Interesting article on Linux and Microsoft:
No Linux on Windows. There is Ubuntu/Windows... but it is specifically not Linux. All Linux was removed to make it just an alternative window dressing for Windows.
-
@Tim_G said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
No Linux on Windows. There is Ubuntu/Windows... but it is specifically not Linux. All Linux was removed to make it just an alternative window dressing for Windows.
That's subsystem for Linux (just Subsystem for UNIX renamed.) It's a set of services commonly used by Linux running on Windows. It's FOR Linux, but it's a Windows subsystem. 100% Windows, has been since it was first introduced like twenty years ago. That's where the NFS server, NIS server and such have traditionally been kept.
It's the equivalent feature as Samba on Linux, in reverse. Just an application.
-
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
-
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
-
@Kelly said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
Yeah, that's right... technically the host OS is a VM when Hyper-V is enabled.
-
@Tim_G said in Interesting article on Linux and Microsoft:
@Kelly said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
Yeah, that's right... technically the host OS is a VM when Hyper-V is enabled.
There's a very good podcast that explains this. It's from RunAs Radio... I'll see if I can find the specific one I'm talking about.
-
@Kelly said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
I found it!: http://www.runasradio.com/Shows/Show/480
Took me awhile because it was so long since I heard it.
To get the proper context of the whole thing, you can start at 11 minutes in, and listen from there. It really doesn't start until about 17, but you need the extra 6 to really get it.
@scottalanmiller have you heard this?
-
@Kelly said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
That's correct. Windows always runs on Hyper-V, never Hyper-V on Windows. So any Linux on Hyper-V is a peer with Windows running alongside of it, not "on" Windows in any way.
-
@Tim_G said in Interesting article on Linux and Microsoft:
@Kelly said in Interesting article on Linux and Microsoft:
@scottalanmiller said in Interesting article on Linux and Microsoft:
Used to be called SFU 3.5 before they retired it to revamp it because it had aged so badly.
Linux on Windows would require a hypervisor layer as the Linux kernel needs to see a computer appears to run and Windows can't provide that currently (Linux can, however.) So nothing that sounds like Linux on Windows will ever be that until Windows addresses that kernel shortcoming, but even if they do, it's just a VM.
I had been under the impression that Client Hyper-V in Windows 10 is a "Type 1" hypervisor, granting VMs direct access to the hypervisor, bypassing the host OS.
I found it!: http://www.runasradio.com/Shows/Show/480
Took me awhile because it was so long since I heard it.
To get the proper context of the whole thing, you can start at 11 minutes in, and listen from there. It really doesn't start until about 17, but you need the extra 6 to really get it.
@scottalanmiller have you heard this?
Of the show? No I have not, I'll check it out.
-
Microsoft officially calls it "Ubuntu on Windows", not Linux on Windows.
Thought I'd throw that out there.
-
@Tim_G said in Interesting article on Linux and Microsoft:
Microsoft officially calls it "Ubuntu on Windows", not Linux on Windows.
Thought I'd throw that out there.
Yes. They are actually pretty good about that. Although one has to ask what Ubuntu means because until MS started saying it Ubuntu was a Linux based OS. Now it's not so what is it? It's good that they don't call it Linux. But calling it Ubuntu is misleading too as it isn't the thing known as Ubuntu anywhere else.
-
@scottalanmiller said in Interesting article on Linux and Microsoft:
@Tim_G said in Interesting article on Linux and Microsoft:
Microsoft officially calls it "Ubuntu on Windows", not Linux on Windows.
Thought I'd throw that out there.
Yes. They are actually pretty good about that. Although one has to ask what Ubuntu means because until MS started saying it Ubuntu was a Linux based OS. Now it's not so what is it? It's good that they don't call it Linux. But calling it Ubuntu is misleading too as it isn't the thing known as Ubuntu anywhere else.
Yeah well, it is Microsoft. They don't have the best reputation with naming things. But I already know I don't need to tell you that!
-
It does "act" an awful lot like Ubuntu. But it's a very existential naming conundrum.
