home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.misc
- Path: sparky!uunet!wupost!sdd.hp.com!zaphod.mps.ohio-state.edu!menudo.uh.edu!usenet
- From: sears@tree.egr.uh.edu (Paul S. Sears)
- Subject: Re: NeXTstep 3.0
- Message-ID: <1992Aug18.222553.2535@menudo.uh.edu>
- Sender: usenet@menudo.uh.edu (USENET News System)
- Nntp-Posting-Host: sierra.egr.uh.edu
- Reply-To: sears@tree.egr.uh.edu
- Organization: University of Houston
- References: <1992Aug18.164709.17243@kakwa.ucs.ualberta.ca>
- Date: Tue, 18 Aug 1992 22:25:53 GMT
- Lines: 64
-
- In article <1992Aug18.164709.17243@kakwa.ucs.ualberta.ca>
- sherwood@fenris.space.ualberta.ca (Sherwood Botsford) writes:
- =>Allen B writes
- =>>
- =>> Considering our semester starts on the 24th, the 3.0
- =>> release is really too late for me whenever it is. I got
- =>the
- =>> impression from early news of 3.0 that I'd have it up and
- =>> running by now. The date kept slipping and so did my
- =>chance
- =>> of using it any time soon.
- =>>
- =>> A big "Boo! Hiss!" to missing a summer release date. I
- =>now
- =>> either have to close our lab or wait 'til October to get
- =>the
- =>> job done right. I'm sure other Universities have similar
- =>> situations.
- =>>
- =>> If NeXT is still aiming at higher education, they're not
- =>> hitting it very well. Our machines should be stable and
- =>> consistent all semester long. Making me do an upgrade
- =>> once a semester is underway is not a way to be my friend.
- =>>
- =>> I'm not opposed to coming in weekends and working late
- =>> nights to get machines upgraded and tested. I'd just
- =>> rather do it between sessions and not when 440 users are
- =>> expecting to use our 24 hour lab.
- =>>
- =>> Allen B (Not the best NeXTperson to piss off)
- =>
- =>(Perhaps the next-best person to....)
- =>
- =>I know that Next has been working hard to make sure this
- =>release is bug-free software (oxymoron?) but having watched
- =>numerous VMS, AIX, Ultrix, DOS (Ugh) Windows (Ugh
- =>factorial) come down the pipe, let me say this: Don't
- =>commit too deeply.
- =>
- =>Were I in Allen's shoes I'd upgrade 1 machine in each lab
- =>to 3.0, and wait and see what happens.
- =>
- =>
- =>On the flip side, I too am eagerly awaiting the release.
- =>But it will b installed on only 1 machine for two months
- =>before I consider putting it on the rest.
-
- We are one of the Beta sites for 3.0 and since we got the first prerelease, we
- have been running 18 NeXTs on 3.0 and our other 50 or so are still on 2.1/2.2.
- What was fun is that our cluster has 2 servers, one is 2.1 and one is 3.0...
- Oh the joys.....
-
- We are going to do a complete upgrade to 3.0 prerelease 2 if we don't get the
- final disk by the time our semester starts.... Then we will have to upgrade
- again once we get the final release. This will only be a pain for me, but we
- need to have all users on some version 3.0 before the semester starts or we
- would end up confusing the hell out of them (Ooo, ahhh)...
- --
- Paul S. Sears * sears@uh.edu (NeXT Mail OK)
- The University of Houston * suggestions@tree.egr.uh.edu (NeXT
- Engineering Computing Center * comments, complaints, questions)
- NeXT System Administration * DoD#1967 '83 NightHawk 650SC
- >>> SSI Diving Certification #755020059 <<<
- "Programming is like sex: One mistake and you support it a lifetime."
-