Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Trusty to Xenial #482

Closed
fenris opened this issue Jun 7, 2016 · 133 comments
Closed

Upgrade Trusty to Xenial #482

fenris opened this issue Jun 7, 2016 · 133 comments

Comments

@fenris
Copy link

fenris commented Jun 7, 2016

I've tried to upgrade from Trusty to Xenial , result ? crash due to missing path and error writing files installations.

Is there inside the milestone to place xenial based bash in future Windows Insiders Fast Ring update?

@fpqc
Copy link

fpqc commented Jun 8, 2016

fenris, Canonical's new image for WSL should be up on the Windows store I think with the next insider update. I don't think it's possible to directly update with any other tool?

@sunilmut
Copy link
Member

sunilmut commented Jun 8, 2016

WSL currently does not support Xenial officially and that's not on plan for the anniversary update. But, that is definitely something we will be looking to support in (during) the next release.

@paladox
Copy link

paladox commented Jun 8, 2016

@fpqc Hi the next insider release has been released is the image on the windows store yet.

@sunilmut
Copy link
Member

sunilmut commented Jun 8, 2016

@fqpc - That is correct, Windows build 14361 has been released to insider preview. But just FYI that the Windows build and the Ubuntu image that comes from the Windows store and not tied together. The are and can be updated independently.

@paladox
Copy link

paladox commented Jun 8, 2016

@sunilmut hi is @fpqc correct about the image being updated on the windows store please.

@sunilmut
Copy link
Member

sunilmut commented Jun 8, 2016

@paladox - This is on our radar, but we don't have any ETA on when the Xenial image will be uploaded on the Windows store.

@paladox
Copy link

paladox commented Jun 9, 2016

Ok thanks for replying.

@Manouchehri
Copy link
Contributor

I have Xenial (16.04) working in WSL.

Bash on Ubuntu 16.04 on Windows

@benhillis
Copy link
Member

@Manouchehri Very nice! Any special workarounds you needed to get this working? I'd be very interested in hearing the process. I'm sure my friend @dustinkirkland from Canonical would be interested too :)

@paladox
Copy link

paladox commented Jun 23, 2016

@Manouchehri how did you get it installed please. And did you have to clean install or did you manage to get your files upgraded without loosing any data.

@Manouchehri
Copy link
Contributor

Worked on my first try, nothing too special.

sudo do-release-upgrade -f DistUpgradeViewNonInteractive -d # Screen is broken.

It still gets stuck at a yes/no type prompt, so I ctrl+c'd out. To fix the remaining packages, just run dpkg.

 sudo dpkg --configure -a

After that I ran apt-get update, apt-get upgrade, apt-get dist-upgrade and apt-get autoremove.

@paladox
Copy link

paladox commented Jun 23, 2016

@Manouchehri thanks, yay it works.

@paladox
Copy link

paladox commented Jun 23, 2016

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial

:)

@dustinkirkland
Copy link

+100 xp :-)

:-Dustin

On Thu, Jun 23, 2016 at 2:11 PM, paladox notifications@github.com wrote:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial

:)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#482 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAzMhlG_YVUvC4DMHzvEe3higVeFAJgqks5qOtpHgaJpZM4IwaTF
.

@paladox
Copy link

paladox commented Jun 23, 2016

@dustinkirkland and @benhillis I get this error

snap find
2016/06/23 20:30:05.121452 main.go:156: WARNING: can not create syslog logger
error: cannot list snaps: cannot communicate with server: Get http://localhost/v2/find?q=: dial unix /run/snapd.socket: setsockopt: invalid argument

when trying to run snap.

@Manouchehri
Copy link
Contributor

That's snapd trying to use systemd's logger. Previously there was separate logging daemon, so init (Uptrack) didn't cause an issue. (There's no systemd or Uptrack support in Ubuntu on Windows from what I understand.)

To fix it, we could probably bring back syslog-ng until systemd works. This is probably @dustinkirkland's job. ;)

@benhillis
Copy link
Member

@paladox This particular issue looks like missing SO_BROADCAST flag support for Unix sockets. #568 is tracking the same issue. I suspect snap will hit other unimplemented things as well as it's a binary that we haven't tried much.

@Manouchehri
Copy link
Contributor

Oops, I stopped reading after the logging warning line.. What @benhillis said sounds correct as for the socket error. =)

@paladox
Copy link

paladox commented Jun 23, 2016

Oh, thanks for replying.

@Manouchehri
Copy link
Contributor

@paladox Does it actually work on 14.04 either?

@benhillis
Copy link
Member

@Manouchehri you're probably right also :)

@paladox
Copy link

paladox commented Jun 23, 2016

@Manouchehri I'm not sure. I didn't hit that problem before. But I doint think snaps are on Ubuntu 14.04.

@Manouchehri
Copy link
Contributor

I found another fun error. Probably PEBKAC related.

ubuntu@DESKTOP-3RQO5S5:~$ ps aux
Error: /proc must be mounted
  To mount /proc at boot you need an /etc/fstab line like:
      proc   /proc   proc    defaults
  In the meantime, run "mount proc /proc -t proc"
ubuntu@DESKTOP-3RQO5S5:~$ mount
rootfs on / type rootfs (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=204320k,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
none on /run/shm type tmpfs (rw,nosuid,nodev,relatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755)

@benhillis
Copy link
Member

@Manouchehri I took a look at what's causing ps to not work in 16.04. As funny as it sounds, it is due to us missing the /proc/sys/vm/min_free_kbytes ProcFs file. I just wrote a change to stubbed out that file and ps is mostly working. TTY is showing up as a '?' which is caused by us not having a /proc/tty directory.

@dustinkirkland
Copy link

Snaps are new, as of 16.04, and generally required systemd to work.

:-Dustin

On Thu, Jun 23, 2016 at 2:53 PM, paladox notifications@github.com wrote:

@Manouchehri https://github.com/Manouchehri I'm not sure. I didn't hit
that problem before. But I doint think snaps are on Ubuntu 14.04.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#482 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAzMhqEvruVxpCr_grAF1BeigURENG7-ks5qOuROgaJpZM4IwaTF
.

@paladox
Copy link

paladox commented Jun 23, 2016

@benhillis is there anyway we could support systemd please and also support /proc/tty please.

@Manouchehri
Copy link
Contributor

@benhillis Ha, I just noticed that too.

read(4, "MemTotal:        8313236 kB\nMemF"..., 8191) = 1164
open("/proc/sys/vm/min_free_kbytes", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, "Error: /proc must be mounted\n  T"..., 176Error: /proc must be mounted

If I want to screw around in /proc/sys/vm/, what's the proper way to do that here?

root@DESKTOP-3RQO5S5:~# strace touch /proc/sys/vm/min_free_kbytes
execve("/usr/bin/touch", ["touch", "/proc/sys/vm/min_free_kbytes"], [/* 19 vars */]) = 0
brk(NULL)                               = 0x1a99000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fca1ed90000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=26136, ...}) = 0
mmap(NULL, 26136, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fca1ed97000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1864888, ...}) = 0
mmap(NULL, 3967488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fca1e630000
mprotect(0x7fca1e7f0000, 2093056, PROT_NONE) = 0
mmap(0x7fca1e9ef000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1bf000) = 0x7fca1e9ef000
mmap(0x7fca1e9f5000, 14848, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fca1e9f5000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fca1ed80000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fca1ed70000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fca1ed60000
arch_prctl(ARCH_SET_FS, 0x7fca1ed70700) = 0
mprotect(0x7fca1e9ef000, 16384, PROT_READ) = 0
mprotect(0x60e000, 4096, PROT_READ)     = 0
mprotect(0x7fca1ec25000, 4096, PROT_READ) = 0
munmap(0x7fca1ed97000, 26136)           = 0
brk(NULL)                               = 0x1a99000
brk(0x1aba000)                          = 0x1aba000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fca1e358000
close(3)                                = 0
open("/proc/sys/vm/min_free_kbytes", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666) = -1 EPERM (Operation not permitted)
utimensat(AT_FDCWD, "/proc/sys/vm/min_free_kbytes", NULL, 0) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 512) = 512
read(3, "See the\n# GNU General Public Lic"..., 512) = 512
read(3, "nd for the time being for\n# back"..., 512) = 512
read(3, "hese lines were removed\n# becaus"..., 512) = 512
read(3, "8859-1\ngalego\t\tgl_ES.ISO-8859-1\n"..., 512) = 512
read(3, "O.ISO-8859-1 nb_NO.ISO-8859-1\nno"..., 512) = 435
read(3, "", 512)                        = 0
close(3)                                = 0
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/coreutils.mo", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=619, ...}) = 0
mmap(NULL, 619, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fca1ed9d000
close(3)                                = 0
write(2, "touch: ", 7touch: )                  = 7
write(2, "setting times of '/proc/sys/vm/m"..., 47setting times of '/proc/sys/vm/min_free_kbytes') = 47
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, ": No such file or directory", 27: No such file or directory) = 27
write(2, "\n", 1
)                       = 1
close(1)                                = 0
close(2)                                = 0
exit_group(1)                           = ?
+++ exited with 1 +++

@Manouchehri
Copy link
Contributor

@benhillis Somewhat off topic, but can I get debugging symbols for the Insider Preview builds? Shoot me an email if you'd prefer to talk about that privately.

@benhillis
Copy link
Member

@Manouchehri The ProcFs filesystem is a virtual file system exposed by our kernel drivers (lxcore.sys and lxss.sys) so unfortunately you can't change them without building a new driver.

Regarding debugging symbols: I know we release public versions of the symbols, I'm not sure about the process for Insider Preview builds though. @russalex would know the right answer to this question. Have you tried Using the Microsoft Symbol Server?

@fpqc
Copy link

fpqc commented Nov 13, 2016

@DJviolin If I remember correctly, it's planned for the end of March. If I didn't remember correctly, the thing to search for is "Windows 10 Creative Update", which is the official name (and the planned release date was also part of the announcement of the official name, which is terrible. Seriously, Microsoft Branding Guys, "Anniversary update" was already questionable, but I was willing to go with it because "oh, first anniversary, woohoo celebrate!!". But now "Creative update"? Come on. "Redstone II" is a far superior name.).

@whorfin
Copy link

whorfin commented Jan 23, 2017

I found this thread while repairing a xenial update, and thought I'd leave some notes here in the interests of helping the next person...

This was all done on multiple machines running Windows 10, Build 14393.693
So tl;dr protip - you don't need to be on insider to enjoy Xenial

First a note for Microsoft: when remotely connecting to a WSL instance over sshd/ssh, the user is presented with the Canonical notice of upgrade availability, and the suggestion to run
do-release-upgrade
So while this is hidden for those just using the shortcut, it shows up with ssh, and thus you'd [microsoft] be well advised to do something about educating us all...

The following worked for me, to upgrade a number of machines.
I chose not to hold back sudo, so be sure to have an alias somewhere or be in the habit:
alias sudo='sudo -S'

Removing screen allowed things to work fine interactively.
I use my own build of tmux [see #1063], so am independent of installed version, and it thus took me a while to understand that screen and tmux are secretly connected; removing one force-installs the other. You do not want screen installed, or the upgrade will fail.

Note: #927 claims that the environment variable RELEASE_UPGRADER_NO_SCREEN can be used to avoid the screen problem. I'm amending my description below, so it may be possible to do this
without removing screen.

sudo -S apt-get remove screen # optional?
sudo -S apt-mark hold procps strace
sudo -S env RELEASE_UPGRADER_NO_SCREEN=1 do-release-upgrade

Sometimes this works straightaway.
Sometimes it breaks, requiring a retry as follows

sudo -S dpkg --configure -a
sudo -S env RELEASE_UPGRADER_NO_SCREEN=1 do-release-upgrade

Repeat until done and ready for next steps.
I had to answer a full-window prompt to "restart services"
On one system I had to review changes to /etc/default/rcS
On all systems so far I had to review a change which added the regular [non
-security] distro to /etc/apt/apt.conf.d/50unattended-upgrades
...and miscellaneous saying "y" to continue etc

After all that, the following:

sudo -S rm /etc/apt/apt.conf.d/50unattended-upgrades.ucf-old
sudo -S dpkg --configure -a
sudo -S apt-get update
sudo -S apt-get upgrade
sudo -S apt-get dist-upgrade
sudo -S apt-get autoremove

And good to go!

An aside - before I knew all this, I did the upgrade w/o the apt hold, and broke ps.
Recovering required not only the advice from others, but one more shared library package, as libprocps.so.3 was missing.
So, recovering a system with broken ps looks like this:

wget http://mirrors.kernel.org/ubuntu/pool/main/p/procps/procps_3.3.9-1ubuntu2_amd64.deb
wget http://mirrors.kernel.org/ubuntu/pool/main/s/strace/strace_4.8-1ubuntu5_amd64.deb
wget http://mirrors.kernel.org/ubuntu/pool/main/p/procps/libprocps3_3.3.9-1ubuntu2_amd64.deb
sudo -S dpkg -i procps_3.3.9-1ubuntu2_amd64.deb
sudo -S dpkg -i strace_4.8-1ubuntu5_amd64.deb
sudo -S dpkg -i libprocps3_3.3.9-1ubuntu2_amd64.deb

Cheers

@bugchecker
Copy link

@whorfin I tested your case without removing screen (#927 (comment)). It works.

@whorfin
Copy link

whorfin commented Feb 4, 2017

I did not know about the RELEASE_UPGRADER_NO_SCREEN environment variable.
I will update my note

@ghost
Copy link

ghost commented Feb 17, 2017

Huge 🥂 to @whorfin for tutorializing the 16.04 upgrade for WSL. Works just fine now.

@DJviolin
Copy link

DJviolin commented Feb 17, 2017

@whorfin Does your method have any advantage compared to editing /etc/apt/sources.list directly and making the upgrade with these commands?

/usr/sbin/update-locale LANG=en_US.UTF8

echo -e "\
deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse\n\
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse\n\
deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse\n\
deb http://security.ubuntu.com/ubuntu xenial-security main restricted universe multiverse" > /etc/apt/sources.list

apt update

apt -f install -y libc6
apt install -y --only-upgrade apt

rm -rf /var/lib/apt/lists/*
apt update
apt upgrade -y
apt full-upgrade -y
apt autoremove -y

rm /etc/apt/apt.conf.d/50unattended-upgrades.ucf-old
rm /etc/apt/apt.conf.d/50unattended-upgrades.ucf-dist
apt -f install

The downside that I found with these commands that it's requires you to manually choose options in the middle of the install.

@bugchecker
Copy link

bugchecker commented Feb 21, 2017

@DJviolin http://askubuntu.com/questions/409555/what-does-do-release-upgrade-really-do
Note: do-release-upgrade comment&disable (not remove) unknown 3rd party repositories. You should check and uncomment&enable they manually.

@NoSubstitute
Copy link

@whorfin Followed your instructions and upgraded to 16.04.2. Worked fine on 14393 AU.
Setting alias sudo="sudo -S" afterwards is definitely the way to go.

@NoSubstitute
Copy link

NoSubstitute commented Mar 7, 2017

So, @whorfin , do I have to keep these held back, even after upgrading to Xenial, on 14393 AU?
I'm not on Insider builds.

The following packages have been kept back:
procps strace

@NoSubstitute
Copy link

While running Xenial on 14393 must I keep the hold on procps and strace, lest they break my system if updated?

@NoSubstitute
Copy link

So is nobody following this thread anymore? (I know it's closed.)
Creators Update is coming soon for us non-insiders, so it's till interesting to know what will be needed when/after upgrading, and if this hold on procps/strace is permanent, or if they will be fine to update too.

@benhillis
Copy link
Member

@NoSubstitute - I'm not sure if I understand the question, let me know if this doesn't answer it.

When you install Creator's Update you'll have two options to get to 16.04.

  1. do-release-upgrade (without workarounds) to upgrade your existing WSL filesystem.
  2. Reinstalling the Linux file system (lxrun /uninstall followed by lxrun /install)

Keeping specific packages at older versions is not a problem specific to WSL. All of that logic lives in user-mode so any workarounds found for native Ubuntu should work.

@NoSubstitute
Copy link

Hi, @benhillis !
I already have xenial (16.04). I followed the instructions in here to get it on 14393 (not insider).
I was hoping I didn't have to re-install it after upgrading to the CU. And my second question was that, after I have installed CU, will I be able to let go of the "hold" on procps and strace, since they haven't been updated since trusty.

@benhillis
Copy link
Member

@NoSubstitute - If you've upgrade then you're good, you won't need to reinstall. After you install CU you should be safe to remove the hold on procps and strace. I'm running CU and the Xenial versions of those packages work for me.

@fpqc
Copy link

fpqc commented Mar 25, 2017

@benhillis By the way, do you know roughly when we'll start seeing the RS3 flights?

@jackchammons
Copy link
Contributor

@fpqc No official word yet on when RS3 flighting will start. Historically, builds start to go out within a month after the previous version (Creators Update in this case) gets released to market.

@therealkenc
Copy link
Collaborator

For some value of historic...

14393 Insiders July 18, and for the proletariat on August 2.
14901 August 11.

It was 15 days from Insiders to RTM, and 9 days from RTM to the next Insiders. The street says RS2 on April 11. YRMV.

@fpqc
Copy link

fpqc commented Mar 27, 2017

@therealkenc Yeah but I think they're going to be a bit more cautious this time given some of the bad press around RS1 (webcams and such).

@OranguTech
Copy link

Thanks @TechBossIceWobs , that worked for me.

@OranguTech
Copy link

Just a reminder to everyone that upgraded WSL early, as the "creators update" is installed, to not forget to "apt-mark unhold procps strace sudo". (and probably a dist-upgrade too.)

@fullerth
Copy link

For those of you still stuck on old windows builds who didn't see the tutorial from @whorfin before upgrading, the kernel.org mirror's have moved. Here's the current commands to fix your sudo/ps/strace:

wget http://mirrors.edge.kernel.org/ubuntu/pool/main/s/sudo/sudo_1.8.9p5-1ubuntu1.4_amd64.deb
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/p/procps/procps_3.3.9-1ubuntu2_amd64.deb
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/s/strace/strace_4.8-1ubuntu5_amd64.deb
wget http://mirrors.edge.kernel.org/ubuntu/pool/main/p/procps/libprocps3_3.3.9-1ubuntu2_amd64.deb
dpkg -i sudo_1.8.9p5-1ubuntu1.4_amd64.deb
dpkg -i libprocps3_3.3.9-1ubuntu2_amd64.deb
dpkg -i procps_3.3.9-1ubuntu2_amd64.deb
dpkg -i strace_4.8-1ubuntu5_amd64.deb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests