My original message:
>Can anyone tell me what this means? I started getting this message in
>boot right after I upgraded to V3.2. (On a 3000/300) Fsck reports no
>problems.
I got a couple of me too's, but no helpful advice from the audience.
I called Digital Tech Support.
Using find / -i 1543, I found out that 1543 is the inode for /dev/null on my
machine. On the tech's advice, I rm'd /dev/null and created a new one, using
# mknod null c 2 2
and rebooted. The vmunix warning was gone upon reboot. Unfortunately
I don't know if the warning was a symptom of something greater or not.
If you choose to remove and rebuild /dev/null, don't forget to set the
permissions correctly. Write access is a good thing.
I would be happy to hear from others who have upgraded to V3.2, especially
on 3000/300's, so I can ferret out any other problems before I upgrade
the other machines here.
We now return you to your regularly scheduled inode.
-amy
__________________________________________________________________________
Amy Skowronek Solar Data Analysis Center
amy_at_aloha.gsfc.nasa.gov NASA/Goddard Space Flight Center
Received on Fri Mar 17 1995 - 17:46:00 NZDT