From 3920c8caf67531d451649b6427c78ad2b96f536b Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Fri, 14 Dec 2007 07:04:07 +0000 Subject: [PATCH] Clarify use of mkfifo() versus mknod(). as per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455825 --- man2/mknod.2 | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/man2/mknod.2 b/man2/mknod.2 index 0b0505beb..88a26b6af 100644 --- a/man2/mknod.2 +++ b/man2/mknod.2 @@ -175,13 +175,16 @@ or is not 0, the behavior of .BR mknod () is unspecified." +However, nowadays one should never use +.BR mknod () +for this purpose; one should use +.BR mkfifo (3), +a function especially defined for this purpose. Under Linux, this call cannot be used to create directories. One should make directories with -.BR mkdir (2), -and FIFOs with -.BR mkfifo (3). -.\" Unix domain sockets with .BR socket " (and " bind ), +.BR mkdir (2). +.\" and one should make Unix domain sockets with socket(2) and bind(2). There are many infelicities in the protocol underlying NFS. Some of these affect