bin/148220: sysinstall(8): 9.0-current gets "Cannot resolv
hostname ftp.freebsd.org" during install [regression]
Gerd Truschinski
gerd at truschinski.de
Mon Aug 9 19:26:31 UTC 2010
Gerd Truschinski wrote:
> Garrett Cooper wrote:
>> The following reply was made to PR bin/148220; it has been noted by
>> GNATS.
>>
>> From: Garrett Cooper <yanegomi at gmail.com>
>> To: bug-followup at FreeBSD.org, gerd at truschinski.de
>> Cc: Subject: Re: bin/148220: sysinstall(8): 9.0-current gets "Cannot
>> resolv hostname ftp.freebsd.org" during install [regression]
>> Date: Tue, 13 Jul 2010 08:32:16 -0700
>>
>> Could you please cat /etc/resolv.conf and call netstat -nr on the holo
>> shell after the failure occurs?
>> Thanks,
>>
>
> Sorry it took so long but real life eat my time and the temperatures
> my brain....
>
> The /etc/resolv.conf is empty.
>
>
> netstat -nr:
>
> Routing tables
>
> Internet:
> Destination Gateway Flags Refs Use Netif
> Expire
>
> Internet6:
> Destination Gateway
> Flags Netif Expire
> fe80::%nfe0/64 link#1
> U nfe0
> fe80::201:2eff:fe23:1263%nfe0 link#1
> UHS lo0
> ff01:1::/32 fe80::201:2eff:fe23:1263%nfe0
> U nfe0
> ff02::%nfe0/32 fe80::201:2eff:fe23:1263%nfe0
> U nfe0
>
>
>
> On the ALT-F2 screen i get the following lines (I copied the lines by
> hand):
>
> DHCPDISCOVER on nfe0 to 255.255.255.255 port 67 interval 8
> nfe0: link state changed to UP
> nfe0: link state changed to DOWN
> nfe0: link state changed to UP
> DHCPOFFER from 192.168.10.1
> DHCPREQUEST on nfe0 to 255.255.255.255 port 67
> DHCPACK from 192.168.10.1
> bound to 192.168.10.108 -- renewal in 3600 seconds
> -- the following lines appear after I close the "network-screen"
> just
> -- before I get the "Cannot resolv hostname ftp.freebsd.org" message
>
> DEBUG: Shutdown called for network device nfe0
> DEBUG: ifconfig nfe0 down
> DEBUG: Deleting default route
> delete net default
>
>
> I tried the same in a VMware machine at work and got the same result.
>
I have tried the last snapshot:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201008/FreeBSD-9.0-CURRENT-201008-amd64-bootonly.iso
and I got the same results.
Am I the only one who is using the bootonly snapshots?
/gT/
More information about the freebsd-sysinstall
mailing list