Index: /tags/cereal/0.17-1/COPYING
===================================================================
--- /tags/cereal/0.17-1/COPYING	(revision 946)
+++ /tags/cereal/0.17-1/COPYING	(revision 946)
@@ -0,0 +1,688 @@
+Cereal is a toolset to simply and robustly manage serial consoles.  It
+is free software, written by Jameson Rollins
+<jrollins@fifthhorseman.net> and Daniel Kahn Gillmor
+<dkg-debian.org@fifthhorseman.net>.
+
+Cereal is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+for more details.
+
+Cereal Copyright 2007, and are all released under the GPL, version 3
+or later.
+
+
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
Index: /tags/cereal/0.17-1/Makefile
===================================================================
--- /tags/cereal/0.17-1/Makefile	(revision 946)
+++ /tags/cereal/0.17-1/Makefile	(revision 946)
@@ -0,0 +1,43 @@
+#!/usr/bin/make -f
+
+# Makefile for cereal
+
+# (c) 2007 Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# Licensed under GPL v3 or later
+
+# this makefile is mostly a dummy, but it provides a convenient
+# "install" target for folks who want to install cereal from a
+# standard "source tarball"
+
+PREFIX=/usr
+CONFIGDIR=/etc
+
+all:
+	echo "cereal is composed of scripts, so no compilation is necessary"
+
+install:
+	install -d $(CONFIGDIR)/cereal
+	install -d $(PREFIX)/bin
+	install -d $(PREFIX)/sbin
+	install -d $(PREFIX)/share/cereal
+	install -d $(PREFIX)/share/man/man1
+	install -d $(PREFIX)/share/man/man8
+	install fs/usr/bin/cereal $(PREFIX)/bin/cereal
+	install fs/usr/sbin/cereal-admin $(PREFIX)/sbin/cereal-admin
+	install -m 0644 fs/usr/share/man/man1/cereal.1 $(PREFIX)/share/man/man1/cereal.1
+	install -m 0644 fs/usr/share/man/man8/cereal-admin.8 $(PREFIX)/share/man/man8/cereal-admin.8
+	install fs/usr/share/cereal/*run $(PREFIX)/share/cereal/
+	install -m 0644 fs/usr/share/cereal/common $(PREFIX)/share/cereal/
+	install -m 0644 fs/etc/cereal/cereal-admin.conf $(CONFIGDIR)/cereal/
+	install -m 0644 fs/etc/cereal/screenrc $(CONFIGDIR)/cereal/
+
+# invoke this target like `make VERSION=0.1 release' to build an
+# "upstream tarball" (note: the curly braces are a bashism -- you can
+# only "make release" from bash or an equivalent)
+release:
+	mkdir -p build/upstream
+	ln -s ../.. build/upstream/cereal-$(VERSION)
+	(cd build/upstream && tar czf ../cereal_$(VERSION).tar.gz --exclude=.svn --exclude=*~ cereal-$(VERSION)/{fs,COPYING,Makefile,docs})
+	rm -f build/upstream/cereal-$(VERSION)
+
+clean:
Index: /tags/cereal/0.17-1/TODO
===================================================================
--- /tags/cereal/0.17-1/TODO	(revision 946)
+++ /tags/cereal/0.17-1/TODO	(revision 946)
@@ -0,0 +1,23 @@
+TODO:
+
+see:
+
+http://cmrg.fifthhorseman.net/query?status=new&status=assigned&status=reopened&component=cereal&order=priority
+
+for outstanding enhancement and bug tickets for debirf.
+
+others:
+
+better error reporting.  when things don't start, provide better feedback
+ - need better checking that a given tty is a valid terminal device.
+ - screen often fails with error code=0.  if screen can not attach to a tty, it
+   will silently fail -> MORE SCREEN TO STDOUT/STDERR!!!
+
+add parameters to "cereal-admin list" to allow for tailored output
+
+make sure all scripts run with dash instead of bash for lighter-weight systems.
+
+change logging to some sort of hexdump form, so that the timestamps are
+   reasonable. 
+ - jamie doesn't want to do this.  jamie thinks timestamps are plenty
+   "reasonable" as they are.
Index: /tags/cereal/0.17-1/build/README
===================================================================
--- /tags/cereal/0.17-1/build/README	(revision 946)
+++ /tags/cereal/0.17-1/build/README	(revision 946)
@@ -0,0 +1,3 @@
+This directory is (ab)used by various packaging scripts.  do not place
+things in it unless you are *sure* they won't get clobbered by a
+build process.
Index: /tags/cereal/0.17-1/debian/cereal.postinst
===================================================================
--- /tags/cereal/0.17-1/debian/cereal.postinst	(revision 946)
+++ /tags/cereal/0.17-1/debian/cereal.postinst	(revision 946)
@@ -0,0 +1,22 @@
+#!/bin/sh -e
+
+# postinst script for cereal
+
+# Author: Jamie Rollins <jrollins@fifthhorseman.net> and 
+#         Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# (c) 2007
+
+if ! getent passwd cereal >/dev/null ; then
+    echo "adding cereal user..."
+    adduser --quiet --system --no-create-home --home '/var/lib/cereal' --shell '/bin/false' --gecos 'cereal logfile owner,,,' cereal
+fi
+
+# restart all running sessions
+cereal-admin restart --running
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
Index: /tags/cereal/0.17-1/debian/cereal.postrm
===================================================================
--- /tags/cereal/0.17-1/debian/cereal.postrm	(revision 946)
+++ /tags/cereal/0.17-1/debian/cereal.postrm	(revision 946)
@@ -0,0 +1,22 @@
+#!/bin/sh -e
+
+# postrm script for cereal
+
+# Author: Jamie Rollins <jrollins@fifthhorseman.net> and 
+#         Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# (c) 2007
+
+case $1 in
+    purge)
+	rmdir --ignore-fail-on-non-empty /var/lib/cereal || true
+	echo "removing cereal user..."
+	userdel cereal > /dev/null || true
+	;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
Index: /tags/cereal/0.17-1/debian/cereal.preinst
===================================================================
--- /tags/cereal/0.17-1/debian/cereal.preinst	(revision 946)
+++ /tags/cereal/0.17-1/debian/cereal.preinst	(revision 946)
@@ -0,0 +1,32 @@
+#!/bin/sh -e
+
+# preinst script for cereal
+
+# Author: Jamie Rollins <jrollins@fifthhorseman.net> and 
+#         Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# (c) 2007
+
+# make new sessions dir and move all old sessions into it
+if [ -d /var/lib/cereal/ -a ! -d /var/lib/cereal/sessions ] ; then
+    echo "moving sessions to new session directory /var/lib/cereal/sessions/..."
+
+    # find all active sessions
+    SESSIONS=$(cereal list | cut -d ' ' -f 2)
+
+    mkdir -p /var/lib/cereal/sessions
+
+    for SESSION in $SESSIONS ; do
+	echo "moving '$SESSION'..."
+	mv /var/lib/cereal/"$SESSION" /var/lib/cereal/sessions/"$SESSION"
+	if [ -L "/var/service/cereal.$SESSION" ] ; then
+	    ln -sfn "/var/lib/cereal/sessions/$SESSION" "/var/service/cereal.$SESSION"
+	fi
+    done
+fi
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
Index: /tags/cereal/0.17-1/debian/cereal.prerm
===================================================================
--- /tags/cereal/0.17-1/debian/cereal.prerm	(revision 946)
+++ /tags/cereal/0.17-1/debian/cereal.prerm	(revision 946)
@@ -0,0 +1,14 @@
+#!/bin/sh -e
+
+# prerm script for cereal
+
+# Author: Jamie Rollins <jrollins@fifthhorseman.net> and 
+#         Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# (c) 2007
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
Index: /tags/cereal/0.17-1/debian/changelog
===================================================================
--- /tags/cereal/0.17-1/debian/changelog	(revision 946)
+++ /tags/cereal/0.17-1/debian/changelog	(revision 946)
@@ -0,0 +1,217 @@
+cereal (0.17-1) unstable; urgency=low
+
+  * New Upstream Release:
+  * Allows multiple concurrent connections (closes CMRG #7)
+  * Improved logging of connections (includes connecting pty info)
+  * debian/control: switched Section: back to utils from admin.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Wed, 16 Jan 2008 23:15:12 -0500
+
+cereal (0.16-4) unstable; urgency=low
+
+  * added Vcs-Svn and Vcs-Browser fields to debian/control
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Sun, 13 Jan 2008 14:38:04 -0500
+
+cereal (0.16-3) unstable; urgency=low
+
+  * updated description so that cereal is relevant to "apt-cache search
+    serial console"
+  * bumped Standards-Version to 3.7.3 (no changes needed)
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Fri, 11 Jan 2008 01:41:53 -0500
+
+cereal (0.16-2) unstable; urgency=low
+
+  * switched DM-Upload-Allowed to XS-DM-Upload-Allowed.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Tue, 27 Nov 2007 00:48:44 -0500
+
+cereal (0.16-1) unstable; urgency=low
+
+  * new upstream version
+  * found/fixed a couple lingering GPL v2 references
+  * removed bashisms from "make install" (Closes: #453040)
+  * add DM-Upload-Allowed: yes to debian/control.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Mon, 26 Nov 2007 19:57:48 -0500
+
+cereal (0.15-2) unstable; urgency=low
+
+  * update debian/control with Homepage field.
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 21 Nov 2007 14:05:40 -0500
+
+cereal (0.15-1) unstable; urgency=low
+
+  * change call to sh to be call to bash in cereal-admin start (fix ticket #36)
+  * fix is_controllable function to be more accurate
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 24 Oct 2007 15:47:49 -0400
+
+cereal (0.14-2) unstable; urgency=low
+
+  * fix to cereal.preinst script to properly upgrade from older versions
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Mon, 15 Oct 2007 12:03:59 -0400
+
+cereal (0.14-1) unstable; urgency=low
+
+  * overhaul/simplification of listing function
+  * overhaul/simplification of error reporting
+  * added log-limiting documentation and mention in cereal-admin man page
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Fri, 12 Oct 2007 01:35:47 -0400
+
+cereal (0.13-3) unstable; urgency=low
+
+  * added var/lib/cereal/sessions to debian/dirs to fix ticket #33
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Thu, 11 Oct 2007 20:55:20 -0400
+
+cereal (0.13-2) unstable; urgency=low
+
+  * added gecos field for cereal user
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 10 Oct 2007 18:27:42 -0400
+
+cereal (0.13-1) unstable; urgency=low
+
+  * update of is_running function with better tests/return
+  * moved session directory to /var/lib/cereal/sessions
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Tue, 09 Oct 2007 22:35:52 -0400
+
+cereal (0.12-1) unstable; urgency=high
+
+  * fixed bug where bin/cereal had not been updated with new function to check
+    whether session was linked, causing bin/cereal to not allow session
+    connection.
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Mon, 03 Sep 2007 13:12:47 -0400
+
+cereal (0.11-1) unstable; urgency=low
+
+  * scripts now use bash instead of sh because we haven't audited for
+    POSIX-compliance.
+  * cleaned up licensing so all files now refer to GPL v3 or later instead
+    of v2.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Sun, 02 Sep 2007 15:38:42 -0400
+
+cereal (0.10-1) unstable; urgency=low
+
+  * added new SFLAG ('!') for linked running sessions, at least for users that
+    can read the supervise/stat file (closes ticket #30).  man fixed as well.
+  * added new /etc/cereal/cereal-admin.conf to control whether or not to make 
+    the supervise directory world accessible or not.
+  * relicense to GPLv3
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Sun, 02 Sep 2007 15:01:03 -0400
+
+cereal (0.9-1) unstable; urgency=low
+
+  * changed possible return value for "restart --running" per dkg's request
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 16 May 2007 12:28:14 -0400
+  
+cereal (0.8-2) unstable; urgency=low
+
+  * fixed postinst script to not fail if there are no sessions running.
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 16 May 2007 09:59:07 -0400
+
+cereal (0.8-1) unstable; urgency=low
+
+  * renamed many of the sub-command (enable->start, disable->stop, 
+    remove->destroy).
+  * added new "restart" subcommand.
+  * changed postinst script to restart enabled sessions.
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Tue, 15 May 2007 01:18:11 -0400
+
+cereal (0.7-1) unstable; urgency=low
+
+  * attempt to fix (patch?) bug during cereal-admin enable (ticket #24)
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Fri, 11 May 2007 01:44:34 -0400
+
+cereal (0.6-1) unstable; urgency=low
+
+  * fixing bugs: the second cereal console creation was failing. 
+  * limited more features in screen, updated man page to match
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Thu, 10 May 2007 21:58:11 -0400
+
+cereal (0.5-1) unstable; urgency=low
+
+  * added log_write function
+  * update default screenrc
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Thu, 19 Apr 2007 14:00:47 -0400
+
+cereal (0.4-1) unstable; urgency=low
+
+  * added restrictions that prevent opening new windows or executing external
+    commands in attached screen sessions
+  * improved look/feel of cereal screen session
+  * expanded default screenrc
+  * added more documentation
+  * improved cereal follow command, added output options
+  * added options to enable/disable/remove all sessions with cereal-admin
+  * more cereal output to log files (maybe even more would be better)
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Sun,  1 Apr 2007 16:37:59 -0400
+
+cereal (0.3-3) unstable; urgency=low
+
+  * added debian/dirs to make sure all the directories are properly
+    created initially.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Fri, 30 Mar 2007 02:03:22 -0400
+
+cereal (0.3-2) unstable; urgency=low
+
+  * added adduser as a dependency for postinst script.
+  * added #DEBHELPER# tags in post{inst,rm} scripts.
+    (thanks to lintian for catching these!)
+  * switched postrm from deluser to userdel (see
+    http://lists.debian.org/debian-release/2007/01/msg01014.html)
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Fri, 30 Mar 2007 00:53:53 -0400
+
+cereal (0.3-1) unstable; urgency=low
+
+  * New upstream version
+  * fixed broken path to common file.
+  * GROUP and LOGUSER now determined by cereal-admin (new 'cereal' system user)
+  * updated all functions to reflect new GROUP/LOGUSER specifications
+  * added flags in session display, tweaked display
+  * added subcommands to cereal script, including primitive log reader
+  * code clean-up/simplification
+  * added post{inst,rm} scripts (add/del cereal user)
+  * added check against tty already being monitored by different session
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Wed, 28 Mar 2007 01:19:52 -0400
+
+cereal (0.2-2) unstable; urgency=low
+
+  * fixed debian/control to build for *all* archs, instead of "any"
+  * add jrollins to "Uploaders" in debian/control
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Sat, 24 Mar 2007 17:17:29 -0400
+
+cereal (0.2-1) unstable; urgency=low
+
+  * New upstream version
+  * added copyright and licensing information to all files.
+  * reorganized build scripts, using upstream makefile for installation.
+
+ -- Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>  Sat, 24 Mar 2007 14:15:53 -0400
+
+cereal (0.1-1) unstable; urgency=low
+
+  * initial version of debian package.
+
+ -- Jameson Rollins <jrollins@fifthhorseman.net>  Sat, 17 Mar 2007 15:41:56 -0400
+
Index: /tags/cereal/0.17-1/debian/compat
===================================================================
--- /tags/cereal/0.17-1/debian/compat	(revision 946)
+++ /tags/cereal/0.17-1/debian/compat	(revision 946)
@@ -0,0 +1,1 @@
+5
Index: /tags/cereal/0.17-1/debian/control
===================================================================
--- /tags/cereal/0.17-1/debian/control	(revision 946)
+++ /tags/cereal/0.17-1/debian/control	(revision 946)
@@ -0,0 +1,27 @@
+Source: cereal
+Section: utils
+Priority: extra
+Maintainer: Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+Uploaders: Jameson Rollins <jrollins@fifthhorseman.net>
+Build-Depends: debhelper (>= 5.0)
+Standards-Version: 3.7.3
+Homepage: http://cmrg.fifthhorseman.net/wiki/cereal
+Vcs-Svn: http://cmrg.fifthhorseman.net/svn/trunk/cereal
+Vcs-Browser: http://cmrg.fifthhorseman.net/browser/trunk/cereal
+XS-Dm-Upload-Allowed: yes
+
+Package: cereal
+Architecture: all
+Depends: runit, screen, adduser
+Description: automated, logged serial terminal management system
+ cereal provides a framework to easily set up and maintain automated,
+ timestamped logs of serial lines, while simultaneously allowing end
+ user access to them.  This is probably most useful for providing
+ automated, logged access to remote serial consoles.  
+ .
+ cereal can control an arbitrary number of independently monitored and
+ logged lines.  Direct access to the monitored lines is allowed only
+ to a specific user (who doesn't necessarily otherwise have access to
+ the direct serial line), but logs can be made available to any group.
+ Logs are rotated automatically and their total space can be limited
+ in size.
Index: /tags/cereal/0.17-1/debian/copyright
===================================================================
--- /tags/cereal/0.17-1/debian/copyright	(revision 946)
+++ /tags/cereal/0.17-1/debian/copyright	(revision 946)
@@ -0,0 +1,12 @@
+This package was debianized by Daniel Kahn Gillmor
+<dkg-debian.org@fifthhorseman.net> on Thu, 15 Mar 2007 01:12:29 -0400.
+
+It was downloaded from http://cmrg.fifthhorseman.net/wiki/cereal
+
+Upstream Authors: Jameson Rollins <jrollins@fifthhorseman.net> and 
+     Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+
+Copyright: 2007 Daniel Kahn Gillmor and Jameson Rollins
+
+License: cereal is distributed under the GNU GPL v3 or later
+ (see /usr/share/common-licenses/GPL) 
Index: /tags/cereal/0.17-1/debian/dirs
===================================================================
--- /tags/cereal/0.17-1/debian/dirs	(revision 946)
+++ /tags/cereal/0.17-1/debian/dirs	(revision 946)
@@ -0,0 +1,10 @@
+var/lib/cereal
+var/lib/cereal/sessions
+usr/bin
+usr/sbin
+usr/share
+usr/share/cereal
+usr/share/man
+usr/share/man/man8
+usr/share/man/man1
+etc/cereal
Index: /tags/cereal/0.17-1/debian/docs
===================================================================
--- /tags/cereal/0.17-1/debian/docs	(revision 946)
+++ /tags/cereal/0.17-1/debian/docs	(revision 946)
@@ -0,0 +1,4 @@
+docs/example-cereal-setup.txt
+docs/log-limits.txt
+docs/cereal-intro.html
+docs/style.howtos.css
Index: /tags/cereal/0.17-1/debian/rules
===================================================================
--- /tags/cereal/0.17-1/debian/rules	(revision 946)
+++ /tags/cereal/0.17-1/debian/rules	(revision 946)
@@ -0,0 +1,44 @@
+#!/usr/bin/make -f
+# -*- makefile -*-
+# cereal makefile for debian packaging
+#
+# (C) 2007 by Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>
+# 
+# This file is released under the GPL, v3 or later
+# (see /usr/share/common-licenses/GPL)
+
+# not much to do here, since we're just moving some shell scripts
+# around.
+
+build:
+
+binary: binary-arch binary-indep
+
+binary-arch: build
+
+install:
+	dh_testdir
+	dh_testroot
+	dh_clean -k 
+	dh_installdirs
+
+	$(MAKE) install PREFIX=$(CURDIR)/debian/cereal/usr CONFIGDIR=$(CURDIR)/debian/cereal/etc
+
+binary-indep: build install
+	dh_testdir
+	dh_testroot
+	dh_installchangelogs 
+	dh_installdocs
+	dh_installexamples
+	dh_installman
+	dh_compress
+	dh_fixperms
+	dh_installdeb
+	dh_gencontrol
+	dh_md5sums
+	dh_builddeb
+
+clean:
+	dh_testdir
+	dh_testroot
+	dh_clean 
Index: /tags/cereal/0.17-1/docs/cereal-intro.html
===================================================================
--- /tags/cereal/0.17-1/docs/cereal-intro.html	(revision 946)
+++ /tags/cereal/0.17-1/docs/cereal-intro.html	(revision 946)
@@ -0,0 +1,332 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-15">
+<title>Introduction to Cereal - the serial line management tool</title>
+<link rel="stylesheet" type="text/css" href="style.howtos.css" />
+</head>
+
+<body>
+<h1>Introduction to Cereal - the serial line management tool</h1>
+
+<p>Many people view serial ports as antiquated, out-dated connectors
+taking up space on their computers.  However, serial ports still offer
+one of the best ways to communicate reliably and simply with a
+machine.  For example, a serial port can be configured to act as a
+full-featured system console.  This article describes how you can use
+<a href="http://cmrg.fifthhorseman.net/wiki/cereal">cereal</a> to
+monitor, log, and control access to serial lines connected to the
+consoles of other computers.
+
+<p>A computer today has several subsystems that <a title="The Remote
+Serial Console HOWTO"
+href="http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/">should be
+run over the serial port to make it a full-featured system
+console</a>:
+
+<ul> <li>most modern operating systems (including the GNU/Linux
+utilities favored by Debian), are able to provide login terminals on
+serial ports,</li> <li>most modern kernels (including Linux) are
+capable of directing their console I/O to a serial line,</li> <li>most
+bootloaders (including stalwarts like <a
+href="http://www.gnu.org/software/grub/">GRUB</a>, <a
+href="http://syslinux.zytor.com/">the SYSLINUX family</a>, and <a
+href="http://lilo.go.dyndns.org/">LILO</a>) can communicate via serial
+ports,</li> <li>and many BIOSs, including <a title="SuperMicro
+example"
+href="http://www.supermicro.com/manuals/motherboard/nForce2200/MNL-H8DCE.pdf">most</a>
+<a title="HP"
+href="ftp://ftp.compaq.com/pub/products/servers/management/smartstart/bios-serialconsole.pdf">modern</a>
+<a title="Intel example"
+href="ftp://download.intel.com/support/motherboards/server/isp1100/configsc.pdf">server</a>
+<a title="Dell"
+href="http://www.dell.com/content/topics/global.aspx/power/en/ps1q03_stanton?c=us&cs=555&l=en&s=biz">BIOSs</a>,
+can be redirected over the serial port.</li> </ul>
+
+<p>Using a null-modem cable, you can connect the primary serial port
+on one computer to a remote computer's spare serial port.  The remote
+computer can have full access to the first machine's console using
+only a terminal emulator like <a
+href="http://www.gnu.org/software/screen/">GNU screen</a> or <a
+href="http://alioth.debian.org/projects/minicom/">minicom</a>.  Not
+only do you not need yet another cumbersome monitor and keyboard, but
+you get a digital text stream to manipulate directly.  You can log,
+timestamp, copy, paste, diff, etc the entire data stream flowing over
+the console, including boot-time spew, kernel crash output, etc.
+
+<p>Using serial ports as system consoles is especially useful in
+high-density computing environments, such as racks in data centers.
+Clutter like monitors, vga cables, video cards, keyboards, keyboard
+cables, and kvm switches can all be thrown out in favor of serial
+cables and a single computer that we will refer to as a <i>serial
+console server</i>.  A serial console server is a machine with <a
+href="http://www.lavalink.com/index.php?id=232">many serial ports</a>,
+each connected to the serial console of another machine.  An
+administrator accesses the serial console server over the network
+(e.g. via ssh) and from there can connect to the console of any of the
+connected machines.  In all examples below, <q><tt>scs</tt></q> is the
+hostname of a serial console server.
+
+<p>This is where <a
+href="http://cmrg.fifthhorseman.net/wiki/cereal"><tt>cereal</tt></a>
+comes in.  <tt>cereal</tt> is a management framework designed to
+monitor, log, and control access to serial lines.  It is installed on
+the serial console server, and makes the task of maintaining such a
+machine simpler.  It can also be used in simpler configurations, such
+as two machines which each monitor the other's console.  This article
+describes how to setup and use <tt>cereal</tt>.  We assume that the
+computers you are connecting to are already configured to send their
+consoles over the serial line.  If that's not the case yet, read <a
+href="http://tldp.org/HOWTO/Remote-Serial-Console-HOWTO/">The Remote
+Serial Console HOWTO</a> and get 'em configured first!
+
+<p>The <tt>cereal</tt> utility is <a title="bug #440565: ITP: cereal"
+href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440565">not yet
+available in Debian proper</a>, but it is packaged and available from
+the <a href="http://cmrg.fifthhorseman.net/">CMRG</a> <a
+href="http://cmrg.fifthhorseman.net/debian/">APT repository</a>.  Once
+you've added this repository to your <tt>sources.list</tt> (you may
+want to <a
+href="http://cmrg.fifthhorseman.net/wiki/apt/importing-keys">update
+your <tt>apt</tt> keys</a> if you care to about verifying packages
+from the repo), you can pull it with <tt>apt-get</tt> or
+<tt>aptitude</tt>:
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">echo deb http://cmrg.fifthhorseman.net/debian unstable cereal &gt;&gt; /etc/apt/sources.list.d/cereal.list</span>
+<span class="prompt">scs:0:~#</span> <span class="input">aptitude update</span>
+<span class="prompt">scs:0:~#</span> <span class="input">aptitude install cereal</span>
+</pre>
+
+<h2>Administering <tt>cereal</tt> sessions: <tt>/usr/sbin/cereal-admin</tt></h2>
+
+<p>Serial line management with <tt>cereal</tt> is broken out into
+<i>sessions</i>.  A <tt>cereal</tt> session is a single <a
+href="http://smarden.org/runit/">runit</a> service controlling a
+special <tt>screen</tt> session attached to a single serial line.
+Creation and control of these sessions is done with the
+<i><tt>cereal-admin</tt></i> utility:
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin help</span>
+Usage: cereal-admin <subcommand> [options] [args]
+Cereal session management program.
+
+subcommands:
+  create (c) SESSION TTY BAUD USER LOGGROUP    create cereal session
+  start (s) [options] SESSION [SESSION]...     start cereal session(s)
+    -a (--all)                                   start all sessions
+  stop (k) [options] SESSION [SESSION]...      stop cereal session(s)
+    -a (--all)                                   stop all sessions
+  restart (r) [options] SESSION [SESSION]...   restart cereal session(s)
+    -a (--all)                                   restart all sessions
+    -r (--running)                               restart any currently running
+                                                  sessions 
+  destroy (d) [options] SESSION [SESSION]...   destroy cereal session(s)
+    -a (--all)                                   destroy all sessions
+  list (l) [SESSION]...                        list session(s)
+  help (h,?)                                   this help
+
+<span class="prompt">scs:0:~#</span>
+</pre>
+
+<h3>Creating a <tt>cereal</tt> session</h3>
+
+<p>Let's assume the first computer whose serial console you want to
+monitor with cereal is called <q><tt>lemur</tt></q>.  Let's assume
+<tt>lemur</tt>'s serial console is configured with baud rate 115200,
+and is connected to the serial console server on <tt>/dev/ttyS1</tt>
+(<tt>/dev/ttyS0</tt> on <tt>scs</tt> is of course reserved for the
+serial console server's own serial console!).
+
+<p>You can give access to <tt>cereal</tt> sessions, and the ability to
+read the session logs, to existing users.  However, it is often a good
+idea to create new users and groups for these purposes.  We begin by
+creating a new group that will be allowed to view ('follow')
+<tt>lemur</tt>'s serial console logs, followed by creating a new user
+that will be able to control ('attach' to) lemur's cereal session.
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">addgroup lemurviewers</span>
+Adding group `lemurviewers' (GID 1001) ...
+Done.
+
+<span class="prompt">scs:0:~#</span> <span class="input">adduser --ingroup lemurviewers --gecos 'lemur cereal session admin,,,' lemuradmin</span>
+Adding user `lemuradmin' ...
+Adding new user `lemuradmin' (1001) with group `lemurviewers' ...
+Creating home directory `/home/lemuradmin' ...
+Copying files from `/etc/skel' ...
+
+<span class="prompt">scs:0:~#</span>
+</pre>
+
+<p>You are now ready to create <tt>lemur</tt>'s <tt>cereal</tt>
+session with <tt>cereal-admin</tt>:
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin create lemur /dev/ttyS1 115200 lemuradmin lemurviewers</span>
+Created session 'lemur':
+--f lemur /dev/ttyS1 115200 lemuradmin lemurviewers
+<span class="prompt">scs:0:~#</span>
+</pre>
+
+<p>The first three characters of the session status line are the
+session flags that indicate the state of the cereal session.  In
+order, they are:
+
+<dl><dt>state</dt> <dd>The first flag indicates whether the session is
+running (+) or not (-), or in some unusual state (!). </dd>
+<dt>attach</dt> <dd>The second flag indicates whether the user can
+attach to the session (a) or not (-).</dd> <dt>follow</dt> <dd>The
+third flag indicates whether the user can follow the session (f) or
+not (-).</dd> </dl>
+
+<p>Once a <tt>cereal</tt> session is created, you can begin monitoring
+of it with the <q><tt>cereal-admin start</tt></q> command:
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin list lemur</span>
+--f lemur /dev/ttyS1 115200 lemuradmin lemurviewers
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin start lemur</span>
+Started session 'lemur'.
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin list lemur</span>
++-f lemur /dev/ttyS1 115200 lemuradmin lemurviewers
+<span class="prompt">scs:0:~#</span>
+</pre>
+
+<h2>Accessing <tt>cereal</tt> sessions: <tt>/usr/bin/cereal</tt></h2>
+
+<p>Now that you have a cereal session up and running, you can test the
+connection.  Log into <tt>scs</tt> as the non-privileged
+<tt>lemuradmin</tt> user and use the <tt>cereal</tt> tool to attach to
+or follow the session:
+
+<pre class="console">
+<span class="prompt">lemuradmin@scs:~$</span> <span class="input">cereal help</span>
+Usage: cereal <subcommand> [options] [args]
+Cereal client program.
+
+subcommands:
+  attach (a) SESSION                      attach to session
+  follow (f) [options] SESSION            follow session log
+    -c (--cat)                              cat log instead of follow
+    -p (--path)                             output just log file path
+  list (l) [SESSION]...                   list session(s)
+  help (h,?)                              this help
+
+<span class="prompt">lemuradmin@scs:~$</span> <span class="input">cereal list lemur</span>
++af lemur /dev/ttyS1 115200 lemuradmin lemurviewers
+<span class="prompt">lemuradmin@scs:~$</span>
+</pre>
+
+<h3>Attaching to a <tt>cereal</tt> session</h3>
+
+<p>Using the attach function will put the the user into a
+<tt>cereal</tt> console, provided by a command-restricted
+<tt>screen</tt> session.  To detach from an attached session, use "C-\
+d".  For help on other available commands, use "C-\ ?".
+
+<pre class="console">
+<span class="prompt">lemuradmin@scs:~$</span> <span class="input">cereal attach lemur</span>
+</pre>
+
+<pre class="console">
+Debian GNU/Linux 4.0 lemur ttyS0
+
+lemur login: root
+Password: 
+Last login: Sat Oct  6 10:16:26 2007 on ttyS0
+Linux lemur 2.6.18-5-amd64 #1 SMP Tue Oct 2 20:37:02 UTC 2007 x86_64
+
+The programs included with the Debian GNU/Linux system are free software;
+the exact distribution terms for each program are described in the
+individual files in /usr/share/doc/*/copyright.
+
+Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
+permitted by applicable law.
+<span class="prompt">lemur:0:~#</span> <span class="input">exit</span>
+
+
+
+
+<span style="background: blue; color: white;"><b>cereal console: <span
+style="color: yellow;">lemur</span></b>              2007-10-06 10:17              "C-\ d" to detach</span>
+</pre>
+
+<pre class="console">
+<span class="prompt">lemuradmin@scs:~$</span> <span class="input">cereal attach lemur</span>
+[detached]
+<span class="prompt">lemuradmin@scs:~$</span>
+</pre>
+
+<h3>Following a <tt>cereal</tt> session</h3>
+
+<p>You can use the <i>follow</i> command to easily view the logs of a
+cereal session.
+
+<pre class="console">
+<span class="prompt">lemuradmin@scs:~$</span> <span class="input">cereal follow --cat lemur | cat -A</span>
+############################################################
+### cereal log: lemur
+### +af lemur /dev/ttyS1 115200 lemuradmin lemurviewers
+### log file: /var/lib/cereal/sessions/lemur/log/main/current
+############################################################
+2007-10-06_14:39:44.56895 
+2007-10-06_14:39:44.56900 cereal: session 'lemur' started.
+2007-10-06_14:39:44.56900 starting screen session...
+2007-10-06_14:39:58.86707 
+2007-10-06_14:39:58.86708 cereal: user 'lemuradmin' attaching to session...
+2007-10-06_14:40:02.57346 
+2007-10-06_14:40:02.57348 Debian GNU/Linux 4.0 lemur ttyS0
+2007-10-06_14:40:02.57348 
+2007-10-06_14:40:02.57349 lemur login: root
+2007-10-06_14:40:13.58131 Password: 
+2007-10-06_14:40:14.58129 Last login: Sat Oct  6 10:16:48 2007 on ttyS0
+2007-10-06_14:40:14.58129 Linux lemur 2.6.18-5-amd64 #1 SMP Tue Oct 2 20:37:02 UTC 2007 x86_64
+2007-10-06_14:40:14.58130 
+2007-10-06_14:40:14.58131 The programs included with the Debian GNU/Linux system are free software;
+2007-10-06_14:40:14.58131 the exact distribution terms for each program are described in the
+2007-10-06_14:40:14.58132 individual files in /usr/share/doc/*/copyright.
+2007-10-06_14:40:14.58132 
+2007-10-06_14:40:14.58133 Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
+2007-10-06_14:40:14.58134 permitted by applicable law.
+2007-10-06_14:40:14.58135 Last was Sat 06 Oct 2007 10:33:15 AM EDT on ttyS0.
+2007-10-06_14:40:14.58135 ESC[31;1mlemur:0:~#ESC[0m exit
+2007-10-06_14:40:17.58525 logout
+2007-10-06_14:40:17.58525 ESC[HESC[J
+2007-10-06_14:40:18.58523 Debian GNU/Linux 4.0 lemur ttyS0
+2007-10-06_14:40:18.58523 
+2007-10-06_14:40:18.58524 lemur login: 
+2007-10-06_14:40:19.62101 cereal: user 'lemuradmin' detached from session.
+<span class="prompt">lemuradmin@scs:~$</span>
+</pre>
+
+<h2>Conclusion</h2>
+
+<p>Now that you've created your first cereal session, you're ready to
+create serial sessions for all the rest of the attached serial
+consoles:
+
+<pre class="console">
+<span class="prompt">scs:0:~#</span> <span class="input">cereal-admin list</span>
++-f lemur /dev/ttyS1 115200 lemuradmin lemurviewers
++-f chimp /dev/ttyS2 115200 chimpadmin chimpviewers
++-f douc /dev/ttyS3 115200 doucadmin doucviewers
++-f galago /dev/ttyS4 115200 galagoadmin galagoviewers
++-f baboon /dev/ttyS5 115200 baboonadmin baboonviewers
+...
+<span class="prompt">scs:0:~#</span>
+</pre>
+
+<p>Cereal is developed and maintained by <a
+href="http://cmrg.fifthhorseman.net">CMRG</a>.  Hopefully the package
+<a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440565">will
+be included in Debian soon</a>, at which point bug tracking will be
+handled in the Debian BTS.  Until then, please send all bug reports,
+questions, and suggestions to <a href="mailto:cereal AT
+fifthhorseman.net">cereal AT fifthhorseman.net</a>.
+
+<hr>
+<address></address>
+<!-- hhmts start -->Last modified: Mon Oct 15 13:27:18 EDT 2007 <!-- hhmts end -->
+</body> </html>
Index: /tags/cereal/0.17-1/docs/example-cereal-setup.txt
===================================================================
--- /tags/cereal/0.17-1/docs/example-cereal-setup.txt	(revision 946)
+++ /tags/cereal/0.17-1/docs/example-cereal-setup.txt	(revision 946)
@@ -0,0 +1,36 @@
+Using Cereal for simple serial console access
+---------------------------------------------
+
+Here is a common way to set up cereal.
+
+The assumption here is that the second serial port on one machine
+(galago) is connected to the serial console of another host (douc).
+
+## begin by creating on galago a group which can view the logs from douc, but
+## can't necessarily attach to douc's serial console:
+0 galago:~# addgroup doucviewers
+Adding group `doucviewers' (GID 1001) ...
+Done.
+
+## create a separate user account who will control douc (and can attach):
+0 galago:~# adduser --ingroup doucviewers --disabled-password --gecos 'douc console controller,,,' doucconsole
+Adding user `doucconsole' ...
+Adding new user `doucconsole' (1001) with group `doucviewers' ...
+Creating home directory `/home/doucconsole' ...
+Copying files from `/etc/skel' ...
+
+## set up access for that user with ssh keys (here we just use the
+## same keypairs that can already connect to root):
+0 galago:~# cat ~/.ssh/authorized_keys >> ~doucconsole/.ssh/authorized_keys 
+
+## set up the cereal session itself:
+0 galago:~# cereal-admin create douc /dev/ttyS1 115200 doucconsole doucviewers
+Created session 'douc'.
+0 galago:~# cereal-admin list douc
+--f douc /dev/ttyS1 115200 doucconsole doucviewers
+0 galago:~# cereal-admin enable douc
+Enabled session 'douc'.
+0 galago:~# cereal-admin list douc
++-f douc /dev/ttyS1 115200 doucconsole doucviewers
+0 galago:~# 
+
Index: /tags/cereal/0.17-1/docs/log-limits.txt
===================================================================
--- /tags/cereal/0.17-1/docs/log-limits.txt	(revision 946)
+++ /tags/cereal/0.17-1/docs/log-limits.txt	(revision 946)
@@ -0,0 +1,23 @@
+Limiting log files in cereal
+----------------------------
+
+Cereal is controlled by runit, so the cereal log files are controlled
+by the svlogd daemon.
+
+Limiting the log files for session 'foo' is done by placing a svlogd
+configuration file in the log directory for session 'foo':
+
+/var/lib/cereal/sessions/foo/log/main/config
+
+By default, svlogd keeps 10 old logfiles around with 1000000 bytes
+(1MB) in each.  If you wanted to keep 15 logfiles around with 2000000
+bytes in each, you would do:
+
+scs:0:~# cat > /var/lib/cereal/sessions/foo/log/main/config <<EOF
+# limit to 15 log files of 2MB each:
+s2000000
+n15
+EOF
+scs:0:~# 
+
+See 'man svlogd' for more funky config options. 
Index: /tags/cereal/0.17-1/docs/style.howtos.css
===================================================================
--- /tags/cereal/0.17-1/docs/style.howtos.css	(revision 946)
+++ /tags/cereal/0.17-1/docs/style.howtos.css	(revision 946)
@@ -0,0 +1,36 @@
+/* CSS stylesheet for how-tos */
+
+BODY { 
+  color: black; 
+  background: #cccccc; 
+}
+
+pre.console { 
+  background: black; 
+  color: #0f0; 
+  border: thin solid blue;
+  padding: 0.5em; 
+  margin: 0.5em;
+  overflow: auto; 
+}
+pre.console .prompt { color: #f00; }
+pre.console .input { color: white; font-weight: bold; }
+pre.console .input-hidden { color: silver; }
+DT { font-weight: bold; }
+
+pre.file {
+  font-weight: bold;
+}
+pre.snippet { 
+  background: white; 
+  color: black;
+  border: thin dashed blue; 
+  padding: 1em; 
+  margin: 0.5em;
+  overflow: auto;
+}
+pre.snippet .comment { color: green; }
+
+img { border: thick solid black; }
+
+#input-hidden-example { background: black; color: silver; font-family: monospace; padding: 0.5em; }
Index: /tags/cereal/0.17-1/fs/etc/cereal/cereal-admin.conf
===================================================================
--- /tags/cereal/0.17-1/fs/etc/cereal/cereal-admin.conf	(revision 946)
+++ /tags/cereal/0.17-1/fs/etc/cereal/cereal-admin.conf	(revision 946)
@@ -0,0 +1,7 @@
+# /etc/cereal/cereal-admin.conf
+
+# If set to 'yes', create sessions with world accessbile supervise directory.
+# This lets all users test the running state of linked sessions.  However, this
+# may be a security vulnerability on systems that do not respect FIFO file
+# permissions.
+SUPERVISE_WORLD_ACCESSIBLE=yes
Index: /tags/cereal/0.17-1/fs/etc/cereal/screenrc
===================================================================
--- /tags/cereal/0.17-1/fs/etc/cereal/screenrc	(revision 946)
+++ /tags/cereal/0.17-1/fs/etc/cereal/screenrc	(revision 946)
@@ -0,0 +1,91 @@
+# default screenrc file for cereal screen sessions
+
+#############################################################
+### IMPORTANT CEREAL SETTINGS BELOW.  MODIFY WITH CAUTION ###
+
+# use C-\ as the escape character
+escape \034\034
+
+# necessary for cereal logging to work properly
+logfile ./socket
+logfile flush 1
+
+# unset important key bindings
+## prevent external command execution
+bind :
+## prevent opening new windows
+bind c
+bind ^c
+## prevent ability to turn off logging
+bind H
+## prevent terminal reset
+bind Z
+## unset kill commands, sincepreference is to "detach")
+## (should unset "quit" too, or is it useful to have a backup "kill"?)
+bind ^k
+bind k
+bind K
+bind \
+bind \\
+bind ^\
+## no lockscreen:
+bind ^x
+bind x
+## no monitor, prev, next:
+bind M
+bind ^@
+bind n
+bind ^N
+bind ' ' 
+bind ^H
+bind ^P
+bind p
+bind ^?
+# no number:
+bind N
+# no clear:
+bind C
+# no displays or dumptermcap:
+bind *
+bind .
+# no window switching:
+bind -
+bind 0
+bind 1
+bind 2
+bind 3
+bind 4
+bind 5
+bind 6
+bind 7
+bind 8
+bind 9
+## no window splitting:
+bind S
+# no title change
+bind A
+# no remove
+bind X
+# no windows:
+bind ^w
+bind w
+# no suspend:
+bind ^z
+# no focus:
+bind ^i
+# no windowlist:
+bind \"
+
+# set default shell to be /bin/false
+# this is a little redundant with unsetting the create new window keys
+shell /bin/false
+
+# set a nice, informative caption
+#caption always "%{= bw}%f %{+b w}cereal console %{-b}(\"C-\ d\" to detach) %= %{+b y}%t%{-b w} %= %Y-%m-%d %c"
+caption always "%{= bw}%f %{+b w}cereal console: %{+b y}%t%{-b w} %= %Y-%m-%d %c %= %{-b}\"C-\ d\" to detach"
+
+startup_message off
+defscrollback 1024
+
+### IMPORTANT CEREAL SETTINGS ABOVE.  MODIFY WITH CAUTOIN ###
+#############################################################
Index: /tags/cereal/0.17-1/fs/usr/bin/cereal
===================================================================
--- /tags/cereal/0.17-1/fs/usr/bin/cereal	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/bin/cereal	(revision 946)
@@ -0,0 +1,151 @@
+#!/bin/bash
+
+# cereal: command line interface to cereal screen serial loggers
+#
+# The cereal scripts were written by
+# Jameson Rollins <jrollins@fifthhorseman.net>
+# and
+# Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>.
+#
+# They are Copyright 2007, and are all released under the GPL, version 3
+# or later.
+
+##################################################
+CMD=$(basename $0)
+
+SHAREDIR=${SHAREDIR:-"/usr/share/cereal"}
+export SHAREDIR
+source "$SHAREDIR/common"
+##################################################
+
+function usage {
+cat <<EOF
+Usage: $CMD <subcommand> [options] [args]
+Cereal client program.
+
+subcommands:
+  attach (a) SESSION                      attach to session
+  follow (f) [options] SESSION            follow session log
+    -c (--cat)                              cat log instead of follow
+    -p (--path)                             output just log file path
+  list (l) [options] [SESSION]...         list session(s)
+    -n (--names)                            list just session names
+  help (h,?)                              this help
+
+EOF
+}
+
+attach() {
+    SESSION="$1"
+
+    if [ -z "$SESSION" ] ; then
+	failure "Not enough input arguments.  Type '$CMD help' for more info."
+    elif ! is_session "$SESSION" ; then
+	failure "Session '$SESSION' not found.
+Type 'cereal list' to list sessions."
+    elif ! is_running "$SESSION" ; then
+	failure "Session '$SESSION' not running."
+    elif ! can_attach "$SESSION" "$USER" ; then
+	failure "You are not allowed to attach to session '$SESSION'."
+    fi
+
+    log_write "$SESSION" "user '$USER' attaching to session from `tty`..."
+    screen -x -S "cereal:$SESSION" || failure "Could not reattach screen."
+    log_write "$SESSION" "user '$USER' on `tty` detached from session."
+}
+
+log_follow() {
+    tail -n 100 -F "$LOG"
+}
+export -f log_follow
+
+log_cat() {
+    cat "$LOG"
+}
+export -f log_cat
+
+log_pwd() {
+    echo "$LOG"
+}
+export -f log_pwd
+
+follow() {
+    local SESSION TEMP
+    local OUTPUT="log_follow"
+
+    TEMP=$(getopt -o cp --long cat,path -n "$CMD follow" -- "$@")
+    if (( $? != 0 )) ; then
+	failure "Invalid options."
+    fi
+
+    # Note the quotes around `$TEMP': they are essential!
+    eval set -- "$TEMP"
+
+    while true ; do
+        case "$1" in
+	    -c|--cat) OUTPUT="log_cat" ; shift 1 ;;
+	    -p|--path) OUTPUT="log_pwd" ; shift 1 ;;
+	    --) shift ;;
+	    *)
+		if (( $# < 1 )) ; then
+		    failure "Not enough input arguments.
+Type '$CMD help' for more info."
+		fi
+		SESSION="$1"
+		break
+		;;
+        esac
+    done
+    
+    if ! is_session "$SESSION" ; then
+	failure "Session '$SESSION' not found.
+Type 'cereal list' to list sessions."
+    elif ! can_follow "$SESSION" "$USER" ; then
+	failure "You are not allowed to follow session '$SESSION'."
+    fi
+
+    LOG="$SESSIONDIR/$SESSION/log/main/current"
+    if [ "$OUTPUT" = 'log_follow' -o "$OUTPUT" = 'log_cat' ] ; then
+	echo "############################################################"
+	echo "### cereal log: $SESSION"
+	echo -n "### "
+	list "$SESSION"
+	echo "### log file: $LOG"
+	echo "############################################################"
+    fi
+    $OUTPUT
+}
+
+###############################################################
+### MAIN
+
+handle_command() {
+
+    COMMAND="$1"
+
+    [ "$COMMAND" ] || failure "Type '$CMD help' for usage."
+    shift
+
+    case $COMMAND in
+	'attach'|'a')
+	    attach "$@"
+	    ;;
+	'follow'|'f')
+	    follow "$@"
+	    ;;
+	'list'|'l')
+	    list "$@" || failure "There are no sessions." 1
+	    ;;
+	'help'|'h'|'?')
+	    usage
+	    ;;
+	*)
+	    failure "Unknown command: '$COMMAND'
+Type '$CMD help' for usage."
+	    ;;
+    esac
+
+    exit "$ERR"
+}
+
+handle_command "$@"
Index: /tags/cereal/0.17-1/fs/usr/sbin/cereal-admin
===================================================================
--- /tags/cereal/0.17-1/fs/usr/sbin/cereal-admin	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/sbin/cereal-admin	(revision 946)
@@ -0,0 +1,315 @@
+#!/bin/bash
+
+# cereal-admin: manage cereal sessions (runit service directory structure
+# and runit run directory).
+#
+# The cereal scripts were written by
+# Jameson Rollins <jrollins@fifthhorseman.net>
+# and
+# Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>.
+#
+# They are Copyright 2007, and are all released under the GPL, version 3
+# or later.
+
+##################################################
+CMD=$(basename $0)
+
+SHAREDIR=${SHAREDIR:-"/usr/share/cereal"}
+export SHAREDIR
+source "$SHAREDIR/common"
+[ -r "$ETC/cereal-admin.conf" ] && source "$ETC/cereal-admin.conf"
+##################################################
+
+usage() {
+cat <<EOF
+Usage: $CMD <subcommand> [options] [args]
+Cereal session management program.
+
+subcommands:
+  create (c) SESSION TTY BAUD USER LOGGROUP    create cereal session
+  start (s) [options] SESSION [SESSION]...     start cereal session(s)
+    -a (--all)                                   start all sessions
+  stop (k) [options] SESSION [SESSION]...      stop cereal session(s)
+    -a (--all)                                   stop all sessions
+  restart (r) [options] SESSION [SESSION]...   restart cereal session(s)
+    -a (--all)                                   restart all sessions
+    -r (--running)                               restart only running sessions
+  destroy (d) [options] SESSION [SESSION]...   destroy cereal session(s)
+    -a (--all)                                   destroy all sessions
+  list (l) [options] [SESSION]...              list session(s)
+    -n (--names)                                 list just session names
+  help (h,?)                                   this help
+
+EOF
+}
+
+# create session
+create() {
+    if (( $# < 5 )) ; then
+	failure "Not enough input arguments.
+Type '$CMD help' for more info."
+    fi
+
+    SESSION="$1"
+    TTY="$2"
+    BAUD="$3"
+    SUSER="$4"
+    SGROUP=$(ls -l "$TTY" | awk '{ print $4 }')
+    LOGUSER='cereal'
+    LOGGROUP="$5"
+
+    is_session "$SESSION" && failure "A session named '$SESSION' already exists."
+    check_is_tty "$TTY"
+    check_is_session_tty "$TTY"
+    check_user "$SUSER"
+    check_group "$SGROUP"
+    check_user "$LOGUSER"
+    check_group "$LOGGROUP"
+    check_tty_rw "$SUSER" "$SGROUP" "$TTY"
+
+    mkdir -p "$SESSIONDIR/$SESSION"
+
+    # create run script
+    ln -s "$SHAREDIR/mainrun" "$SESSIONDIR/$SESSION/run"
+
+    # store environment variables
+    mkdir -p "$SESSIONDIR/$SESSION/env"
+    echo "$SESSION" > "$SESSIONDIR/$SESSION/env/SESSION"
+    echo "$TTY" > "$SESSIONDIR/$SESSION/env/TTY"
+    echo "$BAUD" > "$SESSIONDIR/$SESSION/env/BAUD" 
+    echo "$SUSER" > "$SESSIONDIR/$SESSION/env/USER"
+    echo "$SGROUP" > "$SESSIONDIR/$SESSION/env/GROUP"
+    echo "$LOGUSER" > "$SESSIONDIR/$SESSION/env/LOGUSER"
+    echo "$LOGGROUP" > "$SESSIONDIR/$SESSION/env/LOGGROUP"
+
+    # create logging script
+    mkdir -p -m 0750 "$SESSIONDIR/$SESSION/log/main"
+    touch "$SESSIONDIR/$SESSION/log/main/current"
+    chmod 0640 "$SESSIONDIR/$SESSION/log/main/current"
+    chown -R "$LOGUSER" "$SESSIONDIR/$SESSION/log/main"
+    chgrp -R "$LOGGROUP" "$SESSIONDIR/$SESSION/log"
+
+    # create socket for screen, since it can't log to stdout
+    mkfifo "$SESSIONDIR/$SESSION/socket"
+    chown "$SUSER:$LOGGROUP" "$SESSIONDIR/$SESSION/socket"
+    chmod 0640 "$SESSIONDIR/$SESSION/socket"
+    ln -s "$SHAREDIR/logrun" "$SESSIONDIR/$SESSION/log/run" 
+
+    # make supervise directory world accessible if requested
+    if [ "$SUPERVISE_WORLD_ACCESSIBLE" = 'yes' ] ; then
+	mkdir -p -m 0755 "$SESSIONDIR/$SESSION/supervise"
+    fi
+
+    echo "Created session '$SESSION':"
+    display_session "$SESSION"
+}
+
+# start_check
+start_check() {
+    check_tty_rw "$USER" "$GROUP" "$TTY"
+}
+export -f start_check
+
+# start_session SESSION
+start_session() {
+    local SESSION="$1"
+    ln -s "$SESSIONDIR/$SESSION" "$SERVICE.$SESSION"
+    log_write "$SESSION" "session '$SESSION' started."
+}
+export -f start_session
+
+# start session
+start() {
+    if [ -z "$1" ] ; then
+	failure "Not enough input arguments.
+Type '$CMD help' for more info."
+    elif [ "$1" = '--all' -o "$1" = '-a' ] ; then
+	SESSIONS=$(list -n) || failure "There are no sessions." 1
+    else
+	SESSIONS="$@"
+    fi
+
+    for SESSION in $SESSIONS ; do
+	if ! is_session "$SESSION" ; then
+	    error "Session '$SESSION' not found." 1
+	elif is_linked "$SESSION" ; then
+	    error "Session '$SESSION' is already running." 1
+	elif [ ! -w "$SERVICEDIR" ] ; then
+	    error "You do not have permission to start session '$SESSION'." 2
+	elif ! chpst -e "$SESSIONDIR/$SESSION/env/" bash -c start_check ; then
+	    error "Session '$SESSION' not properly configured." 2
+	else
+	    if start_session "$SESSION" ; then
+		echo "Started session '$SESSION'."
+	    else
+		error "Session '$SESSION' could not be started." 2
+	    fi
+	fi
+    done
+}
+
+# stop_session SESSION
+stop_session() {
+    local SESSION="$1"
+    log_write "$SESSION" "stopping session '$SESSION'..."
+    sv exit "$SERVICE.$SESSION"
+    rm "$SERVICE.$SESSION"
+}
+export -f stop_session
+
+# stop session
+stop() {
+    if [ -z "$1" ] ; then
+	failure "Not enough input arguments.
+Type '$CMD help' for more info."
+    elif [ "$1" = '--all' -o "$1" = '-a' ] ; then
+	SESSIONS=$(list -n) || failure "There are no sessions." 1
+    else
+	SESSIONS="$@"
+    fi
+    
+    for SESSION in $SESSIONS ; do
+	if ! is_session "$SESSION" ; then
+	    error "Session '$SESSION' not found." 1
+	elif ! is_linked "$SESSION" ; then
+	    error "Session '$SESSION' not linked." 1
+	elif ! is_controllable "$SESSION" ; then
+	    error "You do not have permission to stop session '$SESSION'." 2
+	else
+	    if stop_session "$SESSION" ; then
+		echo "Stopped session '$SESSION'."
+	    else
+		error "Session '$SESSION' could not be stopped." 2
+	    fi
+	fi
+    done
+}
+
+# restart_session SESSION
+restart_session() {
+    local SESSION="$1"
+    log_write "$SESSION" "restarting session '$SESSION'..."
+    sv restart "$SERVICE.$SESSION"
+}
+export -f restart_session
+
+# restart session
+restart() {
+    if [ -z "$1" ] ; then
+	failure "Not enough input arguments.
+Type '$CMD help' for more info."
+    elif [ "$1" = '--all' -o "$1" = '-a' ] ; then
+	SESSIONS=$(list -n) || failure "There are no sessions." 1
+    elif [ "$1" = '--running' -o "$1" = '-r' ] ; then
+	SESSIONS=$(list | grep '^+' | cut -d ' ' -f 2)
+	[ "$SESSIONS" ] || failure "There are no running sessions." 0
+    else
+	SESSIONS="$@"
+    fi
+    
+    for SESSION in $SESSIONS ; do
+	if ! is_session "$SESSION" ; then
+	    echo "Session '$SESSION' not found."
+	elif ! is_linked "$SESSION" ; then
+	    start "$SESSION"
+	elif ! is_controllable "$SESSION" ; then
+	    error "You do not have permission to restart session '$SESSION'." 2
+	else
+	    if restart_session "$SESSION" ; then
+		echo "Restarted session '$SESSION'."
+	    else
+		error "Session '$SESSION' could not be restarted." 2
+	    fi
+	fi
+    done
+}
+
+# destroy_session SESSION
+destroy_session() {
+    rm -rf "$SESSIONDIR/$1"
+}
+export -f destroy_session
+
+# destroy session
+destroy() {
+    if [ -z "$1" ] ; then
+	failure "Not enough input arguments.
+Type '$CMD help' for more info."
+    elif [ "$1" = '--all' -o "$1" = '-a' ] ; then
+	SESSIONS=$(list -n) || failure "There are no sessions." 1
+    else
+	SESSIONS="$@"
+    fi
+
+    for SESSION in $SESSIONS ; do
+	if ! is_session "$SESSION" ; then
+	    error "Session '$SESSION' not found." 1
+	elif [ ! -w "$SESSIONDIR/$SESSION" ] ; then
+	    error "You do not have permission to destroy session '$SESSION'." 2
+	elif is_linked "$SESSION" ; then
+	    echo "Session '$SESSION' is currently linked."
+	    read -p "Really stop and destroy session? [Y|n]: " OK
+	    if [ -z "$OK" -o "${OK/y/Y}" = 'Y' ] ; then
+		if stop_session "$SESSION" ; then
+		    if destroy_session "$SESSION" ; then
+			echo "Stopped and destroyed session '$SESSION'."
+		    else
+			error "Session '$SESSION' could not be destroyed." 2
+		    fi
+		else
+		    error "Session '$SESSION' could not be stopped." 2
+		fi
+	    else
+		error "Session '$SESSION' not stopped." 1
+	    fi
+	else
+	    read -p "Really destroy session '$SESSION'? [Y|n]: " OK
+	    if [ -z "$OK" -o "${OK/y/Y}" = 'Y' ] ; then
+		if destroy_session "$SESSION" ; then
+		    echo "Destroyed session '$SESSION'."
+		else
+		    error "Session '$SESSION' could not be destroyed." 2
+		fi
+	    else
+		error "Session '$SESSION' not destroyed." 1
+	    fi
+	fi
+    done
+}
+
+###############################################################
+### MAIN
+
+COMMAND="$1"
+[ "$COMMAND" ] || failure "Type '$CMD help' for usage."
+shift
+
+case $COMMAND in
+    'create'|'c')
+	create "$@"
+	;;
+    'start'|'s')
+	start "$@"
+	;;
+    'restart'|'r')
+	restart "$@"
+	;;
+    'stop'|'k')
+	stop "$@"
+	;;
+    'destroy'|'d')
+	destroy "$@"
+	;;
+    'list'|'l')
+	list "$@" || failure "There are no sessions." 1
+	;;
+    'help'|'h'|'?')
+	usage
+	;;
+    *)
+	failure "Unknown command: '$COMMAND'
+Type '$CMD help' for usage."
+	;;
+esac
+
+exit "$ERR"
Index: /tags/cereal/0.17-1/fs/usr/share/cereal/common
===================================================================
--- /tags/cereal/0.17-1/fs/usr/share/cereal/common	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/share/cereal/common	(revision 946)
@@ -0,0 +1,210 @@
+# Shared bash functions for cereal
+#
+# The cereal scripts were written by
+# Jameson Rollins <jrollins@fifthhorseman.net>
+# and
+# Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>.
+#
+# They are Copyright 2007, and are all released under the GPL, version 3
+# or later.
+
+##################################################
+# managed directories
+export ETC="/etc/cereal"
+export SESSIONDIR="/var/lib/cereal/sessions"
+export SERVICEDIR="/var/service"
+export SERVICE="$SERVICEDIR/cereal"
+export ERR=0
+##################################################
+
+error() {
+    echo "$1" >&2
+    ERR=${2:-'1'}
+}
+export -f error
+
+failure() {
+    echo "$1" >&2
+    exit ${2:-'2'}
+}
+export -f failure
+
+# check if TTY is valid tty
+# check_is_tty TTY
+check_is_tty() {
+    [ -c "$1" ] || failure "'$1' is not a valid tty."
+}
+export -f check_is_tty
+
+# check is tty is already being used in another session
+# check_is_session_tty TTY
+check_is_session_tty() {
+    TTY="$1"
+    local SESSION
+    for SESSION in $(ls "$SESSIONDIR") ; do
+	if grep -q "^$TTY$" "$SESSIONDIR/$SESSION/env/TTY" ; then
+	    failure "TTY '$TTY' is already being monitored by session '$SESSION'."
+	fi
+    done
+}	
+export -f check_is_session_tty
+
+# check if USER is valid
+# check_user USER
+check_user() {
+    getent passwd "$1" > /dev/null || failure "'$1' is not a valid user."
+}
+export -f check_user
+
+# check if GROUP is valid
+# check_group GROUP
+check_group() {
+    getent group "$1" > /dev/null || failure "'$1' is not a valid group."
+}
+export -f check_group
+
+# check if the user can read/write to a TTY
+# check_tty_rw USER GROUP TTY
+check_tty_rw() {
+    chpst -u "$1:$2" bash -c "test -r $3 && test -w $3" || failure "User '$1' does not have read/write access to tty '$3', tty is not g+rw, or you do not have permission to change user."
+}
+export -f check_tty_rw
+
+# check if session exists
+# is_session SESSION
+is_session() {
+    test -d "$SESSIONDIR/$1"
+}
+export -f is_session
+
+# is_linked SESSION
+is_linked() {
+    test -L "$SERVICE.$1"
+}
+export -f is_linked
+
+# is_running SESSION
+is_running() {
+    local SD="$SERVICE.$1"
+    # if session is linked in service dir...
+    if [ -L "$SD" ] ; then
+	# return 2 if supervise/stat says that the service is *not* running
+	if [ -r "$SD/supervise/stat" ] && ! grep -q run "$SD/supervise/stat" ; then
+	    return 2
+	fi
+	# otherwise return 0 since either it is running, or we can't tell
+	# whether the service is actually running or not, so assume that it is
+	# if it's linked.
+	return 0
+    else
+	# return 1 if it's not linked
+	return 1
+    fi
+}
+export -f is_running
+
+# check if user can control session
+# is_controllable SESSION
+is_controllable() {
+    test -w "$SERVICE.$1/supervise/control"
+}
+export -f is_controllable
+
+# can_attach SESSION [USER]
+can_attach() {
+    local USER=${2:-"$USER"}
+    [ "$USER" = $(cat "$SESSIONDIR/$1/env/USER") ]
+}
+export -f can_attach
+
+# in_group USER GROUP
+in_group() {
+    groups "$1" | cut -d ':' -f 2 | tr ' ' '\n' | grep -q "^$2$"
+}
+
+# can_follow SESSION [USER]
+can_follow() {
+    local LOGUSER=$(cat "$SESSIONDIR/$1/env/LOGUSER")
+    local LOGGROUP=$(cat "$SESSIONDIR/$1/env/LOGGROUP")
+    local USER=${2:-"$USER"}
+    [ "$USER" = "$LOGUSER" ] || in_group "$USER" "$LOGGROUP" || [ $(id -u "$USER") = '0' ]
+}
+export -f can_follow
+
+# write to the log of a session
+#log_write SESSION STATEMENT
+log_write() {
+    echo -e "\ncereal: $2" >> "$SERVICE.$1/socket"
+}
+export -f log_write
+
+# display_session SESSION [USER]
+display_session() {
+    local SESSION SFLAG AFLAG FFLAG
+
+    SESSION="$1"
+    USER=${2:-"$USER"}
+
+    # set state flag ('+' linked (0), '-' stopped (1), '!' linked but stopped(2))
+    # last flag works only for users that can read supervise/stat
+    is_running "$SESSION"
+    case $? in
+	0)
+	    SFLAG='+'
+	    ;;
+	1)
+	    SFLAG='-'
+	    ;;
+	2)
+	    SFLAG='!'
+	    ;;
+    esac
+    # set attach flag
+    if can_attach "$SESSION" "$USER" ; then
+	AFLAG='a'
+    else
+	AFLAG='-'
+    fi    
+    # set follow flag
+
+    if can_follow "$SESSION" "$USER" ; then
+	FFLAG='f'
+    else
+	FFLAG='-'
+    fi
+
+    cd "$SESSIONDIR/$SESSION/env"
+    echo "${SFLAG}${AFLAG}${FFLAG} $SESSION $(cat TTY) $(cat BAUD) $(cat USER) $(cat LOGGROUP)"
+}
+export -f display_session
+
+# list [-n] SESSION [SESSION...]
+list() {
+    local SESSION SESSIONS
+    local DISP=0
+
+    # flag to just output session names (otherwise display full info)
+    if [ "$1" = '--names' -o "$1" = '-n' ] ; then
+	unset DISP
+	shift 1
+    fi
+
+    # list of session to display
+    if [ "$1" ] ; then
+	SESSIONS="$@"
+    else
+	SESSIONS=$(ls -1 "$SESSIONDIR" 2> /dev/null)
+	[ "$SESSIONS" ] || return 1
+    fi
+
+    for SESSION in $SESSIONS ; do
+	if ! is_session "$SESSION" ; then
+	    error "Session '$SESSION' not found." 1
+	elif [ "$DISP" ] ; then
+	    display_session "$SESSION"
+	else
+	    echo "$SESSION"
+	fi
+    done
+}
+export -f list
Index: /tags/cereal/0.17-1/fs/usr/share/cereal/logrun
===================================================================
--- /tags/cereal/0.17-1/fs/usr/share/cereal/logrun	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/share/cereal/logrun	(revision 946)
@@ -0,0 +1,22 @@
+#!/bin/bash -e
+
+# The cereal scripts were written by
+# Jameson Rollins <jrollins@fifthhorseman.net>
+# and
+# Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>.
+#
+# They are Copyright 2007, and are all released under the GPL, version 3
+# or later.
+
+exec 2>&1
+
+export SHAREDIR="/usr/share/cereal"
+source "$SHAREDIR/common"
+
+LOGUSER="$(cat ../env/LOGUSER)"
+LOGGROUP="$(cat ../env/LOGGROUP)"
+
+check_user "$LOGUSER"
+check_group "$LOGGROUP"
+    
+exec chpst -u "$LOGUSER:$LOGGROUP" svlogd -tt ./main <../socket
Index: /tags/cereal/0.17-1/fs/usr/share/cereal/mainrun
===================================================================
--- /tags/cereal/0.17-1/fs/usr/share/cereal/mainrun	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/share/cereal/mainrun	(revision 946)
@@ -0,0 +1,43 @@
+#!/bin/bash -e
+
+# The cereal scripts were written by
+# Jameson Rollins <jrollins@fifthhorseman.net>
+# and
+# Daniel Kahn Gillmor <dkg-debian.org@fifthhorseman.net>.
+#
+# They are Copyright 2007, and are all released under the GPL, version 3
+# or later.
+
+exec 2>&1
+
+export SHAREDIR="/usr/share/cereal"
+source "$SHAREDIR/common"
+
+# ensure that the socket is available
+( [ -p ./socket ] || (rm -f ./socket; mkfifo ./socket) ) || failure "Can not create socket."
+
+mainrun() {
+    check_is_tty "$TTY"
+    check_user "$USER"
+    check_group "$GROUP"
+    check_group "$LOGGROUP"
+    check_tty_rw "$USER" "$GROUP" "$TTY"
+    chown "$USER:$LOGGROUP" ./socket || failure "Can not properly set ownership of socket."
+    chmod 0640 ./socket || failure "Can not properly set permissions on socket."
+    
+    echo "starting screen session..."
+    exec chpst -u "$USER:$GROUP" /usr/bin/screen -D -m -L -c "$SCREENRC" -s /bin/false -S "cereal:$SESSION" -t "$SESSION" "$TTY" "$BAUD"
+}
+export -f mainrun
+
+# find screenrc:    
+if [ -e "./screenrc" ] ; then
+    SCREENRC="./screenrc"
+elif [ -e "$ETC/screenrc" ] ; then
+    SCREENRC="$ETC/screenrc"
+else
+    failure "Cereal screenrc file not found."
+fi
+export SCREENRC
+
+exec chpst -e ./env bash -c mainrun 2>./socket 1>&2
Index: /tags/cereal/0.17-1/fs/usr/share/man/man1/cereal.1
===================================================================
--- /tags/cereal/0.17-1/fs/usr/share/man/man1/cereal.1	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/share/man/man1/cereal.1	(revision 946)
@@ -0,0 +1,56 @@
+.TH CEREAL "1" "March 2007" "cereal 0.1" "User Commands"
+.SH NAME
+cereal \- client program to attach to cereal session
+.SH SYNOPSIS
+.B cereal \fIcommand\fP [\fIargs\fP]
+.SH DESCRIPTION
+.PP
+\fBcereal\fP is the client program to attach to a running cereal session.
+.SH SUBCOMMANDS
+\fBcereal\fP takes various subcommands:
+.PD
+.TP
+.B attach SESSION
+Attach to (take control of) cereal session SESSION.  This puts the user into a
+cereal console, provided by a command-restricted screen session.  To detach from
+an attached session, use "C-\\ d".  For help on other available commands, use
+"C-\\ ?".  Cereal uses a limited instance of screen to provide the console.  See
+\fBscreen\fP(1) for more info on the available commands.  `a' may be used in
+place of `attach'.
+.TP
+.B follow [options] SESSION
+Follow (watch, without being able to intervene) a cereal session SESSION.  The
+options are:  -c [--cat] to cat log instead of follow; -p [--path] to output
+just the path to the log file and exit.  `f' may be used in place of `follow'.
+.TP
+.B list [SESSION]...
+List session(s).  With no arguments, will list all sessions.  The leading three
+characters in the list indicate: 
+whether the session is running (+) or not (-) or in some unusual state (!),
+whether the user can attach to the session (a) or not (-),
+whether the user can follow the session (f) or not (-).
+`l' may be used in place of `list'.
+.TP
+.B help
+Output a brief usage summary.  `h' or `?' may be used in place of `help'.
+.PD
+.SH EXIT STATUS
+Exit status is 0 if OK, 1 if minor problems, 2 if serious trouble.
+.PD
+.SH AUTHOR
+Written by Jameson Rollins and Daniel Kahn Gillmor.
+.SH BUGS
+If the invoking user does not have read and execute access to the
+cereal session's supervise directory, `cereal list' may not always
+indicate that session's status accurately.
+.SH "REPORTING BUGS"
+Report bugs to <cereal@fifthhorseman.net>.
+.SH COPYRIGHT
+Copyright \(co 2007 Jameson Rollins and Daniel Kahn Gillmor
+.br
+This is free software.  You may redistribute copies of it under the terms of
+the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
+There is NO WARRANTY, to the extent permitted by law.
+.SH "SEE ALSO"
+.BR screen (1),
+.BR cereal-admin (8)
Index: /tags/cereal/0.17-1/fs/usr/share/man/man8/cereal-admin.8
===================================================================
--- /tags/cereal/0.17-1/fs/usr/share/man/man8/cereal-admin.8	(revision 946)
+++ /tags/cereal/0.17-1/fs/usr/share/man/man8/cereal-admin.8	(revision 946)
@@ -0,0 +1,104 @@
+.TH CEREAL-ADMIN "8" "March 2007" "cereal-admin 0.1" "Administration Commands"
+.SH NAME
+cereal-admin \- administer cereal sessions
+.SH SYNOPSIS
+.B cereal-admin \fIcommand\fP [\fIargs\fP]
+.SH DESCRIPTION
+\fBcereal-admin\fP is a program to administer cereal sessions.  A cereal session
+is a special (restricted) screen(1) session attached to a serial terminal.  Each
+cereal session is owned by a particular user (USER) who is allowed to "attach"
+to the cereal screen session and interact with the specified serial terminal via
+screen.  Each cereal session is also associated with a particular log group
+(LOGGROUP) whose members are allowed to "follow" the logs of the session.
+.PP
+Cereal was designed to monitor serial lines connected to the serial consoles of
+remote machines.  The cereal system is outlined at:
+.PP
+   http://cmrg.fifthhorseman.net/wiki/cereal
+.SH SUBCOMMANDS
+\fBcereal-admin\fP takes various subcommands:
+.PD
+.TP
+.B create SESSION TTY BAUD USER LOGGROUP
+Create a new session named SESSION on tty TTY, with baud rate BAUD.  USER is the
+user that will own the session, and LOGGROUP is the group that will be able to
+follow the session non-interactively (ie. read the logs).  Once created, the
+session will be in a "stopped" state.  `c' may be used in place of `create'.
+.TP
+.B start [options] SESSION [SESSION]...
+Start session(s).  For each session specified, the session directory is linked
+into the runsvdir directory.  The screen session will be attached to the serial
+terminal and logging of the terminal will begin.  `s' may be used in place of
+`start'.  options: -a (--all) to enable all sessions.
+.TP
+.B stop [options] SESSION [SESSION]...
+Stop session(s).  This kills the screen session attached to the serial terminal
+by sending it an "exit" signal, and the session directory is unlinked from
+runsvdir directory.  `k' may be used in place of `stop'.  options: -a (--all) to
+disable all sessions.
+.TP
+.B restart [options] SESSION [SESSION]...
+Restart session(s).  This sends running sessions a "restart" signal, and starts
+session that are not running.  This can be used when changes have been made to
+the screenrc, for instance.  `r' may be used in place of `restart'.  options: -a
+(--all) to disable all sessions, -r (--running) to restart just the currently
+running sessions.
+.TP
+.B destroy [options] SESSION [SESSION]...
+Destroy session(s) entirely.  This will destroy the session directory, including
+all history of the session and the logs.  `d' may be used in place of `destroy'.
+options: -a (--all) to remove all sessions.
+.TP
+.B list [SESSION]...
+List session(s).  With no arguments will list all sessions.  The leading three
+characters in the list indicate:
+whether the session is running (+) or not (-) or in some unusual state (!),
+whether the user can attach to the session (a) or not (-),
+whether the user can follow the session (f) or not (-).
+`l' may be used in place of `list'.
+.TP
+.B help
+Output a brief usage summary.  `h' or `?' may be used in place of `help'.
+.PD
+.SH LOGS
+Logs are handled by
+.BR svlogd.
+For information on how to control session log handling, please see
+svlogd(8) and/or log-limits.txt from the documentation of this
+package.
+.PD
+.SH FILES
+.PD 1
+.TP
+/etc/cereal/screenrc
+Default cereal screenrc file.
+.TP
+/etc/cereal/cereal-admin.conf
+Configuration file to set parameters for session creation and management.
+.TP
+/var/lib/cereal/sessions/$SESSION/screenrc
+Special screenrc file for session SESSION.  The presence of this file overrides
+the default screenrc file /etc/cereal/screenrc.
+.PD
+.SH EXIT STATUS
+Exit status is 0 if OK, 1 if minor problems, 2 if serious trouble.
+.PD
+.SH AUTHOR
+Written by Jameson Rollins and Daniel Kahn Gillmor.
+.SH BUGS
+If the invoking user does not have read and execute access to the
+cereal session's supervise directory, `cereal-admin list' may not
+always indicate that session's status accurately.
+.SH "REPORTING BUGS"
+Report bugs to <cereal@fifthhorseman.net>.
+.SH COPYRIGHT
+Copyright \(co 2007 Jameson Rollins and Daniel Kahn Gillmor
+.br
+This is free software.  You may redistribute copies of it under the terms of
+the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
+There is NO WARRANTY, to the extent permitted by law.
+.SH "SEE ALSO"
+.BR cereal (1),
+.BR screen (1),
+.BR runsvdir (8),
+.BR svlogd (8)