The Best Part of Windows 11 Is Its Linux, Argues Ars Technica (arstechnica.com) 148
The best part of Windows 11 is Linux, argues Ars Technica:
For years now, Windows 10's Windows Subsystem for Linux has been making life easier for developers, sysadmins, and hobbyists who have one foot in the Windows world and one foot in the Linux world. But WSL, handy as it is, has been hobbled by several things it could not do. Installing WSL has never been as easy as it should be — and getting graphical apps to work has historically been possible but also a pain in the butt that required some fairly obscure third-party software. Windows 11 finally fixes both of those problems. The Windows Subsystem for Linux isn't perfect on Windows 11, but it's a huge improvement over what came before.
Microsoft has traditionally made installing WSL more of a hassle than it should be, but the company finally got the process right in Windows 10 build 2004. Just open an elevated Command prompt (start --> type cmd --> click Run as Administrator), type wsl --install at the prompt, and you're good to go. Windows 11, thankfully, carries this process forward unchanged. A simple wsl --install with no further arguments gets you Hyper-V and the other underpinnings of WSL, along with the current version of Ubuntu. If you aren't an Ubuntu fan, you can see what other easily installable distributions are available with the command wsl --list --online. If you decide you'd prefer a different distro, you can install it instead with — for example — wsl --install -d openSUSE-42. If you're not sure which distribution you prefer, don't fret. You can install as many as you like, simply by repeating wsl --list --online to enumerate your options and wsl --install -d distroname to install whichever you like. Installing a second distribution doesn't uninstall the first; it creates a separate environment, independent of any others. You can run as many of these installed environments as you like simultaneously, without fear of one messing up another.
In addition to easy installation, WSL on Windows 11 brings support for both graphics and audio in WSL apps. This isn't exactly a first — Microsoft debuted WSLg in April, with Windows 10 Insider Build 21364. But Windows 11 is the first production Windows build with WSLg support. If this is your first time hearing of WSLg, the short version is simple: you can install GUI apps — for example, Firefox — from your Ubuntu (or other distro) command line, and they'll work as expected, including sound. When I installed WSLg on Windows 11 on the Framework laptop, running firefox from the Ubuntu terminal popped up the iconic browser automatically. Heading to YouTube in it worked perfectly, too, with neither frame drops in the video nor glitches in the audio....
[T]here is one obvious "killer app" for WSLg that has us excited — and that's virt-manager, the RedHat-originated virtualization management tool. virt-manager is a simple tool that streamlines the creation, management, and operation of virtual machines using the Linux Kernel Virtual Machine... virt-manager never got a Windows port and seems unlikely to. But it runs under WSLg like a champ.
They reported a few problems, like when running GNOME's Software Center app (and the GNOME shell desktop environment).
But "If you're already a Windows Subsystem for Linux (WSL) user, Windows 11 offers an enormously improved experience compared to what you're accustomed to from Windows 10. It installs more easily, makes more functionality available, and offers better desktop integration than older workarounds such as running MobaXTerm's X11 server."
Microsoft has traditionally made installing WSL more of a hassle than it should be, but the company finally got the process right in Windows 10 build 2004. Just open an elevated Command prompt (start --> type cmd --> click Run as Administrator), type wsl --install at the prompt, and you're good to go. Windows 11, thankfully, carries this process forward unchanged. A simple wsl --install with no further arguments gets you Hyper-V and the other underpinnings of WSL, along with the current version of Ubuntu. If you aren't an Ubuntu fan, you can see what other easily installable distributions are available with the command wsl --list --online. If you decide you'd prefer a different distro, you can install it instead with — for example — wsl --install -d openSUSE-42. If you're not sure which distribution you prefer, don't fret. You can install as many as you like, simply by repeating wsl --list --online to enumerate your options and wsl --install -d distroname to install whichever you like. Installing a second distribution doesn't uninstall the first; it creates a separate environment, independent of any others. You can run as many of these installed environments as you like simultaneously, without fear of one messing up another.
In addition to easy installation, WSL on Windows 11 brings support for both graphics and audio in WSL apps. This isn't exactly a first — Microsoft debuted WSLg in April, with Windows 10 Insider Build 21364. But Windows 11 is the first production Windows build with WSLg support. If this is your first time hearing of WSLg, the short version is simple: you can install GUI apps — for example, Firefox — from your Ubuntu (or other distro) command line, and they'll work as expected, including sound. When I installed WSLg on Windows 11 on the Framework laptop, running firefox from the Ubuntu terminal popped up the iconic browser automatically. Heading to YouTube in it worked perfectly, too, with neither frame drops in the video nor glitches in the audio....
[T]here is one obvious "killer app" for WSLg that has us excited — and that's virt-manager, the RedHat-originated virtualization management tool. virt-manager is a simple tool that streamlines the creation, management, and operation of virtual machines using the Linux Kernel Virtual Machine... virt-manager never got a Windows port and seems unlikely to. But it runs under WSLg like a champ.
They reported a few problems, like when running GNOME's Software Center app (and the GNOME shell desktop environment).
But "If you're already a Windows Subsystem for Linux (WSL) user, Windows 11 offers an enormously improved experience compared to what you're accustomed to from Windows 10. It installs more easily, makes more functionality available, and offers better desktop integration than older workarounds such as running MobaXTerm's X11 server."
Pro Tip (Score:5, Insightful)
It's quicker AND you get even better security.
Re: (Score:3, Insightful)
You also get a better gui.
FVWM 4 lyfe
Re: (Score:3)
The reason it's better is because you get a choice.
WindowMaker 4 lyfe
Re:Pro Tip (Score:5, Insightful)
Re: (Score:2)
Oh dear. Nanny Microsoft won't like that. They'll be around later to rectify your mistake [only joking]
Microsoft is really trying to lock everyone in before they spring the weekly subscription on the world. They'll have most of you by the short and curlies leaving you with no choice but to start paying up.
I saw the writing on the wall back in 2016 when W10 was let loose. I don't run Windows now and TBH, I don't miss it a bit.
Re: (Score:2)
Used to dual boot. Realised what a pain in the arse Windows is (deliberately) designed to be (Seems sales & marketing department get the last word on what 'features' get included). At that time, the average time to install & configure Windows on a mid-range laptop was the best part of a day but with lots of interruptions the following couple of days.
These days it's abous 20 minutes. Put in a USB stick, power on, choose your language/keyboard.
Just don't forget to skip the network setup during installation so it doesn't force you to create a Microsoft account. Set up the network afterwards.
After it installs and boots for the first time you just edit the hosts file to redirect "bing.com" to 127.0.0.1, install a different web browser instead of Edge and you're golden. The amount of drivers it can find/install these days is impressive. Just about everythi
Re: (Score:2)
Should direct bing.com to 0.0.0.0 to avoid the timeout. Does Windows itself use the hosts file?
Re: (Score:2)
Re: (Score:3)
Why waste your time, effort and money developing for an OS that's barely 2% of the desktop market and is used by people who typically expect the price to be $0 and who do nothing but bitch and whine?
I don't know. Why don't you ask the governments, institutions, corporations & other organisations that use, contribute to, & donate to FOSS?
Re: Pro Tip (Score:2)
Why don't you ask the governments, institutions, corporations & other organisations that use, contribute to, & donate to FOSS?
Please, tell me about these "governments, institutions, corporations & other organisations that use, contribute to, & donate to FOSS?"
Which government(s)? Every government I've heard that publicly broke ties with Windows wound up returning to windows.
Which institution(s)? Name one university or K-12 school system that runs on Linux.
Which corporation(s)? Aside from special engineering applications that used to be run on Unix workstations, where is the widespread adoption of Linux inside any corporati
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
Why don't you ask the governments, institutions, corporations & other organisations that use, contribute to, & donate to FOSS?
Well FOSS != Linux, in fact much (probably the overwhelming majority actually) of the FOSS out there that runs on Linux also runs on Windows. But putting that aside you're talking about organisations like Microsoft, Apple, Google? They're certainly big contributors to FOSS, they don't typically develop specifically or exclusively for Linux though.
Re: (Score:3)
Indeed. So when will MS start bundling CNC Simulator with their OS?
Re: (Score:2)
Valve did so, when it became clear that Microsoft was introducing the App store. Their concern was that they would lose out against a platform that was integrated in the OS and more visible to customers.
Today, the big onslaught by Microsoft did not happen, but Valve continues to make Linux versions of their software. And a WINE version (Proton) that is conveniently integrated into Steam.
Re: (Score:2)
The best part of Windows always ever was Linux, even back in the day of Widows 95, with no WSL support whatsoever :-)
Re: Pro Tip (Score:2)
Re: (Score:3)
Run your Linux Distribution naively for engineering work, and make Windows run as a virtual machine by using VMware Workstation Pro. That is what I do on my works laptop, I have to use Windows Outlook due to Corporate policy. Microsoft do have a Linux version of their MS Teams application which I use on Fedora.
Re: (Score:2)
Run your Linux Distribution naively ... and make Windows run as a virtual machine by using VMware Workstation Pro.
Windows 10 runs fine for me using KVM/QEMU ...
Don't know about Windows 11, my systems can't support it -- CPUs too old and no TPM, but they work great with Win10 and Linux -- but I don't think I care; Win10 will probably be my last Windows version before I make the permanent switch to Linux (or BSD).
Re: Pro Tip (Score:2)
Re: (Score:2)
Thanks for the info. I knew that QEMU supported a pass-through TPM device, but didn't know about the software option. I've selected specific CPUs for a VM before, so I could run them on different systems (one native and one similar) but didn't know about a clock problem on startup...
Like you, I actually only "need" Windows for a few things -- for me, that I've been too lazy to migrate over to Linux. I have a few Office files and a LOT of Publisher files (greeting cards) that look to be problematic to mig
Re: Pro Tip (Score:2)
Too much fuss - Win 11 installs on unsupported hardware without issue - it will advise you your install is unsupported, and ask if you want to proceed.
Re: (Score:2)
Windows 10 runs like a geriatric dog under my VM on macOS. Horrendous performance, enough so that you can tell that it's working behind the scenes as the fan is blowing full blast even if you're not using Windows at the time. The other way around though I suspect Linux under a VM will run circles around Windows 11, so just keep the W11 around for the mandatory worst-in-class enterprise apps from Microsoft.
Re: (Score:2)
Exactly. Windows brings nothing to the table, it's just an attempt to lock in a generation of developers by convincing they have to use visual studio.
And frankly, wsl still sucks compared Linux on bare iron. Christ I can go pick up a few raspberry pis and get a better and more reliable experience
Re: (Score:2)
You do understand the bulk of software isn't developed using Microsoft tools, right?
Re: (Score:2)
It's quicker AND you get even better security.
[Citation needed] The biggest factor affecting security is the same for Linux and Windows: The user.
Re:Pro Tip (Score:4, Insightful)
Depends what exactly you're protecting against. As I recall, the overwhelming majority or computer attacks are fully automated, and the overwhelming majority of those specifically target Windows - no doubt due to its fairly homogeneous ubiquity and the fact that most Windows users are completely oblivious to security concerns, while Linux is a very fragmented install base, with most Linux boxes being part of corporate internet infrastructure with security managed by professionals. As I recall it actually saw the majority of human-managed attacks - but human attacks are expensive, so unless someone has reason to target you specifically, you don't really need to worry about them.
In the face of that - even if the quality of out-of-the-box security were exactly the same on both platforms (a claim I would want some compelling evidence for), the real-world security of Linux is vastly greater. In practical terms "nobody tries to attack me" has exactly the same effect as "my security is so good nobody can breach it". At least so long as no-one of skill is interested in you specifically.
Moreover, I seem to recall that in the big annual hacking competitions, Windows tends to get completely compromised around 2-10x faster than Linux. And while that's not a direct measure of the actual security of the software, it's probably about as close as is realistically possible.
Re: (Score:2)
As I recall, the overwhelming majority or computer attacks are fully automated, and the overwhelming majority of those specifically target Windows
And also nowadays, Android. Pick the biggest target, for personal computing that's Windows and Android.
Re: (Score:2)
As I recall, the overwhelming majority or computer attacks are fully automated
Counting the number of attacks goes counter to goal since the overwhelming majority of attacks amount to nothing. The overwhelming majority of *successful* attacks rely on user intervention.
In practical terms "nobody tries to attack me" has exactly the same effect as "my security is so good nobody can breach it".
Except that people do try and attack you. That myth that Linux is ignored is just that (see the most prominent of most recent ransomware and the gang behind it). Also even if it weren't a myth you're not doing your own security any favours by promoting the unwashed masses adopt Linux.
Moreover, I seem to recall that in the big annual hacking competitions, Windows tends to get completely compromised around 2-10x faster than Linux.
Of course, it's a bigger target with
Re: Pro Tip (Score:2)
Linux is a very fragmented install base, with most Linux boxes being part of corporate internet infrastructure with security managed by professionals.
Citation for the professional management of "most Linux boxes" please?
The low market share of Linux is the pest virus protection feature of Linux.
Re: Pro Tip (Score:2)
Re: Pro Tip (Score:2)
Re: Pro Tip (Score:2)
It's only case sensitive in the way it stores filenames, if I recall correctly. You still can't have two files that only differ in casing.
Re: (Score:2)
Re: (Score:2)
You sure about that? Because I just now did exactly that to make sure I wasn't crazy...
Only one way to improve on that (Score:4, Insightful)
Only one way to improve on that. Run Windows in a vm under Linux. Result: happiness.
Re: (Score:2)
Even better: put Wndows on VM, put the VM on a thumbdrive, then put the thumbdrive under a bus, then burn the bus.
Finally, nuke the entire site from orbit.
Re: (Score:2)
Re: (Score:2)
Are you sure that would destroy it? Perhaps there are other ways?
I've heard that nuking things from orbit is the only way to be sure.
Re: (Score:2)
Isn't bare backing risky, especially if you don't just give Windows direct access to the hardware which also runs important stuff but to a network connection too?
Re: (Score:2)
Yeah, I feel little to no extra safety from running stuff in WSL. The only safety advantage over native code is that malware authors may not have chosen to plan for a Linux to Windows vector, and thus rootkits and keyloggers might not work. It's a type of security through obscurity, and it will go away as WSL becomes more popular.
But those security risks are usability assets. I'd hate to think of not being able to manipulate files on the Windows filesystem or not being able to access the internet (not using
Re:Only one way to improve on that (Score:5, Informative)
Right, but if you run Windows in a VM and do all real work in Linux, not WSL, then Windows can't interfere with that. When Windows shits the bed, you nuke the VM, reload a clean snapshot and nothing of value is lost, because all the important stuff is out of Windows' reach. Accessing Windows files from Linux is easy, but with WSL the Windows system can also access Linux files. I still think that's reckless.
Bare Windows can be made safe (Score:3)
Re: (Score:2)
While true, WINE for the most part gives the counterpart. The issue is that linux's APIs are purposefully open, and thus easily targetted by the WSL for windows subsystem integration.
The inverse is not the case and microsoft's closed APIs change faster than a teenage girl's wardrobe on prom night.
For the most part, I am quite happy with PlayOnLinux (a front-end for WINE that does various wine front-ends). I have Photoshop and a few other odds and ends from the windows world running pretty neat and tidy on
Re: (Score:2)
Re:Only one way to improve on that (Score:5, Informative)
Running Windows in a VM would not have the same level of integration as running WSL.
WSL (at least WSL2 as used with the win11 improvements) is running linux in a (Hyper-V) VM - just one with a bunch of paravirtualization and communication between the VM and the host.
There's pretty much nothing WSL2 does that couldn't be implemented by building a bunch of host-side and guest-side components (you could theoretically even do it over a network with a remote VM, tho it'd be a significant performance hit). MS does have the advantage that they can tune the bits of Windows that their implementation uses to run a bit faster but it's nothing too groundbreaking really.
Other than Windows 11's secure boot requirement possibly getting in the way, you could do the same thing with windows on linux too, if you really wanted to.
WSL can invoke and interact with native executables.
The linux part of WSL2 can't directly invoke and interact with native executables - it talks to a paravirtualized interface that then asks a windows component to do so.
WSL runs on the host storage devices, not needing a virtual drive and the annoyances that come with it.
WSL2 runs in a virtual drive. It does mount Windows disks but they're comparable to network mounts (and perform pretty poorly)
VMs are generally a pain in the ass; WSL is not.
As above, it is a VM, though one with some decent integration work done.
I suspect you're thinking of WSL1 - it ran linux binaries in a Windows NT subsystem (using an interesting system of lightweight processes with custom syscall interfaces). It didn't run the linux kernel at all, it emulated the syscalls and behaviours. Performance to Windows filesystems was near-native (excepting some operations), and since WSL processes were Windows processes, they worked together quite well. Unfortunately MS decided not to pursue that method of running Linux further, and WSL1 has been basically dead for a while now (receiving mostly only security and regression bugfixes). Most of the new Windows 11 stuff won't run on WSL1 at all.
Re: (Score:2)
There's pretty much nothing WSL2 does that couldn't be implemented by building a bunch of host-side and guest-side components
Yep. There's nothing you can't do if you actually sit down and program one to do the same as the other. Sorry but that's an silly argument. May as well say Dos is the same as Windows 11 if only you sat down and programmed Windows 11.
Fact of the matter is in the list of off the shelf commercial programs the integration of WSL2 is unique among all solutions presently on the market.
And while many of your counters to the OP's post focus on WSL2 you completely neglect to say WSL still exists side by side, far fr
Re: (Score:2)
Yep. There's nothing you can't do if you actually sit down and program one to do the same as the other. Sorry but that's an silly argument. May as well say Dos is the same as Windows 11 if only you sat down and programmed Windows 11.
Not really, I'm making an architectural point - using VMs doesn't undermine the ability to integrate the things being referenced here, which is what was being claimed.
WSL2 *is* just a bunch of host-side and guest-side components. Many (most?) of the guest-side components are even open-source, meaning you may not need to reimplement many of them, just the host-side stuff.
And while many of your counters to the OP's post focus on WSL2 you completely neglect to say WSL still exists side by side, far from being dead MS's docs actually provide specific examples of which to chose for your application.
WSL1 still works but is dead as a platform - it's not being actively developed with new features, and will almost certainly be removed fro
Re: (Score:2)
The advantage of WSL is the lower overhead compared to a complete VM. Less memory used, boots in under 1 second. Even stuff like scheduling makes use of the Windows kernel, as well as filesystems and the like.
If your machine is powerful then maybe you don't care about that, or for you the extra protection a VM offers is valuable. For a lot of people WSL is a nice solution though. I use it often in preference to a full VM, it does everything I need and starts instantly.
Re: (Score:2)
You can achieve the same level of integration with running Wine in Linux, and depending on the age of your Windows application, compatibility may even be higher.
Re: (Score:2)
WSL runs on the host storage devices, not needing a virtual drive and the annoyances that come with it.
Did they ever fix the problem in WSL where you couldn't access USB drives or virtual drives like Boxcryptor and Veracrypt containers?
Re: (Score:2)
Yes, I've accessed Veracrypt virtual drives and USB drives. For both, I need to manually mount it from WSL. If there's an automount configuration, I haven't figured it out.
sudo mkdir -p /mnt/f; sudo mount -t drvfs F: /mnt/f
Re: (Score:2)
Running Windows in a VM would not have the same level of integration as running WSL.
Right, that separation is a feature. You're separating Windows from resources it's not sufficiently responsible to manage.
VMs are generally a pain in the ass; WSL is not.
Windows is generally a pain in the ass, which is why you generally benefit from not running it directly. When it inevitably explodes, you simply restart the VM instead of having to go through your entire POST. My potato has XMP memory and other stuff that extends POST and boot, so I like to avoid rebooting.
Why would I run Linux inside Windows inside Linux? (Score:2)
The article is confusing. What is the advantage compared to just running whatever I need directly in Linux?
Re: (Score:2)
I think the notion is:
I typically manage windows boxes, such as the fleet of user desktops in the enterprise, but occasionally need to administer some *nix boxes in the network also (such as remote SAN equipment, et al)--- And PuTTY is a bit cumbersome. Being able to do shell scripting and stuff is useful when I need to tell that shit to reboot, or restart its iSCSI chain.
Compared to the more linux-centric admin folk:
I typically manage *nix boxes, such as switches, routers, NAS equipment, and border gatewa
Re: (Score:2)
I'd say: The (very very expensive) error here is, that those desktops are Windows in the first place. As well as that that Exchange server exists. :)
Re: (Score:2)
Because CygWin is not commercially supported. Some businesses having someone responsible for keeping critical tools working to be vital.especially when another tool such ad a security tool breaks it.
Re: (Score:2)
Re: (Score:2)
Cygwin doesn't need Admin privileged to install.
(setup-x64.exe -B)
And that's an end of it.
Re: (Score:2)
Re: (Score:2)
He was simply confirming that cygwin can be a better solution than wsl. The wsl apparently requires admin access to install, whereas cygwin does not.
I've also used cygwin for many years, mostly to script and automate windows, often from remote machines via ssh.
Re: (Score:2)
Yes, Linux shops don't like supporting treasonous pieces of software that sleep with the enemy. That applies to WSL aswell. Don't expect our support with that setup. At best, it will be way overpriced.
Re: (Score:2)
Re: (Score:2)
Alpine, Kali, Ubuntu, and Debian are not "every major distribution". Those are the 4 listed at the Microsoft Store as supported. There's a complete lack of commercially supported Linux distributions there, especially distributions like SuSE and Red Hat which have their own commercial support from Oracle or AutoCad.
Re: (Score:2)
No Fedora?
Re: (Score:2)
Look for yourself. The store's menu is displayed in a popup link on https://docs.microsoft.com/en-... [microsoft.com], labeled "from the Microsoft Store".
I'd assume that Red Hat and SuSE based distributions are deliberately excluded.
Re: (Score:2)
Oh, but it's no bigotry. It's an accurate description of what any Linux admin worth their salt already thinks. It's free advice.
"Support from the community", so to speak :-p
Re: (Score:2)
It's not bigotry if the concern is well founded. It's why Windows admins are leery of Linux users in their network: we tend to be more demanding, and occasionally tell them how to do their jobs.
Re: (Score:2)
I don't think WSL is CygWin, or are you saying I should run CygWin in WINE to get a more Windows-like user experience? What's better about WSL in a Windows VM than just running the Linux stuff directly on the native OS. It could access the Windows VM if necessary.
Re: (Score:2)
Cygwin is exactly what it's name says it is:
Minimalist Cyngus for Windows. It's a posix distro for windows.
It has been around a very long time. (since the win9x days at least!) Its primary reason for existing was because the Posix subsystem for windows has been garbage/unmaintained for at least 4 windows releases, and there was some need for *nix support on windows boxes. (which Microsoft spent at least 20 years trying OH SO HARD to ignore.) Much like WSL, it is a full deployment package that gives an en
Re: (Score:2)
Back in the day I needed to get a radius server running on a Win2k server. It took a bit of finagling in the Makefile to get it to compile, along with using a utility so the executable would run as a service, but I had a functioning radius server on the windows box in about an hour. The other option was some rather expensive native windows radius servers. Needless to say I was pretty damned impressed by cygwin
Re: (Score:2)
The article is confusing. What is the advantage compared to just running whatever I need directly in Linux?
my use case - students need to be doing stuff in linux, but they're not geeks, have windows laptops, and aren't about to go blow away their whole computing life for the work they need to do for a class or a small research project.
Current WSL involves a lot of fiddling which is difficult for that target audience, because adding an X-server never seems to go the same way twice for two different students a semester apart, gotta find the current version, get env variables set, remember to run the X-server, etc.
Apostrophes (Score:2)
"The best part of Windows 11 is its Linux", not
"The best part of Windows 11 is it's Linux".
Apostrophes matter.
Re: (Score:2)
I thought it was mostly BSD. :D
Or is that just the parts that we can't check?
[That's the reason I prefer the GPL3 over the BSD licenses, even though the latter definitely are more free: The "more free" part applies to the freedom of *somebody else* to abuse *you*. Like use your code but give nothing back. And people who support it always believe they somehow will be that somebody else with the power. All of them. At the same time. (Just like 90% think they're among the smarter 50% of people.)
While GPL is li
Re: (Score:2)
"The best part of Windows 11 is its Linux", not "The best part of Windows 11 is it's Linux".
Apostrophes matter.
They're talking about Windows 12.
Re: (Score:2)
"The best part of Linux is it's not Windows 11”
Ahm, yes, apostrophes, and the ordering of words. And proper negation. And the primary OS, that also matters :-p
Re: (Score:3)
https://www.someecards.com/use... [someecards.com]
https://www.someecards.com/use... [someecards.com]
Re: (Score:2)
Hi isn't a pronoun, it's "him" so hi's doesn't work.
Re: (Score:2)
Commas save lives!
"The panda eats, shoots, and leaves."
Maybe not.
"Fairly obscure third-party software???" (Score:2)
Explain to me how X-server software is "obscure???"
Microsoft doesn't give WSL proper network access (Score:5, Informative)
Next time start with that. You can leave out the "killer-app" bull to make room.
Re: (Score:2)
Also, last I heard the USB and serial port options weren't working.
I still would not trust it ... (Score:3)
Running Linux under MS Windows means that Microsoft can get to snoop any password that is typed and potentially pass it on to the NSA. Now that an account registered with Microsoft is mandatory the NSA have a better idea of what those passwords might be for.
MS Windows under Linux is much safer.
Re: (Score:2)
...not to mention whatever current NSL'd side channel backdoor that hasn't been discovered by researchers yet is grabbing from your linux processes.
Re: I still would not trust it ... (Score:2)
Now that an account registered with Microsoft is mandatory
No, it isn't required - local accounts are supported in Windows 11.
https://www.thewindowsclub.com... [thewindowsclub.com]
Re: (Score:2)
A backdoor is not needed, they just get what they want with telemetry.
But... (Score:3)
Getting better, but it's still crap. You can't mount any old drive in WSl, only NTFS (aka no Paragon file system drivers, no Google drive drivers), you can't mount ext4 natively (though I understand that's in beta now)... and I don't think you can run Gnome and other desktop environents can you? You can run individual apps, but not a window managed environment. Every time I use WSL, I'm thinking, this is neat and all, impressive, but a ways to go before I can take it seriously.
The Best Part of Windows 11 Is Its Linux, (Score:2)
Multiple copies of the same image (Score:2)
Serious ?: nested hypervisor compatibility (Score:2)
So, I briefly attempted to use windows on the metal and WSL / Hyper-V etc to stack VMs on for "real work"
I need to run Windows, Linux and macOS VMs for mobile development environments
My pain point was that nested VMs inside all expect to run nested items (like Docker) using HAXM or QEMU etc, which did not seem possible as soon as you even attempt WSL.
As a concrete example, let's say you need to spin up a macOS VM (which is typically done with e.g. OSX-KVM) and that's QEMU so now that's working with Docker a
Re: (Score:2)
Right, got that. It's running inside the Hyper-V hypervisor, that leads to all the things I discussed above
I'm not able to get nested-virt going inside all of the guest OSes that I need to run, while Hyper-V is my on-the-metal hypervisor
Looking for solutions to that
It portends... (Score:2)
In all likelihood, MS has seen the same light as Crapple, and intends to become Unix rather than keep patching their kludged up I roll my own system.
Certainly not its looks (Score:2, Informative)
The screenshots I've seen of Windows 11 remind me of something designed by a girl about to go through puberty. Useless, annoying items front and center, colors all over the place, lack of coherence, and on the whole, pretty much unusable.
But that's what the programmers at Microsoft get paid for. Whatever it takes to justify their existence even if it means making something more difficult to use.
Go STRAIGHT to Linux.. if you can.. (Score:2)
why would you want that bloated surveillance suite on top of your operating system?
it just SUCKS that we can't run a lot of line of business apps which is forcing us to keep windows to ensure 100% compatibility.
Why bother.. (Score:2)
If you're forced to use Windows for *reasons*, why use an abortion like WSL, when you can either use Virtualbox, if you like Oracle (shudder) or, I suspect, you could use the built-in HyperV (I *assume* Win11Pro will have HyperV... Ya never know with MS) and run your distro of choice as a full VM.. I do the opposite, I use Linux and run a heavily castrated Win10 as a VM for the things I need to run that Wine upchucks over.
Re: (Score:3)
I have a server running Linux which I can ssh into, access it's drives via samba. It doesn't get much faster than that
Windows Subsystem: Bird-Rat (Score:2)
Desperately seeking Susan... (Score:2)
Desperately seeking Susan. Or Gloria. Or Fred. Or Cruella de Vil. Or some reason to consider using Windows 11.
Another juicy target with nary a Funny to its discussion.
Well, at least the FP didn't stink. But I think it was more Funny than Insightful. Your moderators may differ. Obviously.
Sounds good. (Score:2)
But all of the pandering to the lowest common denominator, largely due to popular culture telling people what they 'want' has stolen the spotlight.
This is not at all limited to Windows, as this has infected every major (consumer) OS now in use.
Hey Tim Apple, take note... (Score:2)
The day Microsoft has a viable fully POSIX compliant environment for Windows is the day that macOS will die, so please for the love of god, please port the macOS graphical interface and developer tools to run on top of a Linux kernel with GNU Sys V style userland instead of the current Mach kernel with BSD style userland. I would really appreciate not having to try to remember two separate dialects of the POSIX standard.