9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Corrupted file entry on QEMU - how to recover?
Date: Sun, 16 Dec 2007 11:25:57 -0500	[thread overview]
Message-ID: <39b3c067814d8d4554b3ddad69761d7f@quanstro.net> (raw)
In-Reply-To: <538AA599-3025-4798-B4D8-0CFC69222E72@mac.com>

> 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


  reply	other threads:[~2007-12-16 16:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16  2:48 Pietro Gagliardi
2007-12-16  9:10 ` Skip Tavakkolian
2007-12-16 14:22   ` Pietro Gagliardi
2007-12-16 16:25     ` erik quanstrom [this message]
2007-12-16 16:54       ` Pietro Gagliardi
2007-12-16 17:25         ` erik quanstrom
2007-12-16 23:57           ` Pietro Gagliardi
2007-12-17  1:34           ` Pietro Gagliardi
2007-12-17  1:36             ` Pietro Gagliardi
2007-12-17  1:42               ` erik quanstrom
2007-12-17  1:57                 ` Pietro Gagliardi
2007-12-17 19:24                   ` john
2007-12-17 21:10                     ` Pietro Gagliardi
2007-12-18 18:13                       ` erik quanstrom
2007-12-18 18:19                         ` erik quanstrom
2007-12-19 21:02                 ` Pietro Gagliardi
2007-12-20  1:15                   ` Juan M. Mendez
2007-12-20  1:52                     ` Pietro Gagliardi
2007-12-20  2:02                       ` erik quanstrom
2007-12-20  2:10                         ` Pietro Gagliardi
2007-12-20 19:58                           ` Pietro Gagliardi
2007-12-22 22:29                             ` Pietro Gagliardi
2007-12-23  2:35                               ` Bakul Shah
2007-12-27 16:23                               ` Russ Cox
2007-12-29 16:33                                 ` Pietro Gagliardi
2007-12-29 19:06                                   ` Pietro Gagliardi
2008-01-01  1:37                                 ` Pietro Gagliardi
2008-01-11 20:01                                   ` Pietro Gagliardi
2008-01-11 20:47                                     ` Pietro Gagliardi
2008-01-11 22:29                                       ` Pietro Gagliardi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39b3c067814d8d4554b3ddad69761d7f@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).