Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-15 Thread Justin B Rye
Here's a patch for the Release Notes adding another common corner-case to the list of things to beware of, plus an updated set of external links including "https://wiki.debian.org/NetworkInterfaceNames;. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-13 Thread Dmitry Semyonov
On Mon, 2 Sep 2019 at 22:25, Justin B Rye wrote: > So what did actually go wrong on your systems? You disabled > /etc/udev/rules.d/70-persistent-net.rules and they started using an > unpredictable slot-based "predictable name"? Yes, the interfaces file was updated to use PATH-based names but

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-13 Thread Dmitry Semyonov
Hello Justin, On Thu, 12 Sep 2019 at 16:14, Justin B Rye wrote: > https://wiki.debian.org/NetworkInterfaceNames Thank you! Some notes on the page as I read it, (feel free to apply or ignore; unfortunately I won't have time and energy to discuss this topic further): * I'm glad to see

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-12 Thread Justin B Rye
Justin B Rye wrote on Sep 02: > If I start trying to assemble a Debian Wiki page that the Release > Notes could point at, can you help? (Criticising it counts as help.) Slightly delayed by a badly timed broadband outage, here at last is my first draft:

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-02 Thread Justin B Rye
Dmitry Semyonov wrote: > The existing text creates an impression that what you should pay > attention to is only the "onboard" name. Since all this was new to me, > there was no ONBOARD name, and there was the usual PATH name there, I > just assumed it was safe to use it without paying attention

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-02 Thread Dmitry Semyonov
Justin, On Mon, 2 Sep 2019 at 14:25, Justin B Rye wrote: > > Dmitry Semyonov wrote: > > "(If the udevadm output includes an “onboard” name, that takes priority; > > MAC-based names are normally treated as a fallback, but may be needed > > for USB network hardware.)" > > (Notice that this is a

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-02 Thread Justin B Rye
Dmitry Semyonov wrote: > Package: release-notes > Severity: important > > The 5.1.5 section of the document[1] contains the following text: > [1]https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#migrate-interface-names > > "(If the udevadm output includes an

Bug#939178: release-notes: Describe name selection rules in the "Migrating from legacy network interface names" section

2019-09-01 Thread Dmitry Semyonov
Package: release-notes Severity: important The 5.1.5 section of the document[1] contains the following text: [1]https://www.debian.org/releases/stable/amd64/release-notes/ch-information.en.html#migrate-interface-names "(If the udevadm output includes an “onboard” name, that takes priority;