From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <774294.6588.qm@web83907.mail.sp1.yahoo.com>
Date: Thu, 21 Oct 2010 13:43:27 -0700
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <621112A569DAE948AD25CCDCF1C07533299A0B@dolly.ntdom.cupdx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [9fans] sheevaplug port available
Topicbox-Message-UUID: 6c29ecee-ead6-11e9-9d60-3106f5b1d025

> 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