The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Ivan Vecera <ivecera@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: Failed to start Raise network interfaces error
Date: Thu, 14 Dec 2023 15:33:28 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2312141530500.3217@hadrien> (raw)
In-Reply-To: <88a7a623-ad80-406c-a63b-3136df963888@redhat.com>



On Tue, 12 Dec 2023, Ivan Vecera wrote:

>
>
> On 12. 12. 23 17:33, Julia Lawall wrote:
> > > Look at 'systemd.net-naming-scheme' man page for details how the interface
> > > names are composed.
> > After booting into 6.7.0-rc4, I have the following in
> > /etc/network/interfaces:
> >
> > # This file describes the network interfaces available on your system
> > # and how to activate them. For more information, see interfaces(5).
> >
> > source/etc/network/interfaces.d/*
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > auto enp24s0f0
> > iface enp24s0f0 inet dhcp
>
> Just change 'enp24s0f0' in /etc/network/interfaces to 'enp24s0f0np0'

Hello,

I don't know if anything can be done about it, but this change introduces
complexities.  The people who manage the cluster that I use say that the
name of the network interface should be predictable, which is no longer
the case because it now depends on the kernel version.

thanks,
julia

  parent reply	other threads:[~2023-12-14 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10 22:28 Failed to start Raise network interfaces error Julia Lawall
2023-12-12 14:44 ` Julia Lawall
2023-12-12 14:52 ` Ivan Vecera
2023-12-12 15:08   ` Julia Lawall
2023-12-12 15:45     ` Ivan Vecera
2023-12-12 15:48       ` Julia Lawall
2023-12-12 16:33       ` Julia Lawall
2023-12-12 16:44         ` Ivan Vecera
2023-12-12 16:53           ` Julia Lawall
2023-12-14 14:33           ` Julia Lawall [this message]
2023-12-14 14:47             ` Ivan Vecera
2023-12-14 14:50               ` Julia Lawall
2023-12-14 20:55           ` Lucas Nussbaum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2312141530500.3217@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox