Hide Forgot
Description of Problem: It's not intuitive to configure different network device profiles. From an intuitive point of view, it should be enough to edit & save the configuration of a device *with a certain profile selected* to create a certain configuration. Nicknames as eth0_foo are logically confusing - because, if I (as a user) have selected ProfileFoo from the Profile menu, I expect that all changes in configuration are related to ProfileFoo - "why is the option to select which profile you are working with there, anyway?". Steps to reproduce the problem: Not applicable. Actual Results: Confusion when configuring profiles. Expected Results: "Oh, how easy and intuitive it is to configure network device profiles that I can use when taking my laptop with me traveling!" How often does this happen? Always. Additional Information: Looking in /etc/sysconfig/networking/profiles, I notice that f.eg. the config for eth0 for profile "Away" is stored as ifcfg-eth0_travel (eth0_travel was the nickname I assigned). Shouldn't ifcfg-eth0_Away do as file name, and thus make nicknames unnecessary? (Why does it have to have a unique file name anyway, the "hosts" file and "resolv.conf" files don't have _nickname added and the directory named after the profile itself should be enough as I suppose that profile names have to be unique as well..)
*** Bug 112793 has been marked as a duplicate of this bug. ***
*** Bug 110838 has been marked as a duplicate of this bug. ***
Adding to blocker bug 185486 and to IBM confidential group.
OOps. Sorry for the mistake. I searched by the wrong list and mistakenly made these changes. Sorry for the spam. Removing from blocker bug 185486 and to IBM confidential group.
The last changes to these bugs were mistakenly made. Removing incorrect blocker bug and confidential group.
Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/) for security updates only. If this is a security issue, please reassign to the 'Fedora Legacy' product in bugzilla. Please note that Legacy security update support for these products will stop on December 31st, 2006. If this is not a security issue, please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. If you are currently still running Red Hat Linux 7.3 or 9, please note that Fedora Legacy security update support for these products will stop on December 31st, 2006. You are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a security issue, please change the product as necessary. We thank you for your help, and apologize again that we haven't handled these issues to this point.
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. f you are currently still running Red Hat Linux 7.3 or 9, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX.