Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!uwm.edu!zaphod.mps.ohio-state.edu!samsung!uunet!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO 3.2.2 df/dfspace problem
Message-ID: <48@raysnec.UUCP>
Date: 31 Aug 90 15:34:57 GMT
References: <1417@beaudin.UUCP> <1990Aug29.120821.1409@virtech.uucp>
Distribution: comp
Organization: IRS/CI - Technical Solutions Branch
Lines: 22

>In article <1417@beaudin.UUCP> john@beaudin.UUCP (John Beaudin) writes:
>>df: cannot statfs Bad	 statfs: No such file or directory
>>df: cannot statfs Using	 statfs: No such file or directory
>>
>>Why the complaint about 'cannot statfs'?

	I first encountered this problem after changing root's default
	shell from Bourne to C shell and subsequently rebooting. More
	seriously, I was no longer able to go into single-user mod. Changing
	back to Bourne didn't correct these problems. SCO said (months ago)
	that it was aware of the problems and they would be corrected in
	the next release. 

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).

	This solution was never suggested. I eventually, due to yet
	more serious problems reinstalled the system, leaving root's
	shell as Bourne. So far, so good.