Bug 144564 - Have a way to migrate a old nic to a new nic.
Summary: Have a way to migrate a old nic to a new nic.
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 1
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-20 23:23 UTC by Joe Harmon
Modified: 2008-05-23 08:12 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

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

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Harmon 2006-01-20 23:23:08 UTC 
I would like to see an enhancement in the nic handling..

If a nic is replaced you don't have any network anymore because the
configuration is specific to the mac address..

In yast you still see the old nic (because the file is there)

In the old days ... which you can still achiece by copying the ifcfg-eth
mac to ifcfg-eth0 this wouldn't happen..

I know there could be a reason for this behaviour... like docking stations
with own nic cards etc...

But why not ask the user if a new nic is detected if he wants to configure
this new nic, copy the config from an other nic, or move the config of the
old nic to the new nic?
Comment 1 Andreas Kleen 2006-01-21 02:14:00 UTC 
This bites me regularly too.  Would be nice to fix it in some way.
Comment 2 Martin Vidner 2006-08-28 11:52:32 UTC 
Reassigning to the new maintainer of yast2-network.
Comment 3 Michal Zugec 2006-08-30 06:47:13 UTC 
move to later
Comment 4 Michal Zugec 2008-05-23 08:12:39 UTC 
This is already fixed (by sysconfig + YaST) in 11.0. Since we have network devicename based configurations and devicename editor in YaST, it works fine ;-)