EzRPM takes one or more RPM packages as parameters and installs them handling all dependencies by installing additional RPMs as necessary. These RPMs are located by scanning all directories in the original list of RPMs to be installed, and by scanning the paths in the RPMPATH environment variable.
muser lists processes which have a given directory (or cwd if not specified) as a parent of their current working directory (thus making it impossible to unmount that directory if it is a mount point). This script has overlapping functionality with the fuser program from the psmisc package, but has the advantage that it works on SMB mounts. Additionally, it provides a color, formatted listing of process IDs, executable names, current working directories, and the command lines used to run the programs. It works with varying-sized /proc/*/cwd fields.
netview lets you browse, mount, and unmount SMB shares using any browser, but especially Konqueror or any browser which is also a file manager. It provides actual mounting of shares so you can edit files on them. It addes mounted shares to /etc/fstab automatically so they will be remounted, and manages storage of passwords in a $HOME/.smbpasswd file for later auto-mounting of shares.
LICQ supporting v8 protocol
The LICQ in CVS is working on supporting the v8 protocol. It worked "out of the box" for me at least as well as GAIM did. Though chat requests still use the older protocol, GAIM (and I presume ickle) don't even support it at all.
So, thanks for the informative article, however, for a library like this to be fully useful, it needs to support all the protocol features (such as direct chat). I'm hoping that will happen, as I would enjoy writing my own ICQ client, but only if it could have chat, file transfer, etc., as well as instant messages.
Regarding other's calls to switch to a non-proprietary protocol, I'm all for that if:
1. The protocol has all the functionality of the proprietary ones. So far, I haven't seen a jabber client that could do chat, file transfer, etc. Maybe it's not the protocol's fault, but I don't have time to mess with it.
2. Servers need to be widely available and able to handle the load of a large number of users.
3. Transitioning tools for the other clients need to be available for many platforms, including ICQ on Windows.
From the /herumi subdir, go to [products] and *then* look for gogo*.tgz.