4 ms·
You can compile your own kernel to use with WSL2. See the Config file for how you can specify the path to your own kernel and the command line to pass to it: h
by MarkSweep 4y ago
You can compile your own kernel to use with WSL2. See the Config file for how you can specify the path to your own kernel and the command line to pass to it:
https://learn.microsoft.com/en-us/windows/wsl/wsl-config https://learn.microsoft.com/en-us/windows/wsl/wsl-config
Here is adding ZFS support:
https://wsl.dev/wsl2-kernel-zfs/ https://wsl.dev/wsl2-kernel-zfs/
- mikepurvis 4y agoI think the GP's ask is for native Windows support, which is orthogonal to anything WSL/WSL2 can do.
- barrkel 4y agoNative Windows support would conflict with the WSL2 stack, at its integration level. File system drivers aren't generally designed to share the underlying block device between different kernels concurrently. The block device isn't consistent with the latest writes without flushing caches, and a native driver wouldn't see those caches without hooking the Linux kernel, but that's not the WSL2 integration point. WSL2 is based on virtualization not kernel hooking. Native Windows would be able to access the file system as long as you killed all WSL2 processes first, and vice versa: run any WSL2 process and lose native access. Access via network makes far more sense.
- Dylan16807 4y agoThe WSL2 kernel already has Ext4 support.