<div class="gmail_quote">On Wed, Apr 29, 2009 at 11:44 AM, Dan Williams <<a href="mailto:dcbw@redhat.com">dcbw@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="im">On Wed, 2009-04-29 at 11:12 -0400, Mark Bidewell wrote: > When I installed F11 preview. Network manager configured my eth0 to > never be activiated automatically. Since this was the only NIC on the > system the result was no network. Easily fixable but not user > friendly. I use KDE so I am not sure if this goes against network > manager or knetworkmanager. Any thoughts? </div>People can't have it both ways. Anaconda will write ONBOOT=no if you are not installing over the network, and thus your interface will not be "autoconnect". If you do install over a network, then anaconda will write ONBOOT=yes, and you will get autoconnect. That's the root cause of your problem. Not sure how to fix it, because there are legitimate reasons for not making all interfaces autoconnect when you don't do a network install. Part of that is security; don't bring a network up until you really need it, since connecting to a network makes a machine less secure. Not sure how to fix this, it's more of a policy decision at install-time than anything technical. Dan -- fedora-devel-list mailing list <a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-devel-list</a> </blockquote></div> I guess the question here is what if I was a "Joe SixPack" user who didn't know immediately to look in the settings what would I have done. Without network connectivity it is a little difficult to research the answer. -- Mark Bidewell <a href="http://www.linkedin.com/in/markbidewell">http://www.linkedin.com/in/markbidewell</a>