> I'll check the permissions on /tmp, and I bet you're right > there.
There's a good chance your /tmp issue is not permissions, but a lack of /tmp being mounted. If your hostowner doesn't have a lib/profile or its lib/profile doesn't mount /tmp, then you won't be able to write anything to it. As has been mentioned, ramfs provides a file system that lives in memory and defaults to mounting it on /tmp. So running it will give you a /tmp even without fossil being there. BLS