9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gmail 0: messages
Date: Fri,  9 Dec 2005 23:56:29 +0100	[thread overview]
Message-ID: <9f3897940512091456x4921b14et2e38352ec84bbc9@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60512090813v6e5f1e9fve6db7ff25230b458@mail.gmail.com>

On 12/9/05, David Leimbach <leimy2k@gmail.com> wrote:
>
>
> You tell them that it's for all 9p speaking systems.   That includes linux
> now with v9fs, hopefully with Alan Cox [FreeBSD Alan Cox], anything that can
> use Tim Newsham's Python 9p implementation, etc. :)

A fast hack would be to port gmailfs from Linux/FUSE, as it uses not POP, but
Gmail WebAPI. As it's already an userspace fs, you would only have to
change FUSE-dependant layer and rework it to check "normal" e-mails
instead of
the ones it uses for file-storage.

> It's not as obscure as it once was.  I've seen talk of adding it to OpenBSD
> as well as a translation layer for DragonFlyBSD's native VFS messaging [well
> I proposed that one but god knows when I'll have time for that]

I see 9p more as a RPC/resource sharing system - I have a strong feeling
that I'd rather use sthg like AFS (if they implement files with size
>2GB) or other _fast_
network, file-oriented fs for my files (With driver using 9p as interface :D )

> Anyone interested in adding 9p to NetBSD? :)
>
> We'll just spread out like a virus and take over.  ;-)

Why not... just add it to windows, so you could use 9p mount disks...

And then I'd only have to write XFS/JFS/UFS2 for 9P and stop caring
about not having access to some files :D

> Dave

--
Paweł Lasek
"Once a hitokiri, always a hitokiri. This will never change" - Jine-Ei
http://plasek.jogger.pl [in polish]

      reply	other threads:[~2005-12-09 22:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 17:29 Philippe from Myrealbox
2005-12-07 18:56 ` Russ Cox
2005-12-07 20:47   ` Russ Cox
2005-12-08  1:17   ` Adrian Tritschler
2005-12-08  1:28     ` Russ Cox
2005-12-08  3:00       ` Adrian Tritschler
2005-12-08  3:59         ` Rob Pike
2005-12-08  7:36         ` geoff
2005-12-08  1:30     ` Uriel
2005-12-08  2:27       ` Adrian Tritschler
2005-12-08  2:35         ` John Floren
2005-12-09 16:13           ` David Leimbach
2005-12-09 22:56             ` Paweł Lasek [this message]

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=9f3897940512091456x4921b14et2e38352ec84bbc9@mail.gmail.com \
    --to=pawel.lasek@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).