Slashdot Mirror

← Back to Stories (view on slashdot.org)

Red Hat Enterprise Linux Comes To Windows 10 in the Form of WLinux Enterprise (betanews.com)

Posted by msmash on from the setting-up-a-village dept.

Mark Wilson writes: Earlier in the year open-source software startup Whitewater Foundry brought WLinux to the Windows Subsystem for Linux (WSL). Not content with creating the first native Linux distribution for WSL, the company has now gone a step further, targeting enterprise users with WLinux Enterprise. Whitewater Foundry says that WLinux Enterprise is the first product to support the industry-standard Red Hat Enterprise Linux on Windows Subsystem for Linux.

4 of 124 comments (clear)

  1. Warning: Contains no nuts by skullandbones99 · · Score: 3, Insightful

    I thought the definition of a Linux distribution was that the distribution was based on and included the Linux kernel. But WSL contains a emulation layer for the M$ kernel to implement the Linux system calls.

    Therefore, this Red Hat distribution is a WSL distribution. Sigh.

    This is M$ strategy of killing off the Linux kernel.

  2. What's this crap good for? by Stormwatch · · Score: 4, Insightful

    This subsystem thing makes no sense for me. After all, the point of using Linux is to not use Windows!

    --
    Circumcision is child abuse.
  3. What's the advantage? by guruevi · · Score: 4, Insightful

    I don't see who would actually want to deploy this The primary reason I use Linux is for it to be a stable underpinning to either host Windows or other Linux or applications. The reasons not to use Windows is because it's basically a desktop OS. Live patching the kernel still doesn't happen on Windows and even though Linux is on more systems than ever, so the market share argument doesn't hold anymore, Windows bugs are still major issues all the time requiring reboots for even the simplest of subsystems.

    On the other hand, if I need Linux on a Workstation, it's because the Windows systems doesn't have good hardware support (eg. gpGPU, Real-Time timing support, configurable interrupts, InfiniBand, ASIC, 10/40/100G networking) so a subsystem of Windows wouldn't do me any good.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  4. You forget Microsoft's announcements by raymorris · · Score: 3, Insightful

    It was in Windows 5.0 that Microsoft announced a deal with Citrix to integrate parts of the Citrix app into Windows. The Citrix application code would add a) separate users b) remove access, Microsoft announced.

    So none of this is true:
    > Windows NT was already pretty mature, and was built from the ground up to be part of a network, to support multiple users

    It was designed as a local desktop operating system, not a network operating system, and even in 5.0 "multi-year" was a third-party application tacked on to hide other users' files in File Explorer. To see files in the other person's directory, you had to use the command prompt, write a script, or cleverly navigate to C:\ first in Explorer. Same with remote access - a third party app tacked on in version 5. A network operating system is one that *assumes* use is over the network by default. You can recognize them because local access is via 127.0.0.1. CUPS is a printing and scanning system for network operating systems. It runs on port 631, so you connect to whatever-machine:631. If the print spool you want to use happens to be on the same machine you logged into, that would be localhost:631. X11 is a windowing system for network operating systems, it runs port 6000, so to run a program local machine you use localhost:6000 - precisely the same way you'd run it on any other machine on the network.

    Setting the graphical shell to hide the other guy's "My Documents" folder is not what makes a multi-user, network OS.