From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <39b3c067814d8d4554b3ddad69761d7f@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Sun, 16 Dec 2007 11:25:57 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
In-Reply-To: <538AA599-3025-4798-B4D8-0CFC69222E72@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 1a4eb934-ead3-11e9-9d60-3106f5b1d025

> I'm downloading the latest install disc right now, but how do I get a  
> fossil onto the system? mount -m/n/myfossl /dev/sdC0/fossil?

you likely want to use fossil/flcheck and fossil/conf to see if the
configuration looks sane first.

fossil typically reads its configuration when given the -f option.
you might not want that.  if things are goofy, it might be easier
to start up a fossil with no commands except one to start
a console.

	fossil -c  'srv -p rcons' 

and then enter configuration by hand and fossil's console.  
you can use fossil/conf to see what commands are normally used
to start fossil.

the only problem with this way of debugging things is you need
to remember that the kernel adds a few commands when it
boots:

	; g /boot/fossil /sys/src/9/boot/local.c|grep run
	/sys/src/9/boot/local.c:254: 	run("/boot/fossil", "-f", partition, "-c", "srv -A fboot", "-c", "srv -p fscons", 0);

if your fossil's really corrupt, perhaps you have a dma issue?

- erik