9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Amit Singh <asingh@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Fwd: Reading from FS with inaccurate file sizes?
Date: Thu, 29 Mar 2007 11:19:50 +0000	[thread overview]
Message-ID: <1175166956.000323.155310@d57g2000hsg.googlegroups.com> (raw)
In-Reply-To: <1175051369.282439.191740@e65g2000hsc.googlegroups.com>

On Mar 29, 2:55 am, urie...@gmail.com (Uriel) wrote:
> The more I learn about FUSE, the more broken by design it seems. What
> is the point of userspace file systems if they can't even handle
> open() and close() in any meaningful way?
>
> Ah, the eternal re-invention of square wheels. How infinitely sad *sigh*

MacFUSE (http://code.google.com/p/macfuse) is an implementation of the
FUSE API (http://fuse.sourceforge.net) for Mac OS X. You seem to imply
I was explaining *the FUSE design*--no, I was talking about MacFUSE's
departure from the FUSE/Linux behavior because of the underlying OS
differences.

As for eternal reinvention, that's hardly limited to userspace file
systems, or even software. No, the ubiquity of reinvention doesn't
justify reinvention, but I don't really find it infinitely sad--some
instances of (re)invention just don't succeed the way others might.
What *is* sad (well, disappointing rather than sad) is when people are
ultra-quick in jumping to apparently confident conclusions, especially
when they might not have the necessary context. That's the sole reason
I posted here to begin with: to provide some context so those
interested can understand why something is the way it is, rather than
concluding based on presumptions and stereotypes.


  parent reply	other threads:[~2007-03-29 11:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1174603052.290868.102400@n76g2000hsh.googlegroups.com>
     [not found] ` <1174611197.118455.89640@e1g2000hsg.googlegroups.com>
     [not found]   ` <1174615620.140037.84140@o5g2000hsb.googlegroups.com>
     [not found]     ` <1174671190.917580.16150@l75g2000hse.googlegroups.com>
2007-03-23 20:41       ` [9fans] " CDeVilbiss
2007-03-23 22:39         ` Kris Maglione
2007-03-23 22:54           ` erik quanstrom
2007-03-25 17:59             ` Rolando Segura
2007-03-27 13:19         ` Russ Cox
2007-03-29  9:11         ` [9fans] " Amit Singh
2007-03-29  9:25           ` Charles Forsyth
2007-03-29  9:54           ` Uriel
2007-03-29  9:59             ` Francisco J Ballesteros
2007-03-29 10:14               ` Boris Maryshev
2007-03-29 11:02               ` Amit Singh
2007-03-29 13:36                 ` W B Hacker
2007-03-29 15:35                   ` Francisco J Ballesteros
2007-03-30 14:09                   ` David Leimbach
2007-03-31 18:41                     ` W B Hacker
2007-03-31 18:54                       ` erik quanstrom
2007-03-31 21:15                       ` C H Forsyth
2007-03-31 21:29                         ` W B Hacker
2007-04-01 10:33                           ` Charles Forsyth
2007-04-01 11:19                             ` erik quanstrom
2007-04-01 11:27                               ` Francisco J Ballesteros
2007-03-30  8:37               ` Amit Singh
2007-04-02  9:14               ` Amit Singh
2007-03-29 10:22           ` Amit Singh
2007-03-29 11:19           ` Amit Singh [this message]
2007-03-29 13:39             ` Colin DeVilbiss
2007-03-29 16:02             ` Amit Singh
2007-03-29  9:12         ` jas

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=1175166956.000323.155310@d57g2000hsg.googlegroups.com \
    --to=asingh@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).