Showing posts from February, 2010

run tiger (mac os x 10.4.1) in vmware or virtualbox

I found this article and found it useful, so write it down before I forget. The guide above is very simple , use p2p to download the vmware image , extract it and launch with vmware , then you will get a running tiger (mac os x 10.4.1). But I try it with vmware player 3.0, the performance is very bad. And also the network card is not working. Then after google around , I found that virtualbox had better support , so I try it with Virtualbox 3.1.4 Open source edition, the performance much more better and consider usable. Without much more modification , I can start browsing. One trick is you have to press F8 during boot menu and enter : platform=x86pc , otherwise the boot process will hang at acpi detection. Now have another problem is wanted to update it from version 10.4.1 to 10.4.11 seem no possible , because tiger support intel chip only start from 10.4.4 , so officially there is no updater which can u

Postfix restricting users to send mails to certain domains or their own domain

Follow the steps suggested in postfix wiki will be able to restrict a list of users for sending emails to limited domains. To add on on the wiki , we can replace the ip address with the user email address. For example : Instead of #/etc/postfix/restricted_clients #Add the list of IP addresses which cannot send emails outside local_only local_only change it to #/etc/postfix/restricted_clients local_only local_only The rest is the same , just try to restrict by user account instead of ip address. Zimbra is using postfix as it smtp daemon , so these two guides might help us to have better understanding : ---

Checking root LVM partition

If one day you are facing the problem that I am having now , the following information might be very useful. I am using Fedora 12 and I suspect the root partition some how corrupted or facing bad sector issue power failure. Here is my solution: 1. Boot from Fedora 12 installation CD or DVD , select rescue installed system option. 2. Skip the mount volume step. You can't check file system when a volume is mounted. 3. When you are at the shell prompt, issue the following command. It will activate the LVM volume. lvm vgchange --ignorelockingfailure -P -a y 4. If you don't know the volume name , you can use the following command to list all the LVM volume. lvm lvs 5. then you can issue the following command to check for bad sector. I assume you are using ext4 file system for root partition. fsck.ext4 -c /dev/VolGroup/logVol00 Hope this will help. ---