From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: jmk@plan9.bell-labs.com, rminnich@lanl.gov, 9fans@cse.psu.edu
Subject: Re: [9fans] 3 questions
Date: Mon, 29 May 2006 19:14:14 +0200 [thread overview]
Message-ID: <c6e23e6c03a740c8950cc17620fd2d90@lsub.org> (raw)
: After the 'how do we read/store mail on Plan 9' a couple of months ago,
: has anyone done anything to improve the situation, e.g. memory footprint?
I have done something.
In the Plan B distrib I copied to sources, there's a program that
should work also for Plan 9. It should be at
/n/sources/contrib/nemo/sys/src/cmd/mail2fs/ IIRC
The idea is that mail2fs converts from mbox format to a file tree.
For example, my current inbox (listed from its root), is:
200605/6679/text rsc@swtch.com Re: [9fans] 3 questions
200605/6678/text rsc@swtch.com Re: [9fans] 3 questions
200605/6677/text quanstro@quans Re: [9fans] 3 questions
200605/6676/text jmk@plan9.bell Re: [9fans] 3 questions
200605/6675/text quanstro@quans Re: [9fans] 3 questions
200605/6674/text jcenteno@gsyc. Re: programa en canal historia
....
Then, to read mail, I use mails (which merely pretty-prints */[0-9]*/text)
or one for the wrappers. Indeed, cat */[0-9]*/text works well enough.
Would this suffice?
I remember complaints about the speed of using grep to search within this,
but in practice, I manage. If that's a problem, maybe what we need is a
generic file search a-la google for our files.
next reply other threads:[~2006-05-29 17:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 17:14 Fco. J. Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 16:33 Ronald G. Minnich
2006-05-29 16:36 ` quanstro
2006-05-29 16:40 ` quanstro
2006-05-29 16:49 ` jmk
2006-05-29 17:15 ` lucio
2006-05-30 4:34 ` Ronald G Minnich
2006-05-30 6:26 ` arisawa
2006-05-30 7:35 ` quanstro
2006-05-29 17:57 ` Russ Cox
2006-05-30 0:04 ` geoff
2006-05-29 17:58 ` Russ Cox
2006-05-29 22:55 ` Adrian Tritschler
2006-05-30 3:05 ` Micah Stetson
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=c6e23e6c03a740c8950cc17620fd2d90@lsub.org \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
--cc=jmk@plan9.bell-labs.com \
--cc=rminnich@lanl.gov \
/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).