Bug 423571 – does NetworkManager require system->adminstration->services pokery

Bug 423571 - does NetworkManager require system->adminstration->services pokery

Summary:	does NetworkManager require system->adminstration->services pokery

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	NetworkManager (Show other bugs)
Sub Component:
Version:	8
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Dan Williams
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-12-13 10:23 EST by Andrew Cagney
Modified:	2007-12-13 11:05 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-12-13 11:05:38 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Cagney 2007-12-13 10:23:35 EST

I'm finding that the network manager only starts to work reliably after I've
played around with system -> adminstration -> services and:

+ enabled NetworkManager (and dispatcher)
- disabled "network" (or turned off its control of eth0 (TP) and eth1
(802.11blah) perhaps)

can this be selected during install?

Comment 1 Dan Williams 2007-12-13 11:05:38 EST

Yep, the 'network' service and NetworkManager are incompatible and mutually
exclusive.  NM is only enabled by default on LiveCD installs, I think.  WE'll
fix this in F9.

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