From owner-freebsd-arch@freebsd.org Sun Jun 24 12:14:25 2018 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B46BA102740F for ; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4E26B87017 for ; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 078BF102740E; Sun, 24 Jun 2018 12:14:25 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8F68102740D for ; Sun, 24 Jun 2018 12:14:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4A1F187016 for ; Sun, 24 Jun 2018 12:14:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5OCECHU074062; Sun, 24 Jun 2018 15:14:15 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5OCECHU074062 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5OCECGl074061; Sun, 24 Jun 2018 15:14:12 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 24 Jun 2018 15:14:12 +0300 From: Konstantin Belousov To: Eitan Adler Cc: "freebsd-arch@freebsd.org" Subject: Re: What to do about rcmdsh(3) ? Message-ID: <20180624121412.GY2430@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2018 12:14:25 -0000 On Sun, Jun 24, 2018 at 03:32:13AM -0700, Eitan Adler wrote: > Now that the rcmds are removed from base, it opens a question about > what to do with rcmdsh(3). > This is documented as > rcmdsh ??? return a stream to a remote command without superuser > And is implemented as a rather simple wrapper of getaddrinfo and exec. > > This isn't something I'd imagine we'd add to libc now-a-days and is > currently broken by default (due to defaulting to _PATH_RSH) > > I'm not sure there is much value in keeping this function around. I > did a rather naive search for uses of this function in ports and > couldn't find any. I'm preparing a more comprehensive patch for an > exp-run. There is a huge value in keeping ABI compatibility. The symbol must be kept. You may remove default version for the symbol if you are so inclined. > > Does anyone have a reason to keep in libc? Any objection to removing > it? If no, is there anything special I need to do beyond just removing > the implementation and references? > > -- > Eitan Adler > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"