From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ramfs, lib9p
Date: Tue, 27 Apr 2004 17:32:53 +0100 [thread overview]
Message-ID: <99c511594f4894ba7d456adfac2c3862@vitanuova.com> (raw)
In-Reply-To: <408e8452$1@pfaff2.ethz.ch>
> /sys/src/lib9p/ramfs.c seems newer, because does use lib9p
newer, but not much used.
i'd not be surprised if the newer version was written just to test
lib9p and wasn't as fully featured as /sys/src/cmd/ramfs.c (for
instance, the lib9p version doesn't deal with exclusive-use files, as
far as i can see).
what are the "bad bugs" in the older one?
next prev parent reply other threads:[~2004-04-27 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 16:07 Martin Wyser
2004-04-27 16:18 ` Fco.J.Ballesteros
2004-04-27 16:32 ` rog [this message]
2004-04-27 18:18 ` Russ Cox
2004-04-28 9:33 ` Martin Wyser
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=99c511594f4894ba7d456adfac2c3862@vitanuova.com \
--to=rog@vitanuova.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).