From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] anyone worked on 9pm
Date: Wed, 28 May 2003 13:07:45 -0400 [thread overview]
Message-ID: <702a7aecafd56ff57bb2e29e24329e66@plan9.bell-labs.com> (raw)
In-Reply-To: <17b96adfbd42df33ded4d0165f759d6b@snellwilcox.com>
A few of us have worked on 9pm. The basic problem
is that we don't really know what form it should take.
I have enough of a build environment that I can compile
Venti without any changes, but I don't really like it.
The resulting programs seem too insulated from the
"host" OS as far as I'm concerned.
Separately, I've been trying to package up the Plan 9
libraries in a more host-friendly format. The libraries
I've posted before -- libutf, libfmt, libbio, libregexp9 --
are all part of this effort, and I've got libthread running
on FreeBSD and Linux.
Russ
next prev parent reply other threads:[~2003-05-28 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 13:53 steve.simon
2003-05-28 17:07 ` Russ Cox [this message]
2003-05-29 5:33 ` Gene Garbutt
2003-06-08 16:24 ` Russ Cox
2003-05-28 17:39 ` William K. Josephson
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=702a7aecafd56ff57bb2e29e24329e66@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).