Messages in this thread | | | Date | Fri, 25 Dec 1998 01:37:42 +0100 | From | jens@pinguin ... | Subject | Re: device: /dev/repeat |
| |
On Wed, Dec 23, 1998 at 03:25:51AM -0500, Dave Cinege wrote:
>> There are problems in multi-process setups. Say I have one process >> which wants to have /dev/repeat return 01010101. I have another >> process which wants 00000000, and another which wants 11111111. The >> first process writes 01010101 to /dev/repeat. The second writes >> 00000000. Then the first finally gets around to reading >> /dev/repeat. Then the third process writes 11111111, and the second >> process reads. Oops. :) > Unlike the blabering in the rest of this thread, this is actually a real > problem. I guess the same this exists with serial ports, an that is > 'solved' (somewhat) with lock files. /dev/repeat0-9 could also be > available to help this. Any better ideas?
I had a LD_PRELOAD'able patch floating around making /tmp 'user transparent', i.e. every user only sees 'his' files in /tmp because /tmp is invisbly redirected to /tmp/$USER. Couldn't the same be done with this device?
-- _ciao, Jens_______________________________ http://www.pinguin.conetix.de cat /dev/boiler/water | tea | sieve > /cup mount -t hdev /dev/human/mouth01 /mouth ; cat /cup >/mouth/gulp
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |