Bug 441679 - Choosing not to install NetworkManager leaves system without networking on bootup
Summary: Choosing not to install NetworkManager leaves system without networking on bo...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-04-09 13:53 UTC by Charles R. Anderson
Modified: 2014-03-17 03:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-17 19:37:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Charles R. Anderson 2008-04-09 13:53:28 UTC
Description of problem:

Deselecting NetworkManager in anaconda leaves the installed system without any
way to start the network automatically on first bootup.  Can we please enable
the "network" service in this case?

Comment 1 Jesse Keating 2008-04-09 14:05:05 UTC
Hrm, I don't know if we want to handle that.  Perhaps we should just make
NetworkManager a required rather than a default or optional.

Comment 2 Jeremy Katz 2008-04-09 14:06:27 UTC
Doing things like this doesn't scale.  Fix the packages, either by having
initscripts require NetworkManager or marking the package required rather than
default in comps.

Reassigning to distribution to duke that out there :)

Comment 3 Bill Nottingham 2008-04-17 19:37:18 UTC
Fixed in comps to be mandatory for the 'Base' group.


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