Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 442461 - GUI network config may need rethought for F10
GUI network config may need rethought for F10
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
: FutureFeature
Depends On: NMinAnaconda
Blocks: F10Blocker/F10FinalBlocker
  Show dependency treegraph
Reported: 2008-04-14 17:36 EDT by Bill Nottingham
Modified: 2014-03-16 23:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-15 21:01:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2008-04-14 17:36:54 EDT
Description of problem:

If we're doing NM by default, we may need to rethink how this works. Right now
it just lets you configure some things that may be ignored, and when run from
the live install, doesn't actually reflect things like 'active device' correctly.

Version-Release number of selected component (if applicable):

rawhide-20080408 livecd
Comment 1 Jeremy Katz 2008-04-14 18:17:09 EDT
Yes, we definitely should.  Had NM landed by default in advance of the feature
freeze, we might have actually changed things for F9  :-/
Comment 2 David Cantrell 2008-04-14 18:29:04 EDT
I have a huge patch in the works for networking overhaul to anaconda (stage1 and stage2) to do several 
things, most notably getting rid of libdhcp and making it easier to interact with NM.  Just an fyi.
Comment 3 David Cantrell 2008-09-15 21:01:27 EDT
I've reduced the network post configuration screen to just asking for the hostname.

Note You need to log in before you can comment on or make changes to this bug.