From: G. David Butler gdb@dbSystems.com
Subject: [9fans] Plan 9 file server w/ indexed dirs and logging
Date: Mon, 20 Oct 1997 17:00:09 -0500 [thread overview]
Message-ID: <19971020220009.mYAUYZuhR0e_3P-IyQDGT6VzKuSSCGNnQ13GwB_mXlQ@z> (raw)
I wrote last time.
>
>so if you have a spare PC to use as a Plan9 file server
>and want to have a go at it... This fileserver has indexed
>directories and logging. [It also supports mirrored disks,
>sort of. It works but needs more attention.] The logging comes
>in two versions (compile flag) of full discrete transactions
>and fileserver protection. The one below only provides
>fileserver protection. The other one guarantees the results
>of each successful 9P message. Both are fully compatible with
>the current Plan9 9P protocol.
>
>Get ftp://ftp.dbSystems.com/pub/PLAN9/9pcfs.xor
>
[snip]
Ok, this new one is even better! I now use 16 ccbs on the 1542
and increased the number of log writting processes to 4. Boy
does everything scream now...
David Butler
gdb@dbSystems.com
next reply other threads:[~1997-10-20 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-20 22:00 G.David [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-17 21:09 G.David
1997-10-15 23:41 G.David
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=19971020220009.mYAUYZuhR0e_3P-IyQDGT6VzKuSSCGNnQ13GwB_mXlQ@z \
--to=9fans@9fans.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).