Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.erols.net!news.mathworks.com!uunet!in1.uu.net!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Named pipe with mknod Date: 5 Oct 1996 17:19:29 GMT Organization: Private BSD site, Dresden Lines: 17 Message-ID: <5365b1$ba@uriah.heep.sax.de> References: <GORSKI.96Sep30150728@axiom.somewhere.de> <52qo86$kr1@godzilla.zeta.org.au> <52rvql$5t4@newsbr.eunet.fr> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E fgm@osinet.fr (Frederic G. MARAND) wrote: > There is one compatiblity reason: the command-line (not syscall) for > System V mknod includes the "p" argument for creating a named pipe. It > is therefore more easy to remember than a specific syscall. But that's only (fully) true for SVR3. With SVR4, there's the same mkfifo command available, and it's usually less hidden than the mknod command. (SVR3 mknod was often /etc/mknod, so you wouldn't find that command on BSD at all, either.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)