Linux: recover from failure

When you need to recover from a Linux OS failure.
Locally:
10-boot-time-parameters-you-should-know-about-the-linux-kernel
reboot-or-halt-linux-system-in-emergency

Remotely:
IP Tables network magic SysRq function

IMS-Communicator and IPSec SAs

I've spent the last couple of days trying to implement the establishment of the IPSec Security Associations between the P-CSCF an the IMS-Communicator during the initial registration of the SIP UA.
The IMS-Communicator is a SIP softphone, based on the old version of the SIP-Communicator, in which I added some logic to support the IMS procedures for the UE.
Most of the work was done during my last year's academic project (in 2006) entitled "Protocols and Services in Convergent Networks", and it is used since then by people at PT-Inovação and IT, and some other folks around the globe, specially to test against the OpenIMSCore ...
But like I said in the beginning, I'm trying to support IPsec (for now only on Linux, using the ipsec-tools and setkey) so the AKAv1-MD5 authentication is finally fully implemented.
After I've done this, one of my next objectives regarding IMS-Communicator is to port all this IMS logic to the new and shinning SIP-Communicator.
Unfortunately, must probably I'll have to do it on my (little) spare time :-/



Update 1: Franz Edler manages a VM image for a kind of IMS-in-a-bottle, based on OpenIMSCore and IMS-Communicator.

linux: find string

> grep -r "string" "path"

this will list the lines where the "string" occurs in "path" (folders, files and lines inside files)