From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hardware for Plan 9 file server?
Date: Thu, 28 Sep 2000 09:37:08 +0100 [thread overview]
Message-ID: <20000928084019.0678619A30@mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
i've sent kenji the translated program. it would be cleaner with 9p.h but i haven't
had a chance to do it yet. lib9p would replace a significant chunk of the program,
since it serves a handful of files
ctl management
lock blocks updates to allow external programs to mess with state
msgid looks up lines in history file given msgid
post accepts one or more articles for posting, separated by 0 length writes
[-- Attachment #2: Type: message/rfc822, Size: 1573 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Hardware for Plan 9 file server?
Date: Wed, 27 Sep 2000 21:04:15 -0400
Message-ID: <20000928010423.C81A819A26@mail>
I don't understand why you needed lib9p for it.
Presumably it would translate more directly using
whatever the Alef program used, probably just the
convS2M and convM2S routines.
Russ
next reply other threads:[~2000-09-28 8:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-28 8:37 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-28 9:42 okamoto
2000-09-28 1:30 okamoto
2000-09-28 1:04 Russ Cox
2000-09-28 1:01 okamoto
2000-09-27 20:08 Anthony Sorace
[not found] <anothy@eden.rutgers.edu>
2000-09-27 18:13 ` Anthony Sorace
2000-09-27 18:27 ` Scott Schwartz
2000-09-28 10:19 ` Tim Haynes
2000-09-27 15:42 Anthony Sorace
2000-09-27 17:02 ` Tim Haynes
2000-09-27 15:16 jmk
2000-09-27 18:04 ` Douglas A. Gwyn
2000-09-27 12:58 Ish Rattan
2000-09-27 13:52 ` Jon Snader
2000-09-27 14:03 ` Nigel Roles
2000-09-27 15:17 ` Tim Haynes
2000-09-27 15:52 ` Nigel Roles
2000-09-28 10:18 ` Douglas A. Gwyn
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=20000928084019.0678619A30@mail \
--to=forsyth@caldo.demon.co.uk \
--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).