Every time Firefox releases a major upgrade, we love it because it comes with lots of cool features. At the mean time, we hate it because lots of our favorite add-ons are not working with the new Firefox. Sometimes, the owners of the add-ons might be too busy, and it might take a while to release a compatible version. That’s why I put some of my favorite add-ons here. They are 100% compatible with the new Firefox, and I only modified the source codes that by-pass the version compatibly check.
In the other words, the add-on will work the way it was in the old version, and you will receive an upgrade if the owner releases a newer version.
So far I have made the following add-ons available in the latest version of Firefox:
If you need any add-on, please post in the comment below. I will try to make it available here.
Enjoy your new Firefox!
Many people are confused between the compression and deduplication because they are so similar. Both of them are designed to reduce the size of the data being stored in the storage. Let me explain the difference between them in simple English.
1. This is how your data looks like originally (Assuming only one unique file):
2. This is how your data look like after being stored in a ZFS pool with compression enabled.
3. This is how your data look like after being stored in a ZFS pool with deduplication enabled.
4. Let say we are storing three identical files, i.e.,
5. ZFS: Compression Only
6. ZFS: Deduplication Only
7. ZFS: Compression + Deduplication
Of course, enabling both compression and deduplication will save lots of free space. However, it comes with a very high price tag. If you like to enable deduplication, you need to make sure that you have at least 2GB of memory per 1TB of storage. For example, if your ZFS pool is 10TB, you need to have 20GB of memory installed in your system. Otherwise, you will experience a huge performance hit.
Hope this article helps you to understand the difference between compression and deduplication.
Today, I sent a message to a company through their contact page on their website. It is a standard contact page, i.e., you need to fill in your contact information and the details of your request, and they will follow up with you later. An hour later, I received a reply from them, saying that they would like more information from me. Therefore, I reply to their email. Few seconds later, I got the following:
Delivery has failed to these recipients or distribution lists:
Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.
Sent by Microsoft Exchange Server 2007
Diagnostic information for administrators:
(Another 100 lines of error messages)
Initially, I thought I made a mistake when typing the email address. Therefore, I redid it and verified every single letter in the email address. Unfortunately, I got the same message again. After trying it for 5 times, I gave up, and this company loses a sale.
There are few things we’ve learned here. First, never display very technical error messages to the customers. They are very boring for non-engineers. Second, don’t assume that every customer is patient. Not every one is willing to re-send the same email for 5 times. Third, it takes many years to build a city but it only takes few hours to destroy it. With today’s technology, it is too easy to spread out the bad words.
I think this is not a right way to run a custom request management system (or ticket system). It should never yell to the customer. Instead, it should let the stuffs to evaluate the customer’s reply rather than letting the Microsoft Exchange Server to do it.
I don’t recommend using Microsoft Exchange for your business. It just hurts your business.
After I updated the Apache to 2.2.22 for my FreeBSD box today, I got a problem:
[warn] (2)No such file or directory: Failed to enable the 'dataready' Accept Filter
If you search for Failed to enable the ‘dataready’ Accept Filter on Google, you probably will find a lot of posts about this solution, like the following:
Or include the following in the boot loader (/boot/loader.conf):
However, even you already done these two things, this problem still exists.
kldload: can't load accf_http: File exists
Why? That’s because the problem is not coming from accf_http. Instead, the problem is the missing dataready filter, which is accf_data. To solve this problem, simply do the following. First, update the /boot/loader.conf and add the following into the file:
Of course, any changes to the boot loader requires a reboot. If you don’t want to reboot the machine, simple load the module manually and restart the Apache, i.e.,
That’s it! Apache will stop complaining the dataready filter and will work happily.