From: Matthias Teege <matthias-9fs@mteege.de>
To: kokamoto@hera.eonet.ne.jp, 9fans@9fans.net
Subject: Re: [9fans] standalone authserver on CF card
Date: Tue, 15 Apr 2008 14:32:15 +0200 [thread overview]
Message-ID: <408780322fc9ffc72412f8e87a56b633@mteege.de> (raw)
In-Reply-To: <f7e3936c2c90e8ab7c663fea1100ca0b@hera.eonet.ne.jp>
> Isn't Mathias going to build stand alone _authserver_, but cpu server?
Yes, I'm going to build a standalone authserver. I do not need it as a
CPU Server.
> If he wants to make authserver on CF card, I recommend him to use
> kfs for CF card. I'm using this from may 2004 without any problem.
That sounds good. I think it is not a major problem to make a copy of
the cf as backup but it would be nice to have not as much downtime.
Matthias
prev parent reply other threads:[~2008-04-15 12:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 15:22 Matthias Teege
2008-04-14 15:51 ` erik quanstrom
2008-04-14 16:01 ` john
2008-04-14 16:13 ` erik quanstrom
2008-04-14 16:06 ` Matthias Teege
2008-04-14 16:19 ` erik quanstrom
2008-04-14 16:40 ` John Stalker
2008-04-15 7:26 ` Matthias Teege
2008-04-15 11:31 ` kokamoto
2008-04-15 12:32 ` Matthias Teege [this message]
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=408780322fc9ffc72412f8e87a56b633@mteege.de \
--to=matthias-9fs@mteege.de \
--cc=9fans@9fans.net \
--cc=kokamoto@hera.eonet.ne.jp \
/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).