9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: wb.kloke@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] yet another try to fixup venti
Date: Fri, 16 Aug 2024 13:27:19 -0400	[thread overview]
Message-ID: <17238292390.9187f.37708@composer.9fans.topicbox.com> (raw)
In-Reply-To: <17188975500.FD8FA.38559@composer.9fans.topicbox.com>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

Now I have managed to get my files pushed to github. So the new location of my plan9port fork is now at 

https://github.com/vestein463/plan9port

In addition, there are a couple of FreeBSD related hosted ther, eg. a program ggatev,
which can be used to serve a vbackup'ed UFS filesystem as a geom, thus even writes are now possible (with help of geom_union) on the backup.

In the meantime, I changed my plan9 VMs to use my mventi as 2nd stage storage for fossil. 

I still would not recommend to use write active (unsealed) arenas on SSD (the main culprit isect has gone ), as the arena directory will still be written in partial blocks, probably leading to unnecessary disk wear. 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T21878aa53884911b-M35c05eb463b41f5ad747d5f0
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1639 bytes --]

      reply	other threads:[~2024-08-16 17:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 20:52 wb.kloke
2024-06-12 20:12 ` [9fans] " wb.kloke
2024-06-13  4:08 ` [9fans] " ori
2024-06-13 15:52   ` wb.kloke
2024-06-13 19:41     ` wb.kloke
2024-06-16  9:19       ` wb.kloke
2024-06-20 15:32         ` wb.kloke
2024-08-16 17:27           ` wb.kloke [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=17238292390.9187f.37708@composer.9fans.topicbox.com \
    --to=wb.kloke@gmail.com \
    --cc=9fans@9fans.net \
    /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).