Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

Post reply on HN
Print view View original

261–270 of 316 posts

Re: Bash and Windows Subsystem for Linux Demo [video]

#261

Post by pshposh »

osd wrote: post #226
tornadoboy55 wrote: post #166

Earlier quoted context omitted.

http://eclecticist.co.uk/notes/appledesign/images/image12.jp... That's all I need to say about that. As for the reasons.. Devs want a POSIX (macOS, Linux or BSD) system because many of the utilities used are written for that, and much of the infrastructure you will be working with in the future will also be POSIX. Of all the POSIXes, macOS is by far the most capable and stable laptop OS. Macbooks are still unrivaled,…

http://macdailynews.com/2007/10/02/lecture_hall_photo_shows_... That's apparently the school of journalism...

Wow that site really doesn't like adblockers

Re: Bash and Windows Subsystem for Linux Demo [video]

#262

Post by pshposh »

bitcrazed wrote: post #159
oblio wrote: post #37

Earlier quoted context omitted.

The Notepad line ending thing is kind of shameful but Notepad is ok for what it's supposed to do. It truly is a Note pad. It launches quickly and has a non-nonsense interface. It's not meant to be a programmer's editor. It never was, it never will be.

Agree 1000%! Was waiting for a comment like yours to help drive the case for some updates to Notepad to support NIX file endings, etc. ;) Anyone running Win10 who wants to see Notepad support NIX file endings, PLEASE submit feedback via the feedback app - that way Notepad's owners get to see your pleas ;)

Unfortunately the Feedback Hub application requires me to adjust my system wide privacy settings to allow sending who knows what to Microsoft.

I suppose I could temporarily change the setting just to give line ending feedback for notepad.

Re: Bash and Windows Subsystem for Linux Demo [video]

#263

Post by jaxn »

bitcrazed wrote: post #174
platz wrote: post #100

Earlier quoted context omitted.

I was under the impression that only linux sub-system applications should be modifying files inside the linux sub-system. For example, using windows explorer to edit linux sub-system files would be a big no-no.

Yes, that is the guidance we're giving right now. See my post on this subject for more background: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n... However, it's fine to modify files stored in your Windows filesystem from within Bash, so if you were in `/mnt/c/dev/project/` and launched `code.exe ./`, Code would open the current (Windows-accessible) folder.

First, I switched from OSX to Windows b/c WSL made it possible.

There is some weirdness with the recommended file system sharing. Git on WSL sees files as modified after they have been checked in from Windows. It means I either use Git from the IDE or from the terminal, but not both.

Excited to see how this continues to improve.

Re: Bash and Windows Subsystem for Linux Demo [video]

#264

Post by jaxn »

bitcrazed wrote: post #174
platz wrote: post #100

Earlier quoted context omitted.

I was under the impression that only linux sub-system applications should be modifying files inside the linux sub-system. For example, using windows explorer to edit linux sub-system files would be a big no-no.

Yes, that is the guidance we're giving right now. See my post on this subject for more background: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n... However, it's fine to modify files stored in your Windows filesystem from within Bash, so if you were in `/mnt/c/dev/project/` and launched `code.exe ./`, Code would open the current (Windows-accessible) folder.

First, I switched from OSX to Windows b/c WSL made it possible.

There is some weirdness with the recommended file system sharing. Git on WSL sees files as modified after they have been checked in from Windows. It means I either use Git from the IDE or from the terminal, but not both.

Excited to see how this continues to improve.

Re: Bash and Windows Subsystem for Linux Demo [video]

#265

Post by bitcrazed »

jaxn wrote: post #263
bitcrazed wrote: post #174

Earlier quoted context omitted.

Yes, that is the guidance we're giving right now. See my post on this subject for more background: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n... However, it's fine to modify files stored in your Windows filesystem from within Bash, so if you were in `/mnt/c/dev/project/` and launched `code.exe ./`, Code would open the current (Windows-accessible) folder.

First, I switched from OSX to Windows b/c WSL made it possible. There is some weirdness with the recommended file system sharing. Git on WSL sees files as modified after they have been checked in from Windows. It means I either use Git from the IDE or from the terminal, but not both. Excited to see how this continues to improve.

Great to hear - welcome to the party! :)

What you're seeing with git is likely to be caused by line ending differences. You've probably got "Convert line endings to Windows" configured in your Git on Windows, but "Checkout Linux line endings on Linux". Either way, both should match otherwise all your files will look different because ... well ... they will be ;)

Re: Bash and Windows Subsystem for Linux Demo [video]

#266

Post by bitcrazed »

notaplumber wrote: post #229
bitcrazed wrote: post #191

Earlier quoted context omitted.

We do implement (at least some of) prctl(), but not seccomp() yet. If this is important to you, please file a bug and the team will triage & respond. https://github.com/microsoft/bashonwindows

I don't use github, sorry! :-( I was just saying maybe WSL shouldn't be advertised as ready for prime time without SECCOMP-BPF support implemented, e.g: for OpenSSH pre-auth sandbox. At least not in roles where security is paramount.

Where is it advertised as "ready for prime time"? All I said was that WSL is likely now stable and compatible enough as a daily driver.

Also, remember that our primary goal for WSL right now is to provide a local development environment in which you can build, run, and test *NIX code.

Re: Bash and Windows Subsystem for Linux Demo [video]

#267

Post by bitcrazed »

ZenoArrow wrote: post #251
bitcrazed wrote: post #180

Earlier quoted context omitted.

IO perf isn't where we want it to be yet, but we've some improvements coming in Creators Update and more planned for future releases.

Is it possible to access network drives yet? If not, is this something that's being worked on? Thanks!

Access network drives?

Via SSH? Sure.

Via Samba? Yep: https://www.samba.org/~garming/

If you mean MOUNT network drives, then, not yet, alas. But yes we're keen to build that support when we can.

Re: Bash and Windows Subsystem for Linux Demo [video]

#268

Post by iamcreasy »

bitcrazed wrote: post #135
kej wrote: post #113

Earlier quoted context omitted.

Almost. `code.exe .` will do what you expect IF you are in a folder that's visible from the Windows side. If you're in a WSL folder, the Windows program will be run in C:\Windows\System32. It has worked well for me to make a symlink under ~ to /mnt/c/Users/myaccount/, and that way anything under that symlinked folder is visible to WSL and Windows programs.

Hi - yes, we register the '.exe' extension with binfmt that then triggers WSL whenever a .exe is launched, allowing us to go find and spawn the requested Win32 process. If you just want to type `code ` (without the .exe), then you can create an alias that resolves to code.exe. Same for Notepad, etc. :)

Would I be able to setup Linux environment in VS? i.e. would I be able to include and write POSIX application with this update?

Re: Bash and Windows Subsystem for Linux Demo [video]

#269

Post by bitcrazed »

jzelinskie wrote: post #219
bitcrazed wrote: post #170

Earlier quoted context omitted.

I'll just leave this here: https://blogs.msdn.microsoft.com/commandline/2016/06/08/tmux... :)

I'll just leave this here: https://github.com/Microsoft/BashOnWindows/issues/406

The OP asked if TMux worked on WSL, which it does.

Now, there are many, MANY, improvements required of Windows' Console which is currently receiving its biggest overhaul in > 30 years! Bear with us while we give the Console some much needed TLC and start to re-shape it into a clean Console infrastructure that supports modern Console demands.

Re: Bash and Windows Subsystem for Linux Demo [video]

#270

Post by bitcrazed »

OhSoHumble wrote: post #168
bitcrazed wrote: post #155

Earlier quoted context omitted.

@OhSoHumble: Second Point: "A couple weeks back I tried to give WSL a try but everything was broken" Did you run an Insider build? 14986 completed a batch of inotify related syscall improvements since we first added inotify support in 14328 (Details here: https://msdn.microsoft.com/commandline/wsl/release_notes )

My main project is a Rails/Ember.js application to help people find affordable housing in the bay area. My problem was that the CLI built to help glue the two together didn't work on Windows so I tried it out in the WSL. Because of missing inotify support, hot reloading was broken. I found that I really missed that functionality so I moved to the fast ring of insider builds. After an update, node was completely broke…

What OS build & Linux version are you running? Type `ver` at the Cmd prompt, and `lsb_release -a` at the Bash prompt.

What do you mean when you say your node is "broken"?

And I don't follow re. your Arch install on another drive?

Post reply on HN