9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cosarara <cosa@cosarara.me>
To: 9front@9front.org
Subject: Re: [9front] List archives
Date: Thu, 24 Mar 2022 10:56:38 +0100	[thread overview]
Message-ID: <6f83c848-d08b-351c-5c58-2a270fad3572@cosarara.me> (raw)
In-Reply-To: <753CE532CBA2F3A6640D634F7E6B358C@thinktankworkspaces.com>

On 23/03/2022 19:49, william@thinktankworkspaces.com wrote:
> It should work but please keep in mind its 8506 files of mail
> It tooke me 10 minutes to run tar cvzf $home/9list.tgz /n/list/9front/
> 
> And I stopped it early with only 1067 files.

At 125ms ping away from the server, and a dance of Twalk, Topen, Tstat, 
Tread, Tread (again! but this is a topic for another thread) and Tclunk 
for each file, 800ms per email, it would take me over 2h so I left it 
copying and went to sleep. It was done today morning.

> I untarred in $home/9list
> 
> you can run touch $home/9list/L.mbox
> 
> upas/fs -f $home/9list
> 
> and run acme with Mail like normal

I skipped the touch, and I had to make sure the plumber was running, but 
it worked :)

Reading the nupas.pdf document, it sounds like the whole point of the 
idx file is to let upas/fs work without having to read every single 
message file to get its metadata. I don't know if it being read-only 
would cause trouble, but maybe if there was a more or less up to date 
idx file in the server, this would be fast for everybody, without 
needing the local copy?

Regardless, some clearer instructions in that website would do wonders :)

cosarara

  parent reply	other threads:[~2022-03-24 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23  7:36 cosarara
2022-03-23 18:49 ` william
2022-03-24  2:25   ` umbraticus
2022-03-24  9:56   ` cosarara [this message]
2022-03-23 20:48 ` Humm
2022-03-25  0:58 ` sl

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=6f83c848-d08b-351c-5c58-2a270fad3572@cosarara.me \
    --to=cosa@cosarara.me \
    --cc=9front@9front.org \
    --subject='Re: [9front] List archives' \
    /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

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).