Bug 17928 - Ethernet interfaces shown in summary under old names instead of current practice
Summary: Ethernet interfaces shown in summary under old names instead of current practice
Status: RESOLVED DUPLICATE of bug 17651
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-09 19:55 CET by Dick Gevers
Modified: 2016-04-29 10:58 CEST (History)
1 user (show)

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dick Gevers 2016-03-09 19:55:02 CET 
Description of problem:

Install M6 from iso of 7th March 2016.
In summary go to Firewall and enable it.
Interfaces are shown as eth0 and wlan0.

Current practice should name them to enp1s0 and wlp2s0

Please compare bug No. 12316

The relative report.bug.xz relating to this install may be consulted as attachment to bug # 17288.
Dick Gevers 2016-03-09 19:56:39 CET

Keywords: (none) => 6dev1

Comment 1 Marja Van Waes 2016-03-09 21:03:10 CET 
this was about the iso of 07 March 2016


@ Thierry

I do not know what to assign this bug to, so I take the easy way out (stage2 + you). It reminds me of a user who reported that his eth0 got renamed to enp1s0 and then back to eth0 when booting Mageia, after which he ended up without network (even if that may have been caused by something unrelated :-þ )

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Source RPM: iso of 07 March 2016 => drakx-installer-stage2

Comment 2 Dick Gevers 2016-03-12 12:14:21 CET 
More curious (and inconsistent): after reboot ifconfig shows interfaces that are up as: enp1s0 and wlp2s0  !
Comment 3 Thierry Vignaud 2016-04-29 10:58:13 CEST 
Dup

*** This bug has been marked as a duplicate of bug 17651 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.