Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sun-barr!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.questions Subject: Re: Trouble with mtools Date: 3 Apr 1993 13:00:35 -0600 Organization: Armstrong Lab MIS, Brooks AFB TX Lines: 29 Message-ID: <1pkmsjINN51r@hrd769.brooks.af.mil> References: <C4vp6n.72@skates.gsfc.nasa.gov> NNTP-Posting-Host: hrd769.brooks.af.mil In article <C4vp6n.72@skates.gsfc.nasa.gov> dc@cobi.gsfc.nasa.gov (Dave Cottingham) writes: >I can't get the mtools to work. mread works fine reading the A drive. >If I say "mcd", it dutifully answers "A:/" (or "A:\", whatever). >That's the whole list of what works. If I say mdir, or "mcd b:/", or >anything else, it says "init: open: no such file or directory" >(paraphrasing from memory). Inspection of init.c indicates that this >means it can't open the floppy dev for the given reason. Inspection >of devices.c indicates that the filenames in question are /dev/rfd0a >and /dev/rfd1a. They exist on my system, I checked. Any ideas what >the problem is? > I have seen two suggestions that will make this work. The first is to remake the mtools. The other is to make sure you ran /dev/MAKEDEV fd. This will ensure that all of the devices are created correctly. In addition, make sure that you have permissions to use the files. If you tried these as 'root' and they didn't work, try one of both of the first two. If you tried as a lowly supplicant, you may not have permissions on the devices. These questions will be addressed in the FAQ (there is a whole section about DOS file and disk questions). I am working on it and will try to get to it this weekend. -- ------ TSgt Dave Burgess NCOIC AL/Management Information Systems Office Brooks AFB, TX