In a way Ballmer was right -"Cancer" is eating Windows ;)
File System Improvements to the Windows Subsystem for Linux
41–50 of 108 posts
Re: File System Improvements to the Windows Subsystem for Linux
#42What would be a good X11 server to use? Are there any that support the full stack? (shm, glx, etc.)
I work for the company, mostly use a Mac, sometimes use X11, and started laughing when I read X11 server on WSL/Linux on Windows. Things have come a long way. I don't know if there is X11 support, but when I have some time later this week, I am going to look based off this question and see. I'm having visions of Hummingbird Exceed from back in the day at the moment.
I'm not being flip, I'm actually curious as well and will try figuring out when I have a spare few moments.
Re: File System Improvements to the Windows Subsystem for Linux
#43Earlier quoted context omitted.
Sorry, I have to ask. Why do you need to use Java with WSL? Native methods?
I would love this because I still want a 'real' shell when dealing with Java - things like emacs, grep, find, etc. Cygwin and using shared VM directories has too many glitches with things like npm, links, file system endings, etc. As Docker becomes more important, this gets even worse. Really, developing on a Mac is just so much better than both Windows and Linux, even for Java.
But why not just use Linux?
Re: File System Improvements to the Windows Subsystem for Linux
#44Windows subsystem for Linux? Or the Linux subsystem for Windows?
These names are confusing...
Re: File System Improvements to the Windows Subsystem for Linux
#45Windows subsystem for Linux? Or the Linux subsystem for Windows? These names are confusing...
Microsoft also has an Android emulator for Windows.[1] One would think that would run into licensing problems.
Re: File System Improvements to the Windows Subsystem for Linux
#46What would be a good X11 server to use? Are there any that support the full stack? (shm, glx, etc.)
> What would be a good X11 server to use? Are there any that support the full stack? (shm, glx, etc.)
I recall using exodus in the past (at uni), but it's commercial (pricey). Not to mention these days it seems to be Mac only.
From similar threads I've seen recently, and quick searching, it seems Xming is the preferred Windows-option these days:
Re: File System Improvements to the Windows Subsystem for Linux
#47Windows subsystem for Linux? Or the Linux subsystem for Windows? These names are confusing...
I suppose it might be named that way due to trademark conserns.
Naming something as "X for Y", where "Y" is a trademark owned by someone else is often done, but I haven't seen "Y for X".
Just speculating.
Re: File System Improvements to the Windows Subsystem for Linux
#48Earlier quoted context omitted.
Seems like you might be better served with a linux desktop and windows in a VM then. The use case for WSL right now is someone like a web developer. They can develop and debug node apps locally in their native environment.
That only works because they provide emulation for AF_INET, AF_UNIX and AF_NETLINK sockets. It's not an automatic freebie.
> That only works because they provide emulation for AF_INET, AF_UNIX and AF_NETLINK sockets. It's not an automatic freebie.
To be pedantic, Microsoft is actually emulating the whole lot. You're not running a Linux-kernel on your Windows-machine.
Re: File System Improvements to the Windows Subsystem for Linux
#49Windows subsystem for Linux? Or the Linux subsystem for Windows? These names are confusing...
It's confusing, but accurate. It's a subsystem of Windows ("Subsystem" is a well-defined term in Windows land, the win32 API is o its own subsystem as well).
I wish they had promoted the name lxss more, though. It's short, very googlable, and it's the internal name.
The git repo name is even more ridiculous: https://github.com/Microsoft/BashOnWindows
(after all, I had bash on windows for years already)
Re: File System Improvements to the Windows Subsystem for Linux
#50I wish there was a way to get lxss updates without being a Windows Insider.
I turned on Insider on my brand new laptop last summer and it immediately overwrote some vendor-supplied drivers by newer-but-broken ones. Result: no sound. I didn't manage to fix it except through a full reinstall. Now that's exactly the sort of problem you need to prepared for when doing the Insider thing, but it sortof ruins the point. I want to beta test lxss, not Paint 3D or some fancy new device driver release schedule.