Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!sgiblab!brunix!cat.cis.brown.edu!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!sol.ctr.columbia.edu!startide.ctr.columbia.edu!wpaul From: wpaul@ctr.columbia.edu (Bill Paul) Newsgroups: comp.os.386bsd.questions Subject: Re: mkfifo problem Date: 31 Oct 1994 14:36:07 GMT Organization: Columbia University Center for Telecommunications Research Lines: 37 Message-ID: <392vcn$3ov@sol.ctr.columbia.edu> References: <392kkp$8bu@iaehv.iaehv.nl> NNTP-Posting-Host: startide.ctr.columbia.edu X-Newsreader: TIN [version 1.2 PL2] Daring to challenge the will of the almighty Leviam00se, Walter Belgers (gigawalt@iaehv.iaehv.nl) had the courage to say: : Hi, : I run FreeBSD 1.1.5 and cannot make named pipes. I tried mkfifo (as : superuser) and got a "operation not supported". The kernel is compiled : with the options FIFO on. Does anybody have a suggestion? : Walter. : -- : Walter Belgers ------. Jo man! Tok tok jo! : gigawalt@iaehv.nl \ : gigawalt@giga.iaehv.nl `-> more info: http://www.iaehv.nl/users/gigawalt/ Well, to be blunt, I don't care what you think you did to enable fifo support, you did it wrong. If mkfifo() returns EOPNOTSUPP, then you simply aren't running a kernel with fifo support enabled. There are two possibilities here: a) you built the kernel wrong -- possibly you compiled the kernel in an existing build directory, and you didn't do a 'make clean' and a 'make depend' like you were supposed to. There are several files in /usr/src/sys/kern that need to be rebuilt and the Makefile may not necessarily rebuild them unless you do a 'make clean' first. b) you compiled the kernel correctly by haven't installed it -- the new kernel has to be copied to /386bsd and the system rebooted in order for the changes to take effect. My money's on choice a), personally. Please do a 'make clean,' then try making a new kernel and be sure you install it correctly. Remember to save the existing /386bsd as /386bsd.old in case the new kernel turns out to be hosed. -- -Bill Paul wpaul@ctr.columbia.edu