Xref: utzoo comp.unix.questions:15371 comp.unix.wizards:17479
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Portable mknod ?? does it exist?
Keywords: mknod
Message-ID: <7521@cbmvax.UUCP>
Date: 3 Aug 89 03:04:06 GMT
References: <178@cerc.wvu.wvnet.edu.edu> <1419@riscy.dec.com> <181@cerc.wvu.wvnet.edu.edu> <2320@auspex.auspex.com>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <2320@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
> 
>  >dec: decnod
>  >myfifo created
>  >ERRNO: 6
>  >Open Failed: No such device or address
>  >dec: ls -l myfifo
>  >crw-r--r--  1 drs      255, 255 Aug  1 16:54 myfifo
> 
> That ain't no FIFO, that's a character special file.  The "mknod" call
> in the original posting looked OK, so either there's something funny in
> that code or there's a bug in Ultrix that causes it to create character
> special files when you ask it to create FIFOs....

Righto!  A problem was described over in comp.unix.ultrix today with mknod
of named pipes on NFS filesystems either being remotely accessed or served
by Ultrix 3.X.  The pipe nodes are actually created correctly, but Ultrix
"sees" them as character special files on a filesystem it has remotely
mounted and screws up in other amusing ways when a Sun or other system
tries to access a pipe on a remotely mounted filesystem.

Hopefully, DEC will fix this.

The sample program should work fine on a locally mounted filesystem.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)