Return to BSD News archive
Xref: sserve comp.os.386bsd.development:562 comp.os.386bsd.questions:1981 Newsgroups: comp.os.386bsd.development,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!uxa.cso.uiuc.edu!rkb55989 From: rkb55989@uxa.cso.uiuc.edu (Rafal) Subject: Problems with MTOOLS and locks... Date: Sun, 25 Apr 1993 05:18:15 GMT Message-ID: <C60xEG.B6K@news.cso.uiuc.edu> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Organization: University of Illinois at Urbana Lines: 37 Hello all.. I have just recently installed NetBSD on top of what used to be 386BSD 0.1 pl 0.2.1 and wanted to install MTOOLS, so I could have some way to install stuff other than over 2400 baud... The reading part of MTOOLS works great, but I have had problems with all of the locking mechanisms when trying to write to disk.. I have attempted to do this with both FLOCK and FCNTL style locks, and not gotten very far... Whenever any of the MTOOLs utils tries to lock the device it is using, it get a EOPNOTSUPP error. I (think) I have tracked this down to a piece of code in the kernel that does the following: if (fp->f_type != DTYPE_VNODE) return (EOPNOTSUPP); [This comes from kern/kern_descrip.c, around line 714]. Now the question I have is: WHY? I do not have a in-depth knowledge of the file-system, or kernel internls, but it seems to me that this should NOT bomb out in this fashion... [it says in one of the .h files that type field differentiates between files and sockets.. and this doesn't look like a socket to me...] Let me know, whithout going over my head, please, what the deal is... Thanks, Rafal /------------------------------------------------------------------------\ |Rafal Boni r-boni@uiuc.edu| |"Me have a .sig?? I don't even have a clue!" rkb55989@uxa.cso.uiuc.edu| | -Anonymous rb6775@caffeine.cen.uiuc.edu| \------------------------------------------------------------------------/