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: Thu, 20 Sep 2007 08:23:56 -0600 (MDT)
- Message-id: <20070920142356.53524CC7AB@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=325738#c11
Martin Vidner <mvidner@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #11 from Martin Vidner <mvidner@xxxxxxxxxx> 2007-09-20 08:23:55 MST ---
(In reply to comment #9 from Christian Zoz)
> Does that mean that you change the hostname, routes, and resolver in the
> updated system as well? Why this? This is an update. The system already was
> configured.
When you update over the network, you have the (old) settings of the updated
system and the (new) settings used for the update itself. In rare cases they
can be different (a similar situation exists for autoyast).
We have to decide which set of settings to apply. We used to use the new ones
but because of the naming change, this bug appeared. So the proposed solution
in comment 6 is the smallest change (good) but goes halfway (bad). Another
solution is to always use the old settings. Yet another is to let the user
choose using an advanced option.
The new feature mentioned in comment 10 is that YaST itself is able to set up
networking for the 1st stage. Before, Linuxrc had to do it in advance.
--
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
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #11 from Martin Vidner <mvidner@xxxxxxxxxx> 2007-09-20 08:23:55 MST ---
(In reply to comment #9 from Christian Zoz)
> Does that mean that you change the hostname, routes, and resolver in the
> updated system as well? Why this? This is an update. The system already was
> configured.
When you update over the network, you have the (old) settings of the updated
system and the (new) settings used for the update itself. In rare cases they
can be different (a similar situation exists for autoyast).
We have to decide which set of settings to apply. We used to use the new ones
but because of the naming change, this bug appeared. So the proposed solution
in comment 6 is the smallest change (good) but goes halfway (bad). Another
solution is to always use the old settings. Yet another is to let the user
choose using an advanced option.
The new feature mentioned in comment 10 is that YaST itself is able to set up
networking for the 1st stage. Before, Linuxrc had to do it in advance.
--
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 > |