Live data from Hacker News

Ubuntu on Windows

blog.dustinkirkland.com

171–180 of 933 posts

Re: Ubuntu on Windows

#171
post #79

Earlier quoted context omitted.

Except, it does matter. Not having a unified filesystem, not having a unified window manager, etc are quite some issues.

Those are not meaningful issues for the stated use case of playing some handful of games.

They are when you want to use the game on multiscreen setups, or if you want to backup the game’s save files manually.

Source: I use my VM only for gaming, and it’s a horrible experience.

Re: Ubuntu on Windows

#172

Earlier quoted context omitted.

I've been "stuck" with a 2010 Macbook since Apple isn't refreshing it's laptop hardware soon enough. Plus I'm sick of soldered in RAM and other BS. For devs that do heavy Linux work (but have stuck with a Mac OS for GUI/app reasons), is it time to move (back) to Windows? If so, what would be a good laptop to get at the moment?

Why not move to Linux?

Just out of curiosity, what does a Linux desktop offer that's not also natively offered in Mac and also highly polished?

Every year I try a switch to Linux desktop. This year I made it as far as trying to get multiple monitors working well. I also dabbed in gaming. In the end I went back to my work=Mac game=Windows duopoly.

Re: Ubuntu on Windows

#173

Earlier quoted context omitted.

I've read comments where people wrote that NT always had some kind of POSIX subsystem, and it has probably just now been completed and expanded. Can't find any substantial writings on this, but it seems likely.

NT shipped w/ a POSIX subsystem. Later, Microsoft acquired Interix ( https://en.wikipedia.org/wiki/Interix ), a more fully-featured POSIX subsystem. I have fond memories, in the late 1990's, of running GNU tools on NT under Interix.

Same here. It's like everyone forgot there was such a thing as SFU/SUA. I found it much more pleasant to work with than Cygwin.

Re: Ubuntu on Windows

#174

To clarify, it sounds like what Microsoft has added to Windows 10 is a Linux ABI. This has been done before with other x86 OSes: FreeBSD has had 32-bit ABI compatibility for at least a decade ( https://www.freebsd.org/doc/handbook/linuxemu.html ), and the "lx branded zone" for Solaris has it as well ( https://docs.oracle.com/cd/E19455-01/817-1592/gchhy/index.ht... ).

I think this was a smart balance between getting it out there and seeing if it will stick. Someone said POSIX went by the wayside some time back so they may be a little hesitant in jumping all in. If this gets adoption, they can improve upon it in a future release.

Re: Ubuntu on Windows

#175
post #33

Scott Hanselman has a good write-up here: http://www.hanselman.com/blog/DevelopersCanRunBashShellAndUs... Google Cache: https://webcache.googleusercontent.com/search?q=cache:http:/...

Looks like they are launching ELF files, then translating the linux syscalls to WIN32API calls at runtime.

The link you posted is the original article at the top of this HN thread.

Re: Ubuntu on Windows

#177
post #129

"But there are some imperfections still, especially around tty's an the vt100. My beloved byobu, screen, and tmux don't quite work yet, but they're getting close!" If they actually fix these imperfections, that would be fantastic. It would address a number issues that are "unfixable" in Cygwin flavors of utilities/apps.

It sounds like this would involve tweaking conhost.exe so that it understands all the vt100 sequences, as well as UTF-8. (I hope they wouldn't assume everyone's tmux setup uses only characters from codepage 437.)

If they did that, it would also fix the awfulness of Python's stdout on Windows!

Re: Ubuntu on Windows

#179

A few random thoughts: - Wow, hell is really freezing over! - The hardest part of running bash and other posix things under windows is filesystem access. Windows uses drive letters and backslashes, unix has a root filesystem with forward slashes. It seems they are taking the same route as cygwin by "mounting" windows drives in /mnt/c (or /cygdrive/c). - If you just wanted bash and some posix tools, the harder but nic…

> - If you just wanted bash and some posix tools, the harder but nicer way would be to patch them to understand windows paths. It is not clear to me that it is even possible, for example many tools assume a path that does not start with a slash is a relative path - while "C:\" is absolute. You would also want to make more windows apps understand forward slashes like "C:/Windows". To make things even more complicated, there are NT native paths "\Device\HarddiskVolume4\Users\Bill", UNC paths "\\Server\share", and the crazy syntax "\\?\C:\MyReallyLongPath\File.txt".

One of the good things about using "newer" languages than C for building cross-platform utilities[0] is that things like that come baked in[1].

[0] - https://github.com/EricLagergren/go-coreutils [1] - https://golang.org/pkg/path/filepath/#IsAbs

Post reply on HN