minimal install too minimal

Jesse Keating jkeating at redhat.com
Thu Mar 18 18:19:23 UTC 2010


On Wed, 2010-03-17 at 23:52 -0500, John Morris wrote:
> 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?

These are questions you should ask the anaconda upstream.  As with any
project, what you see is often 1 part design, 2 parts lack of code.

-- 
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/test/attachments/20100318/ae37622a/attachment.bin 


More information about the test mailing list