Comment 12 for bug 219914

That looks alright to me. Is there any way to find out whether the admin configured caching for / after installation, or whether that happened autoamtically during dapper -> hardy upgrade? In the latter case it would be better to disable it again in the postinst. But if that is tricky, I'm fine with uploading this current patch and err on the side of caution.