EchoIRLP is an add-on to IRLP nodes which allows them to connect to the Echolink Network.  The install process for EchoIRLP makes some modifications to a couple of the core IRLP files.  This is fine, as long as EchoIRLP remains installed.  But if you remove EchoIRLP, or need to rebuild your node with a backup file which was created after EchoIRLP was installed, your node will not be functional until you either reverse the EchoIRLP install process, or reinstall EchoIRLP!  Installing EchoIRLP after rebuilding your node is fairly straight-forward.  But if you decide you want to revert back to a purely IRLP node, there are some steps that need to be taken.  By reversing the modifications made by the EchoIRLP installer, you can bring it back to it's original state and your node will begin working as it did before.  During the install of EchoIRLP, the following files get modified:

• /home/irlp/custom/rc.irlp

The follwoing code is added:

# source the EchoIRLP env
if [ -f /home/EchoIRLP/custom/echo_environment ] ; then
. /home/EchoIRLP/custom/echo_environment
fi
echo "Starting the Bridge..."
if ps -A | egrep 'tbd$' > /dev/null 2>&1; then
/etc/init.d/theBridge restart
else
/etc/init.d/theBridge start
fi 
if [ -x "$ECHO_SCRIPT/echo_enable" ] ; then
echo -n "Enabling connections to the EchoLink Node..."
/bin/su - -c "$ECHO_SCRIPT/echo_enable" repeater &>/dev/null
echo "done!"
fi

The relavent EchoIRLP code in your rc.irlp file may differ somewhat from the above but it should be apparent what code was added by your version of the EchoIRLP installer script.  Before you start modifying it, make a backup of your current rc.irlp file! Once you've done that, you can proceed with manually removing the EchoIRLP code within it.  Any stanzas referring to echo_environment, EchoIRLP, tbd, theBridge, echo_enable, $ECHO_SCRIPT, etc. were added by the EchoIRLP installer and need to be removed.  Since the installer probably made a backup of your rc.irlp file before it modified it, you should be able to find and compare that backed up version with the current one to see what was added.  Just keep in mind that some other add-ons may have also modified your rc.irlp file since you installed EchoIRLP so you shouldn't just copy that backed up version over the current one.  If you do, you risk breaking the other add-ons which may rely on the changes they made to it.  The backup file for my rc.irlp is named, "rc.irlp.bak" and is located within the /home/irlp/custom directory.  Yours is probably similar unless you changed or removed it.  By comparing the current version to the backup, it should be obvious which things were added by the EchoIRLP installer.  If you can't find a backed up version of your rc.irlp file for whatever reason, you'll just have to carefully go through and remove all traces of the EchoIRLP code.  Luckily it's fairly easy to spot and it's usually at or near the end of the file since the changes simply get appended to the end during the EchoIRLP install process.

• /home/irlp/custom/custom_decode

The following code is added:

# If you change the EchoIRLP prefix, you must also change "num" below to the number of digits in the prefix.
eval `echo $1 | awk -v num=1 '{
print "PRE="substr($1,1,num);
print "NODE="substr($1,(num)+1,length($1))}'`

# call echolink conferences using pound node method
if [ "$PRE" = "P" ]; then
"$ECHO_SCRIPT"/echo_call $NODE &
exit 1
fi

The relavent EchoIRLP code in your custom_decode file should be very similar to the above.  Again, before you start modifying it, make a backup of your current custom_decode file! Once you've done that, you can procede with manually removing the EchoIRLP code within it.  Any stanzas refereing to EchoIRLP, $ECHO_SCRIPT, echo_call, etc. need to be removed.  Again, the additions made by the EchoIRLP installer will probably be near the bottom of the file unless you have added lots of things to your custom_decode file since installing EchoIRLP.

• /home/irlp/custom/custom_on and /home/irlp/custom/custom_off

The following code is added:

# Added for EchoIRLP status page update
if [ -x "$ECHO_SCRIPT/echo_status" ] ; then
"$ECHO_SCRIPT/echo_status"
fi

Remove those lines from both of the custom_on and custom_off files.  That should be all that's necessary for removal of EchoIRLP modifications from a new IRLP re-install from an, "EchoIRLP tainted" node backup file!  As a last step, and just to make sure the system comes up as expected, a node reboot would be recommended at this point.  Take note of any irregularities during the boot-up process.  There should be none.

* PLEASE NOTE *

If yours is NOT a new re-install and you are just removing EchoIRLP from your node, there are a few other steps that also need to be taken in order to completely remove EchoIRLP.  First, stop the EchoIRLP software and remove it's config from the applicable boot-up runlevel(s).  To do this, issue the following commands as root:

1. /etc/init.d/tbd stop (or for Ubuntu do, "/etc/init.d/theBridge stop")
2. chkconfig --del tbd (or for Ubuntu do, "update-rc.d -f theBridge remove")

Now procede with these final steps for removing EchoIRLP from your node:

• The /home/irlp/custom/environment file will have an entry similar to the following, probably at or near the bottom of the file:

if [ -x /home/EchoIRLP/custom/echo_environment ] ; then

source /home/EchoIRLP/custom/echo_environment

fi

That code should be removed from the environment file as it will no longer be applicable.

• Completely remove the /home/EchoIRLP/ directory.

This is where most of the core EchoIRLP files live.  A new re-install of IRLP won't have this directory unless the EchoIRLP installer script has been run.  This directory in it's entirety can safely be removed.

• Remove the /etc/init.d/tbd or /etc/init.d/thebridge init script.

It will probably be named, "tbd" but for Ubuntu installs, it will be, "theBridge" or similar.  Basically you just want to locate the init script for theBridge and make sure it's been removed.

• Remove the tbd.conf and tbd.conf.sample files from the /usr/local/etc/ directory.

More than likely they will be the only files in there.  Simply delete them.

• Remove all tbd* files from the /usr/local/bin/ directory.

These are mostly symbolic links to the actual files that were located in the /home/EchoIRLP/tbd/ directory but since we removed the /home/EchoIRLP/ directory, these are now broken sym-links and should be removed.

• Remove any thebridge, tbdcnv files and directories from the /usr/src/ directory.

The EchoIRLP build process leaves some files in the /usr/src/ directory.  They should be purged.

That's it!  Those steps should yield you a pure IRLP Node.  Again, for completeness, perform a node reboot and verify proper boot-up and functionality.