From owner-freebsd-current Thu Dec 14 23:49:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA01861 for current-outgoing; Thu, 14 Dec 1995 23:49:06 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA01855 for ; Thu, 14 Dec 1995 23:49:02 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id OAA14491; Thu, 14 Dec 1995 14:19:24 -0700 Date: Thu, 14 Dec 1995 14:19:24 -0700 From: Nate Williams Message-Id: <199512142119.OAA14491@rocky.sri.MT.net> To: Bob Willcox Cc: freebsd-current@freefall.freebsd.org Subject: Re: sups from SUP.FreeBSD.ORG not working well anymore :-( In-Reply-To: <199512141543.JAA25820@luke.pmr.com> References: <4348.818903626@westhill.cdrom.com> <199512141543.JAA25820@luke.pmr.com> Sender: owner-current@FreeBSD.ORG Precedence: bulk Bob Willcox writes: > Well, sup has gone from bad to worse for me. I can no longer get it to > work at all! Using sup.freebsd.org I am now getting: > > SUP 8.26 (4.3 BSD) for file stable-supfile at Dec 14 09:14:46 > SUP: Can't find host entry for sup.FreeBSD.org > SUP: Will retry in 73 seconds > SUP: Can't find host entry for sup.FreeBSD.org This means your host can't resolve sup.FreeBSD.org, and it's now sup's fault. > and with sup2.freebsd.org its simply: > > SUP 8.26 (4.3 BSD) for file stable-supfile at Dec 14 09:27:58 > SUP: Can't connect to server for supfilesrv: Operation timed out This means it can't make a network connection to sup2.FreeBSD.org, which is a network problem and again not sup's fault. The Internet in and around the Bay area is having *lots* of problems due to the recent storms, so I wouldn't expect everything to work for awhile. Nate