X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Tom Van Looy" To: cygwin AT cygwin DOT com Cc: lino DOT m DOT tinoco AT telecom DOT pt Sensitivity: Normal Message-ID: X-Forwarded-For: [10.10.1.191] Date: Wed, 28 May 2008 12:52:12 +0000 Subject: Re: Bug in /usr/bin/ping Reply-To: assarix AT pandora DOT be MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I looked a little further and saw that this is a port that I probably just installed to try it out and hoped it had GNU ping arguments (so bash scripts are portable between Linux and Cygwin). Anyway, I don't know what happend but it's a 4.3BSD utility. Even 4.3BSD derived systems do the return stuff correctly nowadays. Cygwin port maintained by: Lino Tinoco Please address all questions to the Cygwin mailing list at Shouldn't this package just be dropped or at least be marked obsolete? Cygwin is supposed to be a Linux-like environment. I don't think outdated 4.3BSD tools belong there. Windows ping even has more similarities with Linux ping than that ping in packages ... Kind regards, Tom Van Looy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/