From: W B Hacker <wbh@conducive.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Fwd: Reading from FS with inaccurate file sizes?
Date: Thu, 29 Mar 2007 21:36:45 +0800 [thread overview]
Message-ID: <460BC0ED.7070101@conducive.org> (raw)
In-Reply-To: <1175165973.125111.238770@o5g2000hsb.googlegroups.com>
Amit Singh wrote:
> On Mar 29, 3:15 am, boris.marys...@gmail.com (Boris Maryshev) wrote:
>> Unix or not, it would be much appreciated if different fuse
>> implementations were compatible.
>
> Certainly. However:
>
> FUSE was originally designed/implemented for Linux. Unlike Mac OS X,
> which has a FreeBSD-like (but not the same) vnode-centric file system
> architecture, the Linux file system layer is file-centric. This causes
> several issues, combined with the nature of Mac OS X kernel
> interfaces. Therefore, a 100% faithful FUSE API implementation is not
> currently feasible on Mac OS X *under realistic circumstances*. That's
> all.
Not to complicate the issue, but Mac is not limited to BSD 'like'.
I run all those I install with UFS-only. Grant, Mac's UFS is a few releases
behind BSD's, but at least it is not hfs / hfs+.
Which - AFAIK, has sod-all to do with FUSE in any case. But at least gives me
BSD-compatible filenames as well as a faster fs.
And, JFWIW, Mac's UFS supports Inferno-for-OS X just fine. So AFAIK, a Mac with
one or more UFS partitions might not have as great a need for FUSE.
Bill Hacker
next prev parent reply other threads:[~2007-03-29 13:36 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 [this message]
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
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=460BC0ED.7070101@conducive.org \
--to=wbh@conducive.org \
--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).