From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] AUTHENTICATE failed can't get challenge (imap4d)
Date: Mon, 06 May 2024 16:50:17 +0200 [thread overview]
Message-ID: <944CC9D807FB7E302CDDB114CBE15BD0@wopr.sciops.net> (raw)
In-Reply-To: <2F67D591-F391-4C73-AFFB-ACAB0EE6FC06@stanleylieber.com>
On Mon May 6 16:34:44 +0200 2024, sl@stanleylieber.com wrote:
> > It's a bad idea to run cwfs without a worm, especially in a vm.
>
> why?
>
> sl
In my experience cwfs is very sensitive to unclean shutdowns, much
more than hjfs. VPS providers may sometimes reboot instances, or VMs
may go down, or 9front may panic and freeze, etc. I also remember
many instances of corruption (iirc with hjfs) under qemu but this
might have been fixed. Either way I think it's too risky to not have
any recovery method; if the check commands fail it's over. Of course
please correct me if I'm wrong, I'm not very familiar with the code.
qwx
next prev parent reply other threads:[~2024-05-06 14:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 11:12 sirjofri
2024-05-03 11:52 ` Alex Musolino
2024-05-03 18:23 ` sirjofri
2024-05-03 19:51 ` Jacob Moody
2024-05-03 21:09 ` Roberto E. Vargas Caballero
2024-05-06 11:12 ` sirjofri
2024-05-06 12:59 ` qwx
2024-05-06 14:34 ` Stanley Lieber
2024-05-06 14:50 ` qwx [this message]
2024-05-06 15:30 ` sirjofri
2024-05-06 15:40 ` Stanley Lieber
2024-05-06 16:03 ` qwx
2024-05-06 16:24 ` Stanley Lieber
2024-05-06 16:03 ` Stanley Lieber
2024-05-06 16:08 ` [9front] cwfs no-worm + venti (was: AUTHENTICATE failed can't get challenge (imap4d)) sirjofri
2024-05-06 16:21 ` [9front] " Stanley Lieber
2024-05-06 16:37 ` [9front] Re: [9front] cwfs no-worm + venti Jacob Moody
2024-05-06 13:56 ` [9front] AUTHENTICATE failed can't get challenge (imap4d) Jacob Moody
2024-05-06 14:32 ` Stanley Lieber
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=944CC9D807FB7E302CDDB114CBE15BD0@wopr.sciops.net \
--to=qwx@sciops.net \
--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).