On Wed, 2012-04-04 at 09:19 -0400, Felix Miata wrote: > On 2012/04/03 23:56 (GMT-0700) Adam Williamson composed: > > > On Tue, 2012-04-03 at 17:13 -0400, Felix Miata wrote: > > >> I filed a bug and found a workaround: > >> https://bugzilla.redhat.com/show_bug.cgi?id=809470 > > > Did two net installs today from 17 Beta RC2 image, no problems. > > Net installs started with Grub and multiple net and video options on cmdline? > I had no such problem installing using boot.iso either. I suspect > https://bugzilla.redhat.com/show_bug.cgi?id=809475 has something if not a lot > to do with this. > > > are you sure this isn't an issue with your network / ISP? > > Did you read bug 809470 comment 3? The issue is Anaconda started as I did > tried/tries to use an "empty" resolv.conf. My puters are all multiboot, and > working normally, besides the fact that the very same puter had no such > problem installing from boot.iso. :-) yes, that was actually the comment that prompted me to ask; if something had gone wrong in the DHCP chain somewhere, your _already booted_ systems might carry on working happily as they have working nameserver entries, but a newly-booted one might not get proper nameserver entries and be unhappy. But it does sound like that's not the case. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
