From owner-freebsd-current Mon Jan 4 10:04:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13283 for freebsd-current-outgoing; Mon, 4 Jan 1999 10:04:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13278 for ; Mon, 4 Jan 1999 10:04:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id KAA38336; Mon, 4 Jan 1999 10:03:44 -0800 (PST) To: "Daniel C. Sobral" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-19981226-SNAP/src/ssys.ac is corrupt In-reply-to: Your message of "Mon, 04 Jan 1999 16:32:17 +0900." <36906E81.D5AB960A@newsguy.com> Date: Mon, 04 Jan 1999 10:03:44 -0800 Message-ID: <38332.915473024@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err... I happen to have seen the exact same problem. I tried four > times to install the sys sources, and each time the connection would > stop at the precise same point. Perhaps there's a data-sensitive router somewhere in the path, e.g. one which flakes when certain bit patterns fly by. I've seen it happen with terminal servers of various types but rarely a full-blown cisco router. All I know is that when I verified the files on this end, they were fine. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message