From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] standalone cpu server wiki
Date: Wed, 21 Jan 2004 22:58:22 -0700 [thread overview]
Message-ID: <b2dde5dcaa34b4de39b7aaa3dc01027a@plan9.ucalgary.ca> (raw)
In-Reply-To: <32910.138.89.146.98.1074760052.squirrel@www.infernopark.com>
> - if fossil crashes, you could clean it up and restart it with a previous
> snapshot from venti but to do that you have to have a small kfs filesystem
> anyway. (am i right? this is something that i guessed after much pain. i
> was wondering how 9fans recover the machine from a fossil crash)
you can use a live cd with Plan 9 to boot and reinitialize fossil
too, or anything that will get you to sources.cs where you can run
the binaries...
the fact that you need another fs to boot from in order to fix fossil
has been complained about before, but nobody has mentioned yet
that (fossil or no fossil) Plan 9 gives you a much more exciting (and
novel!) way of fixing things -- next time your fossil crashes send me
an email and I'll give you an account on ucalgary.ca where you can
boot your system as a terminal and fix your fossil in about 15
minutes flat. in fact, you can fix pretty much anything from
everywhere as long as you have a decent 9pcdisk kernel to start with.
no mucking around with floppies and installations, no recovery disks.
just a 9fat partition or a floppy that lets you hop on to any Plan 9
installation in the world (to which you have permissions to
authenticate, of course) and you have the full power of a Plan 9
machine at your disposal.
andrey
next prev parent reply other threads:[~2004-01-22 5:58 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 [this message]
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
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=b2dde5dcaa34b4de39b7aaa3dc01027a@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).