Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!convex!convex.COM From: tchrist@convex.COM (Tom Christiansen) Newsgroups: comp.lang.perl Subject: Re: Named pipes (was Re: perl compared to other Unix tools) Message-ID: <110864@convex.convex.com> Date: 12 Dec 90 19:12:16 GMT References: <9592:Dec920:40:5190@kramden.acf.nyu.edu> <110275@convex.convex.com> Sender: usenet@convex.com Reply-To: tchrist@convex.COM (Tom Christiansen) Organization: CONVEX Software Development, Richardson, TX Lines: 24 In article fuchs@it.uka.de (Harald Fuchs) quotes me: :>For unrelated processes, you're going to have to use named pipes :>or sockets. :Named pipes? Hmm... how about adding the mknod system call to perl? Is there some reason why you can't use system("/etc/mknod ...")? I recall that Larry doesn't like to add things that will only be called once; it doesn't buy much time, and it really isn't a bad thing to use other UNIX tools from within Perl. "Ah," you say, "but I want to rewrite MAKEDEV in perl." Ok, then use syscall and SYS_mknod instead then. It doesn't seem too hard to me. $SYS_mknod = 14; # should really have gotten from the "right" place $S_FIFO = 010000; # ditto syscall($SYS_mknod, "rendezvous", $S_FIFO|0666, 0) --tom -- Tom Christiansen tchrist@convex.com convex!tchrist "With a kernel dive, all things are possible, but it sure makes it hard to look at yourself in the mirror the next morning." -me