Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!cfctech!teemc!ka3ovk!ki4pv!cdin-1!dsinc!lgnp1!phil
From: phil@lgnp1.LS.COM (Phil Eschallier)
Newsgroups: comp.unix.xenix
Subject: Re: /u doesn't get fsck'd or mounted during boot
Keywords: fsck /u 2.3.2 286
Message-ID: <3588@lgnp1.LS.COM>
Date: 28 Nov 89 13:40:23 GMT
References: <183@sherpa.uucp>
Reply-To: phil@lgnp1.UUCP (Phil Eschallier)
Organization: Lagniappe Systems [Doylestown PA]
Lines: 22

In article <183@sherpa.uucp> rac@sherpa.uucp (Roger Cornelius) writes:
>Since installing the 2.2.? -> 2.3.2 upgrade for the 286, my /u
>filesystem doesn't get fsck'd during the boot sequence.  This happens
>whether /u is dirty, or I specified "fsck=yes" in /etc/default/filesys
>according to the man page for mnt(C).  (the filesys(F) man page doesn't
>mention the "fsck" keyword, only "fsckflags".)
>If I understand correctly, when "fsck=yes" is specified the
>filesystem is fsck'd regardless of whether it's dirty or not.
>
	actually you need "rcfsck=yes" for cleaning during booting.  i have
	posted before that the "rcfsck=dirty" does not work for 2.3.2 ('286).
	sco has said nothing.

	if you you get any help from them, please let me know.  i have called
	sco and checked the sosco system -- there is no fix available yet.


	phil eschallier
	phil@ls.com

	btw -- please no flames for posting a "mail-type" response, this is
	to give sco another prompt.