9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Compact Flash standalone AUTH server
Date: Fri, 11 Jun 2004 14:14:51 +0900	[thread overview]
Message-ID: <55c5bb256adab41a392c092536230a86@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <da9c1c20ee3d9a4068786df15caace9c@granite.cias.osakafu-u.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 625 bytes --]

It has passed about a month from we started to use CompactFlash
based kfs standalone AUTH server here.

The AUTH server is now counted 13650 process number, and has
not have no problem so far.   I'm now leaning to have convice it
is useful for this purpose.

If someone wants to make this kind of stanalone AUTH server,
I reccommend you to go.   To have standalone AUTH server is
good for anyone who wants to have multiple file servers, such
as Fossil+Venti and Ken's file server.   Furthermore, it has no
mechanical disks, no floppy, no CDROM, no disk, we have no
element to be broken accidentally.☺

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 2946 bytes --]

From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] Compact Flash standalone AUTH server
Date: Thu, 13 May 2004 11:43:22 +0900
Message-ID: <da9c1c20ee3d9a4068786df15caace9c@granite.cias.osakafu-u.ac.jp>

> Ok! Now, I started to use Compact Flash as our Auth server's
> kfs, which means standalone AUTH server.   

The machine is floppy- disk-less Celeron 366MHz Mitsubishi
Aprocot CX-200 (very old machine!) with 160MB SDRAM.
This machine has LAN card on its board (i82557).

The Compact Flash is Toshiba THNCF256MMA (256MB), and
an IDE interface card of "IR-ICF01S".   This machine does only
/bin/service.auth.

Kenji

  parent reply	other threads:[~2004-06-11  5:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-08  8:53 [9fans] disk/^(mbr format fdisk prep) lucio
2004-05-08  9:08 ` Charles Forsyth
2004-05-08  9:30   ` Kenji Okamoto
2004-05-08  9:37     ` Kenji Okamoto
2004-05-08  9:41     ` lucio
2004-05-08  9:50   ` lucio
2004-05-08 11:38     ` Charles Forsyth
2004-05-09  5:50     ` Geoff Collyer
2004-05-09  6:03       ` Geoff Collyer
2004-05-10  0:59         ` Kenji Okamoto
2004-05-10  5:10         ` lucio
2004-05-10  5:25           ` Kenji Okamoto
2004-05-10  5:30             ` lucio
2004-05-13  2:36             ` Kenji Okamoto
2004-05-13  2:42               ` boyd, rounin
2004-05-13  2:50                 ` Kenji Okamoto
2004-05-13  2:43               ` [9fans] Compact Flash standalone AUTH server Kenji Okamoto
2004-05-17  8:20                 ` Kenji Okamoto
2004-05-17  8:25                   ` Kenji Okamoto
2004-05-20  1:41                   ` Kenji Okamoto
2004-05-21  2:04                     ` Kenji Okamoto
2004-05-21  3:05                       ` Kenji Okamoto
2004-06-11  5:14                 ` Kenji Okamoto [this message]
2004-06-11  5:17                   ` Kenji Okamoto
2004-05-10  5:08       ` [9fans] disk/^(mbr format fdisk prep) lucio
2004-05-08  9:56 ` lucio
2004-05-10  9:09   ` Fco.J.Ballesteros
2004-05-10  9:17     ` lucio
2004-05-08  9:58 ` Richard Miller
2004-05-08 10:02   ` lucio
2004-05-08 10:47     ` Richard Miller
2004-05-08 11:13       ` lucio

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=55c5bb256adab41a392c092536230a86@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).