|
|
| Author |
Message |
| 25 new of 137 responses total. |
valerie
|
|
response 25 of 137:
| 
Sep 24 01:02 UTC 1997 |
("Natalie Drest"?)
|
bruin
|
|
response 26 of 137:
|
Sep 24 12:54 UTC 1997 |
I believe I remember "Natalie Drest" as one of the people in the closing
credits of "A Prairie Home Companion."
|
tao
|
|
response 27 of 137:
|
Sep 24 15:25 UTC 1997 |
(Um, yeah. Along with Norman Conquest, Immanuel Transmission, etc)
|
dpc
|
|
response 28 of 137:
|
Sep 24 15:37 UTC 1997 |
When the ice thaws next spring sounds like a good goal to me.
No, of course I don't want my money back! 8-)
|
arthurp
|
|
response 29 of 137:
|
Sep 25 00:19 UTC 1997 |
Thank you staff for all the work and frustration you have endured on the 670.
I've been following the progress and sympathyzing. If I knew anything about
SunOS I'd offer to help, but I'd be a hinderance on this one.
|
mta
|
|
response 30 of 137:
|
Sep 25 15:15 UTC 1997 |
The only "help" I can offer is moral support, pop, and cookies.
Let me know about the next group work session and I'll be there with
baked goods!
|
steve
|
|
response 31 of 137:
|
Sep 25 21:33 UTC 1997 |
Now, thats a thought...
|
other
|
|
response 32 of 137:
|
Nov 19 07:53 UTC 1997 |
out of curiosity, can we get an update on the upgrade progrees?
thanks.
|
janc
|
|
response 33 of 137:
|
Nov 19 17:17 UTC 1997 |
Next step is to install SunOS on the machine. We are currently running an
old version of SunOS on Grach, and we can't copy over the version from Grex
because the software for multiprocessor architectures is slightly different.
So we have to do a fresh installation from the CD. We have two CDs. One is
the SunOS 4.1.3_U1 version that we are running here. Greg has it, but can't
find it, and doesn't think it includes the multiprocessor stuff anyway. The
other is a SunOS 4.1.4 CD that Jared donated. STeve has it, it's in his car,
but it hasn't made it to the pumpkin in the last few weeks. When and if a
installation disk appears, someone will have to actually do the install and
copy over Grex's software. Odds are, this is me. I expect to be able to
do most of it in a solid days work, though there are a few sticky issues with
libc that may take a bit longer to figure out. After that, it will mostly
be a question of doing a good security sweep of the system.
|
janc
|
|
response 34 of 137:
|
Nov 20 20:12 UTC 1997 |
STeve got the CD to me after the board meeting last night. I've done the base
install, and will be doing the Sun patches, then the Grex mods soon.
|
tsty
|
|
response 35 of 137:
|
Nov 21 04:13 UTC 1997 |
yippiyyippiyyippiy-o-day!
|
valerie
|
|
response 36 of 137:
|
Nov 21 15:13 UTC 1997 |
Yay Jan! Cool beans!
|
dpc
|
|
response 37 of 137:
|
Nov 22 18:02 UTC 1997 |
Great!!
|
janc
|
|
response 38 of 137:
|
Nov 22 21:59 UTC 1997 |
I think I've completed the first pass of software installation on the 4/670.
Nearly all of Grex's custom software has been copied over and installed.
We still need to do our kernal modifications and a whole lot of testing.
|
srw
|
|
response 39 of 137:
|
Nov 23 22:31 UTC 1997 |
I spent Sunday afternoon working on the kernel configuration for the
4.1.4 kernel to meet Grex's specific needs, and working on the
installation of the kernel blocks. This is complete now, and the machine
has been rebooted to run on the new kernel but there are still a number
of other things to take care of before we can begin the final testing
and security checks. We have to figure out where to put the mail spool
for one thing.
This was definitely a good weekend for progress on the 670. I'm not at
all sure how long the remaining work will take.
|
janc
|
|
response 40 of 137:
|
Nov 23 22:35 UTC 1997 |
Steve Weiss has rebuilt the 670's kernel, so it now has all the latest Grex
mods.
What's basically left to do now is a variety of minor software work (like the
latest version of Backtalk isn't there yet), a lot of testing to make sure
that all the programs work OK, and some double-checking to ensure that all
our security is correctly installed.
Then we have to generate our change-over plan. A lot of things on Grex are
continously changing, so they cannot be moved to the new system until we
actually make the change. To make sure we get it all, we need to make a plan.
|
remmers
|
|
response 41 of 137:
|
Nov 24 02:25 UTC 1997 |
I suggest that the move not take place during the board election
(i.e. December 1-15).
|
tsty
|
|
response 42 of 137:
|
Nov 25 00:14 UTC 1997 |
fine suggetion, agreed.
|
lilmo
|
|
response 43 of 137:
|
Nov 25 23:08 UTC 1997 |
I presume Grex will have to be shut down during the actual changeover?
|
valerie
|
|
response 44 of 137:
|
Nov 25 23:14 UTC 1997 |
Yes, probably for between half a day and a full day.
|
janc
|
|
response 45 of 137:
|
Nov 26 00:15 UTC 1997 |
I'm not exactly sure why doing the change-over during the election period
would be a problem. As long as we move over the vote directory, it should
not interfere with the election.
|
mary
|
|
response 46 of 137:
|
Nov 26 00:55 UTC 1997 |
If all goes well. Is there any chance at all that changing
over could result in Grex being unavailable for a couple days
or longer? It would be nice if the vote could come off, as
planned, without the need for extensions and added confusion
as to deadlines.
|
valerie
|
|
response 47 of 137:
|
Nov 26 15:30 UTC 1997 |
Ya, I'd rather not do the changeover during the voting period.
|
janc
|
|
response 48 of 137:
|
Nov 26 16:22 UTC 1997 |
I think the chances of that are small. We aren't erasing the old system
when we bring up the new system. If there are any snags in bringing up the
new system, we can always fall back to the old system. This assumes that
we don't screw up badly enough to leave both systems un-workable. This is
possible, of course, but pretty unlikely.
|
remmers
|
|
response 49 of 137:
|
Nov 26 17:47 UTC 1997 |
If the new system is up for a little while, some people cast
votes, and then we have to go back to the old system because of
some unforseen problem, the votes that were cast on the new
system could get lost. Unlikely perhaps, but possible.
|
