🚀 go-pugleaf

dsroberts@beckman.com writes:
> In article <1992Nov18.164347.1@ptavv.llnl.gov>, oberman@ptavv.llnl.gov writes:
> > Is it about time for a VMSNET group for Alpha AXPs? The little devils are sure
> 
> vmsnet.alphaAXP.whatever
> 
> would be my vote (what the hey, AXP is part of the name, after all).  I think
> the Alpha AXP issues are distinct enough to justify starting with the third
> level even if we only have a .misc to start. 
> 
> vmsnet.alphaAXP.misc
> vmsnet.alphaAXP.sysmgt
> vmsnet.alphaAXP.OSF1
> vmsnet.alphaAXP.OpenVMS (this ought to get a reaction from Jamie!)
> vmsnet.alphaAXP.windowsNT

I'm wondering about the alternative structure of 

vmsnet.sysmgt.* (* from set of VAX, AlphaAXP, DECSYSTEM, etc...)
vmsnet.os.* (e.g. * from the set of OSF1, OpenVMS, WindowsNT)

From a conceptual standpoint I see these groupings as a little more
natural than having a group for every member of the cross between
architecture and area of interest.

Comments?
--
----

Bob Boyd
In The Here & Now