search for: 145244

I know this isn't exactly a fun thing for you guys to do, but I cannot find a similar topic anywhere. Whenever I run a .exe based installer, I receive and error saying that the Windows Installation Service could not be accessed. This has been happening ever since I attempted to install Windows Installer 3.1. This error persists after a sudo apt-get remove wine* --purge command. I'm

We've got several CentOS 3.x systems running DNS that we keep updated automatically via YUM. Recently two of those systems (not all of them) when updating themselves to the latest versions of BIND, automatically replaced /etc/named.conf with a new one and saved the old one as /etc/named.conf.rpmsave. Which of course broke DNS for those servers. All servers got updated, but only two of

You get so used to yum upgrades going so smoothly but I learned the hard way to always make a thorough inspection after a yum update. I let yum go ahead and upgrade from 3.5 to 3.6. Afterwards I made some basic queries to httpd, postfix and bind named (probably a cached query). I even checked the /var/named/ directory and saw all my hosts files. So looked like another smooth ride, well until