![]() ![]() Right now, the idea is to implement the syscall interface (consisting mainly of calls from usermode to kernelmode) and parts of the kernel that are visible from userspace (/proc and /dev). Stehufntdev is on the NT kernel team (see his name!), and he is probably genuinely seeing what the demand is for this feature, but if you read some of the blog posts, it seems like this is beyond the scope of the WSL project for the foreseeable future. This is also why WSL doesn't support things like reading ext-filesystems, because the NT Kernel does not have drivers for them. However, since most of the output services for Linux (X, Pulseaudio, etc) are network-transparent, you can run the Win32-ported versions of their servers (vcXsrv, Pulseaudio) in TCP mode, and the Win32 ports have Windows driver support (which means you generally won't need to have WSL supporting Linux drivers). WSL does not have any display hardware, drivers, or really anything you might expect to exist on a real machine. ![]() I wouldn't run virtualbox through WSL anyway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |