From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fuse bashing
Date: Mon, 23 Jan 2006 09:46:17 -0800 [thread overview]
Message-ID: <3e1162e60601230946l2f82933al8c9504bde81f4c4a@mail.gmail.com> (raw)
In-Reply-To: <c9a7ecf2c4dd328f2ada08ffcba3c72e@vitanuova.com>
On 1/23/06, C H Forsyth <forsyth@vitanuova.com> wrote:
> > If you download a fuse distribution and look in
> > kernel/fuse_kernel.h you can see the messages.
>
> which i did, to do a limbo version.
> then i found that as i expected, they'd screwed up the exchange
> between kernel and user level so that the same component didn't
> work even between 64-bit and 32-bit environments on the same host,
> let alone between hosts. ``right everybody, change protocols!''
> then i found that they couldn't get the interrupt
> stuff working properly, so they ifdef'd it out and hacked it.
> then i found ...
>
> after a time, one gets tired of reading badly-worked out
> implementations of badly-thought out ideas.
>
> i don't care who was first.
> the question is: what is right?
>
> they should have done a little `research' first, before jumping in there,
> ``first one to the keyboard wins!''
>
>
DragonFlyBSD also is supposed to get VFS messaging.... but I think
that will be the basis of the entire VFS, it's hard to say where they
are now. I mentioned a few times on their list that they might want
to at least look at 9P... and that people may be interested in writing
DFly VFS->9P translation servers at some point.
Not sure how well-received it all was.
Dave
next prev parent reply other threads:[~2006-01-23 17:46 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 17:06 Russ Cox
2006-01-23 17:28 ` Ronald G Minnich
2006-01-23 17:44 ` David Leimbach
2006-01-23 18:07 ` Eric Van Hensbergen
2006-01-23 18:13 ` Bruce Ellis
2006-01-23 20:31 ` David Leimbach
2006-01-23 20:33 ` Ronald G Minnich
2006-01-23 23:28 ` Dan Cross
2006-01-23 23:53 ` David Leimbach
2006-01-24 0:07 ` Ronald G Minnich
2006-01-25 19:58 ` Enache Adrian
2006-01-25 20:30 ` Christoph Lohmann
2006-01-25 20:51 ` Ronald G Minnich
2006-01-25 21:09 ` Bruce Ellis
2006-01-25 20:50 ` Ronald G Minnich
2006-01-25 21:09 ` Enache Adrian
2006-01-24 0:12 ` John Barham
2006-01-25 5:29 ` Dave Eckhardt
2006-01-25 15:38 ` Ronald G Minnich
2006-01-25 21:31 ` Dave Eckhardt
2006-01-26 1:16 ` erik quanstrom
2006-01-25 5:30 ` Dave Eckhardt
2006-01-25 7:46 ` Jack Johnson
2006-01-25 8:11 ` Lyndon Nerenberg
2006-01-25 8:18 ` Lyndon Nerenberg
2006-01-25 9:46 ` Andriy G. Tereshchenko
2006-01-25 15:45 ` Ronald G Minnich
2006-01-23 17:51 ` C H Forsyth
2006-01-23 17:46 ` David Leimbach [this message]
2006-01-23 20:08 ` Ronald G Minnich
2006-01-23 18:46 ` Skip Tavakkolian
2006-01-24 2:22 ` Latchesar Ionkov
2006-01-24 8:37 ` Charles Forsyth
2006-01-24 9:41 ` Charles Forsyth
2006-01-24 10:04 ` Charles Forsyth
[not found] <000001c620ca$f86f1570$14aaa8c0@utelsystems.local>
2006-01-24 9:46 ` "Nils O. Selåsdal"
2006-01-24 20:10 quanstro
2006-01-24 21:37 ` Eric Van Hensbergen
2006-01-24 23:14 ` Charles Forsyth
2006-01-25 0:26 ` Latchesar Ionkov
2006-01-25 0:25 ` Latchesar Ionkov
2006-01-25 1:31 ` erik quanstrom
2006-01-25 1:40 ` Latchesar Ionkov
2006-01-25 1:42 ` Eric Van Hensbergen
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=3e1162e60601230946l2f82933al8c9504bde81f4c4a@mail.gmail.com \
--to=leimy2k@gmail.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).