From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: corey@bitworthy.net,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] standalone terminal w/ kfs no fossil
Date: Sun, 16 May 2010 03:19:30 -0100 [thread overview]
Message-ID: <AANLkTinBBf-YOMTRZqtuzMxQOsKpikqj5JNqJbZ-jIg5@mail.gmail.com> (raw)
In-Reply-To: <201005152054.09503.corey@bitworthy.net>
I use kfs on a standalone Plan 9 box.
The computer has a 100 MHz CPU with
some 48 MB RAM. fossil hogs all
processing power. kfs on the other hand
is wonderfully stable and low maintenance.
Plus, the code is beautiful.
The install procedure from CD involved
manually going through the install
commands. The install scripts are easy
to read and figure out.
Just make your partition and use the
install scripts as a guide for copying
stuff over from the CD onto kfs disk.
That's all to it.
Best,
ak
On 5/16/10, Corey <corey@bitworthy.net> wrote:
>
> I'm thinking about going through another installation, and I'm wondering
> whether there's usefulness in undertaking a standalone terminal install
> using only kfs rather than fossil? And if so, how is this currently done?
>
> As far as I can tell, I'd want to use Erik's 9atom iso - which seems to
> support Ken's fs (http://www.quanstro.net/plan9/9atom/index.html)? -
> but the current install scripts only prompt for fossil or fossil+venti.
>
>
>
next prev parent reply other threads:[~2010-05-16 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 3:54 Corey
2010-05-16 4:19 ` Akshat Kumar [this message]
2010-05-16 8:04 ` Richard Miller
2010-05-16 13:38 ` erik quanstrom
2010-05-16 14:04 ` David Leimbach
2010-05-16 14:05 ` Ethan Grammatikidis
2010-05-16 14:19 ` erik quanstrom
2010-05-17 1:58 ` Akshat Kumar
2010-05-16 4:23 ` erik quanstrom
2010-05-16 5:07 ` Corey
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=AANLkTinBBf-YOMTRZqtuzMxQOsKpikqj5JNqJbZ-jIg5@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
--cc=corey@bitworthy.net \
/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).