From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] missing venti arenas
Date: Mon, 23 Feb 2004 15:47:05 +0100 [thread overview]
Message-ID: <4c5177acbd09f34a800fdba7351ca8bd@plan9.escet.urjc.es> (raw)
In-Reply-To: <00fd5e4a73a8c5b65a7e164f0ab3f3bd@mteege.de>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
I see. Somehow, IMHO, your sdC0 drive is not being
updated with the partitions contained in your plan9 partition.
Do you have recent 9load and boot(8)? Have you checked?
That would explain why you can use /dev/sdC0/data but not
anything inside /dev/sdC0/plan9
[-- Attachment #2: Type: message/rfc822, Size: 2782 bytes --]
From: Matthias Teege <matthias@mteege.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] missing venti arenas
Date: Mon, 23 Feb 2004 13:46:27 0000
Message-ID: <00fd5e4a73a8c5b65a7e164f0ab3f3bd@mteege.de>
On Mon Feb 23 11:24:30 GMT 2004, nemo@plan9.escet.urjc.es wrote:
> Don't you see `arenas0' when you do
> lc /dev/sdC1
>
> if that's the case there's a missing
> disk/prep -p /dev/sdC1/data >/dev/sdC1/ctl
> in your start script.
Hmm, /bin/termrc? It works if I use lib/profile but I think this
is the wrong place.
I try to build a standalone fossil/venti machine and there is
another problem. I setup venti='#S/sdC1/arenas0' in plan9.ini
and run venti/conf -w /dev/sdC1/arenas0 venti.conf but at
reboot I get:
fatal /boot/venti error can't init server ...
If I use data instead of arenas0 the server comes up but missing
/dev/sdC1/isect0. Snap -a can't connect to venti server.
Another hint?
Matthias
prev parent reply other threads:[~2004-02-23 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 10:18 Matthias Teege
2004-02-23 10:30 ` Fco.J.Ballesteros
2004-02-23 13:46 ` Matthias Teege
2004-02-23 14:47 ` Fco.J.Ballesteros [this message]
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=4c5177acbd09f34a800fdba7351ca8bd@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).