H Terence
Late to the party, but some other things you can talk about are:
- Subsystems - memory pools and tuning etc
- Jobqueues - stacking jobs up and the management capability
- Object based (not oriented) system objects can only do what the object is
permitted to do
- Commands - verb/noun structure allowing you to "predict" what the command
you will need in most cases
- Commands - "long winded" patameters are actually consistent across many
commands and therefore self documenting
I found when talking to the unix guys one of the tricks was understand
enough about the environment they knew to be able to tell them about the
system I "in their words". In fact this is true also when talking to Windows
Guys (although this is a problem sometimes as a lot of the windows guys I've
struck simply don't know anything - they simply remember a lot of procedures
that they repeat until one works)
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Terrence Enger
Sent: Tuesday, 26 August 2008 9:20 a.m.
To: Midrange Systems Technical Discussion
Subject: Re: What should I say to a *nix community?
On Mon, 2008-08-25 at 16:20 -0400, Trevor Perry wrote:
Are you confusing the user group? There is one at www.tug.ca that is
named:
TORONTO USERS GROUP for Power Systems
I wonder if you meant that......
Two domain names, one user group.
midrange.com
