Re: Document removal of ecryptfs-utils from Buster
On 2019-07-01, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
>> >
>> > For whatever it's worth, when I upgraded this machine from stretch to
>> > buster a couple months ago, it continued using eth0 as the interface
>> > name without any immediately obvious issues. I did the conversion to
>> > "predictable interface names" anyway, just in case there might be some
>> > subtle problem that I wasn't yet seeing.
>>
>> And you had that device name defined (as I did) in
>> '/etc/udev/rules.d/70-persistent-net.rules' when you upgraded?
>
> Yes. In fact it's still there, but I commented it out by hand after
> the buster upgrade.
>
> wooledg:~$ cat /etc/udev/rules.d/70-persistent-net.rules
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # PCI device 0x8086:0x15b7 (e1000e)
> # SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a0:8c:fd:c3:89:e0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
>
>
Assuming the name was not also defined elsewhere, I'm at a loss to know
why the release notes for Buster state
...you should be aware that udev in buster no
longer supports the mechanism of defining their names via
/etc/udev/rules.d/70-persistent-net.rules. To avoid the danger of your
machine losing networking after the upgrade to buster, it is recommended
that you migrate in advance to the new naming scheme...
Well, I'm enp6s0 anyway now and somehow feel better about it.
Reply to: