Slashdot Mirror
Microsoft Windows 10 Gains Linux/WSL Console Copy and Paste Functionality (betanews.com)
BrianFagioli writes: For better or worse, the Windows Subsystem for Linux (WSL) initiative seems to be moving full steam ahead. There are some very respectable distributions available in the Microsoft Store, such as Debian, Ubuntu, and Kali to name a few. Not to mention, Microsoft is trying to encourage even more maintainers to submit their distros with a new tool.
Apparently, some Windows 10 users have been clamoring for the ability to copy and paste both from and to WSL consoles -- a reasonable request. Well, as of Insider Build 17643, this is finally possible.
'As of Windows 10 Insider build #17643, you can copy/paste text from/to Linux/WSL Consoles!!! We know that this is a feature MANY of you have been waiting for -- our sincerest thanks for your patience and continued support while we untangled the Console's internals, allowing us to implement this feature. To ensure that we don't break any existing behaviors, you'll need to enable the 'Use Ctrl+Shift+C/V as Copy/Paste' option in the Console 'Options' properties page,' says Rich Turner, Microsoft.
Apparently, some Windows 10 users have been clamoring for the ability to copy and paste both from and to WSL consoles -- a reasonable request. Well, as of Insider Build 17643, this is finally possible.
'As of Windows 10 Insider build #17643, you can copy/paste text from/to Linux/WSL Consoles!!! We know that this is a feature MANY of you have been waiting for -- our sincerest thanks for your patience and continued support while we untangled the Console's internals, allowing us to implement this feature. To ensure that we don't break any existing behaviors, you'll need to enable the 'Use Ctrl+Shift+C/V as Copy/Paste' option in the Console 'Options' properties page,' says Rich Turner, Microsoft.
Seems backwards to me. Windows is the shit I need to install and run in a vm on my linux machine from time to time.
Website Just Down For Me? Find out
You mean the thing you freetards have been claiming Microsoft would do for 5+ years and Apple is supposed to be doing any moment for nearly a decade? Doesn’t it get old being so wrong with these doom and gloom predictions that never pan out?
With Mac going ARM, will the ARM MacOS be more of a walled garden like iOS. Will ARM Macs still permit Boot-Camp type dual-booting?
With Mac going ARM
But will Apple implement a locked bootloader?* Or leave it open? Locking it (per Microsoft's specification) does exactly one thing: It gives a user the ability to load Windows on their hardware. Not something Apple would seem to be promoting.
*Apple may implement a locked bootloader with their own keys, to enable a signed MacOS to run. And then they might sign a Linux bootloader as well. But just kick Microsoft to the curb.
Have gnu, will travel.
And, why would you want to run a high performance OS virtualized on a bloated OS when you can virtualize the bloated OS on top of the high performance OS that has provided this ability for years?
09 F9 11 02 9D 74 E3 5B - D8 41 56 C5 63 56 88 C0 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
I can't answer for anyone else but, while I have no interest in running a full Linux desktop at this time, I do like some of the tools available in the Linux terminal.
I did, in the past, try to run Linux as my main desktop, it failed miserably (don't get me started). I tried booting into it for the few tools that I preferred on the platform, it proved to be much too cumbersome to be worth it. Getting easy access to them from within Windows in a fashion that is not Cygwin, is all good in my book.
So, to answer your question, I guess WSL exists for people like me.
MacOS is not used to run Linux on a Mac.
It can be. macOS includes Apple's Hypervisor.framework, atop which tools (such as xhyve) can be used to run Linux inside macOS.
This is how Docker for Mac works; it runs the Linux kernel inside Apple's Hypervisor.framework, allowing you to run Linux containers. If you have XQuartz installed, with a bit of fiddling you can run Linux GUI apps inside Docker containers on the macOS desktop.
Yaz
The endgame is to marginalize desktop Linux as much as possible. This WSL thing is not desktop linux at all - it's a way to make sure linux back-end developers run Windows on their desktops instead of using desktop linux as the only way to bring their development environment with them.
And maybe, just maybe, that's enough for today's Microsoft. Sure, they'd love to lock down the hardware farther - and they may well try to do it. But they don't need to. Back-end Linux is no longer a threat to them - if only because they've already lost that battle. These days they'd rather you pay them to run Linux for you on their Azure cloud than worry about the fact that you're not using Windows for back-end development. But anything that marginalizes the Windows desktop stands a chance of harming the cash cow that makes the rest of their business work. So, Chromebooks are definitely a threat. Android, again, was a threat up until the moment that Microsoft conceded they'd lost that battle too. The biggest difference between today's Microsoft and Ballmer's is that they're capable of admitting loss and have figured out how to thrive anyway.
Posted from my Android phone. Oh, I can change this? There, that's better...
How long before MS considers mandating locked-down bootloaders on all Win 10 machines, even Intel?
Are you sure that they don't already require this because I have been copying and pasting to the WSL console for the past year. The only new thing that they seem to be adding is that you can do it with the usual windows keys instead of using the right mouse button for pasting from Windows->Linux or selecting with the mouse and Ctrl+C for pasting from Linux->Windows. Copy and paste is not a new feature.
The end game is to provide access to the tools developers like to use. They don't give a shit about "marginalizing Linux on the desktop" The Desktop isn't even a market they are interested in anymore.
WSL is better than CigWin. You get full access to the file system via Bash (or insert any shell you like) and can install any tools you need via the package manager of the distro you setup.
People who actually do real work need local software and storage -- they don't want to upload everything to the "clown" and be dependent on 24/7 connectivity. For pure consumers, maybe you're right.
WSL uses regular GNU/Linux distributions and runs their native binaries. So it's almost as native as, say, running the distribution in a VM, except the distro cannot use GUI tools, but does have access to the native file system.
The major issue I've found with WSL is that features will suddenly stop working and require a reboot after a random period of time. For example, on three separate computers running different versions of Windows 10, and with one maintained by someone who isn't me, I've seen 'ssh' just plain stop working after a few days.
Cygwin doesn't seem to be as well maintained as, say, Ubuntu. And so that's the biggest advantage of WSL. But... Cygwin does at least work as advertised.
You are not alone. This is not normal. None of this is normal.
I moved from Cygwin to WSL when the latter came out. Not sure what the permission quirks are in Cygwin, but the bad news is there are permission quirks in WSL (everything looks like 777). The good news is those will be fixed in the next regular update (and are currently fixed, I'm told, in the Insider Build). Read more here:
https://blogs.msdn.microsoft.c....
I believe another advantage over Cygwin is that you can install Linux apps directly from the distro's app install, rather than waiting for the Cygwin-specific exe's to be built. I also installed the Linux version of TeXLive direct from tug.
WSL is not a virtual machine running Linux, in fact it's not Linux at all. Linux is a kernel. People think of distributions built around the Linux kernel as being Linux, but you can run other kernels with the same tools. Depending on your objectives and kernel choice, you can get very different or practically identical functionality while still not technically running Linux. That's all WSL is; it is a bundle of tools associated with Linux distributions but running on the Microsoft Windows kernel instead.
Your concerns about Windows accessing the Linux RAM don't make any sense in regards to WSL because it isn't a separate or hosted OS. Of course Windows has access to WSL memory; WSL is an integrated part of Windows. The point of WSL is to give Windows users less motivation to switch to a different OS, which it does fairly well. Most of the things I want to do in Windows but would normally have to switch to Linux to do are easy to do with WSL, meaning no switch is necessary. Most of the work I get paid to do needs to be done in a Microsoft OS (not always Windows) but it is easier and sometimes massively faster to do some things with the tools that were previously only supported by dual booting or running a VM. WSL makes my job simpler in that respect.
All that said, your concerns make sense in regard to Hyper-V. I think you're wrong about MS's goals there too, but at least it is a debatable topic.
B) Eliminate all the stupid users. This is frowned upon by society.
There seems to be a common misunderstanding that WSL is running a Linux kernel. It isn't. WSL is still running on the Windows kernel. People think of popular Linux distributions as being Linux, but they're only Linux because of the kernel, not because of the tools they're bundling to create a distribution. When you switch to a BSD or Mach kernel using the same tools, you're no longer using Linux, regardless of the programs you're running. That's what WSL is too. It's a distribution's bundled tools running on a different kernel, in this case the Windows kernel.
It'd make more sense to call it Ubuntu on Windows. Really though, it makes more sense for MS to call it "Linux" because that's what people think of when they hear the word. Otherwise you'd have "GNU on Windows" and spend all your time explaining you're talking about running a Linux distribution on Windows without using actual Linux. It's like insisting people use the original meaning of the word "hacker." If you use the word to mean what it really means, then people won't understand what you mean.
I know this post is pretty much off topic, but a lot of people still seem misled by the term and I hope at to help clear up the misconceptions for a couple people.
B) Eliminate all the stupid users. This is frowned upon by society.
You can use ubuntu's (debian's) `apt` to install/update the actual Ubuntu binaries instead of using cygwin's inferior setup.exe to install recompiled win32 binaries linked to a slew of compatibility libraries.
Try it. You can run them both at the same time - I did for a while until I uninstalled Cygwin.
The endgame is to marginalize desktop Linux as much as possible.
Errr. No. No one at Microsoft gives a crap about the Linux desktop. It barely registers a blip on market share figures. On the other hand they do care quite a bit about Linux being used in 1/3rd of back end instances on their Azure cloud and are trying to give customers a way of using ${APPLICATION} without leaving the Windows environment.