From ccdf8bc04f0ea81c6c812a977f5c507fe8c26a3c Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Tue, 23 Aug 2016 10:03:31 +1200
Subject: [PATCH] accept.2: Demote discussion of DECNet to NOTES

DECNet ceased to be important long ago...

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
 man2/accept.2 | 27 ++++++++++++++-------------
 1 file changed, 14 insertions(+), 13 deletions(-)

diff --git a/man2/accept.2 b/man2/accept.2
index 355b2a2e9..1c2a3773a 100644
--- a/man2/accept.2
+++ b/man2/accept.2
@@ -137,19 +137,6 @@ Alternatively, you can set the socket to deliver
 when activity occurs on a socket; see
 .BR socket (7)
 for details.
-.PP
-For certain protocols which require an explicit confirmation,
-such as
-DECNet,
-.BR accept ()
-can be thought of as merely dequeuing the next connection request and not
-implying confirmation.
-Confirmation can be implied by
-a normal read or write on the new file descriptor, and rejection can be
-implied by closing the new socket.
-Currently, only
-DECNet
-has these semantics on Linux.
 
 If
 .IR flags
@@ -354,6 +341,20 @@ needs to have the
 .B O_NONBLOCK
 flag set (see
 .BR socket (7)).
+
+For certain protocols which require an explicit confirmation,
+such as
+DECNet,
+.BR accept ()
+can be thought of as merely dequeuing the next connection request and not
+implying confirmation.
+Confirmation can be implied by
+a normal read or write on the new file descriptor, and rejection can be
+implied by closing the new socket.
+Currently, only
+DECNet
+has these semantics on Linux.
+.\"
 .SS The socklen_t type
 The third argument of
 .BR accept ()