9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: weigelt@metux.de,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] RFC: MailFS-NG
Date: Tue,  8 Jan 2008 09:04:26 +0100	[thread overview]
Message-ID: <82c890d00801080004s6f191fcbsdfa6f870e585edef@mail.gmail.com> (raw)
In-Reply-To: <20080107184213.GA30950@nibiru.local>

Hello

> Just downloading isn't enough, would require sync back (and that's
> gonna be difficult). And having to download several Gig is not
> an option for me.
>

I don't know what kind of storages are you talking about, but the way
is done by the mail system is just a read-fs and a smtp client, you do
not write into /mail/fs/mbox to send mail :-?,

> It has to be an synthetic filesystem, since the server should do
> most things. As already said: clients should only speak mailfs-ng,
> and not doing their own storage handling anymore. This also includes
> things lke filtering, searching, etc.
>

why do not start with what we have now? making upasfs to use the
remote storage, making it able to order mailbox and move messages
between them and those things? that's why i suggested taking a look at
what Russ said about upasfs from p9p :-? starting from scrach would be
much more painfull :-?

slds

gabi


  reply	other threads:[~2008-01-08  8:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 20:53 Enrico Weigelt
2008-01-07 17:01 ` Gabriel Diaz
2008-01-07 18:42   ` Enrico Weigelt
2008-01-08  8:04     ` Gabriel Diaz [this message]
2008-01-08 17:44       ` Enrico Weigelt
2008-01-09  6:20         ` Gabriel Diaz Lopez de la Llave
2008-01-10  2:38           ` Enrico Weigelt
2008-01-09  6:38         ` ron minnich
2008-01-07 18:05 ` Francisco J Ballesteros
     [not found] ` <f4d8fa40801100520v6560731dnfd481b4e80237d7d@mail.gmail.com>
2008-01-10 13:39   ` Fwd: " hiro

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=82c890d00801080004s6f191fcbsdfa6f870e585edef@mail.gmail.com \
    --to=gabidiaz@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=weigelt@metux.de \
    /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).