From owner-svn-src-head@freebsd.org Mon Nov 25 17:57:22 2019 Return-Path: Delivered-To: svn-src-head@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 9E6901B4495; Mon, 25 Nov 2019 17:57:22 +0000 (UTC) (envelope-from flo@smeets.xyz) Received: from mail-out.smeets.xyz (mail-out.smeets.xyz [IPv6:2a01:4f8:10a:3543::25:11]) by mx1.freebsd.org (Postfix) with ESMTP id 47MF9Y5gzXz3DGK; Mon, 25 Nov 2019 17:57:21 +0000 (UTC) (envelope-from flo@smeets.xyz) Received: from mail.smeets.xyz (mail.smeets.xyz [IPv6:2a01:4f8:10a:3543::25:3]) by mail-out.smeets.xyz (Postfix) with ESMTP id 770341884E; Mon, 25 Nov 2019 18:57:14 +0100 (CET) Received: from amavis.smeets.xyz (amavis.smeets.xyz [IPv6:2a01:4f8:10a:3543::aa:4]) by mail.smeets.xyz (Postfix) with ESMTP id D8C25B05AF; Mon, 25 Nov 2019 17:57:14 +0100 (CET) X-Virus-Scanned: amavisd-new at smeets.xyz Received: from mail.smeets.xyz ([IPv6:2a01:4f8:10a:3543::25:3]) by amavis.smeets.xyz (amavis.smeets.xyz [IPv6:2a01:4f8:10a:3543::aa:4]) (amavisd-new, port 10025) with ESMTP id 2pfbXDKTw8hF; Mon, 25 Nov 2019 17:57:14 +0100 (CET) Received: from nibbler.fritz.box (unknown [IPv6:2a02:8109:240:2b8:6484:a746:8ee6:f7e4]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) by mail.smeets.xyz (Postfix) with ESMTPSA id 59FB5B05A4; Mon, 25 Nov 2019 17:57:14 +0100 (CET) Subject: Re: svn commit: r351423 - in head: . sbin/ping6 sbin/ping6/tests To: Jan Sucan , Alan Somers , "Conrad E. Meyer" Cc: svn-src-head , Hiroki Sato , svn-src-all , src-committers References: <201908231522.x7NFMLuJ068037@repo.freebsd.org> <20190826.042056.1329861772202588895.hrs@allbsd.org> <20190826.050922.1810654532466043358.hrs@allbsd.org> <379c3378-f9dd-4d6b-35ca-fa1ac7e6386b@gmail.com> From: Florian Smeets Message-ID: <8259e67b-2f02-c02e-8aae-cbc8da896559@smeets.xyz> Date: Mon, 25 Nov 2019 18:57:13 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Thunderbird/72.0a1 MIME-Version: 1.0 In-Reply-To: <379c3378-f9dd-4d6b-35ca-fa1ac7e6386b@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47MF9Y5gzXz3DGK X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_FIVE(0.00)[5]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.78)[ipnet: 2a01:4f8::/29(-2.33), asn: 24940(-1.57), country: DE(-0.01)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DMARC_POLICY_ALLOW(-0.50)[smeets.xyz,reject]; RCPT_COUNT_SEVEN(0.00)[7]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2019 17:57:22 -0000 On 26.08.19 06:28, Jan Sucan wrote: > Hello, > > I can implement it. I suppose that ping6's manual page should be kept it > this case. > > I was also thinking about printing a warning for each option renamed to > lead a willing user to use the new unified option set of ping. It could > be either only with -v, or by default and suppressed with -q. Or should > the option translation be completely transparent? Is there an update on this? I found out the hard way today, as I updated my icinga2 host from an revision before this change to a current revision. In this case it's not as easy as fixing a script e.g. net-mgmt/monitoring-plugins check_ping command calls /sbin/ping6 with -X. Will we get a ping6 that is fully backward compatible, or should we start fixing ports? Thanks, Florian > > -Jan > > On 26. 8. 2019 1:58, Alan Somers wrote: >> Jan (please keep him CCed on replies) has been musing about the same >> thing.  That might satisfy everyone.  Jan, would it be straightforward >> to implement? >> -Alan >> >> On Sun, Aug 25, 2019 at 5:51 PM Conrad Meyer wrote: >>> Hi Alan, Hiroki, >>> >>> It would be pretty easy to install a `ping6` link to the `ping(8)` >>> binary with different option parsing (conditional on argv[0]).  That >>> removes most of the issues of code and space duplication, I think? >>> And the goal would be for the 'ping6' name to retain option >>> compatibility with historical ping6. >>> >>> It's not an uncommon pattern; for example, 'id', 'groups', and >>> 'whoami' are all a single binary with multiple linked names.  Another >>> example is Clang, which provides 'cc', 'c++', 'clang', 'clang-cpp', >>> 'clang++' and 'cpp' links to the same inode — and those have very >>> different behavior depending on argv[0]. >>> >>> It's less work than forcing the ping6 compatibility crowd to create a >>> port and doesn't hurt ping(8) much, AFAICT.  Is it an acceptable >>> middle ground? >>> >>> Best, >>> Conrad >>>