![]() ![]() ![]() If any of the others say No, you can’t run Hyper-V. If Virtualization Enabled = No, go into BIOS and enable it. ![]() To verify that my desktop system could run Hyper-V, ZDNet (Bott, 2016) suggested (in effect) running Win-R > msinfo32 > System Summary (in left pane) > scroll to bottom > verify that the four items referring to Hyper-V all say yes. OmgUbuntu said the user could run WSL 1 if the machine did not run WSL 2, but did not provide details on that procedure. The logical sequence in that case would be to set up WSL on the desktop and then create that WTG drive. ![]() Thus, I would be able to run WSL 2 on my Win10 Home laptop only by booting it with a Win10 Pro WTG drive. Microsoft ( 2022) said that Hyper-V was available only on Windows 10 Pro, Enterprise, and Education editions – not on Win10 Home. To install it, however, OmgUbuntu said my system would have to support Microsoft’s Hyper-V. OmgUbuntu ( 2022) stated that the updated version (WSL 2) used in Windows 11 was a major upgrade from WSL 1. But I would find that it didn’t do what I wanted. (See also e.g., GNU Utilities for Win32, circa 2003 GetGnuWin32, 2006 CoreUtils for Windows, 2005.) Certainly it appeared that WSL would require much less disk space: I saw estimates of ~2GB (e.g., SuperUser) as compared to a minimum of 23GiB for Cygwin (Tech Help Notes, 2022). My question was, which was the best way to enable Linux commands on Windows? Sobyte ( 2021) compared the built-in Windows Subsystem for Linux (WSL) against Cygwin as well as the apparently older and more limited MinGW and MSYS, and concluded that WSL offered the best solution. I began this post as what I hoped would be a quick and simple summary of the process of enabling Windows 10 21H2 to run Linux commands, with notes on a few issues encountered along the way. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |