access Linux symlinks from \\wsl$
**Is your feature request related to a problem? Please describe.** I want to be able to open a symlink from the **'\\wsl$\Ubuntu'** directory. The reason for this Is I'm writing a program that would read an elf binary and import the required objects to run it inside the directory that the binary is in. This is from a virtualization perspective the kernel we use is linux based and Im purely looking at a way to improve development of apps on Windows. The only thing I want to do with the files is be able to read them and copy to a location without any changes. But most elf objects link to shared libraries that are symlinks but Windows doesn't seem to know what to do with that file. Any sort of open on that file results in system could not find the name specified. I assume this is because the explorer is attempting to open the symlink but its at a path it doesn't understand like **'/lib/64'** instead of **'\\wsl$\Ubuntu\lib\64**'. **Describe the solution you'd like** Maybe on the file open in the windows explorer prefix it with the location of the symlink. **'/lib/64**' turns into opening **'\\wsl$\\Ubuntu\lib\64'** I imagine this would be a big task probably. **Describe alternatives you've considered** I could probably resolve this from the perspective of installing another daemon on my subsystem and just do the calls there. I'm mainly querying about this so I can improve UX of our application and the user doesn't have to install two of the same thing. Is there a use case
Posted by trentis on Apr 21, 2020, 4:12 AM
Tags
Related issues
- [Codex Desktop][Windows] Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)
- I loathe how difficult Matrix is for normal people though.
- Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking fo...
- Unfortunately there doesn’t seem to be any decent alternative.
- I'm wondering how much of that is bad developer UX and defaults, and how much of that is inherent complexity in the problem space.
- Pulumi support
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
ux (Sysadmin)
[Codex Desktop][Windows] Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)
I loathe how difficult Matrix is for normal people though.
Fragile against upgrades, tons of unmaintained plugins, admin panel UX is a mess where you struggle to find the stuff your are looking fo...
Unfortunately there doesn’t seem to be any decent alternative.
I'm wondering how much of that is bad developer UX and defaults, and how much of that is inherent complexity in the problem space.
Pulumi support
[Feature]: managing cnpg in GitOps workflows (FluxCD, ArgoCD ...)
Merge the platform and UI threads
access Linux symlinks from \\wsl$
**Is your feature request related to a problem? Please describe.** I want to be able to open a symlink from the **'\\wsl$\Ubuntu'** directory. The reason for this Is I'm writing a program that would read an elf binary and import the required objects to run it inside the directory that the binary is in. This is from a virtualization perspective the kernel we use is linux based and Im purely looking at a way to improve development of apps on Windows. The only thing I want to do with the files is be able to read them and copy to a location without any changes. But most elf objects link to shared libraries that are symlinks but Windows doesn't seem to know what to do with that file. Any sort of open on that file results in system could not find the name specified. I assume this is because the explorer is attempting to open the symlink but its at a path it doesn't understand like **'/lib/64'** instead of **'\\wsl$\Ubuntu\lib\64**'. **Describe the solution you'd like** Maybe on the file open in the windows explorer prefix it with the location of the symlink. **'/lib/64**' turns into opening **'\\wsl$\\Ubuntu\lib\64'** I imagine this would be a big task probably. **Describe alternatives you've considered** I could probably resolve this from the perspective of installing another daemon on my subsystem and just do the calls there. I'm mainly querying about this so I can improve UX of our application and the user doesn't have to install two of the same thing. Is there a use case
Comments (0)
No comments yet. Start the discussion.