The INfamous inode bug

Larry Jones scjones at thor.UUCP
Sun Jan 13 11:33:55 AEST 1991


In article <1991Jan12.025119.27665 at nuchat.sccsi.com>, steve at nuchat.sccsi.com (Steve Nuchia) writes:
> In article <1991Jan10.161022.3360 at ism.isc.com> support at bomber.ism.isc.com (Support Account) writes:
> >Code was added/fixed in V2.2 of Interactive Unix which resolved
> >all the instances of the inode problem Interactive could test
> >internally. Recently, another situation which generates the bug
> >was discovered, which was not tested for, and which is being fixed.
> 
> Wouldn't it have been easier to have proved the revised code the
> first time?  Simple little resource managers like that can be proved
> in a half hour or so, and then you don't embarass yourself.

Your have a valid point, but at least Interactive TRIED to fix the
problem.  AT&T has known about this bug for heaven-only-knows how
long and they've just finally gotten around to fixing it for R4.
And who knows if their fix is really right or not?!?
----
Larry Jones, SDRC, 2000 Eastman Dr., Milford, OH  45150-2789  513-576-2070
Domain: scjones at thor.UUCP  Path: uunet!sdrc!thor!scjones
My life needs a rewind/erase button. -- Calvin



More information about the Comp.unix.sysv386 mailing list