From: ori@eigenstate.org
To: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] Cannot
Date: Wed, 02 Dec 2020 17:53:00 -0800 [thread overview]
Message-ID: <45C6D52FCD988ED9364CA4976F5E6C0F@eigenstate.org> (raw)
In-Reply-To: <681273F2-DEEF-4E4D-9EC3-92340268D4F4@stanleylieber.com>
Quoth Stanley Lieber <sl@stanleylieber.com>:
>
> let me present you with my counter-scenario:
>
> 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).
>
> there's no recourse. you're just futzed.
>
> sl
>
Fair enough, I'm convinced.
I'd still want to steer users towards a dump, but I'm ok
with adding this as an option to the installer.
next prev parent reply other threads:[~2020-12-03 1:55 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 [this message]
2020-12-03 2:54 ` Xiao-Yong Jin
2020-12-03 3:11 ` Stanley Lieber
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=45C6D52FCD988ED9364CA4976F5E6C0F@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=sl@stanleylieber.com \
/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).