Ubuntu 16.04 Available in Latest Insider Update To Windows 10 (omgubuntu.co.uk)
The latest Windows 10 Insider preview -- build 14936 -- features Ubuntu 16.04 LTS. When a user enables the 'Bash on Ubuntu on Windows' feature for the first time, OMGUbuntu reports, Windows 10 now installs an Ubuntu 16.04 (Xenial Xerus) image instead of Ubuntu 14.04 (Trusty Tahr). From the report: The updated version of Ubuntu in the WSL only affects new instances, i.e., those created by running lxrun.exe /install or on the very first run of the bash.exe setup. It is possible to upgrade WSL instances from Ubuntu 14.04 to Ubuntu 16.04 manually by running the do-release-upgrade command. Other changes in the WSL in Build 14936 include support for chroot system call, epoll support for /dev/null and the ability for bash -c to redirect to a file.
Systemd? No thanks!
or something
The horse can ride man ! .
Ubuntu in Windows 10.... ugh
Don't want.
Either run a real VM, or dual boot, or ... anything other than a broken cygwin-like substance that only now has things like chroot?
Just use a real operating system for chrissake.
I think this is the "embrace" stage...
A Pirate and a Puritan look the same on a balance sheet.
This now makes me wonder what reason there could be to run Ubuntu on Windows instead of Windows on Linux. For the few pieces of software like CAD (or games) I can understand, but then I can't think of a use for those professionals to use Linux in a virtual machine.
So, what scenario would fit best to use Linux on Windows instead of Windows on Linux for the professional? (I myself use Proxmox as a desktop with severeal machines for testing on it)
home
*several
Proofread too quick. Need edit option.
home
Don't worry, that build is not available anyway. Since 14915, all Windows 10 Insider Preview does is downloading updates over and over, rebooting for several hours long installation that requires you to log in in the middle then rolls back the update for another several hours. Judging by the Feedback Hub, same happens to many or possibly most people on insider builds. And working versions are expired since Oct 1st.
I for one don't let Windows anywhere outside a VM but those who made the mistake of using Win10 Preview for some real use are pretty fucked.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
It doesn't matter what you try to do for the Linux community at large, if it includes windows they'll whine like useless shitbags until MS gives up trying to include better tools to appease them.
We really should be encouraging this move instead of discouraging it.
As an engineer, many places I have worked have IT departments which are run for the benefit of non-techies and completely out-of-touch with engineering. These companies simply do not understand the engineers' desires whatsoever. Windows is forced upon the engineers (80% of the white collar workforce) because it's simpler to maintain a single OS, and the remaining 20% wants windows. I am not saying that every engineer agrees with me. However, only one side of the debate is heard at most companies: those who want Windows.
Devuan is still in beta, Slackware is here now but lacks the Debian package pool (I enjoy nice recent versions of packages that are widely tested with no dependency issues, I love apt), as well as a bunch of other fringe distros...
Personally I've settled on Mint for my desktop, as it has all the software I need, as well as Cinnamon, which is important to me as it remains committed to delivering a consistent desktop UI that won't change for the sake of change, as did Gnome and KDE. If I could get my Cinnamon fix on a non-systemd distro, along with other packages I use, I would move in a heartbeat.
Rosegarden, K3B, Handbrake, Kodi, Inkscape, Gimp, LibreOffice, Cinnamon... That's all I need.
Ever since that day I have understood exactly how systemd eschews the "do one thing do it well" practice, and that even though it seems like individual components of systemd are being developed that way, they still come together as one giant integrated service where one flaw can affect/leverage its other components in attack. In other scenarios you could compromise an individual tool, but maybe SELinux granular permissions could help you, or maybe issues with that individual tool could be addressed, but if something in systemd is affected you're basically fucked top to bottom until a solution or shim is found, it is an ugly situation.
Anyone else in this position? What are you trying?
Twinstiq, game news
They're making all of this GPL code available on a commercial basis. I believe that this makes them responsible for making a source repository available. (been a while since I (re) read the pertinent sections of the GPL.
Sometimes boldness is in fashion. Sometimes only the brave will be bold.
Who cares? Only Microsoft and Canonical as far as I can tell. If you really use Linux in your day to day work, why would you not just work on Linux directly, seriously.
in Ubuntu on Windows? Because, I need to run Windows programs without getting a virus.
Gee, doesn't it make MORE sense to run Windows in Linux (VirtualBox, Proxmox, KVM). Safer, easier to audit network activity. It's amazing how people don't seem to see the light, even when the potion is on the table in front of them saying "drink me" AND they know people who have already tasted the potion and haven't died, or gotten sick.
"Imagination is more important than knowledge" - Einstein
subject says it all
The question is especially interesting in the long term.
Will this be just a limited trick to please the developers that like usual console tools on Ubuntu. ?
Or will this be someday included by default on Windows with enough support to allow to run Linux applications ?
A re-paste of a comment I posted as a reply:
My belief is that the 99% use case of this is for running docker images.
Before this you could run docker on windows, but you had to create a "bizarre" tiny linux distro VM (100mb or so storage), and the docker on windows launcher would leverage that to provision and run the docker images. You had to dedicate ram to that VM to run your docker pool.
With this you can run docker images "natively", without a separate VM memory space, and due to the elf loader support they actually are running on windows itself.
I do not see this as a good alternative to traditional VMs.
... Systemd Edition?
Can anyone tell me if this will allow NFS mounts? I really hate samba + windows and Unix services is only available for enterprise versions.
Where is Microsoft's source repository? They're making all of this GPL code available on a commercial basis. I believe that this makes them responsible for making a source repository available. (been a while since I (re) read the pertinent sections of the GPL.
They don't need one. They are not modifying these tools so you can go to Ubuntu's repository. If you asked MS for the source they could fulfill their GPL obligation by referring you to Ubuntu's.
Note that they do not use the Linux kernel. They have alternative code for providing the necessary Linux APIs for the tools.
I'd figure everyone would be jumping for joy because there's no systemd in this.
Could something like ReactOS be ported on a Linux kernel in userland to run win32 software?
http://saveie6.com/
On a 2GB RAM / 32 GB storage cheap Windows laptop, I have found that Windows Subsystem for Linux (WSL) works fine and I would prefer it to full emulation given the limited amount of RAM available. For 150GBP, I have got a 1kg "disposable" notebook with a small form factor, decent keyboard and 10hrs battery life. I used to have a chromebook for that purpose, but I had to flash its firmware and hardware support wasn't perfect.
As a C++ development environment, you get the usual console tools (vim, git, cmake, gdb, ecc...), but g++ is quite old (4.8) which basically means C++11. Installing clang-3.8 from the repository worked, but I personally had dependency problems when I tried to install libc++. Good C++14 language support with poor C++11 standard library support works fine for me, so I didn't bother to try to solve the issue.
A problem I did not expect is the inability to access removable MicroSD from WSL, so you should be aware of that.
I am looking forward for when Ubuntu 16.04 will be available outside the insider program, so I can get an hassle-free, modern C++14 environment out of the box.
So does ping even work now? This is why I went back to Windows 7 after a drive failure.
liberare massarum ex ignorantia, clausa descendit molestie.
Now twitter, go die in a fucking fire fucktard.
Could you do something more usefull like working hands to hands with Intel to make VLAN work in current Windows 10 release.
And BTW, could you add VLAN natively like all modern OS.