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.

Comments

I want Mint without systemd

[HalAtWork]

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?