4 ms·
Command prompt should run the windows version and bash should run the linux version. Why would there be an issue here?
by manigandham 11y ago
Command prompt should run the windows version and bash should run the linux version. Why would there be an issue here?
- chx 11y agoExactly. The Linux file system will have Windows mounted into it but I think Windows won't be able to see the Linux filesystem. We will see.
- sspiff 11y agoLinux and Windows can both see each others filesystem, but they are visible at specific mount points in each environment. You can't just use /home/chx/todo.txt as a path from any Windows application, but you can find that file through some other path.
- chx 11y agoVery interesting. What about case sensitivity?
- SEMW 11y agoThe underlying filesystem (NTFS) is case-sensitive, so I think it should basically work fine. Sure, Windows tools are case-insensitive, so if you use bash to create foo and Foo in the same directory you'll probably only be able to access one of them from Windows Explorer, but I doubt that's much of a problem for most people
- RobMurray 11y agoIt does seam to be case sensitive! Creating two files called a and A works. They even show up in explorer. It doesn't work to delete one of them from explorer though. No errors - they just reappear. After trying, I now have a file called a that I can't delete from bash or explorer!
- deleted 11y ago[deleted]
- JdeBP 11y agoNo. See https://news.ycombinator.com/item?id=11415671 https://news.ycombinator.com/item?id=11415671 .
- tdicola 11y agoSo will the bash prompt not see any tools like windows python in the windows system path? That seems like an odd decision if so.
- alkonaut 11y agoYou will find windows executables mounted just like the rest of the windows file system, so in bash you can find /mnt/c/windows/notepad.exe but you can't execute it from the bash subsystem (I presume). The opposite is also true: the linux subsystem files are mounted under a regular directory in windows, so you can see all the files but from the normal windows subsystem you can't execute the linux binaries. It means there is a big wall between the two systems, and you can't really automate windows things with bash instead of PS if you wanted. At this point though I find that to be a benefit - It would be fantastically confusing if you typed "find" or "python" and had to wonder whether a linux program or a windows program would actually execute.
- voltagex_ 11y agoI wonder how hard it would be to implement PowerShell Remoting for this environment