Date: Thu, 08 Jul 2010 11:43:08 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: Colin Percival <cperciva@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Randi Harper <randi@freebsd.org> Subject: Re: svn commit: r209787 - head/usr.sbin/sysinstall Message-ID: <4C359DAC.1060307@FreeBSD.org> In-Reply-To: <4C3591F5.2040401@freebsd.org> References: <201007080328.o683SP5k089410@svn.freebsd.org> <4C358891.5010502@FreeBSD.org> <4C3591F5.2040401@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 2010.07.08. 10:53, Colin Percival escreveu: >> I just used this >> feature yesterday to repair my -CURRENT installation on a netbook with >> an USB snapshot image. First I tried freebsd-update but it just failed >> to fetch the keys from the servers and was unable to produce any sensual >> error message >> > Yes, freebsd-update should print a more useful error message when it is asked > to upgrade to a release it doesn't support (freebsd-update only does RELEASEs, > BETAs, and RCs). But a more *sensual* message is probably not necessary. :-) > Btw, I'm not the only one who experienced this problem: http://forums.freebsd.org/showthread.php?t=1280 In my case, the system uses Wifi but everything just works with it, except freebsd-update. I don't know how it fetches the keys but that process should not be that difficult to require extra configuration, it should just work out of the box when network is up. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C359DAC.1060307>