From owner-freebsd-current@freebsd.org Tue Nov 10 21:26:47 2020 Return-Path: Delivered-To: freebsd-current@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 E403E464DDA for ; Tue, 10 Nov 2020 21:26:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CW1CB6Fz0z4vmM for ; Tue, 10 Nov 2020 21:26:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qv1-xf32.google.com with SMTP id q7so2830803qvt.12 for ; Tue, 10 Nov 2020 13:26:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9T6yIIdq6gqkPHeg7MfFTkPVsBgMPpbI3lygi1vLdmM=; b=X/1ugCB5bzhaKtV8D1eHH0F573pyNyLbua0J0qJFydebCMU+Wulo673MHVxdFAViUM sJJPs7qBERGjiZXsKNQ/fUxex8K4cH6hWOQGcNvZu3bajeFwfpIN212rUddrZB6BnCfK v+pZNSywVwZ4v3fnmHdr93BGe1EIYoTWYZHAYvToJ1PRxM8fhsdvYo+AExTJQppdZUWm UUt3XCWZp6fouSpgpjpx422Zq0STTl14KYeehZy9xECRTS9J9LFhVxZa83hxK07CIeQ0 +vxzkURJBzrPTu72N6YqAt8ANlkbOlrk76paQr8T3+m4UiVhrzma0vr7Bdv53ncmK9Ju wgMw== X-Gm-Message-State: AOAM530IYpCdVKDwQAeYxS7VECNl5af9Ta6NW/cbsXuM7b1119zKfm1A Jv1L/wqWMUQMzCFt/CEWNFAVEMqUYYoxY72z+SBCOw== X-Google-Smtp-Source: ABdhPJwNYjg7rHXWBGfUtQ1NUBjPfTMVtDRkhfqPZgF7fmyPvnKCwvfCyXYXzSkqJ34i9tvGiMomk4soW7pJvGZta3w= X-Received: by 2002:a0c:c30d:: with SMTP id f13mr17068628qvi.29.1605043605413; Tue, 10 Nov 2020 13:26:45 -0800 (PST) MIME-Version: 1.0 References: <006f7b702a5b46b08a4303bbce08c4c8@dlr.de> In-Reply-To: <006f7b702a5b46b08a4303bbce08c4c8@dlr.de> From: Warner Losh Date: Tue, 10 Nov 2020 14:26:34 -0700 Message-ID: Subject: Re: Is "/usr/bin/sscop" still relevant? (related to ATM) To: Hartmut Brandt Cc: mj-mailinglist@gmx.de, FreeBSD Current X-Rspamd-Queue-Id: 4CW1CB6Fz0z4vmM X-Spamd-Bar: / X-Spamd-Result: default: False [0.97 / 15.00]; TO_DN_SOME(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RBL_DBL_DONT_QUERY_IPS(0.00)[2607:f8b0:4864:20::f32:from]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; SUBJECT_HAS_QUESTION(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.97)[0.970]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; NEURAL_SPAM_MEDIUM(1.00)[1.000]; SPAMHAUS_ZRD(0.00)[2607:f8b0:4864:20::f32:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f32:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_CC(0.00)[gmx.de,freebsd.org]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Nov 2020 21:26:47 -0000 So both the kernel and userland parts can go away? ./contrib/ngatm/sscop ./sys/modules/netgraph/atm/sscop ./sys/netgraph/atm/sscop ./usr.bin/atm/sscop Warner On Tue, Nov 10, 2020 at 1:27 AM wrote: > Hi, > > this can go away. It is the transport protocol underlying ATM signaling. > > harti > > -----Original Message----- > From: owner-freebsd-current@freebsd.org > On Behalf Of mj-mailinglist@gmx.de > Sent: Monday, November 9, 2020 10:07 PM > To: freebsd-current@freebsd.org > Subject: Is "/usr/bin/sscop" still relevant? (related to ATM) > > Is "/usr/bin/sscop" still relevant? The sscop tool implements the Q.2110 > transport protocol, which is used in ATM-Networks. > The NATM framework was removed in April 2017, but sscop depends on > netgraph (libngatm.so.4), so it seems to be independent from NATM. > > The manpage refers to libunimsg(3), which does not exist, but unimsg(3) > does. > It also depends on libngatm.so.4, which also does not have a man page. > > So, is it still useful? The most documents i found about ATM are from the > early 2000 to mid 2010s. > > -- > Martin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >