source: trunk/athena/lib/zephyr/USING @ 10363

Revision 10363, 3.7 KB checked in by ghudson, 27 years ago (diff)
Pull in sources from zephyr locker. See /mit/zephyr/repository for detailed change information.
Line 
1This file explains how to use an existing Zephyr service once you've
2built and installed the Zephyr 2.0 distribution.  To learn how to
3build and install Zephyr, read the file INSTALL.  To learn how to set
4up Zephyr service at a site, read the file OPERATING.
5
6First, before you can do anything else, your client machine must be
7running zhm from the local system binary directory (/etc/athena/zephyr
8if you built Zephyr with --enable-athena, /usr/local/sbin/zephyr if
9you installed Zephyr in /usr/local and didn't use --enable-athena).
10Only one copy of zhm can be running on a given machine, and it can be
11started by any user.  If you're using a machine you don't administer,
12you may want to check if the machine is configured to start up zhm
13automatically at boot time.
14
15Once you have zhm running, you can start receiving zephyrgrams by
16running the command:
17
18        zwgc
19
20"zwgc" stands for "Zephyr WindowGram Client".  If you built Zephyr
21with X support and are using an X display, you will receive messages
22as windows on your screen (click on them to get rid of them);
23otherwise, you will receive messages in your terminal as text.  Read
24the man page on zwgc to find out how to configure it using the
25.zwgc.desc file in your home directory.
26
27You can send messages to another user with:
28
29        zwrite username
30
31To write to groups of users, you must agree on a "class" and/or
32"instance" to write to (this will be explained in greater detail
33below).  At MIT, most users communicate in private groups via classes.
34Suppose a bunch of people wanted to communicate on a class "newclass".
35They would all subscribe to the class with the command:
36
37        zctl add newclass \* \*
38
39and send messages with:
40
41        zwrite -c newclass
42
43The "zctl add" command adds the subscription to the .zephyr.subs file
44in your home directory, so that you will automatically be subscribed
45to the class the next time you run zwgc.  If you just want to
46subscribe without adding the subscription to your .zephyr.subs file,
47use "zctl sub" instead of "zctl add".
48
49Now for a bit more explanation about what classes and instances are:
50every Zephyr message is send to a class, an instance, and a recipient,
51commonly written as <class,instance,recipient>.  The default class is
52"MESSAGE"; the default instance is "PERSONAL".  When you use "zwrite
53username", you are sending a message to <MESSAGE,PERSONAL,username>.
54If you don't specify a username on the zwrite command line, you will
55be sending to the recipient "*", so when you use "zwrite -c newclass",
56you are sending a message to <newclass,PERSONAL,username>.
57
58Similarly, every time you request a subscription, you are subscribing
59to a class, an instance, and a recipient.  The recipient must be
60either "*" or your username.  The instance can be any string; however,
61if you subscribe to instance "*", you will receive messages to any
62instance as long as the class and recipient also match.  The class can
63be any string; "*" has no special meaning for class names.  When you
64start zwgc, you are automatically subscribed to
65<MESSAGE,PERSONAL,yourusername> and <MESSAGE,URGENT,yourusername> even
66if you don't explicitly request those subscriptions.
67
68As an example of how you might use these features, at MIT we have
69several frequently-used instances of class MESSAGE, called
70"white-magic", "help", "weather", "tmbg" and so forth.  These are
71commonly known as "public" instances because they are not intended to
72exclude anyone.  Users can subscribe to individual instances using
73"zctl add message help \*", or they can subscribe to all of them at
74once using "zctl add message \* \*".  (If users do this, they can tell
75zwgc to filter out messages from certain instances; see the man page
76for zwgc.)  If users want to have semi-private group conversations,
77they use separate classes, as described earlier.
Note: See TracBrowser for help on using the repository browser.