Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.unix.microport
Subject: Re: Another fix for the SYSV inode problem
Message-ID: <366@twwells.uucp>
Date: 1 Feb 89 18:41:01 GMT
References: <347@twwells.uucp> <153@egsner.UUCP>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 34
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <153@egsner.UUCP> eric@egsner.UUCP (Eric Schnoebelen) writes:
: In article <347@twwells.uucp> bill@twwells.UUCP (T. William Wells) writes:
: -System V/386 Release 3. I'm running Microport's 3.0e; and here is
: -what is going on.
: -...
: -Then rebuild your kernel. All kernels made after this change will
: -have the fix.
:
: 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? )

It might, but someone will have to go look.

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

I dunno. Someone with a disassembler should have no problem creating
such a fix, if it can be done at all.  If you want to do it, go get
_The Design of the UNIX Operating System_, (Maurice J. Bach,
Prentice-Hall, ISBN 0-13-201799-7), it gives rather detailed (though
not C code!) descriptions of what goes on in the UNIX kernel. It is
based on Release 2, though it is still a useful guide for Release 3.
 For example, there is pseudocode for ialloc (aka s5ialloc) on page
78, something really useful when trying to understand the assembly.

BTW, running fsck doesn't prevent the bug. Twice now I've had the
inode bug hit me within minutes of fsck'ing my system.

---
Bill
{ uunet!proxftl | novavax } !twwells!bill