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] Re: venti+fossil problems on new install
Date: Fri, 22 Sep 2006 15:09:48 -0500	[thread overview]
Message-ID: <dfda9633b4b0232b84f8f20a20ae5ac2@quanstro.net> (raw)
In-Reply-To: <200609222048.ab36275@salmon.maths.tcd.ie>

On Fri Sep 22 14:49:38 CDT 2006, stalker@maths.tcd.ie wrote:
> > when you boot to freebsd, do you see "MBR" printed first thing?
> > if you don't then there the plan9 MBR is not installed.
> 
> Sorry, I should have been a bit more precise.  The mbr is in
> two parts.  There is the bootstrap code and then there is
> the partition table.  The bootstrap code isn't from plan9,

this means that you have not installed the plan 9 mbr; the fact that one
can't be written; it could mean that there's a bad parameter somewhere.

now that' you have your machine to this state, what you can do is
try to check to see if any look at all healthy.  the easiest is 9fat.
try
	9fat:
does this mount the partition?  if not you'll need to read prep(8)
and follow the directions for setting up a bootable partition there.

after that's sorted, you can mount venti by hand.
	venti=tcp!$youripaddress!17034	# 17034 = venti
	venti -c /dev/sdC0/arenas

and fossil by hand

	fossil -f /dev/sdC0/fossil -c 'srv -A fossil' -c 'srv -p fossilcons'

the fossilcons(8) man page can get you through some reconfiguration,
if required.

if that all works use "fshalt" to make sure that everything is cleanly
shutdown. then reboot.  if things still aren't working, perhaps your
boot loader needs some help  or there are other problems with, say,
your plan9.ini.

- erik


  reply	other threads:[~2006-09-22 20:09 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  6:50 John Stalker
2006-09-21  8:13 ` erik quanstrom
2006-09-21 18:19 ` Lyndon Nerenberg
2006-09-21 18:25   ` erik quanstrom
2006-09-21 18:51     ` jmk
2006-09-21 20:27       ` C H Forsyth
2006-09-21 20:47     ` Charles Forsyth
2006-09-21 20:56       ` jmk
2006-09-21 21:08         ` Charles Forsyth
2006-09-21 21:50           ` erik quanstrom
2006-09-21 22:00             ` Charles Forsyth
2006-09-21 22:16               ` erik quanstrom
2006-09-21 22:31                 ` Charles Forsyth
2006-09-21 22:31                 ` jmk
2006-09-21 23:22                   ` erik quanstrom
2006-09-21 23:28                     ` geoff
2006-09-21 23:47                       ` geoff
2006-09-22  0:05                         ` erik quanstrom
2006-09-22  0:24                           ` Russ Cox
2006-09-22  0:50                             ` erik quanstrom
2006-09-22  1:25                               ` jmk
2006-09-22  7:23                             ` John Stalker
2006-09-22 11:23                               ` erik quanstrom
2006-09-22 17:30                                 ` John Stalker
2006-09-22 17:45                                   ` erik quanstrom
2006-09-22 19:48                                     ` John Stalker
2006-09-22 20:09                                       ` erik quanstrom [this message]
2006-09-22 20:50                                         ` John Stalker
2006-09-22 21:06                                           ` erik quanstrom
2006-09-22  0:29                           ` jmk
2006-09-21 23:52                       ` erik quanstrom
2006-09-21 23:59                       ` erik quanstrom
2006-09-22  0:50                         ` geoff
2006-09-22 16:39                           ` erik quanstrom
2006-09-23  5:24 Zoran Kolic
2006-09-23  6:51 ` John Stalker
2006-09-23 10:34   ` erik quanstrom
2006-09-23 15:04     ` Russ Cox

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=dfda9633b4b0232b84f8f20a20ae5ac2@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).