HP3000-L Archives

October 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Isaacblake <[log in to unmask]>
Reply To:
Isaacblake <[log in to unmask]>
Date:
Thu, 12 Oct 1995 05:39:32 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
In article <[log in to unmask]>,
John Dunlop <[log in to unmask]> writes:
 
> I don't see a way around this unless the SIG is changed to encompass 2
>mini-SIGs (MPE and UNIX) with a
> common area for the SIG in general (e.g. like sub-committees) to deal
with
>the
>system specific technical items.
> I haven't really thought this through all the way and would be
interested to
>hear other people's opinions.
 
Hi John,
 
SIGSYSMAN has expanded to include more than Unix/hp-ux.  The majority of
system managers nowdays have multiple platforms to worry about.  So if you
were taking a look at a high level for SIGSYSMAN you might say it's
addressing the enterprise-wide, strategic/upper technical levels of system
management.  This would include issues like support, DCE, DHCP, CDE,
etc...  Where items like specific functionality would be handled at the
specific SIG level.
 
Setting the clock back, SIGSYSMAN would probably address network or
enterprise printing, where SIGUnix, SIGMPE and SIGNetworking would work
out the specific implementations in each area.
 
Cheers,
/isaac
[log in to unmask]

ATOM RSS1 RSS2