On Wed, 2010-03-17 at 11:10 -0700, Jesse Keating wrote: > Because you don't have NetworkManager installed (not in the minimal > set), and the "network" service isn't set to start at boot time anymore > (in favor of NetworkManager starting). Anaconda doesn't have code to > try and guess what service to enable based on what package set was > installed, so you're left with a minimal system that boots up and that's > about it. It's up to you to configure it from there. And it would just kill someone to add a patch into anaconda to test for the existence of NetworkManager and fire off "chkconfig network on" chrooted in the new install if NM isn't present. A patch to fix the problem is going to be a lot simpler than even documenting the broken behavior properly in the release notes, or is that also going to be left undone because anyone doing a minimal install should know how to fix it?
Attachment:
signature.asc
Description: This is a digitally signed message part
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
