> If we're in the business of expending cycles to guard against
> nil-probability risks, let's checksum our executables every time we
> start up, to make sure they're not overwritten.  Actually, we'd
better
> re-checksum program text memory every few seconds, in case RAM
dropped
> a bit since we looked last.  And let's follow every memcpy by a
memcmp
> to make sure that didn't drop a bit.  Heck, let's keep a CRC on
every

Why does it sound like you have problems with radiation eating away at
your live memory for satellite operations?


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to