On Mon 19 Feb 2018 at 09:46:27 -0500, Gene Heskett wrote: > On Monday 19 February 2018 07:44:04 Brian wrote: > > > On Sun 18 Feb 2018 at 20:21:57 -0500, Gene Heskett wrote: > > > On Sunday 18 February 2018 18:47:58 Brian wrote: > > > > On Sun 18 Feb 2018 at 17:51:50 -0500, Gene Heskett wrote: > > > > > On Sunday 18 February 2018 17:19:48 Roger Price wrote: > > > > > > > > [Snipped] > > > > > > > > > > It looks as if the network setup in the EeePC is correct, but > > > > > > wget fails. Any suggestion would be very welcome, Roger > > > > > > > > > > Check the list, I think wget was mentioned as a problem child > > > > > child within the last 2 or 3 weeks. Is the machine fully > > > > > uptodate? > > > > > > > > What significance does "fully uptodate" have when using the > > > > installer? > > > > > > The install media may be dated, so if it will boot at all, the first > > > thing should be to update it and see if wget is replaced and now > > > works. > > > > Sounds reasonable until one realises the installer uses a busybox > > version of wget. And busybox hasn't changed during the lifetime of > > 9.x.x. > > while wget (and curl) has been updated, apparently trying to fix a bug or > attack vector, several times in the last 6 weeks or so. > > So this would appear to be a busybox problem from my point of view? Or
I've been misleading (because I did not check /usr/bin within the installer). Apologies. The installer actually uses wget 1.18-5+deb9u1, not the busybox version. -- Brian.