9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] is sources unreachable?
Date: Wed, 27 Aug 2003 09:48:09 -0400	[thread overview]
Message-ID: <847c8b7fc679b6f8f33d5056ca449956@plan9.bell-labs.com> (raw)
In-Reply-To: <3F4CBB00.6060103@ameritech.net>

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

You are right, sources was up last time I updated something which was Monday
afternoon.  If people have been having problems for a week, it was probably
something else.  Two weeks ago it was the power grid.

This was indeed the worst infection I've seen.  The Plan9/Linux/BSDers got
to look really smug while helping people disinfect their µsoft machines.

I found the worm quite helpful.  It pinpointed every machine that wasn't
keeping up with windows critical updates and/or mcafee .dat's without really
doing any permanent harm (I hope).  A lot of those systems were infected
with a bunch of other viruses that noone was noticing because they were
latent or just not noisey enough.  It'll cause a change in tools/precedures
to keep everyone's system updated.

Of course, you have to count that against the man hours it sonsumed, which was
sizable.  Also, it doesn't seem to be affecting anyone's attitude towards
depending so heavily on one very vulnerable OS.

[-- Attachment #2: Type: message/rfc822, Size: 2742 bytes --]

From: northern snowfall <dbailey27@ameritech.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] is sources unreachable?
Date: Wed, 27 Aug 2003 09:06:56 -0500
Message-ID: <3F4CBB00.6060103@ameritech.net>

>
>
>No, the fossil serving the sources crashed.  I've rebooted while we try to figure out
>what broke.
>
It may have crashed lately, but people have been complaining
about reaching sources for the past week. So, unless it's been
crashed for a week (yet still randomly is able to server users)
I'll still attribute the brunt of the trouble to the worms.

Just the other day a friend of mine and I noticed that network
connections from his UK machine to other UK machines
were being routed through the US and Canada, whereas
they previously had not.

Don

http://www.7f.no-ip.com/~north_


  reply	other threads:[~2003-08-27 13:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27  5:46 lucio
2003-08-27 12:17 ` Jim Choate
2003-08-27 12:37   ` lucio
2003-08-27 12:45     ` Jim Choate
2003-08-27 13:45   ` northern snowfall
2003-08-27 12:49     ` David Presotto
2003-08-27 14:06       ` northern snowfall
2003-08-27 13:48         ` David Presotto [this message]
2003-08-27 13:56           ` ron minnich
2003-08-27 15:57             ` northern snowfall
2003-08-27 15:39               ` matt
2003-08-27 21:41                 ` northern snowfall
2003-08-27 21:58                   ` matt
2003-08-27 23:33                     ` northern snowfall
2003-08-27 22:44                       ` matt
2003-08-27 23:51                         ` northern snowfall
2003-08-27 14:29           ` Wes Kussmaul

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=847c8b7fc679b6f8f33d5056ca449956@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /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).