Slashdot Mirror
Red Hat Enterprise Linux Comes To Windows 10 in the Form of WLinux Enterprise (betanews.com)
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.
Oh my God job security here I come
Poettering announced today that from now on systemd will include an integrated kernel as part of systemd. Systemd-kernel is a mostly compatible replacement for the Linux kernel, but is a hybrid between Linux and MS DOS 2.0.
The kernel integration was fast-tracked, having previously been scheduled to occur only after the integration of the new systemd-officesuite and renaming of systemd to Officed.
Responding to criticism that systemd just keeps getting bigger, Poettering pointed out that some things are actually being removed. Specifically, they plan to separate out the systemd / Officed init system and make that a separate project. The newly independent init system will be called SysFkdInit.
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.
This subsystem thing makes no sense for me. After all, the point of using Linux is to not use Windows!
Circumcision is child abuse.
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
If I want two OS', I use a hypervisor or a virtual machine. OS-in-OS works with Linux running in Linux or RTAI because Linux and RTAI are fast.
Windows is slow, violently unstable, insecure, doesn't provide the necessary low level support, and was only supposed to blow the bloody doors off.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
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.
Strong is the Woosh, this one is.
Some drink at the fountain of knowledge. Others just gargle.
I use WSL with so-called Debian every day. It's useful for programming but very limited and not production quality. Microsoft explicitly states that WSL is not intended or recommended for production applications.
One issue I ran into was writing to the end of an r+ open file. Explicitly placing a new record at the end by byte-number is inconsistent between openings of the file. I found that the exact positioning is a byte off via the Linux VFS verses the NTFS. If you check environment, your code can thus account for this. However, when using WSL, it's inconsistent between each time you open the file. Open once and read/write all you want. Close and re-open and it's scewed by one byte position.
I imagine there are other issues. Overall, I am happy that WSL exists but yes, they did not name it properly. It's not Linux at all. And the Debian for it, is not Debian, either.. Also, it would be so nice if they could make Xorg work...
If I were a Microsoft executive, I would have created Microsoft Linux a long time ago... Build in .Net and PowerShell. Give Red Hat a run for its money.
Copy-pasting from your link:
> the sharing of data, users, groups, security, applications, and other networking functions
Windows STILL isn't designed for sharing applications. Windows NT didn't share users, groups, and security 20 years ago. Active directory came out with Windows 2000.
So of the five things mentioned in the Wikipedia definition, Windows did ONE, and that very poorly. So I'll be glad to use the definition you found and call it 20% network OS. Last time I checked, which admittedly was a few years ago, file locking and some other basic functions still don't work reliably on NTFS, but we'll pretend it was solid and give NT a score of 20% on being a network OS.