Learn About Windows Console & Windows Subsystem For Linux (WSL)

最新推荐文章于 2025-11-24 13:05:01 发布
转载 最新推荐文章于 2025-11-24 13:05:01 发布 · 293 阅读 · 0
文章标签：

#windows #linux #WSL #linux kernel

本文围绕Windows Subsystem for Linux (WSL)展开，介绍了其自2016年发布以来的相关情况，包括官方文档更新、不同Windows 10版本中WSL和Windows Console的新特性，还提供了播客、深度解析等学习资源，以及使用WSL进行C++代码构建和调试的示例。

Windows Subsystem for Linux (WSL) has made a lot of waves since it was announced at //Build 2016 in April 2016. But as with any new technology, many people have questions including:

  • How does Bash on Ubuntu on Windows (Bash) work?
  • What is Windows Subsystem for Linux (WSL)?
  • Where do the Linux files exist on my HDD/SSD?
  • How are Linux binaries loaded and executed?
  • How the heck does this thing work??? (Hint: Magic ;))
  • How do I install it?
  • Etc.

Official Documentation

The official WSL documentation is regularly updated with improved instructions, and documentation for new features as we continue to improve WSL. Be sure to revisit regularly to keep up to date!

Overviews

To help answer some of these questions we’ve collected together most of the learning resources – docs, blog posts, and videos, below, where you can learn all about this exciting new Windows 10 feature:

Original Build 2016 WSL Introduction

This is our original intro video which was published simultaneously with the original launch of WSL at Build 2016:

Note that most of the caution urged in the video regarding WSL’s initial “gaps” and “missing features” have been remedied in the Insider builds leading up to, and including, Windows 10 Creators Update.

 

What’s new in WSL and Windows Console in Windows 10 Anniversary Update?

Here’s a video summarizing what’s new in WSL and Console in Windows 10 Anniversary Update:

 

What’s new in WSL and Windows Console in Windows 10 Creators Update?

After Windows 10 Anniversary Update was launched, we immediately began work on features that will ultimately show-up in Windows 10 Creator Update (due spring 2017). These new WSL and Console features were introduced in the Windows Insider builds rolling out of our build labs during the latter half of 2016, which I summarize in this post:

What’s new in WSL & Windows Console in Windows 10 Fall Creators Update?

In this video, Craig Loewen outlines what’s new in Windows 10 Fall Creators Update for Windows Console and WSL:

 

You can also read about new WSL features in Fall Creators Update.

Podcasts

Want to learn more about WSL while you’re away from your screen? Listen to the following podcast interviews:

  1. Shortly after unveiling Bash/WSL for the first time, Rich was interviewed by Richard Campbell & Carl Franklin, of .NET Rocks fame for episode #1284 titled “Making Windows Command Line Cool Again”:

  2. After the Windows 10 Creators Update release, Rich was interviewed by Mary Jo Foley, Paul Thurrott & Leo Laporte on episode 514 of the popular “Windows Weekly” video/audio cast show, for a session titled “Bash on Windows” (of course :D)

Deep Dives

We invited some of the key WSL architects and developers to explain the key internal workings of WSL. The result is a series of WSL internals-focused blog posts and Channel9 videos recorded by the inimitable Seth Juarez for your viewing enjoyment!

Note: This list of posts and videos will be updated as we publish new content!

  1. Blog: Windows Subsystem for Linux: Architectural Overview
  2. Blog: Windows Subsystem for Linux: Process Architecture
  3. Blog: Windows Subsystem for Linux: WSL System Calls
  4. Blog: Windows Subsystem for Linux: WSL File System Support
  5. Blog: Windows and Ubuntu Interoperability
  6. Blog: WSL Networking Hope you enjoy these resources. We have more planned, but if there’s anything you’re particularly interested in learning about, pile onto the comments

What can you do with WSL?

The resources below share examples of what you can do with WSL. We hope to grow this list over time, so please check-back often to see some of the cool things people do with WSL!

Use Visual C++ for Linux to build and debug C++ code on WSL

During Windows DevDays on Feb 8th 2017, Stacey and Rick demonstrated using Visual C++ for Linux to compile and debug an application on WSL! Many thanks to Marc & the team for their help building this demo!DevDays Feb 2017  

Updates

  • 2017/10/17 – Added “What’s new in Win10 FCU” for Console & WSL blog posts
  • 2017/10/10 – Added “What you can do with WSL” section & VC++ link
  • 2017/07/21 – Added link to official docs
  • 2017/07/07 – Added podcast links
  • 2016/06/09 – Added Syscalls post & video
  • 2016/06/15 – Added Filesystem post & video
  • 2016/10/20 – Added Interop post & video
  • 2016/11/15 – Added Networking post & video
  • 2016/12/15 – Added Update video

 

原文：https://devblogs.microsoft.com/commandline/learn-about-windows-console-and-windows-subsystem-for-linux-wsl/

WSL安装与入门
m8705的博客
09-07 2971
WSL ，是一个允许Linux 二进制程序在 Windows 10 环境下运行的兼容层。 WSL 本身不是一个虚拟机，并没有模拟硬件环境，它是通过动态翻译系统调用来实现运行 Linux 应用程序的。 有了 WSL ，就可以在 Windows 10 里跑常用的Linux 程序，无需安装庞大笨重的 VM，有效提升开发体验。 1. 安装 WSL 第一步，启用 Windows 系统...
如何在win10环境下搭建visual studio跨平台开发环境
u013526342的博客
03-06 483
安装visual studio 2019：安装时根据需要选择相关模块：C++、Linux 下载并安装WSL：可以选择unbutu，并配置好相关环境 下载并安装visual studio code集成开发环境：安装C/C++，Remote WSL组件 待续。。。 相关链接： 1.Get started with the Windows Subsystem for Linux https://do...
在适用于Linux的Windows子系统(WSL)上运行和调试多平台.NET（.NET Core、.NET5和.NET6）GUI和控制台应用程序
寒冰屋的专栏
11-16 2034
本文详细介绍了如何使用非常强大的.NET和Avalonia组合以及WSL来调试在Windows上的Visual Studio 2022中开发的Linux .NET应用程序。
linux conf文件读写,WSL文件读写权限的配置方法
weixin_35625324的博客
04-28 1921
Windows subsystem for Linux昨天晚上俄罗斯世界杯开踢了，看起来足球世界还是没怎么变，梅罗仍然统治世界，沙特仍然被欧洲球队打穿，中国队仍然四年一度的缺席……但是技术的世界却是日新月异，连微软都拥抱开源了，Windows subsystem for Linux (WSL) 简直是在赤裸裸的勾引程序员扔掉Mac投奔Windows。既有Windows的桌面和Office套件，又可...
折腾记录：WSL（Windows Subsystem for Linux，Windows上的Linux子系统）安装后的环境配置
贵州山魈羡民|大定府羡民|贵州穿青人的博客
05-20 2142
WSL（Windows Subsystem for Linux，Windows上的Linux子系统）的安装比较简单，教程网上较多，此处略过。安装后须要进行一系列配置（如软件源配置、中文配置、图形化配置、开发环境配置）才能投入使用，以Ubuntu为例（其他Debian、Kali、OpenSUSE等Linux系统也类似）。 1、配置中国科学技术大学的软件源 Ubuntu自带的软件源天朝访问比较慢，...
WSL(Windows Subsystem for Linux)的安装与使用
01-03 2413
有关WSL的介绍这里就不做解释了。另外，本文仅适用于win10build16215以及之后的版本，之前的版本可参考官方链接。 （可使用“winver”命令查看windows版本号） 安装： 1. 管理员权限运行powershell并运行下面的命令： Enable-WindowsOptionalFeature -Online -FeatureName Microso...
使用 wsl-terminal 更好地体验 Win 10 WSL 终端环境
weixin_33852020的博客
09-17 733
WSL 从最初功能不全 bug 遍地都是，到现在除了少数几个比较顽固的 bug 外，基本足以正常使用了。但自带终端模拟器的体验依然非常糟糕，而且在可以预期的未来都不会有太大的长进了。我是从去年 8 月开始开发wsl-terminal（中文页面）的，期间因为想不到可以添加什么功能而搁置了比较长时间。最近心血来潮，添加了很多实用功能，用户体...
windows上的linux子系统（WSL）
千霜的博客
03-19 1万+
目录一 介绍二 原理2.1 wsl组件 一 介绍 Windows Subsystem for Linux（WSL）是一个用于在本地运行linux二进制可执行文件（ELF格式）的兼容层。与虚拟机相比，wsl没有虚拟硬件的过程，而是直接在windows上虚拟一个linux内核，模拟linux系统调用，以运行linux执行文件。因此效率要比虚拟机高，但是它使用的是自己实现的init进程而不是发行版的in...
wsl使Windows上的软件开发再次变酷
weixin_26711867的博客
10-16 1109
I felt in love with Ubuntu a long time ago, when I was able to run World of Warcraft on my machine that had 256MB and no graphics card at all, and I’ve been coding there ever since. The bad thing abou...
构建您的第一个应用程序 按照教程进行作 这是 Electron 教程的第 2 部分。 先决条件 构建您的第一个应用程序 使用预加载脚本 添加功能 打包您的应用程序 发布和更新 学习目标 在本教程的这一部分中，您将学习如何设置 Electron 项目 并编写一个最小的入门应用程序。在本节结束时， 您应该能够在开发模式下运行一个有效的 Electron 应用程序，来自 您的终端。 设置项目 避免 WSL 如果您使用的是 Windows 计算机，请不要使用适用于 Linux 的 Windows 子系统 （WSL） 在遵循本教程时，因为您在尝试执行 应用。 初始化 npm 项目 电子应用程序使用 npm 搭建脚手架，文件为 package.json 作为切入点。首先创建一个文件夹并初始化一个 npm 包 在其中有 .npm init npm 纱 mkdir my-electron-app && cd my-electron-app npm init 此命令将提示您在package.json中配置一些字段。 出于本教程的目的，需要遵循一些规则： 入口点应该是（你很快就会创建该文件）。main.js author、license 和 description 可以是任何值，但以后打包时将是必需的。 使用常规文件夹安装依赖项node_modules Electron 的打包工具链要求文件夹物理位于磁盘上，在 npm 安装节点依赖项的方式。默认情况下，Yarn Berry 和 pnpm 都使用替代安装策略。node_modules 因此，如果您使用 那些包管理器。 然后，将 Electron 安装到应用程序的 devDependencies 中，这是外部 生产中不需要仅开发包依赖项。 为什么 Electron 是开发依赖项？ 这似乎有悖常理，因为你的生产代码正在运行 Electron API。在引擎盖下， Electron 的 JavaScript API 绑定到包含其实现的二进制文件。包装步骤 Electron 处理此二进制文件的捆绑，无需将其指定为生产 屬地。 npm 纱 npm install electron --save-dev 警告 为了正确安装 Electron，您需要确保其生命周期 脚本能够运行。这意味着避免在 npm 上使用标志，并允许列入在其他包管理器上运行构建脚本的权限。postinstall--ignore-scriptselectron 这可能会在 Electron 的未来版本中改变。有关更多详细信息，请参阅 electron/rfcs#22。 初始化包后，您的package.json文件应该如下所示 并安装 Electron。您现在还应该有一个文件夹，其中包含 Electron 可执行文件，以及指定 要安装的确切依赖项版本。node_modulespackage-lock.json package.json { "name": "my-electron-app", "version": "1.0.0", "description": "Hello World!", "main": "main.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "author": "Jane Doe", "license": "MIT", "devDependencies": { "electron": "23.1.3" } } 高级 Electron 安装步骤 如果直接安装 Electron 失败，请参阅我们的高级安装文档，了解有关下载镜像、代理和故障排除步骤的说明。 添加 .gitignore .gitignore 文件指定要避免跟踪的文件和目录与 Git。您应该将 GitHub 的 Node.js gitignore 模板的副本放入项目的根文件夹中，以避免提交项目的文件夹。node_modules 运行 Electron 应用程序 进一步阅读 阅读 Electron 的流程模型文档以更好地了解 Electron 的多个流程如何协同工作。 您在 package.json 中定义的主脚本是任何Electron 应用程序的入口点。该脚本控制主进程，该进程在Node.js环境中运行，负责控制应用程序的生命周期、显示本机接口、执行特权作以及管理渲染器进程（稍后会详细介绍）。 在创建您的第一个 Electron 应用程序之前，您将首先使用一个简单的脚本来确保您的main 进程入口点配置正确。在根文件夹中创建一个文件使用一行代码：main.js main.js console.log('Hello from Electron 👋') 因为 Electron 的主进程是一个Node.js运行时，所以你可以执行任意的Node.js代码（你甚至可以把它用作 REPL）。要执行这个脚本，add 到你package.json的 scripts 字段中的命令。这个命令会告诉 Electron 可执行文件在当前目录中查找主script 并在开发模式下运行它。electronelectron .start package.json { "name": "my-electron-app", "version": "1.0.0", "description": "Hello World!", "main": "main.js", "scripts": { "start": "electron .", "test": "echo \"Error: no test specified\" && exit 1" }, "author": "Jane Doe", "license": "MIT", "devDependencies": { "electron": "23.1.3" } } npm Yarn npm run start Your terminal should print out . Congratulations, you have executed your first line of code in Electron! Next, you will learn how to create user interfaces with HTML and load that into a native window.Hello from Electron 👋 Loading a web page into a BrowserWindow In Electron, each window displays a web page that can be loaded either from a local HTML file or a remote web address. For this example, you will be loading in a local file. Start by creating a barebones web page in an file in the root folder of your project:index.html index.html <!DOCTYPE html> <html> <head> <meta charset="UTF-8" /> <!-- https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP --> <meta http-equiv="Content-Security-Policy" content="default-src 'self'; script-src 'self'" /> <meta http-equiv="X-Content-Security-Policy" content="default-src 'self'; script-src 'self'" /> <title>Hello from Electron renderer!</title> </head> <body> <h1>Hello from Electron renderer!</h1> <p>👋</p> </body> </html> Now that you have a web page, you can load it into an Electron BrowserWindow. Replace the contents of your file with the following code. We will explain each highlighted block separately.main.js main.js const { app, BrowserWindow } = require('electron') const createWindow = () => { const win = new BrowserWindow({ width: 800, height: 600 }) win.loadFile('index.html') } app.whenReady().then(() => { createWindow() }) Importing modules main.js (Line 1) const { app, BrowserWindow } = require('electron') In the first line, we are importing two Electron modules with CommonJS module syntax: app, which controls your application's event lifecycle. BrowserWindow, which creates and manages app windows. Module capitalization conventions Typed import aliases ES Modules in Electron ECMAScript modules (i.e. using to load a module) are supported in Electron as of Electron 28. You can find more information about the state of ESM in Electron and how to use them in our app in our ESM guide.import Writing a reusable function to instantiate windows The function loads your web page into a new BrowserWindow instance:createWindow() main.js (Lines 3-10) const createWindow = () => { const win = new BrowserWindow({ width: 800, height: 600 }) win.loadFile('index.html') } Calling your function when the app is ready main.js (Lines 12-14) app.whenReady().then(() => { createWindow() }) Many of Electron's core modules are Node.js event emitters that adhere to Node's asynchronous event-driven architecture. The app module is one of these emitters. In Electron, BrowserWindows can only be created after the app module's ready event is fired. You can wait for this event by using the app.whenReady() API and calling once its promise is fulfilled.createWindow() info You typically listen to Node.js events by using an emitter's function..on + app.on('ready', () => { - app.whenReady().then(() => { createWindow() }) However, Electron exposes as a helper specifically for the event to avoid subtle pitfalls with directly listening to that event in particular. See electron/electron#21972 for details.app.whenReady()ready At this point, running your Electron application's command should successfully open a window that displays your web page!start Each web page your app displays in a window will run in a separate process called a renderer process (or simply renderer for short). Renderer processes have access to the same JavaScript APIs and tooling you use for typical front-end web development, such as using webpack to bundle and minify your code or React to build your user interfaces. Managing your app's window lifecycle Application windows behave differently on each operating system. Rather than enforce these conventions by default, Electron gives you the choice to implement them in your app code if you wish to follow them. You can implement basic window conventions by listening for events emitted by the app and BrowserWindow modules. Process-specific control flow Checking against Node's process.platform variable can help you to run code conditionally on certain platforms. Note that there are only three possible platforms that Electron can run in: (Windows), (Linux), and (macOS).win32linuxdarwin Quit the app when all windows are closed (Windows & Linux) On Windows and Linux, closing all windows will generally quit an application entirely. To implement this pattern in your Electron app, listen for the app module's window-all-closed event, and call app.quit() to exit your app if the user is not on macOS. app.on('window-all-closed', () => { if (process.platform !== 'darwin') app.quit() }) Open a window if none are open (macOS) In contrast, macOS apps generally continue running even without any windows open. Activating the app when no windows are available should open a new one. To implement this feature, listen for the app module's activate event, and call your existing method if no BrowserWindows are open.createWindow() Because windows cannot be created before the event, you should only listen for events after your app is initialized. Do this by only listening for activate events inside your existing callback.readyactivatewhenReady() app.whenReady().then(() => { createWindow() app.on('activate', () => { if (BrowserWindow.getAllWindows().length === 0) createWindow() }) }) Final starter code docs/fiddles/tutorial-first-app (39.0.0) main.js index.html const { app, BrowserWindow } = require('electron/main') const createWindow = () => { const win = new BrowserWindow({ width: 800, height: 600 }) win.loadFile('index.html') } app.whenReady().then(() => { createWindow() app.on('activate', () => { if (BrowserWindow.getAllWindows().length === 0) { createWindow() } }) }) app.on('window-all-closed', () => { if (process.platform !== 'darwin') { app.quit() } }) Optional: Debugging from VS Code If you want to debug your application using VS Code, you need to attach VS Code to both the main and renderer processes. Here is a sample configuration for you to run. Create a launch.json configuration in a new folder in your project:.vscode .vscode/launch.json { "version": "0.2.0", "compounds": [ { "name": "Main + renderer", "configurations": ["Main", "Renderer"], "stopAll": true } ], "configurations": [ { "name": "Renderer", "port": 9222, "request": "attach", "type": "chrome", "webRoot": "${workspaceFolder}" }, { "name": "Main", "type": "node", "request": "launch", "cwd": "${workspaceFolder}", "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron", "windows": { "runtimeExecutable": "${workspaceFolder}/node_modules/.bin/electron.cmd" }, "args": [".", "--remote-debugging-port=9222"], "outputCapture": "std", "console": "integratedTerminal" } ] } The "Main + renderer" option will appear when you select "Run and Debug" from the sidebar, allowing you to set breakpoints and inspect all the variables among other things in both the main and renderer processes. What we have done in the file is to create 3 configurations:launch.json Main is used to start the main process and also expose port 9222 for remote debugging (). This is the port that we will use to attach the debugger for the . Because the main process is a Node.js process, the type is set to .--remote-debugging-port=9222Renderernode Renderer is used to debug the renderer process. Because the main process is the one that creates the process, we have to "attach" to it () instead of creating a new one. The renderer process is a web one, so the debugger we have to use is ."request": "attach"chrome Main + renderer is a compound task that executes the previous ones simultaneously. caution Because we are attaching to a process in , it is possible that the first lines of your code will be skipped as the debugger will not have had enough time to connect before they are being executed. You can work around this by refreshing the page or setting a timeout before executing the code in development mode.Renderer Further reading If you want to dig deeper in the debugging area, the following guides provide more information: Application Debugging DevTools Extensions 总结 电子应用程序是使用 npm 包设置的。应该安装 Electron 可执行文件 ，可以使用 package.json文件。devDependencies 可执行文件运行在package.json属性中找到的 JavaScript 入口点。 该文件控制 Electron 的主进程，该进程运行 Node.js 的实例，并且是 负责应用的生命周期，显示本机接口，执行特权作， 以及管理渲染器进程。main 渲染器进程（或简称渲染器）负责显示图形内容。您可以 通过将网页指向网址或本地 HTML 文件，将网页加载到渲染器中。 渲染器的行为与常规网页非常相似，并且可以访问相同的 Web API。 在本教程的下一节中，我们将学习如何使用 特权 API 以及如何在进程之间进行通信。 总结并为我写出完整的步骤
11-01
> 建议不要使用 WSL（Windows Subsystem for Linux）来运行 Electron 开发环境，可能会导致图形界面无法显示。 --- ### 2. 初始化 npm 项目 ```bash npm init -y ``` 这会生成一个默认的 `package.json` 文件。你...
windows_安装WSL2
浪漫韫秋
04-05 2223
参考文章：https://learn.microsoft.com/en-us/windows/wsl/installTheand useutilities, andunmodifiedor开发者可以在Windows机器上同时访问Windows和Linux的强大功能。允许开发者安装并直接在Windows上使用Linux应用程序实用程序和Bash命令行工具，而无需对其进行修改，也无需传统虚拟机或双启动设置的开销。
Linux Bash on Win10 (WSL)在cmder下使用vim时方向键失灵问题解决
热门推荐
路茫茫
01-07 1万+
Linux Bash on Win10 (WSL) 方向键最终解决　　 cmder代替cmd，PowerShell
解决cmder启动wsl报错
veiTian的博客
09-16 1875
Windows 在 cmder 启动 wsl 时出现以下问题： wslbridge error: failed to start backend process note: backend error output: -v: -c: line 0: unexpected EOF while looking for matching `'' -v: -c: line 1: syntax error: unexpected end of file ConEmuC: Root process was aliv
Java泛型详解：尖括号＜＞、通配符?与类型参数T
倚肆的博客
11-21 141
语法基础：尖括号<>是泛型的语法标志。定义泛型：当需要定义一个可重用的泛型类、接口或方法时，使用类型参数T（或EKV。它提供了类型安全和一致性。使用泛型：当需要使用泛型结构，且方法的逻辑不依赖于具体类型时，使用通配符?（尤其是上界extends T>和下界super T>），这能极大提高API的灵活性。记住PECS原则。避免使用原始类型：不要使用没有类型参数的泛型类（如List list），这会失去类型安全优势。# Java泛型详解：尖括号<>、通配符?与类型参数T。
单链表（C语言，手撕）
最新发布
weixin_51226647的博客
11-24 108
手撕单链表
Python 数据结构
weixin_45776000的博客
11-21 556
1.2 常用操作1.3 列表推导式1.4 性能考虑。
Kotlin中的infix函数：优雅的DSL设计利器
dongdeaiziji的专栏
11-21 504
Kotlin的infix函数允许以更自然的语法调用函数，省略点号和括号。它必须是成员/扩展函数，且只能有一个参数。常见应用场景包括：创建测试断言（如x shouldBe y）、构建DSL（如SQL查询）、数学运算和集合操作。虽然infix能提高代码简洁性，但需注意优先级规则（低于算术运算符）并避免过度使用影响可读性。最佳实践包括选用直观的函数名、保持简单逻辑，特别适合领域特定语言开发。合理使用infix可使API更优雅，但应始终以代码清晰度为优先考量。
Spring boot启动原理及相关组件
2509_94083376的博客
11-21 1058
ConfigurationClassPostProcessor的优先级为最高，它会对项目中的@Configuration注解修饰的类(@Component、@ComponentScan、@Import、@ImportResource修饰的类也会被处理)进行解析，解析完成之后把这些bean注册到BeanFactory中。在github里，我把Spring Boot应用启动的拓展组件（自定义的应用初始器、监听器、事件、ApplicationRunner）都写了例子，可参照阅读。
Windows Subsystem for Linux (WSL) 教程与指南
&quot;Windows Subsystem for Linux (WSL) 是微软推出的一项技术，允许用户在Windows操作系统上直接运行原生的Linux环境，包括各种命令行工具、实用程序和应用程序，无需虚拟机或双启动设置。该文档详细介绍了WSL2及其与...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值