Mailinglist Archive: opensuse-bugs (15090 mails)
| < Previous | Next > |
[Bug 325738] YaST should not copy ifcfg-* config file in case of an system update to 10 .3
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 21 Sep 2007 02:58:18 -0600 (MDT)
- Message-id: <20070921085818.C57B0245269@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=325738#c16
Martin Vidner <mvidner@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|mvidner@xxxxxxxxxx |zoz@xxxxxxxxxx
--- Comment #16 from Martin Vidner <mvidner@xxxxxxxxxx> 2007-09-21 02:58:18 MST ---
So the old behavior of copying the installation-time settings to the updated
system has been there since ages (I stopped in 2004) and I could not find any
related bugs.
I can't think of possible breakage when we keep the old settings (except where
there are no settings (comment 6). But still it is a substantial change at a
very late stage.
So let's also consider leaving the yast code as it
is and modifying the ifcfg migration script instead.
Comment 0:
> It causes failure messages on system boot.
Without knowing the script, I imagine that it complains when it converts an
ifcfg from an old name to a new one and the new one already exists (because
yast has created it). So perhaps we could just delete the old file and let the
new one prevail. Christian?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Martin Vidner <mvidner@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|mvidner@xxxxxxxxxx |zoz@xxxxxxxxxx
--- Comment #16 from Martin Vidner <mvidner@xxxxxxxxxx> 2007-09-21 02:58:18 MST ---
So the old behavior of copying the installation-time settings to the updated
system has been there since ages (I stopped in 2004) and I could not find any
related bugs.
I can't think of possible breakage when we keep the old settings (except where
there are no settings (comment 6). But still it is a substantial change at a
very late stage.
So let's also consider leaving the yast code as it
is and modifying the ifcfg migration script instead.
Comment 0:
> It causes failure messages on system boot.
Without knowing the script, I imagine that it complains when it converts an
ifcfg from an old name to a new one and the new one already exists (because
yast has created it). So perhaps we could just delete the old file and let the
new one prevail. Christian?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |