Article View: vmsnet.admin
Article #94Re: CFD: VMSNET Alpha newsgroup
From: Terry Poot
Date: Mon, 23 Nov 1992 15:14
Date: Mon, 23 Nov 1992 15:14
42 lines
2868 bytes
2868 bytes
In article <20NOV199219380835@eql.caltech.edu>, rankin@eql.caltech.edu (Pat Rankin) writes: > The login banner on an Alpha running VMS says "OpenVMS AXP (tm)" >(where VAX/VMS still says "VAX/VMS", without the extra marketeers' nonsense) I'll bet that changes. :-) >and there's no mention of "Alpha" to be seen. Personally I prefer "Alpha/VMS" >>and "VAX/VMS" and hope to relegate "OpenVMS" to the circular file where >it belongs. > > An Alpha porting group would be useful, but VMS is still VMS and >there's no need for separate groups for regular software. I can't imagine >why someone would propose an OSF/1 or WindowsNT group in the vmsnet >hierarchy though. Haven't we been through this several times before? I agree we need something, but I'm not sure exactly how to position it. Due to the transitional nature if things, perhaps we need just a single group to discuss any and all topics specific to the Alpha. This could cover everything from porting issues to chip architecture to the software rollout schedule. However, I disagree with the idea that the group(s) will grow. In fact, after an initial spurt of activity, I suspect it/they will shrink. Note that there are no groups about the VAX architecture, nor any about porting from RSX to VMS. Several years after the fact, there will no longer be a need for any alpha specific groups. If anything, we'll need to create VAX groups for the small group of people that still want to talk about them. The Alpha will take over all the groups related to VMS as it becomes the de facto platform for VMS. I'm not sure more than one group will be justified by the traffic, and in a year or 3, even this one will die out as the Alpha takes over. Such a catchall group should probably be called vmsnet.alpha. I suppose v.alpha-axp would be a possibility. I don't think enough people have heard of the AXP designation to call it vmsnet.axp. (Hmm... sounds like Kevin's original proposal, doesn't it?) :-) Ideas? Opinions on the name(s)? -- Terry Poot <tp@mccall.com> The McCall Pattern Company (uucp: ...!rutgers!depot!mccall!tp) 615 McCall Road (800)255-2762, in KS (913)776-4041 Manhattan, KS 66502, USA
Technical Details
Message-ID:
<1992Nov23.091431@mccall.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mccall!mccall!tpReferences:
<1992Nov18.164347.1@ptavv.llnl.gov> <1992Nov20.075031.1048@beckman.com> <20NOV199219380835@eql.caltech.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!sdd.hp.com!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mccall!mccall!tp Newsgroups: vmsnet.admin Subject: Re: CFD: VMSNET Alpha newsgroup Message-ID: <1992Nov23.091431@mccall.com> From: tp@mccall.com (Terry Poot) Date: Mon, 23 Nov 1992 09:14:31 CST Reply-To: tp@mccall.com (Terry Poot) References: <1992Nov18.164347.1@ptavv.llnl.gov> <1992Nov20.075031.1048@beckman.com> <20NOV199219380835@eql.caltech.edu> Distribution: world Organization: The McCall Pattern Co., Manhattan, KS, USA Nntp-Posting-Host: mis1 Nntp-Posting-User: tp Lines: 42