I just upgraded an Ubuntu 14.04 virtual machine (running on VMWare) to 16.04 using do-release-upgrade on the command line. It isn't the first time I have done this with similar VMs running 14.04 so I was not expecting problems.
All appeared to go well until after the reboot when I could no longer SSH into the system. Thanks to this answer on Ask Ubuntu I discovered that for some reason Ubuntu now names their ethernet interfaces differently but didn't change the eth0 device configured statically in my /etc/networking/interfaces to the new device ens32 name.
I searched the Ubuntu bug tracker and found this bug that pretty much matches but claims to have fixed this back in March.
Subscribe to:
Post Comments (Atom)
Modern Ubuntu web kiosk using chromium as the browser engine
I have been working to prepare a digital atlas exhibit for the Natillik Heritage Centre in Gjoa Haven, Nunavut, Canada. Working with Indig...
-
Ubuntu Server 18.04 uses netplan instead of NetworkManager by default. ModemManager is still required to deal with modems and it requires N...
-
A colleague was trying to create a postgresql datastore in his GeoServer installation and was having trouble connecting it with our PostgreS...
No comments:
Post a Comment