24 ms·
Do not change Linux files using Windows apps and tools
- hartator 10y agoIt sounds bad but WSL is working really good, but yeah use '/mnt/c' to share files between the 2 systems. It actually comes organically.
- softawre 10y agoYou have it backwards. The problem is changing linux files with windows editors.
- Whitestrake 10y agoThe problem is changing Linux files that are currently stored in %localappdata\lxss\ using a Windows tool. Changing Linux files that are stored in C: and are accessed in Windows from C: and in Linux from /mnt/c/ is fine.
- SwellJoe 10y agoI ran into this problem within days of starting to use Bash on Windows. Had several files just disappear, though I didn't need to reinstall anything (so far). They should really document this issue better, like in the docs for installing WSL.
- cyptus 10y agosame here, tried to modify some files in my windows IDE while using them from an apache on the linux subsystem - had to change the webserver directory to /mnt/c/...
- ocdtrekkie 10y agoIn fairness, as the author points out, the files are hidden and marked as "system". People tinkering with files flagged system are usually going to have a bad time. You have to specifically go digging for this, and then decide you want to mess with it. Microsoft's platform design is generally open enough to allow you to do dumb things. This is a good thing, because you can reg-hack your way around problems with the OS. But like editing the registry, doing so is very much at your own peril, it's really not designed to be tampered with by users.
- mcbits 10y agoI don't think it's fair to blame people for thinking they could edit simple text files under that folder, well-hidden as it is. How many people already knew there would be any issues beyond line endings (not counting those who learned by breaking things)? I sure didn't. It's pure luck that I hadn't tried it yet.
- ocdtrekkie 10y agoIt's absolutely fair. To even SEE these files, there's a warning you must click through that notifies you that you can cause significant harm to your system if you modify them. So when one does so, and then one modifies them... one should definitely expect to cause significant harm. People who enable visibility on protected system files and then act upset that messing with protected system files breaks things, are the sort of reason we don't give out admin rights where I come from.
- mcbits 10y agoI don't think it's fair to be upset when editing those files breaks things, either. To be surprised? Yes, definitely. It is fair to expect software labeled "beta" to break in surprising ways, so I hope they're not giving permission to use WSL in production where you come from.
- SwellJoe 10y agoHmm...none of that matches my experience. I opened them from Powershell or git bash and from Atom, maybe vim was involved. I don't remember the process of getting there, but I do remember it being tricky to find the directory where the Linux environment lived, but, maybe, a grep or find was involved. Windows Explorer was not involved. I'm a 20+ year Linux user. I use Linux tools to find things and to navigate places. I guess if I were a Windows user, who does things in the usual Windows way, I might have received a warning of some sort. I'm just saying it'd be cool if there were a warning somewhere in the docs about this issue. It wasn't something I expected. I mean, I don't have to worry about editing "Windows" files on my Linux system with WINE. And, I'm able to mount my Windows partition from Linux and edit files without fear of harming things. I assumed things worked the same way for WSL. It was a wrong assumption, but I don't feel like it means I'm stupid to have made it, based on the knowledge I had at the time.
- bitcrazed 10y ago"They should really document this issue better, like in the docs for installing WSL" What, like this bit in the install instructions page: https://msdn.microsoft.com/en-us/commandline/wsl/install_guide https://msdn.microsoft.com/en-us/commandline/wsl/install_gui... After installation your Linux file system components will be located at: C:\Users\<Windows user name>\AppData\Local\lxss\ This directory is marked as a system file which are hidden by default. Accessing this location directly is not advised due to caching between the Linux and Windows file systems. Check out our blog post for more information.
- sqeaky 10y agoWhy should an application need to be aware of the file meta data in most situations anyway? Shouldn't the OS handle the metadata unless the application specifically requests otherwise?
- willtim 10y agoI'm guessing the issue is that many apps use the Windows APIs badly and just recreate files rather than updating them.
- saurik 10y agoOr they use the Windows API well and purposely create new files rather than updating old ones to get atomic updates (the same way that most editors on Unix never ever update existing files and instead create new ones on which they call rename()).
- willtim 10y agoWell they obviously aren't checking for metadata / extended attributes when reading the files.
- lucaspiller 10y agoThis issue exists on Linux too :-) ext4 supports extended attributes including the creation time, but most apps blindly rename which means the metadata is lost.
- KirinDave 10y agoI'm glad someone else said it. I was biting my tongue.
- sqeaky 10y agoIn both operating systems, aren't there APIs for this?
- hs86 10y agoRecently I tried to cut corners by copying my ~/.ssh from Cygwin into my WSL-user's home directory with the Windows Explorer and wondered why the folder was not visible from within WSL. cp-ing it from within WSL's /mnt/... solved the issue but left me still wondering. At least this post confirms that there be dragons, if I move files manually into the lxss folder.
- willtim 10y agoTo be fair cygwin has a similar problem. It attempts to map Unix permissions to NT and gets confused if Windows apps modify the permissions.
- qwertyuiop924 10y agoBut this happens even if window tools don't change permissions. That is awful.
- jxy 10y ago"Windows deleted my homework…" Seriously, is mounting files readonly that hard to do? If you can't deal with linux files, leave them alone.
- deleted 10y ago[deleted]
- matt_wulfeck 10y agoYou sound like the kind of engineer that keeps software perpetually stuck in a UX nightmare. "Of course it doesn't work that way, idiot! If only you read the obscure documentation and had years of experience like me you'd understand why you're the problem and not the software!"
- TheCapn 10y agoI mean.... the article does point out: Remember: There’s a reason we gave the %localappdata%\lxss\ folder ‘hidden’ & ‘system’ attributes You gotta work your way around a couple mild safeguards to go fucking with things.
- matt_wulfeck 10y agoAnything that has the potential to corrupt your filesystem should come with a huge disclaimer.
- freekh 10y agoYeah... I learnt this the hard way a couple of weeks back... Sigh...
- ChuckMcM 10y agoHah I wasn't the only one reporting this "mis-feature" I bet. I wonder if Microsoft could license the old NetApp 'unified' protections code that let you export a volume to both CIFS and NFS. In my case I pulled a git clone into the Linux side of a project that was building using a third party gui tool, ran that from windows and my Bash window got soooo confused. Seriously though, if they can improve the terminal "behavior" and figure out a work around for USB device access this will be really stellar.
- alecthomas 10y agoOut of curiosity, how is the Linux integration? Does it feel like native, or is it disjointed like Cygwin always has?
- ChuckMcM 10y agoI find it much more useful/natural than cygwin. The places where it reminds me it isn't Linux is when something wants to create a Unix domain socket (screen) or needs access to /dev or something like that. CPAN works fine as does ssh and most things I use from the command line (gcc embedded and make, vim, etc). Nothing that would pop up an xwindow works (as expected).
- bitcrazed 10y agoIn more recent Windows Insider builds, Tmux & Screen now work correctly, as does network connection enumeration (e.g. via ifconfig), sshd works as expected, along with MySQL, Apache, nginx, etc.
- ChuckMcM 10y agoI am clearly very excited that you seem to be making this a 'real' thing rather than just a talking point. You realize there is a 'usb over ethernet' spec right? And using that and a windows service on a local socket on the windows side you could arbitrate exclusive access to plugged in USB devices to the Bash shell user right?
- angryasian 10y agoIn general these types of issues are why their implementation doesn't work for me. I'd prefer something with more seamless integration. When on windows I pretty much stick with git bash and windows implementations of my dev stack.
- matt_wulfeck 10y agoMicrosoft is adding the ubuntu subsystem, which means this is a "problem" that's only going to get worse before it gets better. Thankfully once it gets better it will be a lot easier to use both systems and you won't need to keep such rigid isolation between the systems.
- arjie 10y agoI would expect that something that's marked Hidden and System requires you to think a little harder before you do something to it. You have to jump through hoops to do something to those files.
- wnevets 10y agowhat is the general opinion of linux for windows so far?
- KirinDave 10y agoIt's good, although "beta" is a fair description. Many things work, but there are a few sharp edges. For example, gradle doesn't work well yet, and if you go backwards into lxrun (rather than out via /mnt/c) you run into this bug. It's surprisingly good for an initial implementation, but it's far from perfect.
- mmirate 10y agoWrong direction of layering, and thus of limited use imho. Of the two OSes, the weaker link, security-wise, is definitely Windows 10 rather than Linux. Putting Linux programs under a Windows 10 abstraction layer means that any malware, bugs or "bugs" (remember, this is proprietary software) in Windows 10 have the ability to transparently subvert or surveil the Linux programs. In this aspect, WSL is just like putting a Linux VM on a Windows host (albeit more performant and convenient, yes).
- nxc18 10y agoEvidence? Windows has continuously made improvements in security and there has been a lot of emphasis there in the last ~10 years. If you have some reasoning, I want to see it, because I just can't find any studies/blogs/anything one way or the other. Also note that this isn't intended as a security feature - it is a convenience to get Linux userland programs on Windows without a resource-hogging VM.
- klagermkii 10y agoThis is a pity. One of the things I like with the Mac is being able to use Mac-side editors like BBEdit to be able to make changes to the configuration and files of the Unix-y server tools I need. If I can't reliably use Windows GUI editors that would limit my ability to migrate from macOS. If one is running NGINX/PHP under WSL would one not even be able to safely edit .php files?
- bphogan 10y agoLike the article says. You point your Nginx to serve files out of the "c" drive mount point.
- sp332 10y agoNo, at least not from that directory. You need to use tools that know how to update the WSL-specific metadata in the NTFS extended attributes, and Windows programs do not do that. You would need to set up a file server so that the programs could communicate using a standard protocol. Edit: or as hartator says in another thread, store your files somewhere under /mnt/c/.
- kej 10y agoThe lxss folder is for things you only want to access from Linux. Things like a .php file you want to access from both sides goes somewhere else. In Windows you go to C:\MyPHPFiles and in Linux you go to /mnt/c/MyPHPFiles.
- sbuttgereit 10y agoThis. I use WSL daily and edit in both Linux & Windows... but the files I'm dealing with are in a directory structure that set up on the windows side and I get to them through /mnt/<drive letter>. Completely painless for me. I do have to occasionally edit Linux config files and whatnot and, yes, I do that with emacs or vim (depending on mood), but it's honestly not often and I personally prefer the terminal based editors in Linux for that better (yeah, a preference thing there... ). Anyway, been working like this since before the Anniversary Update on the later insider builds and it's been pretty solid and seamless for me.
- bphogan 10y agoFTA: > I have to provide this guidance at least 2-3 times a day so instead I am publishing it here so everyone can find / link-to this guidance. This may be oversimplifying, but if that's the case, then there's a design problem. Either you should make it work, or you should do some better defense against it up front. If the solution is "eh, just work out of a Windows folder", this isn't really better than using a VM. Heck, I've been using WSL since the beta, and using Vagrant + Putty gives me better results. I was hopeful it would get better, but then I saw this post and shook my head. "Silly users, stop trying to do things we didn't plan for you to do!"
- ad-hominem 10y agoFrom the article: "Remember: There’s a reason we gave the %localappdata%\lxss\ folder ‘hidden’ & ‘system’ attributes " So if you go messing about in hidden system folders, you get what you deserve.
- josho 10y agoOne could also argue that an editor that loses extended file attributes when editing a file is broken. I would have preferred msft to have posted an article explaining that files have attributes and editors must not loose those attributes when making edits.
- jahewson 10y agoFiles on Windows don't have attributes. Files on an NTFS volume may have extended attributes associated with them but you'll need to go out of your way to find them and doing so has never been a requirement of working with files on Windows. Not supporting an obscure non-mandatory thing hardly constitutes "broken". An editor which just kept the existing attributes would still end up with incorrect time stamps - so now all Windows apps need to know how to handle Linux file attributes? Nope - because these files were never meant to be edited by Windows apps. And it works best that way.
- 10y ago
- captainmuon 10y agoFun fact: the linux metadata is stored in a little known NTFS feature called "extended attributes" (EA), which is not the same as alternate data streams. You need to use a pretty obscure API to access them. I started writing a tool to do so, only to find that someone already did, including a decoding of the (binary) EAs (which basically contain Linux uid, gid, permissions, ctime I think): https://www.reddit.com/r/bashonubuntuonwindows/comments/52w86h/lxssattr_a_very_basic_stat_of_sorts_to_show_linux/ https://www.reddit.com/r/bashonubuntuonwindows/comments/52w8... There is currently no tool that writes the EAs. It should be not too hard to write one, however it won't work transparently - WSL maintains a cache of this metadata, so you'd likely have to quit all WSL applications before you make any changes to avoid corruption.
- j_s 10y agoLXSS extended file attributes viewer https://github.com/dmex/lxssattr https://github.com/dmex/lxssattr - the actual project for the decoder
- JorgeGT 10y agoAccording to their UserVoice response, this feature is "in the backlog", so maybe someday it will be available: https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13856379-make-wsl-filesystem-accessible-from-windows#comments https://wpdev.uservoice.com/forums/266908-command-prompt-con...
- jasonjei 10y agoHas Windows harmonized line breaks? Or is it still \r\n rather than \n like in the *nix world?
- OliverJones 10y agoIs the Pope Hindu? Do bears use the restrooms in the Waldorf Astoria hotel?
- zouhair 10y agoThis is like some bad teen movie where the bully is forced to live with the nerd.
- MBCook 10y agoIf this directory is special, why doesn't Windows treat it that way? Put something in the EA that means "This file can't be read/modified by normal programs" so people can't make the mistake in the first place. Obviously making it so programs can modify these files successfully would be great, but that's a much bigger job.
- nxc18 10y agoIt is marked special. You have to go out of your way to even see it, and Windows Explorer complains and gives you a stern warning when you do.
- MBCook 10y agoAs someone who hasn't used Windows in 15 years... I didn't know that. I'm glad I got down voted to find out. Either way, once you get to it, couldn't the filesystem APIs treat it read-only and prevents someone from making these kind of mistakes in the first place?
- wvenable 10y agoThat's a lot of exceptional cases for something you shouldn't touch. It's kind of like saying, if I'm root and I've disabled "--preserve-root" and then I "rm * /", that Linux should have something else to prevent the user from hosing their own system. I mean they could do that, but where do you draw the line?
- wvenable 10y agoYou can also delete your entire C:\Windows folder and on Linux you can delete /sbin -- same permissions apply.
- mcbits 10y agoAnother thing to watch out for is how you have git configured to handle newlines. Usually the recommended config under Windows is to have it transparently change them to \r\n when you clone a project, and back to \n when you push. This trips up some Linux tools when you use those files from the Linux subsystem. Best either turn that feature off or only use the Linux git for any projects you plan to touch from there, even if you're saving them under /mnt/... to share with Windows. And of course you'll have to beware of how your Windows editors are saving those files. I wish the Windows world had just migrated to UTF-8 and \n 10 years ago. It would all be smooth sailing by now.
- Const-me 10y agoMost Windows apps, both third-party and built-in, support UTF-8 for many years. Just not by default. You need to specify your data is UTF-8: http://unicode.org/faq/utf_bom.html http://unicode.org/faq/utf_bom.html
- revelation 10y agoThis is clearly broken. Don't be too smart for your own good and use long abandoned features like NTFS "Extended attributes". Save the stuff you need in a metadata file and be done with it.
- deleted 10y ago[deleted]
- quotemstr 10y agoUse Cygwin. This problem and related issues point toward reasons why: Cygwin is _designed_ to bridge, by hook or by crook, the gap between the Win32 and POSIX worlds. It's not perfect, but it tries to work in a mixed environment --- even ACLs mostly work. Cygwin's Windows integration is so good that you can call CreateWindow from a Cygwin process and have it Just Work. The NT POSIX subsystem, on the other hand, is a very different beast. It's more of a container or VM-like object. That kind of operation is useful for some tasks, but when I want to use POSIX and Windows tools together on the same task, I don't want a container. I want tight integration, which Cygwin provides.
- Callmenorm 10y agoMy experience with cygwin never "Just works". WSL needs to hit a much higher bar if they are going to seduce the people who use macOS because it's a better linux.
- TazeTSchnitzel 10y agoWSL is not the NT POSIX subsystem, which was a completely different thing that died a while ago.
- quotemstr 10y agoIt's not SFU either, but it's a reincarnation of the same idea. It's a subsystem distinct from the Windows one. This year's branding is irrelevant.
- xorblurb 10y agoThe new approach is relevant. NT POSIX or SFU was a completely different target from mainly used Unixes of their time. Now GNU/Linux has supplanted everything (Mac Os does not really rely on nor is administered by its Unix layer), Ubuntu is a major and well maintained distro, and even the WSL Beta in the AU has a quite impressive compat -- and the last insider versions are even better. So will WSL become irrelevant? Maybe: either at the same time Ubuntu does, or if MS decides to stop this subsystem project. I hope they don't... :)
- mevile 10y agoIn this comment thread there are many people who did not read the entire article to its conclusion, and then also failed to read the many comments about the very last and very important bit at the end of the article. There ought to be like a "didn't read the article" link next to the comment people can click to quickly bury those comments. It would avoid people having to reply again and again to say the same thing that commentator could have just learned had they read the article. Especially, you know, this bit: > Remember: There’s a reason we gave the %localappdata%\lxss\ folder ‘hidden’ & ‘system’ attributes There are multiple comments in this thread right now with that line in them.
- hueving 10y ago>There ought to be like a "didn't read the article" link next to the comment people can click to quickly bury those comments. There is, it's the downvote button. The distinction of why a downvote is useless.
- wst_ 10y agoWhat are the requirements to be able to down vote?
- nothrabannosir 10y agoa karma threshold. 800 or something?
- EdwardCoffin 10y ago500, I only just gained downvote ability in the past few weeks, when I finally gained more than 500. Edit: another thing I should have mentioned is that it seemed to me that only those comments made after I gained this ability were downvotable, the thread my last few comments were in was sprinkled with downvotable comments, which were newer, and non-downvotable comments which were there before mine. I might have been imagining this or be mistaken though.
- necessity 10y ago"What should I do instead?" - use a decent os
- z3t4 10y agoOr cryptic error messages because the config file contains a "carriage return".
- smegel 10y ago1. DO store files in your Windows filesystem that you want to create/modify using Windows tools AND Linux tools 2. DO NOT create / modify Linux files from Windows apps, tools, scripts or consoles What bizarrely contradictory advice. "Use Windows tools to modify files used by Linux, but don't use them to modify Linux files".
- hakonrossebo 10y agoWSL is a great feature that could really improve the development workflow on windows. The WSL would benefit from a blogpost with a different perspective, describing how to do web development, mounting into Windows filesystem, -how to setup and use tmux/vim etc.
- bitcrazed 10y agoGreat idea - can't wait to see your post :)
- Someone 10y agohttps://blogs.msdn.microsoft.com/oldnewthing/20050715-14/?p=34923/ https://blogs.msdn.microsoft.com/oldnewthing/20050715-14/?p=...: "if you delete some file "File with long name.txt" and then create a new file with the same name, that new file will have the same short name and the same creation time as the original file." It might open a security can of worms, but there might be a safe way to do that for those essential Linux attributes, too, for example if the program deleting the file has write permissions on it.
- deleted 10y ago[deleted]
- eriknstr 10y agoI think what's sad about this is the users who will believe that it was a fault of Linux that their files disappeared and as a result they will stay with MS.
- brak1 10y agoi'm a bit out of the loop - why/how would you be doing this? Windows has a directory now for linux files?
- djsumdog 10y agoWindows 10 has an entire Linux subsystem now. They've implemented the posix APIs and there are other blog posts where people have gotten things like i3 running natively in Windows. It's only in the preview builds and you have to specifically enable it.
- xorxornop 10y agoWell, um, I'm not running a preview build, but I have it. It's been there since the Anniversary update
- mastazi 10y agoWindows 10, since Anniversary Update, has a new feature (not enabled by default) where you can have an entire (Ubuntu-based) Linux user space running natively (no VM) on your Windows machine, it's called Windows Subsystem for Linux: https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subsystem-for-linux-overview/ https://blogs.msdn.microsoft.com/wsl/2016/04/22/windows-subs...
- mastazi 10y agoHonestly, this should be obvious for anyone who has at least a bit of experience with Linux. It's the same reason why you use tar.[extension] when you create an archive - Tar saves the Linux metadata (ownership, permissions). To those who claim this need to be fixed, I want to ask: how? I mean if I modify a file in the Linux filesystem as a Windows user, what should the ownership be? Root? Some non-root user? Should we just make those files 777? Each of those solutions would bring more problems. It seems to me that there is no "one size fits all" fix here.
- jaza 10y agoFor many years now, I've had one or two NTFS partitions on my dual-boot machine (Win7/Ubuntu), which are regular drives in Windows, and which are volumes mounted with all files set to 777 permissions in Linux. Have never had any problems with corruption, access denied, etc. Works great for volumes that mainly contain documents and media (and some Windows executables). But you can't mount "/" and co like that, and similarly, I can imagine that it would be inadequate for WSL, which stores many system files on NTFS, where many of those files have to use more restrictive permissions (e.g. 600 for many core binaries / configs), otherwise errors result.
- userbinator 10y agoI mean if I modify a file in the Linux filesystem as a Windows user, what should the ownership be? Inherited from the directory, like it is on Windows and Linux (by default)? And 777 is a perfectly fine default, since it's a good match for the Windows default attributes and ACLs. It seems to me that there is no "one size fits all" fix here. There isn't. But there is a sensible default, which is not "assumes the file is corrupted/damaged". Consider what happens in Linux if you mount a filesystem like FAT which doesn't even support all the extended metadata. No extended metadata does not mean "I can't do anything with the files", unlike what seems to be happening with WSL here.
- dozzie 10y ago> Inherited from the directory, like it is on Windows and Linux (by default)? Who lied you such horribly that under any unix a newly created file is owned by the owner of the directory? It's not even generally true for group ownership, which has a little more frivolous behaviour! > And 777 is a perfectly fine default 0777 permissions are never fine as a default. It's asking for security vulnerabilities.
- rmurri 10y ago
- rmurri 10y ago
- johnhenry 10y agoI ran into an issue when I first started using WSL. I was able to mitigate it by changing the settings on my text editor to use LF line endings and ensuring that git does not automatically modify line endings upon checkout. I have not had any issues since.
- 45h34jh53k4j 10y agoPerfectly reasonable but I do suggest that Microsoft should have made the folder invisible to admin (need SYSTEM or higher, etc), so users were not tempted to touch the files in that folder.
- wvenable 10y agoExcept that you need permissions to those files to, you know, use them in the subsystem for Linux. The WSL, correctly and securely, runs under your user account.
- sytelus 10y agoTLDR; if you are using BashOnWindows then don't modify files in lxss folder from Windows or otherwise BashOnWindows will break. Use bash to modify those files.
- drieddust 10y agoSame goes other way. Modifying windows files on a POSIX system end up creating incompatibility which aren't easily resolvable. As an example, one can create a file with a trailing space easily but good luck trying to mamage it using standard windows tools. I am not sure why MS thinks this is a good idea.
- SticksAndBreaks 10y agoAddition: Do not modify files which where modifyied in another OS that was send into hibernation. A world of pain awaits you.
- krzrak 10y ago> Creating/changing Linux files from Windows will likely result in data corruption and/or damage your Linux environment requiring you to uninstall & reinstall your distro! It's funny, that this is so Windows-centered advice (regarding the "uninstall & reinstall"). Fixing things in Windows very often boils down to "just do the reinstall". In Linux you have lots of other tools and methods to recover from such disaster.
- ygra 10y agoWell, if you're so inclined, you can re-create the NTFS extended attributes on the file you broke and things should be back to normal. However, the article is for people who clearly don't know what they're doing, or what they broke and how, so I think giving the »Have you tried turning it off and on again« advice is just about right for those folks. And even on Windows you can fix most issues in different ways than reinstalling, it's just that for some degrees of brokenness it's by far the faster solution (cf. just re-cloning a git repository instead of figuring out what is broken).
- jmsmistral 10y agoJust don't use Windows... See how this gets down-voted
- fetbaffe 10y agoSo many people in this thread that think that this is the end of WSL and you should use Cygwin instead. Laughing. Cygwin is awful compared to WSL. Poor performance, always gotchas, cygpath handling etc. Sure it was a good option back in the day and a good engineering feat. With WSL I get an environment that behaves exactly like Linux, complete POSIX without gotchas. I work with WSL all the time on files located on Windows partions. Works perfectly. Just create symlinks in WSL to Windows folders and you are ready to go. Why do people even need to work with files in the hidden system folder? The only files that I maybe want to change from Windows to WSL would be .bashrc et al, but just copy it or edit them from WSL and problem solved. If I don't want to use WSL and I only need a shell, then MSYS2 is the way to go, handles Windows and POSIX paths interchangeably without the cygpaths hassle. And no, WSL is not like SFU, that never really worked.
- JdeBP 10y agoYou clearly only used the first Windows NT POSIX subsystem, and never used Interix, the second one. * https://news.ycombinator.com/item?id=11416392 https://news.ycombinator.com/item?id=11416392 * https://news.ycombinator.com/item?id=12866843 https://news.ycombinator.com/item?id=12866843
- ezy 10y ago
- fetbaffe 10y agoPro tip: I use wsl-terminal with WSL https://github.com/goreliu/wsl-terminal https://github.com/goreliu/wsl-terminal