If Windows 7 doesn't support WSL, then what is “Subsystem for UNIX-based Applications”?How do you make Windows 7 fully case-sensitive with respect to the filesystem?NFS mount in windows XPUser accounts under WSL (Windows Subsystem for Linux)Local Django Server Runs from Windows Command Prompt but not Windows Subsystem for LinuxWhat is the home directory on Windows Subsystem for Linux?Local reinstalling of Windows Subsystem for Linux (WSL) tens of times a month can damage SSD?Editing files in a Windows Subsystem for Linux development environmentFixing 'Input/output error' from .bashrc in Windows Subsystem for LinuxHow can reverse-SSH be established with Windows Subsystem for Linux (WSL)?Does Microsoft WSL have full support for network and devices?' Windows Subsystem for Linux' option not showing up in Windows Server 2016Windows Shortcut for bash command: what does 12345678 … ~ mean?
What is the most expensive material in the world that could be used to create Pun-Pun's lute?
Can I criticise the more senior developers around me for not writing clean code?
Why did C use the -> operator instead of reusing the . operator?
Providing evidence of Consent of Parents for Marriage by minor in England in early 1800s?
How to fry ground beef so it is well-browned
How to have a sharp product image?
As an international instructor, should I openly talk about my accent?
Why does nature favour the Laplacian?
On The Origin of Dissonant Chords
What are the characteristics of a typeless programming language?
acheter à, to mean both "from" and "for"?
Does tea made with boiling water cool faster than tea made with boiled (but still hot) water?
What are the steps to solving this definite integral?
How could Tony Stark make this in Endgame?
How to write a column outside the braces in a matrix?
Multiple options vs single option UI
What's the name of these pliers?
Re-entry to Germany after vacation using blue card
What makes accurate emulation of old systems a difficult task?
What does ゆーか mean?
A Note on N!
Aliens crash on Earth and go into stasis to wait for technology to fix their ship
Aligning equation numbers vertically
Why must Chinese maps be obfuscated?
If Windows 7 doesn't support WSL, then what is “Subsystem for UNIX-based Applications”?
How do you make Windows 7 fully case-sensitive with respect to the filesystem?NFS mount in windows XPUser accounts under WSL (Windows Subsystem for Linux)Local Django Server Runs from Windows Command Prompt but not Windows Subsystem for LinuxWhat is the home directory on Windows Subsystem for Linux?Local reinstalling of Windows Subsystem for Linux (WSL) tens of times a month can damage SSD?Editing files in a Windows Subsystem for Linux development environmentFixing 'Input/output error' from .bashrc in Windows Subsystem for LinuxHow can reverse-SSH be established with Windows Subsystem for Linux (WSL)?Does Microsoft WSL have full support for network and devices?' Windows Subsystem for Linux' option not showing up in Windows Server 2016Windows Shortcut for bash command: what does 12345678 … ~ mean?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Everyone says that the Linux subsystem, or WSL, is only supported in Windows 10.
So if this is true, can someone explain what does this, very similar looking, option in Windows 7 mean? What exactly does it enable?
windows unix windows-subsystem-for-linux
add a comment |
Everyone says that the Linux subsystem, or WSL, is only supported in Windows 10.
So if this is true, can someone explain what does this, very similar looking, option in Windows 7 mean? What exactly does it enable?
windows unix windows-subsystem-for-linux
27
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36
add a comment |
Everyone says that the Linux subsystem, or WSL, is only supported in Windows 10.
So if this is true, can someone explain what does this, very similar looking, option in Windows 7 mean? What exactly does it enable?
windows unix windows-subsystem-for-linux
Everyone says that the Linux subsystem, or WSL, is only supported in Windows 10.
So if this is true, can someone explain what does this, very similar looking, option in Windows 7 mean? What exactly does it enable?
windows unix windows-subsystem-for-linux
windows unix windows-subsystem-for-linux
edited Apr 19 at 15:38
Peter Cordes
2,5451622
2,5451622
asked Apr 18 at 3:49
PragmaticEdPragmaticEd
14725
14725
27
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36
add a comment |
27
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36
27
27
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36
add a comment |
2 Answers
2
active
oldest
votes
In the 1980s the US federal government required that certain types of government purchases be POSIX-compliant, therefore MS had to include a POSIX subsystem in Windows
Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT. (The other three being the Win32 subsystem which provided the primary programming API for Windows NT, plus the OS/2 and security subsystems.)
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
That was one of the reasons of POSIX filename support in NTFS, and the existence of the registry key HKLMSYSTEMCurrentControlSetControlSession ManagerkernelObCaseInsensitive
for compatibility with case-sensitive file names in POSIX subsystem and on the network
- How do you make Windows 7 fully case-sensitive with respect to the filesystem?
- Enable case sensitive behavior with Windows XP and Interix Subsystem or SFU
However the POSIX subsystem only implements POSIX.1 which doesn't include command line tools. In Windows XP / Windows Server 2003 it has been replaced with Windows Services for UNIX (SFU) which is what you see. It's much more powerful and was later renamed to Subsystem for UNIX-based Applications in Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2
Subsystem for UNIX-based Applications (SUA) is a source-compatibility subsystem for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system. You can make your UNIX applications fully interoperable with Windows in SUA with little or no change to your original source code.
Subsystem for UNIX-based Applications
SUA was removed in Windows 8 and Windows Server 2012
Unlike WSL in Windows 10, those subsystems are not meant for running Linux ELF executable files directly, therefore you'll have to recompile for that subsystem if you want to run under it
Further reading:
- POSIX and UNIX Support in Windows
- Services for UNIX – Interoperability
- Features Removed or Deprecated in Windows Server 2012
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
|
show 2 more comments
Everyone says, that Linux subsystem,or WSL, IS only supported in windows 10.
Everyone is absolutely correct. Windows Linux Subsystem does not exist and cannot be enabled/installed on Windows 7.
Subsystem for UNIX-based Applications has nothing to do with the Windows 10 feature. It was also known as Interix before it was discontinued with the release of Windows 10.
Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem.
The tools that were supported were recompiled versions. The tools contained within a WSL instance are the same tools that run on Linux.
Unlike in the past the actual Linux distribution, is compiled into a UWP application, which interfaces with the Linux Subsystem allowing virtually any Linux distribution to now be compatible.
We distribute Linux distros for WSL as UWP applications through the Microsoft Store. You can install those applications that will then run on WSL - the subsystem that sits in the Windows kernel. This delivery mechanism has many benefits as discussed in an earlier blog post.
Source: Creating a Custom Linux Distro for WSL
There is an inherited limitation dealing with Linux kernel level drivers (they are not supported) so
all devices interface indirectly with the Windows device driver.
Source: Interix
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
|
show 2 more comments
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1426824%2fif-windows-7-doesnt-support-wsl-then-what-is-subsystem-for-unix-based-applica%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
In the 1980s the US federal government required that certain types of government purchases be POSIX-compliant, therefore MS had to include a POSIX subsystem in Windows
Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT. (The other three being the Win32 subsystem which provided the primary programming API for Windows NT, plus the OS/2 and security subsystems.)
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
That was one of the reasons of POSIX filename support in NTFS, and the existence of the registry key HKLMSYSTEMCurrentControlSetControlSession ManagerkernelObCaseInsensitive
for compatibility with case-sensitive file names in POSIX subsystem and on the network
- How do you make Windows 7 fully case-sensitive with respect to the filesystem?
- Enable case sensitive behavior with Windows XP and Interix Subsystem or SFU
However the POSIX subsystem only implements POSIX.1 which doesn't include command line tools. In Windows XP / Windows Server 2003 it has been replaced with Windows Services for UNIX (SFU) which is what you see. It's much more powerful and was later renamed to Subsystem for UNIX-based Applications in Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2
Subsystem for UNIX-based Applications (SUA) is a source-compatibility subsystem for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system. You can make your UNIX applications fully interoperable with Windows in SUA with little or no change to your original source code.
Subsystem for UNIX-based Applications
SUA was removed in Windows 8 and Windows Server 2012
Unlike WSL in Windows 10, those subsystems are not meant for running Linux ELF executable files directly, therefore you'll have to recompile for that subsystem if you want to run under it
Further reading:
- POSIX and UNIX Support in Windows
- Services for UNIX – Interoperability
- Features Removed or Deprecated in Windows Server 2012
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
|
show 2 more comments
In the 1980s the US federal government required that certain types of government purchases be POSIX-compliant, therefore MS had to include a POSIX subsystem in Windows
Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT. (The other three being the Win32 subsystem which provided the primary programming API for Windows NT, plus the OS/2 and security subsystems.)
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
That was one of the reasons of POSIX filename support in NTFS, and the existence of the registry key HKLMSYSTEMCurrentControlSetControlSession ManagerkernelObCaseInsensitive
for compatibility with case-sensitive file names in POSIX subsystem and on the network
- How do you make Windows 7 fully case-sensitive with respect to the filesystem?
- Enable case sensitive behavior with Windows XP and Interix Subsystem or SFU
However the POSIX subsystem only implements POSIX.1 which doesn't include command line tools. In Windows XP / Windows Server 2003 it has been replaced with Windows Services for UNIX (SFU) which is what you see. It's much more powerful and was later renamed to Subsystem for UNIX-based Applications in Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2
Subsystem for UNIX-based Applications (SUA) is a source-compatibility subsystem for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system. You can make your UNIX applications fully interoperable with Windows in SUA with little or no change to your original source code.
Subsystem for UNIX-based Applications
SUA was removed in Windows 8 and Windows Server 2012
Unlike WSL in Windows 10, those subsystems are not meant for running Linux ELF executable files directly, therefore you'll have to recompile for that subsystem if you want to run under it
Further reading:
- POSIX and UNIX Support in Windows
- Services for UNIX – Interoperability
- Features Removed or Deprecated in Windows Server 2012
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
|
show 2 more comments
In the 1980s the US federal government required that certain types of government purchases be POSIX-compliant, therefore MS had to include a POSIX subsystem in Windows
Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT. (The other three being the Win32 subsystem which provided the primary programming API for Windows NT, plus the OS/2 and security subsystems.)
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
That was one of the reasons of POSIX filename support in NTFS, and the existence of the registry key HKLMSYSTEMCurrentControlSetControlSession ManagerkernelObCaseInsensitive
for compatibility with case-sensitive file names in POSIX subsystem and on the network
- How do you make Windows 7 fully case-sensitive with respect to the filesystem?
- Enable case sensitive behavior with Windows XP and Interix Subsystem or SFU
However the POSIX subsystem only implements POSIX.1 which doesn't include command line tools. In Windows XP / Windows Server 2003 it has been replaced with Windows Services for UNIX (SFU) which is what you see. It's much more powerful and was later renamed to Subsystem for UNIX-based Applications in Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2
Subsystem for UNIX-based Applications (SUA) is a source-compatibility subsystem for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system. You can make your UNIX applications fully interoperable with Windows in SUA with little or no change to your original source code.
Subsystem for UNIX-based Applications
SUA was removed in Windows 8 and Windows Server 2012
Unlike WSL in Windows 10, those subsystems are not meant for running Linux ELF executable files directly, therefore you'll have to recompile for that subsystem if you want to run under it
Further reading:
- POSIX and UNIX Support in Windows
- Services for UNIX – Interoperability
- Features Removed or Deprecated in Windows Server 2012
In the 1980s the US federal government required that certain types of government purchases be POSIX-compliant, therefore MS had to include a POSIX subsystem in Windows
Microsoft POSIX subsystem is one of four subsystems shipped with the first versions of Windows NT. (The other three being the Win32 subsystem which provided the primary programming API for Windows NT, plus the OS/2 and security subsystems.)
https://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem
That was one of the reasons of POSIX filename support in NTFS, and the existence of the registry key HKLMSYSTEMCurrentControlSetControlSession ManagerkernelObCaseInsensitive
for compatibility with case-sensitive file names in POSIX subsystem and on the network
- How do you make Windows 7 fully case-sensitive with respect to the filesystem?
- Enable case sensitive behavior with Windows XP and Interix Subsystem or SFU
However the POSIX subsystem only implements POSIX.1 which doesn't include command line tools. In Windows XP / Windows Server 2003 it has been replaced with Windows Services for UNIX (SFU) which is what you see. It's much more powerful and was later renamed to Subsystem for UNIX-based Applications in Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2
Subsystem for UNIX-based Applications (SUA) is a source-compatibility subsystem for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system. You can make your UNIX applications fully interoperable with Windows in SUA with little or no change to your original source code.
Subsystem for UNIX-based Applications
SUA was removed in Windows 8 and Windows Server 2012
Unlike WSL in Windows 10, those subsystems are not meant for running Linux ELF executable files directly, therefore you'll have to recompile for that subsystem if you want to run under it
Further reading:
- POSIX and UNIX Support in Windows
- Services for UNIX – Interoperability
- Features Removed or Deprecated in Windows Server 2012
edited Apr 19 at 15:23
answered Apr 18 at 7:06
phuclvphuclv
11.3k64498
11.3k64498
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
|
show 2 more comments
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
Good answer, but unless I’m mistaken you haven’t actually said what the SFU is for - that is, mounting NFS shares etc - only what it can’t be used for.
– Darren
Apr 19 at 17:33
2
2
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@Darren: I think you're mistaken, the quote block says "Subsystem for UNIX-based Applications (SUA) is ... for compiling and running custom UNIX-based applications on a computer running a Microsoft® Windows® server-class operating system" The NFS network redirector is a different component, also visible in OP's screenshot.
– Ben Voigt
Apr 20 at 7:13
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt hmm, maybe. It’s been a while since I did anything like that, but was sure I’ve used it to mount NFS shares.
– Darren
Apr 20 at 7:17
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
@BenVoigt superuser.com/questions/359968/nfs-mount-in-windows-xp
– Darren
Apr 20 at 7:18
2
2
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
@Darren: Most of it did, but the NFS file share support was split off into a separate component (Services for NFS, subcomponent Client for NFS)... It's visible right there as the very first checkbox in OP's Windows 7 screen image, and it's a few rows off-screen in the Windows 10 screenshot.
– Ben Voigt
Apr 20 at 7:26
|
show 2 more comments
Everyone says, that Linux subsystem,or WSL, IS only supported in windows 10.
Everyone is absolutely correct. Windows Linux Subsystem does not exist and cannot be enabled/installed on Windows 7.
Subsystem for UNIX-based Applications has nothing to do with the Windows 10 feature. It was also known as Interix before it was discontinued with the release of Windows 10.
Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem.
The tools that were supported were recompiled versions. The tools contained within a WSL instance are the same tools that run on Linux.
Unlike in the past the actual Linux distribution, is compiled into a UWP application, which interfaces with the Linux Subsystem allowing virtually any Linux distribution to now be compatible.
We distribute Linux distros for WSL as UWP applications through the Microsoft Store. You can install those applications that will then run on WSL - the subsystem that sits in the Windows kernel. This delivery mechanism has many benefits as discussed in an earlier blog post.
Source: Creating a Custom Linux Distro for WSL
There is an inherited limitation dealing with Linux kernel level drivers (they are not supported) so
all devices interface indirectly with the Windows device driver.
Source: Interix
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
|
show 2 more comments
Everyone says, that Linux subsystem,or WSL, IS only supported in windows 10.
Everyone is absolutely correct. Windows Linux Subsystem does not exist and cannot be enabled/installed on Windows 7.
Subsystem for UNIX-based Applications has nothing to do with the Windows 10 feature. It was also known as Interix before it was discontinued with the release of Windows 10.
Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem.
The tools that were supported were recompiled versions. The tools contained within a WSL instance are the same tools that run on Linux.
Unlike in the past the actual Linux distribution, is compiled into a UWP application, which interfaces with the Linux Subsystem allowing virtually any Linux distribution to now be compatible.
We distribute Linux distros for WSL as UWP applications through the Microsoft Store. You can install those applications that will then run on WSL - the subsystem that sits in the Windows kernel. This delivery mechanism has many benefits as discussed in an earlier blog post.
Source: Creating a Custom Linux Distro for WSL
There is an inherited limitation dealing with Linux kernel level drivers (they are not supported) so
all devices interface indirectly with the Windows device driver.
Source: Interix
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
|
show 2 more comments
Everyone says, that Linux subsystem,or WSL, IS only supported in windows 10.
Everyone is absolutely correct. Windows Linux Subsystem does not exist and cannot be enabled/installed on Windows 7.
Subsystem for UNIX-based Applications has nothing to do with the Windows 10 feature. It was also known as Interix before it was discontinued with the release of Windows 10.
Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem.
The tools that were supported were recompiled versions. The tools contained within a WSL instance are the same tools that run on Linux.
Unlike in the past the actual Linux distribution, is compiled into a UWP application, which interfaces with the Linux Subsystem allowing virtually any Linux distribution to now be compatible.
We distribute Linux distros for WSL as UWP applications through the Microsoft Store. You can install those applications that will then run on WSL - the subsystem that sits in the Windows kernel. This delivery mechanism has many benefits as discussed in an earlier blog post.
Source: Creating a Custom Linux Distro for WSL
There is an inherited limitation dealing with Linux kernel level drivers (they are not supported) so
all devices interface indirectly with the Windows device driver.
Source: Interix
Everyone says, that Linux subsystem,or WSL, IS only supported in windows 10.
Everyone is absolutely correct. Windows Linux Subsystem does not exist and cannot be enabled/installed on Windows 7.
Subsystem for UNIX-based Applications has nothing to do with the Windows 10 feature. It was also known as Interix before it was discontinued with the release of Windows 10.
Interix was an optional, POSIX-conformant Unix subsystem for Windows NT operating systems. Interix was a component of Windows Services for UNIX, and a superset of the Microsoft POSIX subsystem.
The tools that were supported were recompiled versions. The tools contained within a WSL instance are the same tools that run on Linux.
Unlike in the past the actual Linux distribution, is compiled into a UWP application, which interfaces with the Linux Subsystem allowing virtually any Linux distribution to now be compatible.
We distribute Linux distros for WSL as UWP applications through the Microsoft Store. You can install those applications that will then run on WSL - the subsystem that sits in the Windows kernel. This delivery mechanism has many benefits as discussed in an earlier blog post.
Source: Creating a Custom Linux Distro for WSL
There is an inherited limitation dealing with Linux kernel level drivers (they are not supported) so
all devices interface indirectly with the Windows device driver.
Source: Interix
edited Apr 20 at 17:58
answered Apr 18 at 3:56
RamhoundRamhound
21.6k156288
21.6k156288
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
|
show 2 more comments
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
No, the Linux distribution isn't compiled as UWP. The ELF executables run directly.
– Ben Voigt
Apr 20 at 7:14
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
How could you compile a distribution into a UWP application? What would that even mean? A distribution is a large collection of executables, scripts, configuration files etc. It isn't a single thing. I admit I haven't used Windows since the 90s so I don't know how this works, but are you sure an entire distribution is somehow packaged as a single thing? That really doesn't make much sense to me. AFAIK, the WSL is just a compatibility layer allowing the execution of Linux tools on the Windows machine.
– terdon
Apr 20 at 15:31
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@terdon - I will work on the statement, but WSL is NOT just a compatibility layer, that runs Linux tools. I can remote into my Kali WSL instance. The Kali instance when properly configured has a desktop, while remotely accessing it, it can run applications with a GUI. Blog
– Ramhound
Apr 20 at 17:51
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@Ramhound yes, but all of those are presumably running through the same compatibility layer. And I call it this because that's what it's called on WIkipedia and because it is described as "the space between the user mode Linux binaries and the Windows kernel components where the magic happens." on the official msdn blog, and it's commonly referred to as such.
– terdon
Apr 20 at 17:59
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
@terdon - I Provided a source for my statement and I stand by the verbiage I used. While it might be overly simplified, it is indeed accurate, to say the distribution is compiled into a UWP application.. Microsoft themselves say the distribution is compiled into a UWP (launcher) application.
– Ramhound
Apr 20 at 18:00
|
show 2 more comments
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1426824%2fif-windows-7-doesnt-support-wsl-then-what-is-subsystem-for-unix-based-applica%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
27
Unix and Linux are different. And to take a screenshot just use use the PrintScreen key or the snipping tool instead of capturing such a terrible photo
– phuclv
Apr 18 at 13:09
@JariullahSafi thank you for you useless comment. I'm already aware that part of it doesn't apply to the current edit. You're free to revert the edit if you don't like
– phuclv
Apr 21 at 4:36