[Bug 1277436] Re: biosdevname renaming rule not present in initramfs, leads to unpredictable names
Margarita Manterola
marga at google.com
Fri Feb 7 13:33:35 UTC 2014
I'm attaching a debdiff of a package that includes an initramfs hook
that copies both the rule file and the binary necessary to have
biosdevname working at boot time, it also includes a postinst hook to
regenerate the update-initramfs image.
** Patch added: "Patch to make biosdevname be installed in the initramfs"
https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1277436/+attachment/3972422/+files/biosdevname-initramfs.diff
** Patch removed: "Debdiff with solution to the problem"
https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1277436/+attachment/3972396/+files/biosdevname-initramfs.diff
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to biosdevname in Ubuntu.
https://bugs.launchpad.net/bugs/1277436
Title:
biosdevname renaming rule not present in initramfs, leads to
unpredictable names
Status in “biosdevname” package in Ubuntu:
New
Bug description:
The biosdevname package includes
/lib/udev/rules.d/71-biosdevname.rules, which makes it rename the
interfaces when the machine boots. This is now installed by default
in trusty, and so most machines will have this rename going on.
However, the rule is not present in the initramfs, so that if there's
any program that calls configure_networking (like dropbear does)
during the initial boot, then the interface stays with the unrenamed
name.
What this means is that the interface is called something different
depending on the fact that another program (dropbear) is installed or
not. This shouldn't be the case.
The biosdevname rule should be copied into the initramfs, like other
udev rules are copied.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/biosdevname/+bug/1277436/+subscriptions
More information about the foundations-bugs
mailing list