From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from netcomsv.netcom.com ([163.179.1.9]) by hawkwind.utcs.toronto.edu with SMTP id <2688>; Sun, 21 Mar 1993 22:21:03 -0500
Received: from netapp.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1)
	id AA03742; Sun, 21 Mar 93 19:21:11 PST
Received: from ghoti.netapp by netapp.netapp.com (4.1/SMI-4.1)
	id AA12650; Sun, 21 Mar 93 19:12:26 PST
Date:	Sun, 21 Mar 1993 22:12:26 -0500
From:	byron@netapp.com (Byron Rakitzis)
Message-Id: <9303220312.AA12650@netapp.netapp.com>
To:	rc@hawkwind.utcs.toronto.edu
Subject: informal survey regarding <{}

I was wondering if anyone in rc-land is using the <{} feature
with fifos.

Specifically, I've been thinking about ditching fifos in favor
of synchronous operation with tmp files.

Advantages:

	o You can seek on a tmp file, so diff will work.
	o tmp files are much closer in semantics to real pipes,
		so I expect fewer bugs.
	o fifos aren't present everywhere, files are.
	o fifos don't work everywhere (e.g., the notorious
		tmpfs bug), files do.

Disadvantages:

	o Existing users might depend on fifos.
	o Advantage of pipe in the kernel is lost; command must
		wait on all the tmp files being written first.

I could even argue, based on the first item in "Advantages",
that one might want to use tmp files even over /dev/fd, but
I don't want to risk starting a flame war.

Anyway, reply to me and I can summarize to the list.