|
|
|
I'm not a member of M-Net's staff, so this is second-hand, but here's what
I know:
1. It does not look like we'll be able to bring the old M-Box back up.
2. Rex is working on getting M-Net up and running on a new machine.
3. There is a hardware problem with some component of the new machine --
tentatively diagnosed as the SCSI card -- that makes it impossible to
write to its hard drive.
4. Funding is not an issue. (But thanks to all of the people who have
offered money to help us get back up faster.)
5. Once the machine is running, it will still take several days to test
it adequately, especially given security considerations.
6. No user or BBS files have been lost.
When I say up to a week, I'm guessing. I don't know whether it would be
possible to slap another machine up there just to handle email. If that's
practical, it's a good idea, and we should do it. I'll look into that, if
one of our staff folks doesn't post here on the topic first.
I wish I could tell you that the machine will be back up tomorrow, but I
can't. I can tell you that M-Net *will* be back up, and will be far more
stable and fast when it is. I can also tell you that people are working hard
on it, and have already put a lot of time in.
On behalf of Arbornet, I apologize for the inconvenience caused by this
downtime, and I promise that we'll do our best to resolve it as quickly as
possible within the limitations of our volunteer schedules, and try to prevent
a recurrence.
137 responses total.
Congratulations on not having lost any files! Thats an excellent thing, and will mollify a lot of people when the system does come back up. A week (or more) is not an unreasonable amount of time for the reappearance of M-Net. Just testing the system for security problems should take several days, assuming no problems found. Six months from now people won't remember this as anything more than a pain in the ass--and if it takes an extra few days to come up, so be it.
How current will the files be? Understandably you probably couldn't use the last backup because it has all the hacked stuff on it.
Have you given any thought to "donating" the old M-Box to the Attorney General's new on-line crimes unit, for a full forensic investigation?
Re #2: Rex dumped all the files to tape pretty much as soon as he got to
WWNet.
Re #3: Are they a 501(c)(3), so we can get a tax writeoff? ;-)
That's really cool that we are getting back our files. I do have a lot of files that I have linked from my website. As someone wrote, I too have a lot of addresses in address book and saved-messages in mnet. Are we really goin to loose them? :(
8D
Re #5: I don't see why you would. We should have everything on those tapes.
#0: That's pretty accurate, Joe. I'm fairly confident that we will be
able to restore user home directories (and hopefully mailboxes) as
they were at the time of our crash.
If we were confident that the system's binaries were uncorrupted,
this process would be quite a bit simpler. To the contrary, we're
positive that M-Net is swiss-cheese at this point, and before we can
restore service, we need to have a certain degree of confidence that
those holes have been filled.
We're running into all sorts of fun barriers. Stuff that a lot of
people don't really think too hard about, like the fact that we
require a customized kernel that prevents non-patron users from
opening socket connections. (Anyone got time to dig into this one
while we're working on other stuff? We'll have to settle on an
operating system first.)
which os is on this new b0x?
re #5 DID YOU NOT UNDERSTAND ME? I said "your friends ate my balls in a ball eating contest" WHAT ELSE DO YOU NEED TO KNOW?
This response has been erased.
This response has been erased.
the ability to limit outgoing network traffic to certian groups is already in the FreeBSD kernel :) the scsi problems mentioned above are as follows: any os I try to install on this hardware hasn't been able to put files on the disk, apparently. it can format it just fine, but get weird errors when actually trying to install the OS. this happens with FreeBSD, Linux, OpenBSD and even Windows 2000. I've tried swapping SCSI cards, but it was just an older model with the same chipset. and I've tried a new hard drive. monday I'll try a different scsi card if I can find one laying around.
#13: Excellent. Let me know if that stuff doesn't work out, Rex, and I
will get a new motherboard in your hands ASAP.
This response has been erased.
if a new scsi card(s) are needed to get m-net back up, let me know how much it (they) costs and i'll get a check either to a bod member or k8 within 24 hours.
Whoa! cool.
Thanks, Void!
Thanks very much indeed, void!
I like aaron's idea
moi aussi.
I missed it...
drift; congrats to dpc for winning a seat on the library board in yesterday's election. drift off
When this thing finally is back up, Do you know how much mail is going to be coming in?!?!?! Make sur you load it slow!
Yes, we've already planned for that. Our staff is actually pretty competent, Bruce.
drop 'em joe...it's time fer yer spankin.
Hey, I thought *you* were the submissive!
JOE SAUL IS ON MY TEAM! HE IS A SUPERFRIEND HI-FIVE! HI-FIVE!
actually, m-net's e-mail is being spooled on wwnet's backbone. so, when we bring the machine back up, it should get it's old mail rather quickly.
Didn't someone say a long time ago (read: first few days of the crash) that mail was getting bounced? Did this change?
it should have changed now, yes.
latest news: the problems with the athlon seem to be with the ram, I've since swapped the chip, and everything is running smoothly. I'm restoring lotsa user data, and bringing the machine up to speed. there are quite a few system utilities that need to be installed, custom m-net programs, and then we gotta make sure everyone can and cannot do what we want them to. we should be back up in a week.
http://webcam.wccnet.org/latest.jpg that should be pointed at m-net. :) and/or me
re 32: cool beans! <applause!><cheers!><fanfare>
I have seen the new M-Net, and it is good. 12:43PM up 1:40, 5 users, load averages: 0.00, 0.05, 0.06 USER TTY FROM LOGIN@ IDLE WHAT root v0 - 11:04AM 1:34 tar xpv /migs /va trex p0 shaolin.wccnet.o 11:09AM 1:11 _su -m (tcsh) jp2 p1 205.252.37.3 12:11PM 12 bash jp2 p2 205.252.37.3 12:16PM - more willard p3 216.86.76.90 12:37PM - w CPU: AMD Athlon(tm) Processor (757.46-MHz 686-class CPU) Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 496111 153414 303009 34% / /dev/da0s1g 99183 1 91248 0% /bin/suid /dev/da0s2e 2977220 434158 2304885 16% /home /dev/da0s3h 9887 9 9088 0% /root /dev/da0s1h 49583 3 45614 0% /tmp /dev/da0s3e 744175 462641 222000 68% /usr /dev/da0s3g 744175 300513 384128 44% /usr/bbs /dev/da0s3f 992239 84205 828655 9% /usr/local /dev/da0s1e 992239 27960 884900 3% /var /dev/da0s1f 992239 303900 608960 33% /var/mail procfs 4 4 0 100% /proc
so does that mean we can log on now?
Nope. Not yet.
It has alreayd been despoiled by jp2? Hm. ;)
This response has been erased.
| Last 40 Responses and Response Form. |
|
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss