Date: Tue, 10 Nov 2020 08:27:02 +0000 From: <Hartmut.Brandt@dlr.de> To: <mj-mailinglist@gmx.de>, <freebsd-current@freebsd.org> Subject: RE: Is "/usr/bin/sscop" still relevant? (related to ATM) Message-ID: <006f7b702a5b46b08a4303bbce08c4c8@dlr.de> In-Reply-To: <trinity-cd1ffccb-8907-4d5f-90ad-deb5807cf5ea-1604956034265@3c-app-gmx-bap62> References: <trinity-cd1ffccb-8907-4d5f-90ad-deb5807cf5ea-1604956034265@3c-app-gmx-bap62>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, this can go away. It is the transport protocol underlying ATM signaling. harti -----Original Message----- From: owner-freebsd-current@freebsd.org <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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006f7b702a5b46b08a4303bbce08c4c8>