I guess it is my own fault for wanting to run on the bleedin' edge. So I go back to the install floppies and successfully reinstall debian, only this time the dang thing decides not prompt me if I'd rather run a static IP address or one from DHCP. You'd think that debian installers would consider that this might be a server machine, but nooooooo. Running the install in Expert mode proved futile (where the installer actually prompts for this), but for whatever reason expert mode would not install any kernel the installer chose. So how did I get around this blasted anomoly? Yank out the network wire during the dhcp detection phase. Woohoo, I get the prompts for a static IP Address.
So, because I'm running unstable, instead of running head-long into piling on the packages after install, I meticulously pick and install each package one-by-one until I finally get down to request tracker. Slowly I add apache. Then Perl. Then apache-perl. then libapache-mod-perl. At least "apt-get" includes all the little bonus packages that are needed to run these apps. Can't get away from running OpenBSD's SSH protocol, gottah run putty off my XP desktop. Last but not least, Request Tracker. gunzip the doc install file for debian, setup the mysql user for the tables and run the debian install init script.
Strange, Request tracker doesn't want to run from apache-perl. Directory not found keeps poppin up in the browser. libhtml-mason-perl wanted the normal apache anyhoo, so lets try that. Bingo! Request Tracker login. Images ain't loading, but all I need is a symlink and it'll be fixed.
Now only if this headache between XP's built-in active-directory dns-client would quit complaining about my ISC Bind9 + Dynamic updat'ng DHCPD v3, my stupid computer would find more hosts. Could the bug exist in my auto-proxy configuration script? Why not just disable the dang service in Windows XP you ask? I would if I wasn't upgrading the local lan here to Windows Server 2003 and Active Directory...