Return to README CVS log

Up to [CSRG BSD Unix] / 43BSD / contrib / notes

Annotation of 43BSD/contrib/notes/README, revision 1.1

1.1     ! root        1: Notesfiles revison 1.x
        !             2: 
        !             3:        This directory contains a release of the Unix notesfile
        !             4: system as developed at the University of Illinois. The Notesfile 
        !             5: concept was taken from PLATO (trademark CDC), a system developed for
        !             6: CAI applications.
        !             7:        The correct version of this distribution can be
        !             8: found by looking for the string "$Header:" in the src directory.
        !             9: Most files (some documentation files don't) have a version number in them.
        !            10: The file "Revisions" in the src directory lists the version number of each
        !            11: file in that directory.  If you can FTP this code from UIUC.ARPA, you
        !            12: will then be able to grab this particular file to find out what
        !            13: has changed and then selectively grab the modified files.
        !            14: For FTP users, the packed file lives in /pub/Notes.tar on "uiuc.arpa"
        !            15: and the unpacked tree is rooted at /pub/notes.
        !            16: 
        !            17:        The directories here contain:
        !            18: 
        !            19: doc    t/nroff source to the user manual
        !            20: man    t/nroff sources used for man(1)
        !            21: src    The source code for the system.
        !            22: Samples        Some sample files that might make installation a little easier
        !            23: utility        Some utility programs that I have found to be useful. They
        !            24:        are, for the most part, undocumented. You'll have to read the
        !            25:        code to figure out just what they mean.
        !            26: 
        !            27: The code is distributed configured for a 4.2 BSD system with a
        !            28: standard directory structure. Anything else will likely require 
        !            29: changs in the configuration. The best way to do this is to make a copy of
        !            30: the user manual:
        !            31: 
        !            32:        cd doc
        !            33:        make man
        !            34: 
        !            35: and read it. In particular, it tells you what you will have to change to
        !            36: fit the system to your local configuration. The important part is
        !            37: Appendix A which contains a checklist of what you might want to
        !            38: modify to install the package.
        !            39: 
        !            40: 
        !            41: 
        !            42:        Please answer the questions in the file "Answer.this" and return
        !            43: it to me (via computer or U.S. mail, it doesn't matter). I am supposed
        !            44: to keep track of who gets copies of the code, and I imagine not all
        !            45: of the copies will be distributed directly from me.
        !            46: 
        !            47: Problem reports, suggestions and the like will reach me at:
        !            48: 
        !            49:        Ray Essick
        !            50:        222 Digital Computer Laboratory
        !            51:        University of Illinois at Urbana-Champaign
        !            52:        1304 West Springfield Avenue
        !            53:        Urbana, Illinois        61801
        !            54:        (217)-333-7937
        !            55: 
        !            56:        decvax!pur-ee!uiucdcs!essick
        !            57:                harpo!uiucdcs!essick
        !            58:                ihnp4!uiucdcs!essick
        !            59:        essick%[email protected]
        !            60:        [email protected]
        !            61: 

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.