Re: overriding udev rules
Kay Sievers <firstname.lastname@example.org> writes:
> On Mon, Sep 9, 2013 at 11:48 PM, Michael Biebl <email@example.com> wrote:
>> We (Debian pkg-systemd team) decided to keep the old persistent naming
>> scheme "as default" for now, for the simple reason, that we didn't want
>> to break upgrades. It just didn't seem possible to detect every case
>> where the old ethX names were used and losing network connection as
>> part of the upgrade is a big no-go.
>> As documented in the debian changelog, you can opt-in to use the new
>> naming scheme, but this requires explicit configuration from the
>> We might make the new network interface naming the default for new
>> installations, but this isn't something we haven't been working on yet.
> Hmm, why would upgrades break?
> The old file would still be there, rename the devices (if you keep the
> patch to swap names, which upstream does not support any more), and take
> precedence over tht new names; the old rules file would just not be
> updated anymore when new devices appear.
Manually-deployed /etc/network/interfaces files that assume a specific
device naming come to mind. We have tons of those at work.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>