From owner-freebsd-net@FreeBSD.ORG Sun Jan 12 16:48:06 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E6934AD for ; Sun, 12 Jan 2014 16:48:06 +0000 (UTC) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [IPv6:2607:f2f8:a450::66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 417531F42 for ; Sun, 12 Jan 2014 16:48:06 +0000 (UTC) Received: from chombo.houseloki.net (c-71-236-222-167.hsd1.wa.comcast.net [71.236.222.167]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id 48364E6040; Sun, 12 Jan 2014 08:48:04 -0800 (PST) Received: from [IPv6:2601:7:880:bd0:fc09:c077:33b5:32cc] (unknown [IPv6:2601:7:880:bd0:fc09:c077:33b5:32cc]) by chombo.houseloki.net (Postfix) with ESMTPSA id 6A36BD5E; Sun, 12 Jan 2014 08:47:49 -0800 (PST) Message-ID: <52D2C734.8000808@bluerosetech.com> Date: Sun, 12 Jan 2014 08:47:48 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Chris H , freebsd-net@freebsd.org Subject: Re: Merge ping+ping6 and traceroue+traceroute6 to single utilities? References: <1063008459.20140111160525@serebryakov.spb.ru> <20140111164047.GA97150@edge.bac.lab> <20140111.180057.78714603.sthaug@nethelp.no> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: freebsd-net List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Jan 2014 16:48:06 -0000 On 1/12/2014 1:15 AM, Chris H wrote: > How is ping -6 || ping -4 better? It would make them behave the same way as almost everything else, thus following the concept of feature parity between IPv4 and IPv6. > How will modifying all the some thousands of scripts everyone currently uses > based on the current commands, make it better? No need to modify scripts. Provide a hardlink to ping6 and add code that checks argv[0] and runs in compatibility mode if called as ping6. We can then use this opportunity to homogenize the IPv4 and IPv6 ping parameter assignments without breaking backward compatibility.