9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fuse bashing
Date: Tue, 24 Jan 2006 09:41:22 +0000	[thread overview]
Message-ID: <a43208067b2cae40044ec774864cb8ad@terzarima.net> (raw)
In-Reply-To: <24e5acab674ffd8cc2ff5d460b6ad552@terzarima.net>

i probably ought to make clear that i have not been commenting on the
quality of the code of fuse--not at all--but rather various limitations of what it does,
and (to be fair to it even more) of the creaky system(s) beneath it.

as Tad used to say, though, about yet another attempt to
make anything interesting look as boring as everything else,
``come on [X], it's the 90s!!'' (and that was last century!)

at least to me, distribution is a big task of systems now, on
increasingly large scale and range.  space, the final frontier;
something like that.  it's hard enough as it is, but linux seems
currently no help whatsoever: each system is still stuck in its own
little box, fretting about those tlbs.  `distribution' occurs mainly
in discussing which new ones turned up this month.

i'm not surprised everything has fallen on the broad shoulders of apache.
no, that can't be right: that must be ajax.  interesting nomenclature:
apache, tomcat, jaguar, ..., all suggest potential for blood and pain to me.
or is it appealing to the warrior in the geek?



  reply	other threads:[~2006-01-24  9:41 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
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 [this message]
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=a43208067b2cae40044ec774864cb8ad@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).