How exactly do you rename your interfaces? Do you use a udev rule? Can you post those scripts/rules?
Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Date: Mon, 16 Aug 2021 16:16:43 +0200
- Cc: "systemd-devel@xxxxxxxxxxxxxxxxxxxxx" <systemd-devel@xxxxxxxxxxxxxxxxxxxxx>
- In-reply-to: <59ff1394-7715-e40a-cbce-ec6e02e30f2d@gmail.com>
- References: <83597df0-fef1-049e-3707-2aa2a3819fb9@gmail.com> <611A4E62020000A1000433A3@gwsmtp.uni-regensburg.de> <59ff1394-7715-e40a-cbce-ec6e02e30f2d@gmail.com>
- Follow-Ups:
- References:
- Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- From: Amish
- Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- From: Ulrich Windl
- Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- From: Amish
- Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- Prev by Date: Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- Next by Date: Can't manage to start a task when bluetooth is ready with systemd
- Previous by thread: Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- Next by thread: Re: Antw: [EXT] Upgraded multiple systems to systemd 249.3 and all had eth1 not started / configured
- Index(es):
 |