From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] standalone cpu server wiki
Date: Thu, 22 Jan 2004 16:00:27 -0500 [thread overview]
Message-ID: <3390.192.11.226.116.1074805227.squirrel@www.infernopark.com> (raw)
In-Reply-To: <b2dde5dcaa34b4de39b7aaa3dc01027a@plan9.ucalgary.ca>
hi,
> 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.
that sounds really cool!!
may be it is the documentation that kills. for an experienced 9fan, it is a
good reference material. for someone new, there are many surprises. the
document is good as individual parts, but they dont seem to fit together. i
feel something is missing. if someone who is new tries to install using the
fossil method, i am sure he will be locked up somewhere.
thanks
dharani
next prev parent reply other threads:[~2004-01-22 21:00 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 [this message]
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=3390.192.11.226.116.1074805227.squirrel@www.infernopark.com \
--to=vdharani@infernopark.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).