From: Andrew <afrayedknot@thefrayedknot.armory.com>
To: 9fans@cse.psu.edu
Subject: [9fans] fossil
Date: Mon, 14 Apr 2003 22:26:54 -0700 [thread overview]
Message-ID: <20030415052654.GA4410@thefrayedknot.armory.com> (raw)
This has been nagging at me for a while. Currently my plan9 system has
the standard old fs server, and auth server and some terms. Everything
boots from floppies or small hard drives, then mounts its root from the
file server. I want to update to fossil, and do away with the old file
server. Is there an [easy] way to make the fossil server boot up on its
own in the same way fs does? Im just not really clear on how it all
fits together.
next reply other threads:[~2003-04-15 5:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-15 5:26 Andrew [this message]
2003-04-15 15:12 ` Russ Cox
2003-04-15 21:00 ` Andrew
2004-03-20 2:27 David Presotto
2004-06-12 3:12 Russ Cox
2005-01-03 18:37 Bruce Ellis
2005-01-03 18:51 ` Russ Cox
2005-01-04 17:42 ` Russ Cox
2009-06-04 9:29 Charles Forsyth
2009-06-04 19:25 ` erik quanstrom
2024-05-17 16:16 [9fans] Interoperating between 9legacy and 9front Noam Preil
2024-05-18 19:08 ` [9fans] fossil Richard Miller
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=20030415052654.GA4410@thefrayedknot.armory.com \
--to=afrayedknot@thefrayedknot.armory.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).