Return to BSD News archive
#! rnews 1341 sserve.cc.adfa.oz.au Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.ecn.uoknor.edu!qns3.qns.com!news.sprintlink.net!cs.utexas.edu!howland.reston.ans.net!EU.net!uknet!warwick!news.ncl.ac.uk!blagdon!njkw From: Jim Wight <J.K.Wight@ncl.ac.uk> Newsgroups: comp.os.386bsd.questions Subject: Re: Problem with mtools "device busy" Date: 30 May 1995 08:42:15 GMT Organization: University of Newcastle upon Tyne Lines: 20 Message-ID: <3qelp7$hpg@whitbeck.ncl.ac.uk> References: <3q422t$s7j@hpsystem1.informatik.tu-muenchen.de> NNTP-Posting-Host: blagdon.ncl.ac.uk liebsche@Informatik.TU-Muenchen.DE (Andreas Liebscher) writes: >I have a problem with MTOOLS. mdir, mread, mformat work well, but using >mwrite or mcopy results in the following error-message: >Device "/dev/rfd1440" busy >Who can help me? I recently had this problem on a NetBSD 1.0 system with mtools 2.0.7. The problem was that the flock call in lock_dev (init.c) was failing with an EOPNOTSUPP error. However, lock_dev treats all errors alike and init prints `Device "xxx" is busy' irrespective of the problem. I simply got round it by turning lock_dev into a noop by commenting out the flock call. Jim --- J.K.Wight@newcastle.ac.uk Department of Computing Science, University of Newcastle, Tel: +44 191 222 8238 Newcastle upon Tyne, NE1 7RU, United Kingdom. Fax: +44 191 222 8232