Would it hurt then to have left the legacy network on by default ? Or at least spew an orange warning when detecting legacy config files that would require legacy network to run<br><br><div class="gmail_quote">On Sat, May 17, 2008 at 1:27 AM, Jeff Spaleta <<a href="mailto:jspaleta@gmail.com">jspaleta@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2008/5/16 Ahmed Kamal <<a href="mailto:email.ahmedkamal@googlemail.com">email.ahmedkamal@googlemail.com</a>>:<br>
<div class="Ih2E3d">> ick, nope. Well, thanks for the hint :) But it should really work without<br>
> even disabling NM. Instead I'm getting this in the logs:<br>
> messages-20080514:May 13 09:15:32 magic1 nm-system-settings:<br>
> ifcfg-fedora: error: Unknown connection type 'Bridge'<br>
><br>
> What else could be wrong?<br>
<br>
</div>NM doesn't handle all usage cases yet, which is why the legacy network<br>
stack is still available for people who need it.<br>
<br>
-jef"Rome wasn't built in a day and all that jazz"spaleta<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c">fedora-devel-list mailing list<br>
<a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-devel-list</a><br>
</div></div></blockquote></div><br>