From owner-freebsd-questions Sat Nov 14 04:25:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11736 for freebsd-questions-outgoing; Sat, 14 Nov 1998 04:25:36 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from hecate.webcom.com (hecate.webcom.com [209.1.28.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA11731 for ; Sat, 14 Nov 1998 04:25:35 -0800 (PST) (envelope-from graeme@echidna.com) Received: from eresh.webcom.com (eresh.webcom.com [209.1.28.49]) by hecate.webcom.com (8.9.1/8.9.1) with SMTP id EAA21870; Sat, 14 Nov 1998 04:25:14 -0800 Received: from [199.183.207.35] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 19776010; Sat Nov 14 04:23 PST 1998 Message-Id: <364DA0FE.6203@echidna.com> Date: Sat, 14 Nov 1998 07:25:50 -0800 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: Michael Lothian Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Not able to download boot floppy images References: <364D4CFA.50140E77@bigfoot.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Lothian wrote: > > Hello. I think there might be some problem with the ftp and its > mirrors... I tried to download the file > /pub/FreeBSD/3.0-RELEASE/floppies/boot.flp and it won't download. I > tried from ftp.freebsd.org and many mirrors in the US and other > countries. Also tried the 2.2.7-RELEASE boot floppies. I tried to > download from Netscape communicator 4.5, NcFTP, and lynx... Downloading > any other file in the archive works, even with files of the same size or > larger, so I don't think it's a problem with my computer or ISP... In > case it helps any, I am on an Intel Linux 2.0.32 machine, over a 56k > dial-up line. Works fine for me. Hard to see what would stop a binary download from working at the server end, especially from multiple servers, as long as the file has appropriate read permission. You don't say *what* went wrong, but, putting my Sherlock Holmes hat on, it would seem that you have not eliminated the obvious: namely that apart from the file, your ISP and machine are common in all cases. Try a different ISP and/or machine, and proceed deductively from there. Elementary (I think)! -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message