Mac OS X

ClamAV update – 0.97.2

There is a update for ClamAV available for download. The current version is 0.97.2. Upgrading is relatively easy and straight forward. All that needs to be done is remove the old version and install the new.

You can check the instructions on what to do here Upgrading ClamAV.

There is no need to reconfigure anything.

ClamAV after upgrading to Lion

Upgrading to Lion damages the ClamAV instillation documented here. Not only are the config files removed, but the virus database is also deleted along with the log files.

Because of the seriousness of the breakage, it is easier to simply install as though you never had ClamAV on your machine to begin with. Simply follow the instructions for Snow Leopard.

Update on OS X Lion

The release of OS X 10.7, or Lion as it will be more widely known is getting close. The blogosphere is already mentioning the release of the “Golden Master” to developers. This also means that more and more details on how and what we will be included or not. One revelation that cleared our earlier worries on a server release were cleared a month ago with the notion of the server becoming an add-on costing you $50,- which is still a lot cheaper then the earlier $499,- server version of OS X.

An important thing for myself came with the, propably, final EULA. Finally it is allowed to run OS X virtualized on your Mac Desktop without having to buy extra licenses. Quote from the 10.7 EULA:

to install, use and run up to two (2) additional copies or instances of the Apple Software within virtual operating system environments on each Mac Computer you own or control that is already running the Apple Software.

This will bring my efforts back to being legal, as I run virtual Mac’s on my iMac (here is the howto do it yourself). For testing and development. It’s great to try things out on a virtual machine before you might ruin your desktop or server and with Lion you can do it legally as well!

Update: It looks like the release date for Lion is going to be the 14th of July!

Mac OS X update 10.6.8 and Security Update 2011-004

I’ve just installed the updates on all my test machines running Snow Leopard 10.6.7 and Leopard 10.5.8 before running it on my production server. I did a couple of tests on the machines and could not see an immediate problem on Snow Leopard. Therefore I’m happy to inform you that the Mac OS X 10.6.8 update does not introduce any problem for our setup.

The Security Update 2011-004 however does change Leopard. I’ve noticed that it replace the postfix binaries and adds Apple’s idea of a security feature to the configuration file. To correct the binaries, go to your latest postfix source directory from which you installed it last and run

sudo make install

For the changed configuration please comment out or delete the following line from ‘/etc/postfix/main.cf‘:

inet_interfaces = localhost

Restart postfix (reloading config does not work) with:

sudo postfix stop

Postfix should restart automatically (if not run “sudo postfix start”).

This is expected to be the last update before Lion and I’ve got everything lined up to test the upgrade to Lion and a new install on that same platform. I hope to be able to tell you what the results will be as soon as possible.

Security Update 2011-002

I’ve just installed the updates on all my test and production machines running Snow Leopard and Leopard. I did a couple of tests on the machines and could not see an immediate problem. The Security Update 2011-002 does an uncomfortable change on Leopard. I’ve noticed that it adds Apple’s idea of a security feature to the Postfix configuration file. To correct it please comment out or delete the following line from ‘/etc/postfix/main.cf‘:

inet_interfaces = localhost

Restart postfix (reloading config does not work) with:

sudo postfix stop

Postfix should restart automatically (if not run “sudo postfix start”).

By the way the postfix binary could also have been updated on Leopard, you can check that by running:

sudo postconf -m

If it has been updated you won’t see MySQL being named in the list. Re-install postfix by going into your latest source directory you’ve used the last time and run

sudo make install
sudo postfix stop

« Previous PageNext Page »