*BSD News Article 79645


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!not-for-mail
From: bde@zeta.org.au (Bruce Evans)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Named pipe with mknod
Date: 1 Oct 1996 19:28:38 +1000
Organization: Kralizec Dialup Unix
Lines: 17
Message-ID: <52qo86$kr1@godzilla.zeta.org.au>
References: <GORSKI.96Sep30150728@axiom.somewhere.de>
NNTP-Posting-Host: godzilla.zeta.org.au

In article <GORSKI.96Sep30150728@axiom.somewhere.de>,
 <gorski@cips01.physik.uni-bonn.de> wrote:
>
>
>Compile the program below and run it. On FreeBSD it produces:
>mknod: Invalid argument
>
>Why ??
>I thought this should run on FreeBSD without using mkfifo.

FreeBSD supports the POSIX syscall mkfifo().  There is no reason to
use mknod() to create named pipes except for backwards compatibility,
and since old BSDs didn't support named pipes there is nothing to be
backwards compatible with.  There is no reason to support creating named
pipes using mknod() since anything that uses it must be misconfigured.
-- 
Bruce Evans  bde@zeta.org.au