|
|
This item is for system announcements (new computer equipment on Grex, system upgrades, Grex meetings, etc.). Personal announcements should go back in item 2; Grex system *problems* belong in the next item (#4).
71 responses total.
Anyone ever hear of bill Vajk ?
Nominations are open through November 15 for the Grex Board of Directors. See Item 288 in the Coop conference for details.
Sweet, I love those.
I'd like to announce that someone said she was going to report me to Grex cops based on what I said to her in party, and, based solely on what was said in party, it probably looks like I deserve to be castrated, but please keep in mind that context is everything.
I'm now FAIRLY sure such a complaint won't be made, but I'm still more than prepared to put up a fight if I'm wrong.
By the way: Yes, I'm mostly just entering this because I hope people will go search out exactly what the conversation was.
Meaning you're actually rather proud of it, just too chicken to say so?
I'd like to see the conservation.
Of what?
my penis.
Has it been shrinking?
Well, no. I can make it grow really big if you want.
Just so it is conserved...
Well, we are up on OpenBSD 3.8. The process did not live up to my ideals, It should have gone quicker, and we lost the /va/mail partition. Sigh. I'll enter a more detailed postmortem in another item.
We appreciate everything you do for Grex Jan. Good work!
Thanks Gan!
Postmortem is in item 94.
Thanks for all you do!
What nate said.
Thanks, JAn!
Grex is now running with 512M of ram. I think the system will be a lot more stable now.
As of this moment, Grex has an uptime of 1 day, 15 hours, and 20 minutes. That's a lot better than we were doing before. To compensate for the downtime during the OS upgrade, nominations for the 2006 Board of Directors will remain open through November 25. See Item 288 in the Coop conference (item:coop,288) for details.
Happy Thanksgiving!
Now a bit more than 5 days. Thanksgiving indeed!
Over 6 and a half days now. Looks like it was a memory problem all right, or at least a problem accessing the memory.
This response has been erased.
COuld it be that the motherboard would crash no matter which DIMM you put in the second or third slot?
Yes. I don't think the memory per se is bad. I've been thinking along the lines of Dan's thoughts. I have a call into Crucial about the best way to get the memory back to them for testing. Given the hassles of getting to Grex and taking it down for that kind of stuff, if I can get the memory out to them and back in a week or so, I think we can live with that. With the current usage patterns on Grex 512M works pretty well.
hey cross. they did it without you. :( :(
This response has been erased.
Your hips are too wide!
a pear-like kim il sung physique?
This response has been erased.
http://media.portland.indymedia.org/images/2004/02/281656.jpg
geeeeze, tod, where do you find all that shit? =======<<....>>=================== #3.13 Rane Curl (rcurl) Thu, Nov 10, 2005 (11:29): Just so it is conserved... #3.14 Jan Wolter (janc) Sat, Nov 19, 2005 (13:58): Well, we are up on OpenBSD 3.8. The process did not live up to my ideals, nine damn days and not a whisper of what was to happen? mary had to send me email (elsewhere) to an hvcn site that *hid* the grex situation? i';ll bet there are a whole buncha folks who are pissed as hell at the nine days and no notice (well maybe there was someting hidden in the last day or so of motd) point me to the ITEM in agora that discussed the *downtime* anticipated? not everyone reads coop.cf with the same regulatiry as agora.cf. item #94 is a post-motrem .. wehre was teh damn PRE-mortem ????? hellz=-bellz ... what a fsckup (and no, i'm not tallking about /var/spool/mail - a separate problem).
Put the AE unit back in and see if it fails as HAL predicted...
Re #35: Well, there was an MOTD announcement, if that counts as a "whisper". Unfortunately, the *amount* of downtime was not anticipated, hence no extensive "pre-mortem". Hardware problems were discovered during the upgrade, which prolonged the downtime significantly and unexpectedly. The HVCN "Grex status page" has been around for years but could probably be better publicized. I'll put a pointer to it in the motd, suggesting that users bookmark it in their browsers. http://www.hvcn.org/info/grex/
I've found the HVCN status page is often inaccurate. I don't even bother with it any more. What's worse is there's no way to find it when it's needed. How about putting the link in the login for the M-Net Grex conference? (Which is where I usually go to find out why Grex is down, when it's down.)
The status page currently says this: --- Fri Nov 18 21:33:44 EST 2005 Grex is UP! --- Is there some way to have it updated periodically by an automatic process (and the date/time updated as well)?
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss