From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] standalone cpu server wiki
Date: Thu, 22 Jan 2004 14:13:01 -0500 [thread overview]
Message-ID: <6734968bbcac801729f716dd35f918bd@plan9.bell-labs.com> (raw)
In-Reply-To: <9585.192.11.226.116.1074806350.squirrel@www.infernopark.com>
> > You don't need to set up venti. What you set with fossil only is the
> > same as you get with kfs only; a not backed up file system. I don't
> if fossil crashes, is there a way to recover?
yes, reboot the system and then run flchk to clean up. If you've lost
some part of the fs that you need for rebooting, you're hosed, same
as for kfs.
>
> > I also dislike the fact that 'snap -a' makes fossil totally dependent
> > on venti. We used to have our main fossil and venti as separate
> > machines but this forced us to put them both on one. Rsc, jmk, and I
> cant venti be in another machine? is it necessary that venti needs to run
> on the same machine as fossil? i thought it should be fine.
>
You can run them on different machines. However, now you depend on
2 systems being up in order to boot.
next prev parent reply other threads:[~2004-01-22 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 1:53 James Horey
2004-01-22 2:20 ` mirtchov
2004-01-22 8:27 ` vdharani
2004-01-22 5:58 ` mirtchov
2004-01-22 21:00 ` vdharani
2004-01-23 5:00 ` Jack Johnson
2004-01-23 5:33 ` mirtchov
2004-01-23 11:52 ` a
2004-01-22 16:27 ` David Presotto
2004-01-22 21:19 ` vdharani
2004-01-22 19:13 ` David Presotto [this message]
2004-01-22 19:14 ` David Presotto
2004-01-23 2:02 ` James Horey
2004-01-23 2:27 ` okamoto
2004-01-23 5:17 ` Jack Johnson
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=6734968bbcac801729f716dd35f918bd@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).