Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!newstop!texsun!csccat!egsner!eric
From: eric@egsner.cirr.com (Eric Schnoebelen)
Newsgroups: comp.unix.i386
Subject: Re: SCO 3.2.2 df/dfspace problem
Message-ID: <1990Aug30.143252.10986@egsner.cirr.com>
Date: 30 Aug 90 14:32:52 GMT
References: <1417@beaudin.UUCP> <1990Aug29.120821.1409@virtech.uucp>
Followup-To: comp.unix.sysv386
Organization: Central Iowa (Model) Railroad, Dallas, Tx.
Lines: 18

In article <1990Aug29.120821.1409@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
- This is probably due to a corrupted /etc/mount file.  This should be fixed
- when you reboot, but if it is not, go to single user mode, remove the file
- and reboot the system (/etc/mount should be re-created).

        I'm sure that Conner means the /etc/mnttab, since /etc/mount is
the program that one runs to mount a file system.  If you remove that,
you won't be able to use anything besides your root partition..

- df reads this file to get the list of currently mounted file systems and
- then calls statfs(2) to get the space characteristics for each file system.

	The /etc/mnttab file contains a binary list of all the mounted file
systems, name of the device, and the file system type.
-- 
Eric Schnoebelen		eric@cirr.com		schnoebe@convex.com
	Due to circumstances beyond your control, you are master of
		your fate and captain of your soul.