From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4BCD85B5.1060404@tecmav.com>
Date: Tue, 20 Apr 2010 12:45:09 +0200
From: Adriano Verardo <a.verardo@tecmav.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.8.1.21) Gecko/20090430 SeaMonkey/1.1.16
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [9fans] Fossil robustness
Topicbox-Message-UUID: 09be302e-ead6-11e9-9d60-3106f5b1d025

Hi all.

I'm building an industrial  application  hosted by several independent
cpu server,
each of them booted from a CFlash on sdD0.

The application doesn't write on sdD0 and there are no redirection on
local files
in the cpurc scripts.

In this particular situation fossil should be actually used read only so
allowing
to use write protected CF and/or to suddenly power off the system without
damaging the file system.

Instead, fossil writes on sdD0 (doesn't boot fom a write protected CF)
and the
power loss destroy the file system more than fifty-fifty.

Unfortunately I cannot guarantee stable/correct operating conditions.

Any suggestion ?

Thanks in advance

adriano