therube wrote: ↑
Fri May 22, 2020 2:40 am
is not a good idea, as it messes with files inside the subsystem in way it's not directly notified of
(Not at all familiar with WSL) but it not "real", or does it rely on pseudo-linkages back to Windows?
(What a travesty that must be if that's the case. Take a real OS & kludge it into a kludge.)
Anyhow, while Everything can be used for darn near Everything, for the file searching
part, can't see how that would negatively affect - anything?
Is \\wsl$\ "real"? As in can you add that as a Folder Index in Everything?
Well, I'm not an expert on the exact anatomy of this process, but I believe WSL runs on Hyper-V somehow, but perhaps not directly -- I know it requires Hyper-V to be enabled to be installed. WSL2 is supposed to be a full-on Linux kernel with managed virtualization, but that doesn't come out to full release until the 28th of this month. Anyhow, you can enable WSL and install a Linux flavor from the Microsoft store.
As I understand it, it has a virtualized environment where files live inside from the linux end like you'd expect
, but actually exist in the above-mentioned AppData directory. I believe this is just how the virtualization is being done, rather than using, a managed volume file (though I think WSL2 will do that). So editing the files from the Windows side is done "outside" of the WSL linux, so it can cause issues in some situations, again, so I'm to understand.
The preferred, supposedly "correct" way to access the files is through the network share hosted from WSL's linux side that it is aware of this. But I don't know how to add it. Folders gives me a tree instead of an input, and if I look into Network, I can't see it, but I don't see \\wsl$\ in my Network window normally. I just know it's there, and I pinned it to my quick access.
I was just wondering if there was an established way to index files from it -- even if that required installing something inside the linux. Currently, I am searching the file, finding the Windows AppData one, then going into the network share and following the directory string to get to the file I want, then sending that file to the application I want. This is obviously not ideal, haha. I don't think searching this way affects anything, it's just super inconvenient. I wanted to have Everything find files how we're meant to.
If you give me a test to establish if \\wsl$\ is real or not, I can certainly perform it, but I'm not sure how else to check. Hopefully I've given enough helpful information anyhow.