From owner-svn-src-all@freebsd.org Sun Aug 25 20:11:18 2019 Return-Path: Delivered-To: svn-src-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 983D5C0B4A; Sun, 25 Aug 2019 20:11:18 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail.allbsd.org (mx.allbsd.org [IPv6:2001:2f0:104:e001::41]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.allbsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46GmVX6MqHz4NxX; Sun, 25 Aug 2019 20:11:16 +0000 (UTC) (envelope-from hrs@allbsd.org) Received: from mail-d.allbsd.org ([IPv6:2409:11:a740:4700:58:65ff:fe00:b0b]) (authenticated bits=56) by mail.allbsd.org (8.15.2/8.15.2) with ESMTPSA id x7PKAojq095081 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK) (Client CN "/CN=mail-d.allbsd.org", Issuer "/C=US/O=Let's+20Encrypt/CN=Let's+20Encrypt+20Authority+20X3"); Mon, 26 Aug 2019 05:11:01 +0900 (JST) (envelope-from hrs@allbsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=allbsd.org; s=20190220; t=1566763870; bh=+acWF/4g1KU26RlnooamDtN8IbTBbDMTABy/2fZEQgw=; h=Date:To:Cc:From:In-Reply-To:References; b=H6BQU4olFW0wpRZBDWBU64Rn0/Dq9wlBxzE/ukgS4oRgi+SQrtMhBG7n4WNoNuecI oRBCFqMSfE4oHsp1oIBQ5V6poGpXSaqEWGCU0NV14XdkfR6teZFUN5qwodCy3W0D49 rk5oT3c+KOgrZZQZpTeEflgZkF0QHcuvTAHWbqa4= Received: from alph.d.allbsd.org ([IPv6:2409:11:a740:4700:16:ceff:fe34:2700]) by mail-d.allbsd.org (8.15.2/8.15.2) with ESMTPS id x7PKAi5K069014 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 26 Aug 2019 05:10:45 +0900 (JST) (envelope-from hrs@allbsd.org) Received: from localhost (localhost [[UNIX: localhost]]) (authenticated bits=0) by alph.d.allbsd.org (8.15.2/8.15.2) with ESMTPA id x7PKAhWk069011; Mon, 26 Aug 2019 05:10:44 +0900 (JST) (envelope-from hrs@allbsd.org) Date: Mon, 26 Aug 2019 05:09:22 +0900 (JST) Message-Id: <20190826.050922.1810654532466043358.hrs@allbsd.org> To: asomers@freebsd.org Cc: sucanjan@gmail.com, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r351423 - in head: . sbin/ping6 sbin/ping6/tests From: Hiroki Sato In-Reply-To: References: <201908231522.x7NFMLuJ068037@repo.freebsd.org> <20190826.042056.1329861772202588895.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Mon_Aug_26_05_09_22_2019_925)--" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.allbsd.org [IPv6:2001:2f0:104:e001:0:0:0:41]); Mon, 26 Aug 2019 05:11:10 +0900 (JST) X-Rspamd-Queue-Id: 46GmVX6MqHz4NxX X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=allbsd.org header.s=20190220 header.b=H6BQU4ol; dmarc=none; spf=pass (mx1.freebsd.org: domain of hrs@allbsd.org designates 2001:2f0:104:e001::41 as permitted sender) smtp.mailfrom=hrs@allbsd.org X-Spamd-Result: default: False [-6.12 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[allbsd.org:s=20190220]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MV_CASE(0.50)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[allbsd.org]; RCPT_COUNT_FIVE(0.00)[5]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[allbsd.org:+]; NEURAL_HAM_SHORT(-0.96)[-0.959,0]; MID_CONTAINS_FROM(1.00)[]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:7514, ipnet:2001:2f0::/32, country:JP]; FREEMAIL_CC(0.00)[gmail.com]; IP_SCORE(-2.06)[ip: (-9.71), ipnet: 2001:2f0::/32(-4.06), asn: 7514(3.48), country: JP(-0.03)] X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Aug 2019 20:11:18 -0000 ----Security_Multipart(Mon_Aug_26_05_09_22_2019_925)-- Content-Type: Text/Plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Alan Somers wrote in : as> On Sun, Aug 25, 2019 at 1:22 PM Hiroki Sato wrote:= as> > as> > Hi, as> > as> > Alan Somers wrote as> > in <201908231522.x7NFMLuJ068037@repo.freebsd.org>: as> > as> > as> Author: asomers as> > as> Date: Fri Aug 23 15:22:20 2019 as> > as> New Revision: 351423 as> > as> URL: https://svnweb.freebsd.org/changeset/base/351423 as> > as> as> > as> Log: as> > as> ping6: Rename options for better consistency with ping as> > as> as> > as> Now equivalent options have the same flags, and nonequivale= nt options have as> > as> different flags. This is a prelude to merging the two comm= ands. as> > as> as> > as> Submitted by: J=E1n Su=E8an as> > as> MFC: Never as> > as> Sponsored by: Google LLC (Google Summer of Code 2019) as> > as> Differential Revision: https://reviews.freebsd.org/D2134= 5 as> > as> > I have an objection on renaming the existing option flags in pin= g6(8) as> > for compatibility with ping(8). as> > as> > Is it sufficient to add INET6 support to ping(8) with consistent= as> > flags and keep CLI of ping6(8) backward compatible? People have= used as> > ping6(8) for >15 years, so it is too late to rename the flags. = I do as> > not think the renaming is useful if "ping -6 localhost" or "ping= ::1" as> > works. as> > as> > -- Hiroki as> = as> If ping works with inet6, then why would we want to keep a separate= as> tool around? If it's just for the sake of people who don't want to= or as> can't update scripts, would a version in ports suffice? Because removing (or renaming) it causes a POLA violation. Do we really have a strong, unavoidable reason to force people to rewrite their script now? This is still a fairly essential and actively used tool, not like rcp or rlogin. Although deprecating ping6(8) and removing it from the base system in the future release at some point may work, changing the existing interface will simply confuse people who have used IPv6 for a long time. In my understanding, the purpose to integrate ping(8) and ping6(8) into a single utility is to provide a consistent CLI and reduce duplicate code, not to break compatibility. -- Hiroki ----Security_Multipart(Mon_Aug_26_05_09_22_2019_925)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iEYEABECAAYFAl1i6vIACgkQTyzT2CeTzy2ClwCfTYqnZFiqnhupVBSSMWJgwBhC IX0An1MVdAFw/iYenhcKqjXJ97XO9tfY =+FC4 -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Aug_26_05_09_22_2019_925)----