Yet ANOTHER null pointer dereference problem (in "cat")

[Rich A. Hammond]

> > The zero deference bug still exists in my Vr2 code. Does anyone think that
> > for Vr3 they'll turn on the loader option to disallow zero deferences?
> 
> Probably not until they run into the same situation that forced Berkeley
> to do something about it:  a machine which *cannot* support a readable
> location 0.  (Let there be no illusions that Berkeley fixed *NULL problems
> out of nobility or purity of heart; they fixed them because they had no
> choice if they wanted their code to run on the first Suns.)
> -- 
> 				Henry Spencer @ U of Toronto Zoology
> 				{allegra,ihnp4,linus,decvax}!utzoo!henry

The sad thing about all this is that I know of development groups in
AT&T Information Systems that have done the fixes, because they had
machines that didn't have readable location zero's.  However, getting
USG to buy back those modifications (and others for porting) never seemed
to work out.  After all, AT&T IS is a fully separated subsidiary.
Rich Hammond