9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Andrew <afrayedknot@thefrayedknot.armory.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more silly fossil questions
Date: Tue, 24 Jun 2003 10:26:49 -0700	[thread overview]
Message-ID: <20030624172649.GA9492@thefrayedknot.armory.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306241053360.18127-100000@fbsd.cpsc.ucalgary.ca>


fwiw I currently do the standalone fossil setup. It seems to work
reasonably well except you are kinda screwed if you mess up the boot
scripts or something. I had to reload from a seperate system with kfs. The
system does cpu/fossil, i have a seperate auth server.

Basically what happens is the files you need to boot up get on the network
and run fossil/venti all get compiled into the kernel, which unfortunatly
makes it fairly big and bulky, and you get to recompile everytime
something gets updated or you want to change some of the initial settings.

I had to go this route because i lacked the drives/space at the time
to do anything else. I will probably swap over to booting onto kfs then
exporting fossil now that i have some extra drives, hopefully things
will be easier that way.



  reply	other threads:[~2003-06-24 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-24 17:09 andrey mirtchovski
2003-06-24 17:26 ` Andrew [this message]
2003-06-24 18:08 ` plan9
2003-06-24 18:19   ` Dan Cross
2003-06-25  0:08     ` Russ Cox
2003-06-25  1:34       ` Dan Cross
2003-06-25  0:49     ` bs
2003-06-25  1:42       ` Dan Cross
2003-06-26 10:58         ` Martin C.Atkins
2003-06-26 13:45           ` Dan Cross
2003-06-26 14:00             ` boyd, rounin
2003-06-25  7:59   ` Fco.J.Ballesteros, nemo
2003-06-25  8:06 ` Fco.J.Ballesteros, nemo

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=20030624172649.GA9492@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).