Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!killer!texbell!egsner!eric
From: eric@egsner.UUCP (Eric Schnoebelen)
Newsgroups: comp.unix.microport
Subject: Re: Another fix for the SYSV inode problem
Summary: what about System V/AT?
Message-ID: <153@egsner.UUCP>
Date: 30 Jan 89 04:35:35 GMT
References: <347@twwells.uucp>
Reply-To: eric@egsner.UUCP (Eric Schnoebelen)
Organization: Central Iowa (Model) Railroad, Lewisville, Tx.
Lines: 33

In article <347@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes:
-Two things happened today (really yesterday, but this fix took all
-night): first, my system crashed twice due to the inode bug, and
-second, I received Jim Valerio's stuff on fixing the inode problem for
-System V/386 Release 3. I'm running Microport's 3.0e; and here is
-what is going on.

[ long dissertation on chasing and fixing System V inode bug..  ]

-Then rebuild your kernel. All kernels made after this change will
-have the fix.
-
----
-Bill
-{ uunet!proxftl | novavax } !twwells!bill

My questions are:
	
	1.  Will this fix work on 2.2... ( I realize the addresses are
probably different, any hints what the new(old?) addresses are? )

	2. ( and more importantly.. )  Has a similar fix been found for
Microport System V/AT?  I am currently running fsck nightly from a
crontab to keep news from killing my system, and would like to stop.

	Thanks in advance
		Eric

-- 
Eric Schnoebelen
egsner!eric@texbell.uucp			...!texbell!egsner!eric
egs@u-word.dallas.tx.us				...!killer!u-word!egs
"All this science, I can't understand; It's just my job 5 days a week"