9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sigrid Solveig Haflínudóttir" <ftrvxmtrx@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] SFF 9legacy fileserver hardware
Date: Tue, 27 Apr 2021 11:28:19 +0200	[thread overview]
Message-ID: <CAP9joag_vVji4qW+veiGZTFBpQAmSjX=zG+XXuh2Wyrs2kEorw@mail.gmail.com> (raw)
In-Reply-To: <e84034b56f578c7f@orthanc.ca>

From the information floating around, short summary of my
understanding (hopefully I'm not wrong):

1) 9legacy on amd64 is unable to use more than 4Gb of memory (and
possibly has other issues?)
2) fossil+venti on amd64 seems to be largely untested and bugs are
being discovered and fixed:
https://pixelhero.dev/patches/venti/set.patch
3) some are using fossil+venti extensively on 9front/amd64 with
success, even though fossil was removed from the base system due to
bugs and no one stepping up to fix those

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T055ff8c5321ac6a2-Mc17ca820c799be539031222c
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2021-04-27  9:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 20:27 Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-26 21:16 ` hiro
2021-04-26 21:20   ` hiro
2021-04-26 21:40   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-26 23:32 ` kokamoto
2021-04-26 23:36   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-26 23:41     ` kokamoto
2021-04-28  1:31       ` kokamoto
2021-04-28  2:33         ` kokamoto
2021-04-27  5:02 ` ori
2021-04-27  9:28 ` Sigrid Solveig Haflínudóttir [this message]
2021-04-27 10:33   ` kokamoto
2021-04-27 10:35     ` kokamoto
2021-04-28  9:40 ` Steve Simon
2021-04-28 18:21   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-04-28 18:41     ` 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='CAP9joag_vVji4qW+veiGZTFBpQAmSjX=zG+XXuh2Wyrs2kEorw@mail.gmail.com' \
    --to=ftrvxmtrx@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).