Bug#881771: release-notes: No mention of "predictable network interface names" in Debian 10

["Karl O. Pinc" <kop@meme.com>]

On Sat, 6 Apr 2019 14:43:40 +0200
Paul Gevers <elbrus@debian.org> wrote:

> Kind ping :)

Thanks.  Did some work this week, but have nothing final.
There's a jumble of text needing assembly, editing, so forth.

I can send you a patch so you can see where I am if you'd
like early feedback.

A) Added text in "what's new" section explaining the (sorta-new)
interface naming scheme and why it's good.  Mention there
that if you upgrade from a stretch which was itself
upgraded to stretch you need to migrate interface names,
so people see the warning.

Want to say "why the name change" to give people motivation.
This is also a place to put links to outside resources so people can 
answer the question "what's this all about?".  

Try to keep the new text brief but
there is an itemized list.

B) Added text in "preparing for upgrade" section to provide
a test code fragment that shows if old interface names are
used and must be upgraded.  If so, refers user to "issues
to be aware of" for migration instructions.

Keep this text brief too.

C) Actual upgrade instructions.  This is in-progress.

There are really 2 paths for manual migration of
interface names: one for when you have console/physical
access and another when you don't.  In the first case,
you can try the new names, see what name you get, and
migrate /etc/.  Without console access you need to
calculate the new interface name, migrate, and hope
you got the right name after reboot.  To calculate
the right interface name you need additional background
information.  I've whacked up a teeny script, with
no dependencies, to compute the common case.  But it
does require the pciid as input, and I suggest installing
pciutils to get lspci to find pciids.

Regards,

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein