From owner-freebsd-arch@freebsd.org Wed Jun 27 03:32:05 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 7DA38102AEB6 for ; Wed, 27 Jun 2018 03:32:05 +0000 (UTC) (envelope-from lists@eitanadler.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 16A8790D24 for ; Wed, 27 Jun 2018 03:32:05 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id CE678102AEB5; Wed, 27 Jun 2018 03:32:04 +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 BC32C102AEB1 for ; Wed, 27 Jun 2018 03:32:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6DF90D20 for ; Wed, 27 Jun 2018 03:32:04 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x231.google.com with SMTP id j5-v6so201070ywe.8 for ; Tue, 26 Jun 2018 20:32:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hRG2mSKhMZbnMJGDFgPokDGYJDpyec5qnYemKz9/eRo=; b=gCPqgQYKmc2dk/2CFZqWEMeHn/o2iHyNMjpw53nqPqzFrujp/AQB4cqboyyXqHADcS 3/y+HRm8gunsPhD9++39+EvHm6f+yD5KsnTVDMpoojk07/BG5Mmudoayt90czbOUbV7M huSCdZSY9s7TFq3Jh8mxLGohUYspQoE7Gvnfs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hRG2mSKhMZbnMJGDFgPokDGYJDpyec5qnYemKz9/eRo=; b=CqEoI9NSRx62De1Vl/85JOG/ZRnFHT0nBONk/puBlHnG4Cp5rcMQVRftO5IKZRp2q3 ohfLHChxr5d/YDjKIu1rCGsY5kgXhvAXrp5rLCDqCHMBLPoYT+u8RCKUkHtZ7s2+b+Wt e+K5oH/0EF+mWYtu9eQkuvHTHEuMJmgjbyEvUAyCuoTpgIpFxptfva2FmGrMAwHPgFUM fR++6wHybxFJUScUczzwdZEnG5Tw5eX9KBZh4+oK2f35aAlohW8O3Ic/D3GNwNvjSJKm 3yrRQq21viKLRMUcwd5c1Ml6knl/Pj3+4pFqjGVhXgVGkx6aEjI2Bp+k+HBwjYihaOxQ E+qQ== X-Gm-Message-State: APt69E1sShQ2BiCPGXPNpQb22YKJrAQs2FtNIzy9oZtqNHyrulry+5gI 3KN6HqAHjwKEjWkzq5WmB6URLq/YMjuxRhGq7mV4qA== X-Google-Smtp-Source: AAOMgpfEHnJ6J+I/dlC65NYgcX7Vft7SBuo6X4jGIxjp2VvooHWTnUBkTvhy9kMOr/KMKPPwlsyuXcsNEO2QA+hWLnE= X-Received: by 2002:a81:af1d:: with SMTP id n29-v6mr2037432ywh.113.1530070323572; Tue, 26 Jun 2018 20:32:03 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Tue, 26 Jun 2018 20:31:32 -0700 (PDT) In-Reply-To: <20180624121412.GY2430@kib.kiev.ua> References: <20180624121412.GY2430@kib.kiev.ua> From: Eitan Adler Date: Tue, 26 Jun 2018 20:31:32 -0700 Message-ID: Subject: Re: What to do about rcmdsh(3) ? To: Konstantin Belousov Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" 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: Wed, 27 Jun 2018 03:32:05 -0000 On 24 June 2018 at 05:14, Konstantin Belousov wrote: > 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. I'm new at this. How does one do that? -- Eitan Adler