there are users who do not know that there are other ways to send (and
receive) zephyrgrams. This wiki will cover the traditional commands,
typed at the athena% prompt, as well as the more common modern zephyr
-client Barnowl.
+client BarnOwl.
-The information in this wiki about Barnowl just barely touches the
-surface. More for in-depth functionality, visit the [Barnowl
-wiki](https://barnowl.scripts.mit.edu:444/wiki).
+The information in this wiki about BarnOwl just barely touches the
+surface. More for in-depth functionality, visit the [BarnOwl
+wiki](https://barnowl.mit.edu/).
## Modern Zephyr
### Other Clients
-There are other clients besides Barnowl, however their use is not
+There are other clients besides BarnOwl, however their use is not
nearly as widespread. Some of these include:
-* Owl (unmaintained, Barnowl evolved from this)
+* Owl (unmaintained, BarnOwl evolved from this)
* vt / jervt
* zwgc (see TraditionalZephyr)
* Pidgin
* zephyr-mode for emacs
-Using Barnowl is recommended, as it is better supported and more
+Using BarnOwl is recommended, as it is better supported and more
documentation exists for it.
-### Using Barnowl
+### Using BarnOwl
You will need access to an Athena machine to run barnowl. The easiest
-way to do this would be to SSH into linerva.mit.edu.
+way to do this would be to SSH into linux.mit.edu.
On a Debian-based linux distro, open up a terminal and type `ssh
-<username>@linerva.mit.edu`.
+<username>@linux.mit.edu`.
On Windows, download a SSH client (such as
[PuTTY](http://chiark.greenend.org.uk/~sgtatham/putty/download.html); you will need to [change PuTTY’s character set](http://utf-8.scripts.mit.edu/wiki/PuTTY) to UTF-8 to prevent occasional display glitches.)
-and install it. Once you've opened it, type `<username>@linerva.mit.edu`
+and install it. Once you've opened it, type `<username>@linux.mit.edu`
into the prompt and hit enter.
On a Mac, open Terminal from the Utilities Folder in Applications. Type
`kinit <username>@ATHENA.MIT.EDU && ssh -K
-<username>@linerva.mit.edu` If this command fails (saying -K is
-invalid), then just do `ssh <username>@linerva.mit.edu`.
+<username>@linux.mit.edu` If this command fails (saying -K is
+invalid), then just do `ssh <username>@linux.mit.edu`.
+Alternatively, use a Java applet called Mindterm SSH inside any web browser. MIT makes this available at [athena.dialup.mit.edu](http://athena.dialup.mit.edu/ssh.html); although this will give you an Athena terminal, you may want to ssh from there to linux.mit.edu so as to follow the rest of these instructions exactly:
+
+ athena.dialup.mit.edu login: <username>
+ <username>@athena.dialup.mit.edu's password: <password>
+ (wait a while)
+ <username>@<some-server>:~$ ssh <username>@linux.mit.edu
+ <username>@<other-server>:~$
+
(In all these cases, don't include the angle brackets, just replace
<username> with your MIT username). You will then be prompted for your
password. Enter it, and then carry on with running barnowl!
To start barnowl, run the command `add barnowl; barnowl` at the prompt
-on any Athena machine or dialup, such as linerva.mit.edu.
+on any Athena machine or dialup, such as linux.mit.edu.
The simplest use of Zephyr is to send personal zephyrs to other
users. To send a zephyr, type `:` to bring up a command line, and run
To subscribe to a class, use the subscribe command:
- :subscribe CLASSNAME * *
+ :subscribe CLASSNAME * *
To send a zephyr to a class, use the zwrite command with the -c option:
session to session; you don't want to have to set the same variables
each time. You can fix this by adding the commands to your "startup"
file, for example, `.owl/startup`. This can be done from within
-Barnowl, by using the `startup` command:
+BarnOwl, by using the `startup` command:
:startup set foo bar
Where `foo` is the variable you want to set, and `bar` is the value.
You do not necessarily have to use the `set` command, either, any
-command you can type in Barnowl can be added to the startup file.
+command you can type in BarnOwl can be added to the startup file.
### Logging
### Filters
-Some people like to customize their Barnowl by color-coding classes.
+Some people like to customize their BarnOwl by color-coding classes.
This makes it easier to tell different classes apart (and minimize
-mixing). Barnowl has some already existing filters, for example,
+mixing). BarnOwl has some already existing filters, for example,
`personal` (for incoming personals), `out` (for outgoing personals),
and `ping` (for pings). To assign a color to a filter, add the
following to your startup file:
What if you want to color-code your class, or a friends class? You
can create and color filters with:
- filter johndoe class johndoe
+ filter johndoe class ^johndoe$
filter johndoe -c blue
You can update your settings and filters without restarting your
-Barnowl session by:
+BarnOwl session by:
:source ~/path/to/config/file
For more detailed information on filters, visit
[https://barnowl.scripts.mit.edu:444/wiki/Filters](https://barnowl.scripts.mit.edu:444/wiki/Filters).
-## Running Barnowl in Screen
+## Running BarnOwl in Screen
-It can be very annoying to have to close Barnowl when you turn off
+It can be very annoying to have to close BarnOwl when you turn off
your computer. During the time your computer is off, you're missing
many (possibly important) zephyrs. It can be aggravating to be using
zephyr via an unreliable network connection. It can also be
A more detailed and extensive explanation of this can be found at
[http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt](http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt). Basic commands are [Ctrl-a] followed by [c] to open a new window (like a tab), [Ctrl-a][w] to see a list of open windows, and [Ctrl-a] followed by a number to go to that window.
-Do note that running `owl-screen` as apposed to just runnning `screen` and then a barnowl instance provides niceties such as reminders to renew your tickets (the process /mit/kchen/arch/i386_rhel4/bin/cont-renew-notify). Also, Barnowl will always be located on the `0` tab of an `owl-screen` instance, so [Ctrl-a][0] will always take you back to Barnowl.
+Do note that running `owl-screen` as apposed to just runnning `screen` and then a barnowl instance provides niceties such as reminders to renew your tickets (the process `/mit/kchen/arch/i386_rhel4/bin/cont-renew-notify`). Also, BarnOwl will always be located on the `0` tab of an `owl-screen` instance, so [Ctrl-a][0] will always take you back to BarnOwl.
### Screen
You should find a computer or server on which to run your screen
-session(s) that is up all the time, for example, linerva.mit.edu.
+session(s) that is up all the time, for example, linux.mit.edu.
Screen allows you to run programs inside of it on one computer, and to
access those same programs from other computers via ssh.
kinit -l7d -54
(length 7 days, both Kerberos 5 and Kerberos 4). Press C-a 0 to return
-back to your Barnowl window.
+back to your BarnOwl window.
When you're ready to log out, press C-a d to "detach" your screen, and
then type `exit` or `logout` to log out. Later, when you want to
sipb-www / wiki.git / blobdiff