Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!datran2!smb
From: smb@datran2.uunet (Steven M. Boker)
Newsgroups: comp.sys.next
Subject: Kernal-Corruption-Bug-Fix bug
Keywords: kernal bug next mailing
Message-ID: <422@datran2.uunet>
Date: 18 Jan 90 19:35:18 GMT
Organization: Data Transforms, Denver, CO
Lines: 25

------------WARNING-------------

There is a problem with the documentation sent out to NeXT developers
this week.  The instruction sheet for preventing the kernal corruption
bug lists two methods for preventing the bug.  The first method, using
chmod from the shell doesn't work.  My experience:  After su-ing to
root I used chmod to change the permissions on the /sdmach file such
that execution permission was denied.  (chmod a-x /sdmach).  A quich
check of the permissions with ls -l revealed that the change had indeed
taken effect.  However, after a cold boot the Directory Browser still
showed the sdmach file as executable!  I have never seen this discrepancy
between the Directory Browser and the Shell after a cold boot.

Fool that I am, I decided to give it a try.  One hand poised on the
power switch, I double clicked /sdmach from the Directory Browser.
Astonished, I watched sdmach begin to launch.  Everything seems fine
after my fingers did the walking on my powerbar.  Anyone have
suggestions about what's going on or how to test if my kernal is
corrupted?


-- 
   Steve Boker                                   
   smb@datran2.uunet.uu.net
   Black holes are where God divides by zero.... I have my own methods.