From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9fans is back
Date: Fri, 24 Dec 2010 16:53:07 +0000 [thread overview]
Message-ID: <EB7E7A05-45A3-4400-8886-E349FDAF70F1@fastmail.fm> (raw)
In-Reply-To: <AANLkTinXiGhm5PrfKsdeDFJ8bAtj4ktqrd7ughUCt7Sy@mail.gmail.com>
On 24 Dec 2010, at 3:52 pm, Russ Cox wrote:
> 9fans.net was rejecting mail for the past week,
> due to an incomplete system upgrade attempted
> by someone who broke into the ancient Linux VM
> that ran the list. Even script kiddies can't get shared
> libraries right, it appears.
>
> I was away for the past week and unable to
> look into the problem until today. I have reinstalled
> the VM and restored the list configuration from
> backups.
Cheers Russ, it's good to have it back.
So someone broke in to attempt an upgrade? ... Oh, I suppose there
was a time I would have done it too.
>
> Apologies for the interruption.
> Now back to your regularly scheduled programming.
>
> Russ
>
next prev parent reply other threads:[~2010-12-24 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 15:52 Russ Cox
2010-12-24 16:53 ` Ethan Grammatikidis [this message]
2010-12-24 17:51 ` [9fans] " Russ Cox
2011-02-07 19:48 ` Russ Cox
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=EB7E7A05-45A3-4400-8886-E349FDAF70F1@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).