> So, what exactly is the reason for not supporting MSGBUFSIZE, like we > do on all other platforms? I'll probably add code to support that soon. The snag is that the current location of the message buffer (at physical address 0) allow the messages to survive a reboot, if the machine's PROM permits that at all. -pk