From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Cannot
Date: Wed, 02 Dec 2020 22:11:43 -0500 [thread overview]
Message-ID: <3FCB396E-3A8D-44B1-908F-36FBA7AC49C0@stanleylieber.com> (raw)
In-Reply-To: <E311B6FD-AFC8-4D6D-8E0B-84B1B39C160D@gmail.com>
On December 2, 2020 9:54:30 PM EST, Xiao-Yong Jin <meta.jxy@gmail.com> wrote:
>
>> On Dec 2, 2020, at 7:28 PM, Stanley Lieber <sl@stanleylieber.com>
>wrote:
>>
>> 9front.org worm fills up before i notice it happened (this actually
>happened at least three times, over the years, which is why we now run
>hjfs without taking a dump).
>
>What are the options when worm fills up? Are there any docs dealing
>with this situation?
there are no options. the worm is designed to be read-only. once it's full, it's full.
sl
next prev parent reply other threads:[~2020-12-03 3:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:19 [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues Vladimir Nikishkin
2020-12-02 0:03 ` Josuah Demangeon
2020-12-02 4:03 ` Vladimir Nikishkin
2020-12-02 4:40 ` ori
2020-12-02 5:45 ` Vladimir Nikishkin
2020-12-02 16:46 ` ori
2020-12-02 17:12 ` Stanley Lieber
2020-12-02 18:07 ` ori
2020-12-02 19:03 ` Stanley Lieber
2020-12-03 0:35 ` kvik
2020-12-03 0:52 ` Stanley Lieber
2020-12-03 1:02 ` [9front] Cannot ori
2020-12-03 1:28 ` Stanley Lieber
2020-12-03 1:53 ` ori
2020-12-03 2:54 ` Xiao-Yong Jin
2020-12-03 3:11 ` Stanley Lieber [this message]
2020-12-03 3:22 ` Alex Musolino
2020-12-03 3:35 ` kvik
2020-12-03 16:07 ` kvik
2020-12-03 16:36 ` Stuart Morrow
2020-12-04 0:39 ` Alex Musolino
2020-12-02 7:15 ` [9front] Cannot install 9front-8013.d9e940a768d1.amd64.iso due to network issues Iruatã Souza
2020-12-02 16:44 ` ori
2020-12-03 18:02 ` Stuart Morrow
2020-12-03 18:18 ` hiro
2020-12-03 18:32 ` Stuart Morrow
2020-12-03 18:46 ` hiro
2020-12-03 18:53 ` Stuart Morrow
2020-12-03 19:37 ` hiro
2020-12-06 3:52 ` 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=3FCB396E-3A8D-44B1-908F-36FBA7AC49C0@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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).