From owner-freebsd-arch@freebsd.org Tue Jul 3 16:43:40 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 03E251030691 for ; Tue, 3 Jul 2018 16:43:40 +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 8784E8B2AE for ; Tue, 3 Jul 2018 16:43:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 48E6B103068E; Tue, 3 Jul 2018 16:43:39 +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 25150103068D for ; Tue, 3 Jul 2018 16:43:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (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 B972E8B2AA for ; Tue, 3 Jul 2018 16:43:38 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x232.google.com with SMTP id p129-v6so923101ywg.7 for ; Tue, 03 Jul 2018 09:43:38 -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=buYahHmh2qPOETDy6cw7xaJMHHXJaqiNBjFkrf5EDm0=; b=j9T0YMQMoTmarpMTxep680DYSJ+p7fZWC/6DFC8ukQXoVWuIXd2CdKlKfs5Uzduyr2 dJ3N9fUIas3C5hB/ixaOUEBX9h1FkYyk4VZlFzb0FzRBl8SBXR+cugewsoLvUzmT1T91 rk2XwAm6iU/swcd0DxINAPe2g1jzSo/z4zlnM= 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=buYahHmh2qPOETDy6cw7xaJMHHXJaqiNBjFkrf5EDm0=; b=jgt2ES7K3YxynjsNGGAedsUGTdPLEDtUHWM5WhBKJy/Yg1b/yS5wk7GaRXZ71+4R18 6WuWMjhqJyfN3Z4EESn3K3j+xGpjkajWOvQgt17xdelVLouy5ld/9dRHqyTM9J9YK//q 6SYLhzRsQCyoa/CcCpaCZUZmR56XOy9cF9z7BCGLM7U6m4POnZO18DzgJdf4MEJEZ0NM cMumohXiBuOa1toP5GYTYDy716+NBkhsxvYwN9NSWz42wMahqGBXN1RiOdeW3Y8saSfj b9fslq5lwunawEr5xf9jpK991ncNzeWvHqwn8Jv3aPsh/RiAccRCiMoYCjI/HI27wEPP k34Q== X-Gm-Message-State: APt69E2NTd3KMkxDudNgGGHqKlynqm9eQRtCLwrHQNPXrppn6fJjvjvE ZvZNCBbafFp2jPDjk+oM6FE5ZlIB/DLqMnpVj2vGmA== X-Google-Smtp-Source: AAOMgpeSl48+Jg9d1eiZKwqU1nsE2v+us141AK99+ELJpFOh/IOwyKp/L4cmduEJJsMTYwuB+nSZPS8PZJYA0/QV8eI= X-Received: by 2002:a0d:cf01:: with SMTP id r1-v6mr14498044ywd.162.1530636217930; Tue, 03 Jul 2018 09:43:37 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:870e:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 09:43:37 -0700 (PDT) In-Reply-To: References: <201807030330.w633Uchd087857@slippy.cwsent.com> From: Eitan Adler Date: Tue, 3 Jul 2018 09:43:37 -0700 Message-ID: Subject: Re: What to do about rcmdsh(3) ? To: John Baldwin Cc: Cy Schubert , Konstantin Belousov , "freebsd-arch@freebsd.org" , "O'Connor, Daniel" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 16:43:40 -0000 I'm new at this. How does one do that? On Tuesday, 3 July 2018, John Baldwin wrote: > On 7/2/18 8:30 PM, Cy Schubert wrote: > > In message > il.com> > > , Eitan Adler writes: > >> On 26 June 2018 at 23:45, O'Connor, Daniel wrote: > >>> > >>> > >>>> On 27 Jun 2018, at 13:01, Eitan Adler wrote: > >>>> > >>>> 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 k > >> ept. > >>>>> You may remove default version for the symbol if you are so inclined. > >>>> > >>>> I'm new at this. How does one do that? > > > > > If you wanted to retire the symbol as suggested > by kib@ that would also be fine and would prevent new applications from > using it going forward (but you don't get to remove the source from libc). Sounds like a plan. I'm new at this. How does one do that? -- Sent from my Turing Machine