wirespot
06-03-2007, 09:55
I've compiled several small tools. They depend only on /opt/lib/libc.so.0 and /opt/lib/ld-uClibc.so.0 (this means you have to install Oleg's uclibc package from his repository (http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/)).
wol is a wake-on-lan tool. You can use it to wake up computers on your LAN remotely. The source comes from here (http://ahh.sourceforge.net/wol/). Here's a nice WOL tutorial (http://xlife.zuavra.net/index.php/60/).
symlinks is a tool for symlink maintenance. It can clean up dead symlinks and convert absolute ones into relative. You can get the source package anywhere (http://www.filesearching.com/cgi-bin/s?q=symlinks*tar.gz).
ccache (http://ccache.samba.org) is a nifty little thing that helps you cache gcc output so you don't actually have to compile for real if you've done it before at least once. It's useful for those of you who are crazy enough to actually compile stuff directly on the 500gP CPU, repeatedly. To use it, you have to:
1) Put the ccache binary in a separate dir somewhere. In the same dir, make symlinks called gcc, g++ and cpp pointing to ccache.
2) Make sure the dir appears in the PATH before the one where the real gcc/g++/cpp are.
3) Export CCACHE_DIR=/opt/var/lib/ccache and create that dir, so the cache doesn't build up in /usr/local/root, which is located in flash.
wol is a wake-on-lan tool. You can use it to wake up computers on your LAN remotely. The source comes from here (http://ahh.sourceforge.net/wol/). Here's a nice WOL tutorial (http://xlife.zuavra.net/index.php/60/).
symlinks is a tool for symlink maintenance. It can clean up dead symlinks and convert absolute ones into relative. You can get the source package anywhere (http://www.filesearching.com/cgi-bin/s?q=symlinks*tar.gz).
ccache (http://ccache.samba.org) is a nifty little thing that helps you cache gcc output so you don't actually have to compile for real if you've done it before at least once. It's useful for those of you who are crazy enough to actually compile stuff directly on the 500gP CPU, repeatedly. To use it, you have to:
1) Put the ccache binary in a separate dir somewhere. In the same dir, make symlinks called gcc, g++ and cpp pointing to ccache.
2) Make sure the dir appears in the PATH before the one where the real gcc/g++/cpp are.
3) Export CCACHE_DIR=/opt/var/lib/ccache and create that dir, so the cache doesn't build up in /usr/local/root, which is located in flash.