-### Startup
-
-There might be some options that you want to be consistent from
-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:
-
- :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.
-
-### Logging
-
-It is handy to be able to log your conversations so you can refer back
-to them later. To log classes, for example:
-
- :set classlogging on
-
-And to log personals:
-
- :set logging on
-
-This will log to the "zlog" directory in your locker. You probably
-don't want people to see what classes you're on or what people you
-talk to, so you can run the Athena commands
-
- mkdir -p ~/zlog
- fs sa ~/zlog system:anyuser none
- mkdir -p ~/zlog/people
- mkdir -p ~/zlog/class
-
-to create the necessary directories and make them completely hidden.
-
-### Colors
-
-By default, there are seven colors you may use in the terminal: red,
-green, yellow, blue, magenta, cyan, and white. In order to use color
-in Zephyr, you can use the following notation: `@(@color(red)This is
-some red text)`
-
-Colors may vary from machine to machine, as different terminal
-profiles may have different shades of the seven colors.
-
-### Filters
-
-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,
-`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:
-
- filter personal -c green
-
-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 -c blue
-
-You can update your settings and filters without restarting your
-BarnOwl session by:
-
- :source ~/path/to/config/file
-
-You can see all the filters by using `:show filters`, and narrow to a
-particular filter with, e.g., `:view personal`. You can use `:view
-all` or the keyboard shortcut `V` to see all messages again.
-
-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
-
-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
-frustrating if you leave your computer on with Zephyr up, but go to a
-different computer and want to check your zephyrs - how do you do
-this? These problems can be solved with the magic of screen.
-
-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.
-
-### Screen
-
-You should find a computer or server on which to run your screen
-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.
-
-### Quickstart
-
-1. Pick a machine to host your screen session on.
- If you don't know of any options, linux.mit.edu (Linerva) is a good choice.
-2. ssh to that machine.
-3. Run "add kchen". You may want to add this to your `~/.environment` file.
-4. Run "owl-screen"
-
-Your screen session is now ready. Once you start the screen session,
-you'll need to get renewable Kerberos tickets in order to run it for
-any extended period of time. Press C-a C-c to open a new screen
-window, and run
-
- kinit -l7d -54
-
-(length 7 days, both Kerberos 5 and Kerberos 4). Press C-a 0 to return
-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
-"reattach" your screen, ssh to the machine again, and run `screen -r`.
-
-### Kerberos Tickets and AFS Tokens
-
-In order to keep your screen session authenticated, you'll need to
-keep your Kerberos tickets and AFS tokens up-to-date. There is a
-script that will do this for you, located in the `kchen` locker.
-After you ssh into the machine that hosts your screen sessions, run
-the following commands:
-
- add kchen
- owl-screen
- C-a C-c
- kinit -l1d -r7d
-
-### Attaching and Detaching Sessions
-
-To detach a screen session (for example, if you want to log out),
-press C-a d (Control-A, then D). Screen continues to run, but is no
-longer active.
-
-To reattach a screen session, possibly detaching from wherever it's
-currently attached, run:
-
- screen -dr
-
-`screen` can do a whole lot more. To find out about it, see
-[UsingScreen](https://sipb-www.scripts.mit.edu:444/doc/wiki/UsingScreen).