RPM like Russian doll

You know, the one in Sesame Street where a small doll contains a smaller doll, and so on, ad nauseam.

I'm talking about the dependencies chain in RPM installation, of course. For example, as I was about to upgrade Webmin, Maui complained that the package depended on several Perl modules, which in turn, needed some other Perl modules. It was doubly harder because I still couldn't make the problem of Maui not resolving FQDNs properly, so I had to rely on the IP addresses of the RPM repositories in doing wgets -- a tedious process, I tell you.

But, I finally made it work: upgraded Webmin to version 1.5, and added SSL functionality for additional security; but only for almost a day of scrounging the web for the correct and compatible RPMs (Net::SSLeay, Mon::client and Convert::BER, just to name a few).

I also had to rebuild the index file for the SARG to reflect the previous month. It still does not make weekly and monthly reports, though. I probably forgot to add cron entries for them.

There's still no reply from my predecessor regarding his documentation for the TACACS+ and NAS configuration. Meanwhile, the modem pool is just laying there, unused.

Bridging would not work for the network reconfiguration. We have to resort to a file server sitting between the two subnets. This server will also have Jabber for messaging.

I've installed FC2 on the staging server, which will be promoted to either the proxy or the LDAP server to be connected to the W2K3 domain controller for one-time login and authentication.

Whew! Lots of work ahead.