Release Notes for buster: 70-persistent-net-rules still supported?

[andreimpopescu at gmail.com]

On Mi, 03 iul 19, 18:22:30, Michael Biebl wrote:
> Am 03.07.19 um 17:53 schrieb andreimpopescu at gmail.com:
> > 
> > diff --git a/en/issues.dbk b/en/issues.dbk
> > index 4769f9d6..c7634151 100644
> > --- a/en/issues.dbk
> > +++ b/en/issues.dbk
> > @@ -136,7 +136,7 @@ information mentioned in <xref linkend="morereading"/>.
> >       the old-style network interface names that were deprecated with
> >       stretch (such as <literal>eth0</literal> or <literal>wlan0</literal>),
> >       you should be aware that <systemitem role="package">udev</systemitem>
> > -     in buster no longer supports the mechanism of defining their names via
> > +     in buster does not reliably support the mechanism of defining their names via
> 
> I'd prefer if we rephrased that and declared the old naming scheme as
> officially unsupported in buster.

As per the e-mail thread that started this, users will find out it does 
work. If the Release Notes entry contradicts their experience they will 
dismiss the advice as outdated/incorrect/etc.

Would attached patch be better?

> It might still work under certain circumstances (not sure if it makes
> sense to go into detail here what those circumstances are) but users are
> strongly advised to migrate to the new naming scheme.

Sure.

> >       <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>. 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
> > @@ -148,10 +148,11 @@ information mentioned in <xref linkend="morereading"/>.
> >      </para>
> >      <para>
> >       The alternative is to switch to a supported mechanism for enforcing
> > -     the old naming scheme, such as the <literal>net.ifname=0</literal>
> > -     kernel commandline option or a systemd <filename>.link</filename>
> > -     file (see <ulink
> > -     url="https://manpages.debian.org/systemd.link">systemd.link(5)</ulink>).
> > +     the old naming scheme, such as a systemd <filename>.link</filename>
> 
> As said, net.ifnames=0 does not enforce the old naming scheme, it means
> use the kernel provided names.
> 
> If users want to stick with the kernel provided interfaces names, they
> should be aware that this is can lead to interfaces having different
> names on each boot if they have multiple interfaces.

I believe systems with multiple interfaces of the same type are not very 
common outside data centers and such.

> Usually ethernet interfaces are name eth* and wifi interfaces are named
> wlan*, so yeah, if you have a single ethernet interface which is named
> eth0 and a single wifi interface that is named wlan0, then you are safe
> as well. I do vaguely remember seeing wifi interfaces named as eth*
> though. I've seen this a long time ago, not sure if this is still valid
> today and you can safely say nowadays that wifi interfaces are always
> called wlan*.

My new patch tries to address this.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-udev-stil-supports-the-old-method-net.ifnames-0-is-n.patch
Type: text/x-diff
Size: 2352 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190703/104fd3f0/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20190703/104fd3f0/attachment.sig>