[Bug 1679400] Re: [udev] initrd xenial doesn't include biosdevname

JulienPrigent julienprigent at wanadoo.fr
Tue Apr 4 20:39:25 UTC 2017


** Description changed:

  The former version of ubuntu-installer (14.04) included an initrd.gz
  with the biosdevname binary and 71-biosdevname.rules for udev.
  
  Since 16.04, there is no more biosdevname traces in the ubuntu-installer.
- That induce a different name for network card (e.g eno1 instead of em1) during installing phase.
+ That induces a different name for network card (e.g eno1 instead of em1) during installing phase.
  
- It is a backward compatibility issue for preseed and post-installation
+ It's a backward compatibility issue for preseed and post-installation
  scripts as they become  deprecated (even with the same hardware).
  
- Futhermore, if you installed biosdevname on the fresh install, your
+ Futhermore, if you install biosdevname on the fresh install, your
  network card will fall back to the old 14.04 (em1) scheme... That's
- really disruptive when one want to automatize and deploy at scale.
+ really disruptive when one wants to automatize and deploy at scale.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1679400

Title:
  [udev] initrd xenial doesn't include biosdevname

Status in debian-installer package in Ubuntu:
  New

Bug description:
  The former version of ubuntu-installer (14.04) included an initrd.gz
  with the biosdevname binary and 71-biosdevname.rules for udev.

  Since 16.04, there is no more biosdevname traces in the ubuntu-installer.
  That induces a different name for network card (e.g eno1 instead of em1) during installing phase.

  It's a backward compatibility issue for preseed and post-installation
  scripts as they become  deprecated (even with the same hardware).

  Futhermore, if you install biosdevname on the fresh install, your
  network card will fall back to the old 14.04 (em1) scheme... That's
  really disruptive when one wants to automatize and deploy at scale.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1679400/+subscriptions



More information about the foundations-bugs mailing list