From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti crashes at startup
Date: Wed, 3 Nov 2004 12:30:38 +0000 [thread overview]
Message-ID: <4da86f650eaafaa7cf0cf6fdab87a7b1@vitanuova.com> (raw)
In-Reply-To: <20041103104736.GA7923@SDF.LONESTAR.ORG>
> > have you done venti/conf -w ...?
> > otherwise venti won't know its configuration
>
> No. After do venti/conf -w venti.conf plan9 try to boot from
i hope you meant
venti/conf -w /dev/sdC0/arenas <venti.conf
have you also done a similar thing for fossil
fossil/conf -w /dev/sdC0/fossil
giving your (initial) fossil configuration on the standard input,
perhaps from an existing file.
otherwise, /boot will assume you've got a kfs installation, not fossil[+venti]
bootdisk seems to be set correctly, by default in pccpuf, so i don't think you
need any more plan9.ini variables. you do need the conf data in both fossil and venti.
mind you, if you've got the partition(s) but not the configuration(s),
it ought to have complained about
`no fossil config found ...' or `no venti config found ...'
next prev parent reply other threads:[~2004-11-03 12:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 8:28 Matthias Teege
2004-11-03 8:40 ` C H Forsyth
2004-11-03 8:58 ` Tiit Lankots
2004-11-03 9:35 ` Matthias Teege
[not found] ` <38c3fbecc91da8da2200ca416342ca86@vitanuova.com>
2004-11-03 9:27 ` Matthias Teege
2004-11-03 10:47 ` Heiko Dudzus
2004-11-03 12:30 ` C H Forsyth [this message]
2004-11-03 16:01 ` Matthias Teege
2004-11-03 16:41 ` Heiko Dudzus
2004-11-03 17:12 ` gdiaz
2004-11-06 15:01 ` Matthias Teege
2004-11-06 15:15 ` andrey mirtchovski
2004-11-06 17:01 ` Heiko Dudzus
2004-11-10 9:03 ` gdiaz
2004-11-10 10:36 ` Matthias Teege
2004-11-10 12:42 ` Steve Simon
2004-11-06 15:27 andrey mirtchovski
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=4da86f650eaafaa7cf0cf6fdab87a7b1@vitanuova.com \
--to=forsyth@vitanuova.com \
--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).