pax_global_header00006660000000000000000000000064112563332540014516gustar00rootroot0000000000000052 comment=fd9ef62a235e73cf6413101f3f25032d0493f1f3 cinit-0.3pre15/000077500000000000000000000000001125633325400133435ustar00rootroot00000000000000cinit-0.3pre15/ 000066400000000000000000000002621125633325400134050ustar00rootroot00000000000000This is a non-existing file, how did you find it? ;-) It seems like you know a bit about your system, perhaps you want to join cinit development in #cLinux on irc.freenode.org? cinit-0.3pre15/.ditz-config000066400000000000000000000001621125633325400155600ustar00rootroot00000000000000--- !ditz.rubyforge.org,2008-03-06/config name: Nico Schottelius email: nico@ikn.schottelius.org issue_dir: bugs cinit-0.3pre15/.gitignore000066400000000000000000000005201125633325400153300ustar00rootroot00000000000000*.o *.a MT ddoc contrib+tools/cinit.graph.text config.h sbin tmp os/current tmpbin src/os/current src/ipc/current src/cinit *.html *.htm *.man *.texi *.texi *.docbook src/halt.kill src/poweroff.kill src/reboot.kill doc/man/*.[0-9] doc/man/*.xml src/cmd .*.swp .exclude src/.configured src/cinit.halt src/cinit.poweroff src/cinit.reboot cinit-0.3pre15/COPYING000066400000000000000000001045131125633325400144020ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. 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. Copyright (C) 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 . 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: Copyright (C) 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 . 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 . cinit-0.3pre15/CREDITS000066400000000000000000000016441125633325400143700ustar00rootroot00000000000000-------------------------------------------------------------------------------- Credits - People contributed to cinit Nico Schottelius, 2005-05-17 (Last Change: ls -l) -------------------------------------------------------------------------------- The following list is sorted chronological, new contributors are added at the end of the list. René Nussbaumer * helping with the general IPC idea * testing and proof-reading code Marcus Przyklink * coding linear lists, making MAX_SVC obsolete * providing cinit-vs.pl to visualize the cinit-tree Matteo Croce * finding good strip parameters to save about 30KiB (on glibc) Sandro Koechli * testing, testing and testing cinit and cinit documentation Marcus Wagner * building and maintaining the Debian package Peter Portmann * testing cinit and documentation, writing cinit.graph.text in C, other coding Tonnerre Lombard * NetBSD support (host + hints) cinit-0.3pre15/Makefile000066400000000000000000000056721125633325400150150ustar00rootroot00000000000000# # cinit # Nico Schottelius # # Don't edit Makefiles, use conf/* for configuration. # # Directories and files CDIRS=src doc # # Targets # # # Warn per default, make sure the user knows what she does # warn: @cat doc/.buildwarn all: sources documentation dev-all: all sizecheck install clean dist distclean: @for subdir in ${CDIRS}; do \ echo "Making $@ in $$subdir"; \ (cd $$subdir && ${MAKE} ${MAKEFLAGS} $@) || break; \ done; .PHONY: sources sources: ${MAKE} -C src all .PHONY: documentation documentation: ${MAKE} -C doc documentation sizecheck: sources FILE="size/`date +%Y-%m-%d-%H%M%S`"; ls -l src/cinit > $$FILE; cat $$FILE; \ cg-add $$FILE cg-commit $$FILE -m "Size added" #cg-commit $$FILE -m "Size: $$(awk '{ print $5 }' $$FILE)" source-size: clean @echo -n "Source size (in KiB): " @du -s src/ | awk '{ sum+=$$1 } END { print sum }' install-miniconf: ./bin/cinit.install.miniconf install-dir: ./bin/cinit.install.dir config: @./bin/cinit.configure.os @./bin/cinit.configure.tools @./bin/cinit.configure.ipc @touch src/.configured ################################################################################ # Tests # tests: # does not work, due getting killed, due to design :-) #./scripts/internal/compile_run_as_compiler.sh ./scripts/internal/test_on_hosts.sh ./scripts/internal/compile_test.sh DEBIAN=lenny UMLDIR=test/uml CONFDIR=etc/cinit/ uml-install-debian: mkdir -p $(UMLDIR) sudo /usr/sbin/debootstrap $(DEBIAN) $(UMLDIR) me=$$(whoami); sudo chown -R $$me $(UMLDIR) # only install binaries, no need to test documentation uml-install-config: rsync -av --delete ./$(CONFDIR) $(UMLDIR)/$(CONFDIR) uml-install-cinit: dir=$$(cd $(UMLDIR); pwd -P); make -C src DESTDIR=$$dir install uml-run: uml-install-config dir=$$(cd $(UMLDIR); pwd -P); linux root=/dev/root rootflags=$$dir rootfstype=hostfs init=/sbin/cinit uml-run-sysv: dir=$$(cd $(UMLDIR); pwd -P); linux root=/dev/root rootflags=$$dir rootfstype=hostfs # debian-etch de-install: rsync -av --delete ./ root@de:cinit rsync -av --delete ./etc/cinit/ root@de:/etc/cinit ssh root@de '(cd cinit; make clean install)' de-run: ssh root@de reboot UBUNTUHOST=cinit@192.168.122.2 UBUNTUCONF=./etc/cinit-ubuntu UBUNTUINSTALL="cd cinit && make clean && sudo make install" UBUNTUTEST="sudo reboot" ubuntu-install: rsync -av --delete ./ $(UBUNTUHOST):cinit # rsync -av --delete ./$(UBUNTUCONF) $(UBUNTUHOST):/etc/cinit ssh "$(UBUNTUHOST)" $(UBUNTUINSTALL) ubuntu-test: ubuntu-install ssh "$(UBUNTUHOST)" $(UBUNTUTEST) ################################################################################ # # Developer targets # release: ./scripts/internal/cinit.release ./scripts/internal/cinit.release now scripts/internal/cinit.release: ./scripts/internal/test-cmd.sh ./scripts/internal/test-cmd.sh cinitconfconfdir=../cinit-conf/conf sync-conf: rsync --delete -av ./conf/ $(cinitconfconfdir) cd $(cinitconfconfdir); git add .; git commit -m "sync with cinit/conf" cinit-0.3pre15/NEXTTODO000066400000000000000000000024201125633325400145300ustar00rootroot00000000000000-------------------------------------------------------------------------------- - Add service start/stop to cinit cinit_svc_disable.c -------------------------------------------------------------------------------- - svc_stop_wait() => calls svc_stop() and waits until the process is finished => pay attention for child handler! => wait for that specific PID! => use global lock? - answer_svc_stop(char *svc, int method) => is called by the IPC methods => checks whether the service exists => returns the status of the service (NOT_EXISTS or the new one) => calls svc_stop_wait(), which returns => method = o including needed_by o including wanted_by o including needed_by and wanted_by o only the service - cinit blocking while shutting down => not good! => only needed when being in ipc! => otherwise tree_stop() catches that again. - - Documentate off exit codes: * 0: successfully stopped * 1: internal error: service status unknown * 2: ...? Done for pre14: - svc_stop() => stops an existing service => sets status => calls "off" - svc_stop_deps() => takes care about dependencies - Add comment about path_absolute in manpage of cmd => requires the directory to be there. cinit-0.3pre15/PLAN-2009000066400000000000000000000006531125633325400144140ustar00rootroot000000000000001. get the situation 2. fix the problems 3. release 0.3 -------------------------------------------------------------------------------- 1. - SIGCHLD not handled carefully - service status changing not supported - shutdown needs to be checked - documentation is a mess -------------------------------------------------------------------------------- 2. began to cleanup child handler - test on linux and freebsd cinit-0.3pre15/README000066400000000000000000000066351125633325400142350ustar00rootroot00000000000000-------------------------------------------------------------------------------- cinit, Nico Schottelius, 2005-04-28 [last change: 2005-05-07] -------------------------------------------------------------------------------- Introduction ============ cinit is a fast init system with dependency features and profile support. It was orientated on the design off Richard Gooch's need [0] and Felix von Leitner's minit[1]. Minit does not support real dependencies (you don't know whether the service you depend on really started) and the need concept is somehow slow (as seen in gentoo). In addition, minit needs libowfat and dietlibc, which may not be found on every Unix system. cinit main features: - portability: it should run on every Unix - true dependencies (soft and hard!) - parallel execution - highly customisable (see conf/*) - profile support (specify what services to start depending on the profile) Getting cinit ============= This README is part of the source, so you should have it. If not, goto the homepage [2] and download the tar archive or get the lastest snapshot via git. Pre-Configuring =============== If you want to fine tune cinit parameters, add different path names, change the DESTDIR, ... have a look at conf/*. Installing ========== You can install cinit parallel to any other init-system, it won't kill other init's config nor /sbin/init, if it exists. You only have to tell your kernel to execute /sbin/cinit instead of /sbin/init. Everybody do: # make all install This will create /sbin/cinit. If /sbin/init does not exist, it will be linked to /sbin/cinit. If it's the first time you operate with cinit, you can also do: # make install-test This will populate /etc/cinit with a testing configuration, which is somehow minimalistic (mounting root r/w, starting gettys, setting hostname). Although this should work on most Linux systems, it's really minimalistic. Please configure your cinit installation yourself, see below how to do that. After configuring you need to tell your kernel to boot cinit instead of your current init system. How to do that depends on your system: Linux/LILO and Linux/yaboot (ppc): append="init=/sbin/cinit" Linux/grub1 and Linux/grub2: kernel init=/sbin/cinit Configuring =========== You'll have to configure /etc/cinit and add your existing services. Please read doc/configuring.cinit for details. Please read doc/FAO if there are still questions open. Please join #cLinux on irc.freenode.org if there are still questions open. There can be found some (currently only one) testing examples below samples/ (some I do use for testing, beware if you use it: It loads the dvorak keymapping at startup!). There are currently no tools to merge your existing init-system to cinit (like sysvinit-merge, bsd-merge or minit-merge) available. If someone cares and tries to do that, I would be happy to include the script(s). Additionally I would be thankful for tar-balls containing a complete replacement of $your_unix_init. Author, Contact, Bug reports, etc. ================================== Nico Schottelius (nico-cinit<>schottelius [[dot]] org) is the author. Bug reports should be send to this address. FIXME: Add mailing list here The homepage of cinit is [2]. References: =========== [0]: need: http://www.atnf.csiro.au/people/rgooch/linux/boot-scripts/ [1]: minit: http://www.fefe.de/minit/ [2]: cinit: http://linux.schottelius.org/cinit/ cinit-0.3pre15/ROADMAP000066400000000000000000000076701125633325400143630ustar00rootroot00000000000000-------------------------------------------------------------------------------- THIS DOCUMENT SHOULD VANISH AS SOON AS EVERYTHING IS FINE -------------------------------------------------------------------------------- Timeline --------- * ~ End of October 2006: Reunderstand the code, manifest changes [DONE] * ~ Mid of November 2006: Have a compile-able cinit [DONE] * ~ End of November 2006: Have a testsystem booting cinit [DONE] * ~ Mid of December 2006: Have production stable cinit - Begin with migration scripts - publish installable pre-releases * ~ End of December 2006: Have some generic migration scripts - Have (different) understanable documents * ~ Mid of January 2007: Begin official release of cinit-0.3 Versions --------- 0.3: ~~~ code: Make cinit compile again :) [DONE] code: double check to remove Linux specific source from general tree [DONE] code: seperate ipc from the rest [DONE] code: fix / check signal handlers [DONE] code: cleanup makefile [DONE] code: add porting code: add support for any unix in general [DONE] code: stabilize code, remove experimenting parts code: remove delay support, let off/off.params do that. [DONE] code: add special directory (/etc/cinit/conf?) for non-services [DONE] code: move production code to src/ [DONE] end user doc: add warning for special binaries and hint for r/o only amiga alike systems doc: begin to merge old documents into new structure and move them to the doc/ancient directory [DONE] 0.3.1: devel doc: how to write merging scripts devel doc: merging framework: - minimal (do not look at the current configuration, build minimal) - use current system (slowly, may use old scripts) - rebuilt current system (recommened) tools: general framework for merging end user doc: merging old init to cinit code: add porting code: add support for freebsd code: better readable output: -> starting [ started once ] [ respawning ] [ failed ] (+ REASON!) [ needs failed ] (which ones) -> stopping [ stopping ] (for dependencies) [ stopped ] ? [ not running ] ? code: export profile information (CINIT_PROFILE) end user doc: using different profiles in user space end user doc: write examples for profiles: o switch ssh known_hosts based on profile o different proxy settings in browsers - environment - mozilla settings o start samba (for lan) o start samba (for company lan) o use nis and nfs (company profile) doc: continue to merge old documents into new structure and move them to the doc/ancient directory 0.3.2: end user doc: what to read to use cinit end user doc: installing cinit end user doc: configuring cinit tools: writing cinit-config (graphical (dialog based?) configuration tool) code: add porting code: add support for openbsd code: add reverse dependency chain (or earlier?) [DONE] code: better support for external tools o neustarten o mit herunterfahren o mit herunterfahren und allen Diensten, die abhaengen o ohne herunterfahren o Statische Daten o pid vom Daemon o pid vom einmal ausgefuehrten Programm doc: end to merge old documents into new structure and move them to the doc/ancient directory 0.3.3: devel doc: writing an init system devel doc: the conf/-configuration system code: check conf/ and perhaps rewrite b0rken english sentences code / doc: add logging support for services -> use multilog? code: add porting code: add support for netbsd 0.4: first stable, tested, well documented version. code: check for optimisation other: compare with other init systems 0.4.x: code: add porting code: add support for other unices cinit-0.3pre15/TODO000066400000000000000000000210271125633325400140350ustar00rootroot00000000000000svc_stop vs. svc_disable: coded tired? -------------------------------------------------------------------------------- - define service status in one document, so repeatition stops! -------------------------------------------------------------------------------- - add error handling to cinit.install.binary -------------------------------------------------------------------------------- - add code do implement stopping / restarting with dependency tree -------------------------------------------------------------------------------- # cinit.create.empty.service: can only be started from the bin directory - Fix Switching services off !! - Error codes when shutting down a service? - Delay dokumentieren - no_kill dokumentieren - on.out, on.err, on.in? -> reading/writing from/to files - implement "no_kill" until cinit-0.2 or 0.3? -------------------------------------------------------------------------------- - Source Logic issues - remove FIXME entries (and what should be fixed, too) -------------------------------------------------------------------------------- Helper scripts, rausgenommen aus Der Doku, muessen fuer cinit-0.3 ueberprueft werden: Configure help scripts ~~~~~~~~~~~~~~~~~~~~~~ cinit-conf later Using prepared scripts In the bin/ directory of this tarball you'll find at least: cinit.add.dependency - add a dependency to a service cinit.add.getty - add a new getty cinit.create.empty.service - create an empty service cinit.reboot - reboot in /bin/sh cinit.remove.getty - remove a getty service cinit.respawn.off - switch respawing off cinit.respawn.on - switch respawing on cinit.shutdown - shutdown in /bin/sh -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Optimisations ------------- - Configuring * add scripts! see below - define coding guidelines -> general, with url? - Write manpages (use doc/* as base for that) - Check Spell and Grammar in documentation - write howto: o Howto-cinit o Howto-cinit-uml tree_exec ~~~~~~~~~ - only check dependencies (=needs) after the basic run? Documentation ------------- developer ~~~~~~~~~ - ST_IN_LIST == startup marker, used to (NOT) insert services into startup - dep_needs_wants_add is used to add dependencies of a service to the general starter list user ---- - do we really need swapoff? remove umount, swapoff! * to services! -> they have to do it! - dependencies with leading '.' (dot) are ignored. - about cinit-configuration structure * cconfig * svc/ * special/ (or however we called it) - panic - halt - poweroff - reboot -------------------------------------------------------------------------------- FAQ ~~~ - DOKU: what happens when a service does not terminate.... und er als once drin ist --> Wenn kein ReSPAWN und der Prozess beendet sich nicht, dann haengt init! - multuicall probleme -> busysbox --> GIBT ES NICHT!! ---> DOKU DAZU! mit links, doppelt links, aus test ---> erklaeren, dass es unproblematisch ist! -------------------------------------------------------------------------------- csvc: 11:09 < folken23> telmich: oder service allready started. -------------------------------------------------------------------------------- cinit: 11:09 < folken23> telmich: zsb. eine grund angabe warum ein dienst nicht gestartet werden konnte. 11:09 < folken23> telmich: e.g. file nicht gefunden, service hat nicht 0 zurueckgeworfen. ---> errno in execute_sth! Child handlin ~~~~~~~~~~~~~g - free() everything before starting child Later ~~~~~ - close(*>2) before forking / executing -> close fds, clean environment, etc., ... -> do we really need that? -> yep, clean environment! - logging service! -> write output $somewhere, wait for syslog? -> flush at the end of start-process? -> perhaps pipe logging output to a program? -------------------------------------------------------------------------------- - Doc * main.text -> cleanup / remove / split * config-dirs * FAQ * ideas * meta.dependencies - config/hints/meta depps * optimising - integrate into other * README.text - update * replacing.init - update / integrate * special-services.text - into configuring/hints? * TODO - into paths, if necessary * updating.cinit - update as soon as update is possible? * using.rescue - update as soon as update is possible? * 'os-integration.text' * 'daemons.backgrounding' * There are some hints on how to migrate to cinit in general and also some os specific help in the file 'migrating-init-systems.text', - CODECHECK: * what happens with the wants of the last services? - are they added? - are they added at the correct position? - scripts * `cinit.check.config` (doc/user/configuring.cinit.text) -> circular depedencies! - Doc.next: - installing: report! -> write report script. - Doc later * current-init-problems.text - current-init-problems.text explains why cinit does not use nor recommends the use of shell scripts. * special-services.text - Begin documentation * Check Makefile * Integrate Makefile into main Makefile * create manpage * Write a small manual - install - configure - boot (different OS) * generate asciidoc! - Doc way: * installing * configuring - testconfig! * booting - different OS / bootloader * debugging - Shutdomn code: * begin at init, then shutdown wants/needs, ... - check that the new wants and need elements are nserted the other way round * we go to next, elements must be put before us! - replace cinit_ipc_logon with cinit_ipc_init... * delay ipc code -> after start! - Cleanup / create object lists object-lists/ cinit cservice ccontrol cinit.halt cinit.reboot cinit.shutdown (shell script?!?) TODO.pre9: Done: - pfad korrigieren (home/..../ -> cinit.release) - cg-add nicht aufrufen beim make all! ser/nico/oeffentlich/computer/projekte/cinit/cinit-0.3pre8/doc' FILE="size/`date +%Y-%m-%d-%H%M%S`"; ls -l src/cinit > $FILE; cat $FILE; \ cg-add $FILE -rwx------ 1 nico nico 72601 2007-04-06 17:52 src/cinit There is no GIT repository here (.git not found) make: *** [sizecheck] Fehler 1 - setup VM for testing: qemu/kvm/virtualbox (no commercial bloaty) -> uml! - sleep when respawnig! -> static delay of five seconds do_reboot.c: is ipc closed? -> check! => done! - ignore msgrcv: Interrupted system call Session terminated, killing shell...msgq-destroy: Invalid argument msgq-destroy: Invalid argument - do not print an error if /etc/cinit/conf/last is non-existent! => print it. Do not not print it, as this can aid debugging. include locking via shm, remove test on pid1 => not necessary imho currently TODO.pre11: Remove some debugging, re-introduce DEBUG() macro.. Fix doc: make dist should cleanup cc / ld to sane values? or do I experiement in tmp/*? http://linux.schottelius.org/cinit/browse_source/current/doc/user/config-dirs conf/c_halt IPC: * check msqg-code * documentate the ipc functions: update devel/ipc.text * check cinit_read_command() (devel/ipc.h) do_reboot.c: write cinit_svc_shutdown - implement do_reboot() * so not only booting with cinit works, but also the shutdown - write libcinit for use in cmd() - find out why gettimeofday() and time() do strange things when called in SIG_CHLD => bug opened in glibc, got to code testprogram - write cinit.conf.check * report broken links in needs/wants * report circular dependencies - pretty print, reporting is ugly! Add handler for ctrl+alt+delete * document in paths * check whether there's an os-unspecific way to do that cleanup bin/ - write sys-v-init-shutdown-wrapper * shutdown * halt * reboot * poweroff - write manpages for - *.kill - cmd install: make install => does not overwrite critical targets * cinit * *.kill (see client/*) * cmd make force-install => overwrites /sbin/{halt,poweroff,reboot}? => with script that wraps cmd make install-template: * creates categories make install-miniconf: * creates categories * creates one service starting a shell (depending on the OS!) cinit-0.3pre15/TODO.doc000066400000000000000000000010361125633325400145770ustar00rootroot00000000000000caveats ------- - cinit will sleep after respawing if ... a) the service did not terminate normally (!WIFEXITED(status)) b) the service did return a non-zero exit status - cinit ignores the Keyboard request - Currently there is no support to react on 'ctr+alt+del': - cinit will start a little bit faster if you omit non needed 'wants' and 'needs' dirs as they need to be scanned if they do not exist - Dependencies beginning with a '.' (dot) are ignored. So you can temporarily disable a dependency moving it to want/.name cinit-0.3pre15/bin/000077500000000000000000000000001125633325400141135ustar00rootroot00000000000000cinit-0.3pre15/bin/cinit.reboot.sh000077500000000000000000000002721125633325400170520ustar00rootroot00000000000000#!/bin/sh # Nico Schottelius # reboot system # 2005-06-09 usage() { echo "`basename $0`" echo " Reboot the system:" exit 1 } if [ $# -ne 0 ]; then usage fi kill -HUP 1 cinit-0.3pre15/bin/cinit.shutdown.sh000077500000000000000000000011301125633325400174250ustar00rootroot00000000000000#!/bin/sh # Nico Schottelius # shutdown system # TODO: use ccontrol! # 2005-05-24 (Last changed: 2005-06-18) usage() { echo "`basename $0` -[ohr]" echo " Shutdown the system:" echo " -p|--power-off: Power off" echo " -h|--halt: Halt" echo " -r|--reboot: Reboot" echo " -s|--rescue: Rescue mode" echo " " exit 1 } if [ $# -ne 1 ]; then usage fi case $1 in -r|--reboot) kill -HUP 1 ;; -p|--power-off) kill -TERM 1 ;; -h|--halt) kill -USR1 1 ;; -s|--rescue) kill -USR2 1 ;; *) usage ;; esac cinit-0.3pre15/bin/cinit.wait.for.daemon.sh000077500000000000000000000011711125633325400205520ustar00rootroot00000000000000#!/bin/sh # Nico Schottelius # wait for daemon to terminate # the pidfile is our first argument, # the dameon the second and all others are for the daemon # 2005-06-12 (Last Changed: 2005-06-17) # how long to sleep before rechecking SLEEP=5 if [ $# -lt 2 ]; then echo "`basename $0` [daemon arguments]" exit 1 fi PIDFILE=$1; shift DAEMON=$1; shift # remove old pidfile [ -e "$PIDFILE" ] && rm -f $PIDFILE $DAEMON $@ PID=$(cat "$PIDFILE") ISALIVE=$(ps ax | awk '{ print $1 }' | grep "^$PID\$") while [ "$ISALIVE" ]; do sleep ${SLEEP} ISALIVE=$(ps ax | awk '{ print $1 }' | grep "^$PID\$") done cinit-0.3pre15/bugs/000077500000000000000000000000001125633325400143035ustar00rootroot00000000000000cinit-0.3pre15/bugs/issue-25822475f5d01c35eb9edd8d75c065c83032701b.yaml000066400000000000000000000010211125633325400235240ustar00rootroot00000000000000--- !ditz.rubyforge.org,2008-03-06/issue title: "Documentate: How to cross compile" desc: |- conf/os to destination os conf/cc conf/ld conf/cflags conf/ldflags type: :task component: documentation release: future reporter: Nico Schottelius status: :unstarted disposition: creation_time: 2009-09-07 06:31:53.866741 Z references: [] id: 25822475f5d01c35eb9edd8d75c065c83032701b log_events: - - 2009-09-07 06:31:54.990478 Z - Nico Schottelius - created - "" cinit-0.3pre15/bugs/project.yaml000066400000000000000000000016111125633325400166340ustar00rootroot00000000000000--- !ditz.rubyforge.org,2008-03-06/project name: cinit version: "0.5" components: - !ditz.rubyforge.org,2008-03-06/component name: cinit - !ditz.rubyforge.org,2008-03-06/component name: core - !ditz.rubyforge.org,2008-03-06/component name: user interface - !ditz.rubyforge.org,2008-03-06/component name: portability - !ditz.rubyforge.org,2008-03-06/component name: documentation releases: - !ditz.rubyforge.org,2008-03-06/release name: "0.3" status: :unreleased release_time: log_events: - - 2009-09-07 06:28:02.974644 Z - Nico Schottelius - created - The first cleaned up version - !ditz.rubyforge.org,2008-03-06/release name: future status: :unreleased release_time: log_events: - - 2009-09-07 06:29:14.264777 Z - Nico Schottelius - created - All things to be fixed in the future. cinit-0.3pre15/conf/000077500000000000000000000000001125633325400142705ustar00rootroot00000000000000cinit-0.3pre15/conf/.README000066400000000000000000000004521125633325400152270ustar00rootroot00000000000000This is an example for a cinit and cinit-conf configuration. The first line of a file contains the configuration value, the rest of the file may contain a description. The conf/ directory is shared by cinit and cinit-conf and may contain files that are only relevant for one of the two projects. cinit-0.3pre15/conf/c_confdir000066400000000000000000000000751125633325400161430ustar00rootroot00000000000000conf The directory below cinit_dir for cinit configuration. cinit-0.3pre15/conf/c_delay000066400000000000000000000001611125633325400156110ustar00rootroot00000000000000delay Name of the file which contains the delay between sending SIGKILL after SIGTERM for respawning processes. cinit-0.3pre15/conf/c_desaster000066400000000000000000000002511125633325400163250ustar00rootroot00000000000000/bin/sh The path to a program, that we execute if nothing else helps. We'll execute it, if the standard panic action fails (as specified in cinit_dir/c_confdir/panic). cinit-0.3pre15/conf/c_env000066400000000000000000000002201125633325400152770ustar00rootroot00000000000000.env The extension to c_on and c_off, which will contain the environment \n seperated. For instance: CLIENT_IP=192.168.23.42 ACCEPT_CONN=32 cinit-0.3pre15/conf/c_init000066400000000000000000000000441125633325400154560ustar00rootroot00000000000000init The name of the init service. cinit-0.3pre15/conf/c_last000066400000000000000000000003431125633325400154600ustar00rootroot00000000000000last Name of the file below cinit_dir/c_confdir/ to execute right before reboot/halt/poweroff. This maybe a shellscript with the OS-specific umount procedure (like umount -a), see doc/user/configuring.cinit for more details. cinit-0.3pre15/conf/c_needs000066400000000000000000000001111125633325400156040ustar00rootroot00000000000000needs Name of the service sub-directory containing the needed services. cinit-0.3pre15/conf/c_off000066400000000000000000000000731125633325400152670ustar00rootroot00000000000000off Name of the file we start, when stopping the service. cinit-0.3pre15/conf/c_on000066400000000000000000000000721125633325400151300ustar00rootroot00000000000000on Name of the file we start, when starting the service. cinit-0.3pre15/conf/c_panic000066400000000000000000000002441125633325400156070ustar00rootroot00000000000000panic Name of the file below cinit_dir/c_confdir/ to execute on panic. This name .params (normally panic.params) will be passed as parameters/ argumunts to panic. cinit-0.3pre15/conf/c_params000066400000000000000000000001321125633325400157740ustar00rootroot00000000000000.params The extension to c_on and c_off, which will contain the parameters \n seperated. cinit-0.3pre15/conf/c_respawn000066400000000000000000000001251125633325400161720ustar00rootroot00000000000000respawn If this file exists in a service directory, cinit will respawn the service. cinit-0.3pre15/conf/c_sock000066400000000000000000000001371125633325400154550ustar00rootroot00000000000000coala The name of the socket cinit will use (currently: below tmpdir, see doc/ipc.thoughts). cinit-0.3pre15/conf/c_tmp000066400000000000000000000001271125633325400153150ustar00rootroot00000000000000tmp The name of the temporary directory, where we'll mount tmpfs to create the socket cinit-0.3pre15/conf/c_tmpfs000066400000000000000000000001411125633325400156420ustar00rootroot00000000000000tmpfs The name of the filesystem to use to mount a memory filesystem. On Linux this is "tmpfs". cinit-0.3pre15/conf/c_tmpmount000066400000000000000000000002321125633325400163750ustar00rootroot00000000000000tmpfs The name of the mount target, we'll mount with c_tmpfs on the c_tmp directory. On Linux this can be anything, but we will use the default "tmpfs". cinit-0.3pre15/conf/c_wants000066400000000000000000000001111125633325400156420ustar00rootroot00000000000000wants Name of the service sub-directory containing the wanted services. cinit-0.3pre15/conf/cc000066400000000000000000000000341125633325400145750ustar00rootroot00000000000000gcc The c-compiler to use. cinit-0.3pre15/conf/cflags000066400000000000000000000003401125633325400154470ustar00rootroot00000000000000-pipe -W -Wall -Werror -Iinclude -g -D_XOPEN_SOURCE=600 -D_USE_POSIX Standard flags to pass to (g)cc. -D_XOPEN_SOURCE=600 must be used on glibc to select the right standard. -D_USE_POSIX is needed for sigemptyset on glibc cinit-0.3pre15/conf/cinit_dir000066400000000000000000000001061125633325400161540ustar00rootroot00000000000000/etc/cinit This is where all configuration for cinit will be stored. cinit-0.3pre15/conf/cinitconfdir000066400000000000000000000000631125633325400166650ustar00rootroot00000000000000conf General cinit-configuration (below cinitdir) cinit-0.3pre15/conf/destdir000066400000000000000000000003011125633325400156430ustar00rootroot00000000000000 The destination to install to. This is not used when running cinit, but only for installing it. Normally the first line is blank. cinit-conf uses this file for installing the configuration. cinit-0.3pre15/conf/gettydir000066400000000000000000000002201125633325400160400ustar00rootroot00000000000000getty This is the subdirectry in which the scripts will create the gettys, if you are using 'install-conf'. It's not used be cinit internally. cinit-0.3pre15/conf/install_directory000066400000000000000000000000751125633325400177470ustar00rootroot00000000000000-d Parameter to pass to install_prog to create directories. cinit-0.3pre15/conf/install_prog000066400000000000000000000001471125633325400167120ustar00rootroot00000000000000/usr/bin/install Program we use to install. install_directory contains parameter to create directory. cinit-0.3pre15/conf/ipc_method000066400000000000000000000001641125633325400163270ustar00rootroot00000000000000msgq The type of IPC (inter process communication) to use. Valid values can be optained by issuing `ls src/ipc/`. cinit-0.3pre15/conf/ld000066400000000000000000000000261125633325400146100ustar00rootroot00000000000000gcc Comment missing. cinit-0.3pre15/conf/ldflags000066400000000000000000000000371125633325400156270ustar00rootroot00000000000000 No flags specified normally. cinit-0.3pre15/conf/max_delay000066400000000000000000000001241125633325400161530ustar00rootroot0000000000000030 Maximum number of seconds to sleep between retrying to start it (respawn only). cinit-0.3pre15/conf/max_deps000066400000000000000000000002121125633325400160060ustar00rootroot0000000000000032 Maximum number of direct dependencies (in each wants and needs, that way doubling this number) a service may have. The default is 32. cinit-0.3pre15/conf/msgq_pathname000066400000000000000000000001231125633325400170330ustar00rootroot00000000000000/bin/sh Used to generate an unique identifier for the message queue. See ftok(3). cinit-0.3pre15/conf/msgq_to_clients000066400000000000000000000001531125633325400174040ustar00rootroot00000000000000o This is use in ftok to generate a key_t for the message queue use to write to the clients. See ftok(3). cinit-0.3pre15/conf/msgq_to_server000066400000000000000000000001521125633325400172500ustar00rootroot00000000000000i This is use in ftok to generate a key_t for the message queue use to write to the server. See ftok(3). cinit-0.3pre15/conf/os000066400000000000000000000002401125633325400146300ustar00rootroot00000000000000linux Select the operating system compiling for. Current possibilities: - linux Currently Planned possibilities: - freebsd - openbsd - netbsd cinit-0.3pre15/conf/p_asciidoc000066400000000000000000000001661125633325400163130ustar00rootroot00000000000000asciidoc The binary on your system (with or without path) which does what I expect asciidoc todo. Default: asciidoc cinit-0.3pre15/conf/p_docbooktoman000066400000000000000000000001741125633325400172130ustar00rootroot00000000000000docbook2x-man The binary on your system (with or without path) which converts docbook to manpages. Default: docbook2x-man cinit-0.3pre15/conf/p_docbooktotexi000066400000000000000000000001751125633325400174120ustar00rootroot00000000000000docbook2x-texi The binary on your system (with or without path) which converts docbook to texinfo. Default: docbook2x-texi cinit-0.3pre15/conf/prefix000066400000000000000000000003001125633325400155010ustar00rootroot00000000000000 Where to install cinit. Normally this will be /, but you can put it anywhere. The subdirectory 'sbin' under this prefix must be readable by the kernel. This is normally either empty or "/". cinit-0.3pre15/conf/profile000066400000000000000000000004701125633325400156540ustar00rootroot00000000000000cprofile: The argument should be passed to cinit to recognize that a profile will follow. "cprofile:" is the standard, as the Linux kernel eats everything in the form 'var=parm'. The old (pre cinit-0.1) option "cprofile=" should therefore NOT be used. Under Linux you tell it the bootloader like grub or LILO. cinit-0.3pre15/conf/service_categories000066400000000000000000000004651125633325400200650ustar00rootroot00000000000000getty init local-tuning local-services mount network remote-services List of directories normally created below /etc/cinit/svc/ as 'pseudo-services'. Btw, 'init' is the first service and has always to be there, but it does not really fit into here, because it's a real one, compraed to the pseudo services. cinit-0.3pre15/conf/sleep_before_kill000066400000000000000000000003471125633325400176640ustar00rootroot00000000000000sleep_before_kill The file that specifies how long to sleep after sending SIGTERM, before sending SIGKILL to every process. If this file is non-existing the builtin value from 'sleep_kill'. The file should be located below conf/ cinit-0.3pre15/conf/sleep_kill000066400000000000000000000003771125633325400163450ustar00rootroot000000000000002 Seconds to sleep after sending SIGTERM, before sending SIGKILL to every process. 5 is a good working value, but makes me tired. Testing with 2 currently. Note: This does NOT affect terminating services, they are shutdown by their own 'off' functions. cinit-0.3pre15/conf/sleep_kill_svc000066400000000000000000000002551125633325400172130ustar00rootroot000000000000001 Seconds to sleep after sending SIGTERM, before sending SIGKILL to the service we are shutting down. This is only used for bringing down respawning processes. Default: 1. cinit-0.3pre15/conf/sleep_rerun000066400000000000000000000001371125633325400165370ustar00rootroot000000000000001 How many seconds to sleep before rechecking if the service was executed. Used by run_svc(). cinit-0.3pre15/conf/sleep_svc000066400000000000000000000001011125633325400161660ustar00rootroot000000000000005 How many seconds to sleep before respawning a failed process. cinit-0.3pre15/conf/sock_queue000066400000000000000000000001271125633325400163560ustar00rootroot0000000000000032 Maximum process waiting in the socket queue. The default is much more than enough. cinit-0.3pre15/conf/strip000066400000000000000000000001101125633325400153440ustar00rootroot00000000000000strip -R .comment -R .note Strip out unecessary parts of the binaries. cinit-0.3pre15/conf/svcdir000066400000000000000000000000741125633325400155060ustar00rootroot00000000000000svc Directory below /etc/cinit that contains the services. cinit-0.3pre15/conf/version000066400000000000000000000000311125633325400156720ustar00rootroot00000000000000"0.3pre15" The version. cinit-0.3pre15/conf2/000077500000000000000000000000001125633325400143525ustar00rootroot00000000000000cinit-0.3pre15/conf2/README000066400000000000000000000017171125633325400152400ustar00rootroot00000000000000Migrate conf/ to general conf/-buildsystem (write documentation for it). gpm2 may be an example for this! conf/targets: targets to make available in Makefile and their dependencies abstract the build-process somehow, so one can create build-targets? c-programs/ (includes cc / ld) cinit (link to conf/object_listings cinit?) conf/object_listings lists of dependencies: conf/object_listings/cinit contains all objects needed for cinit conf/programs/ like cc, ld, install, ... conf/built-options/ like --... in ./configure conf/install/ options/ destdir (prefixed before everything) prefix (standard prefix) bin (relative to prefix, if not beginning with a /) sbin (relative to prefix, if not beginning with a /) lib (relative to prefix, if not beginning with a /) targets/ cinit/ built-target (link to conf/targets/cinit) destination (relative to cinit-0.3pre15/contrib+tools/000077500000000000000000000000001125633325400161375ustar00rootroot00000000000000cinit-0.3pre15/contrib+tools/Makefile000066400000000000000000000023011125633325400175730ustar00rootroot00000000000000# # (c) 2005 Peter Portmann (pp at bluewin.ch) # cinit/contrib+tools # # This script is written for the clinux-System and published # under the terms of GPL 2.0 # # Version: 0.2 # clean with a single command instead of two commands. # # ChangeLog: # 0.1 initial version # # Todo: # # Features: # # compile/link options # # do not use DEBUG and OPTIMIZE at the same time! #DEBUG=-DDEBUG #OPTIMIZE=-Werror DEBUG=-g -DDEBUG #OPTIMIZE=-pipe -Os -Werror # init should be static per default! LDFLAGS= # programs CC=gcc $(DEBUG) $(OPTIMIZE) $(TIMEME) CFLAGS=-Wall -I. -I../ LD=gcc STRIP=strip -R .comment -R .note INSTALL = install prefix = /usr bindir = $(prefix)/bin # objects CLIENT=cinit.graph.text.o COMMUNICATION=error.o usage.o mini_printf.o OBJ=$(CLIENT) $(COMMUNICATION) # PROGRAMS=cinit.graph.text SCRIPTS=cconfig.graph.xml.rb \ make.cconfig.from.xml.rb \ cinit-vis.pl # targets all: $(PROGRAMS) cinit.graph.text: $(OBJ) $(LD) $(LDFLAGS) $(OBJ) -o $@ $(STRIP) $@ clean: rm -f *.o $(PROGRAMS) install: all @echo '*** Installing contrib+tools ***' $(INSTALL) -d -m755 $(DESTDIR)$(bindir) for bin in $(SCRIPTS) $(PROGRAMS); do \ $(INSTALL) $$bin $(DESTDIR)/$(bindir); \ done cinit-0.3pre15/contrib+tools/README000066400000000000000000000006631125633325400170240ustar00rootroot00000000000000contrib+tools/ programs written by others and external tools not necessary needed but (very) nice to have cinit-vis.pl - draw an ascii graph of cinit configuration [perl] cinit.graph.text - draw an ascii graph of cinit configuration [c] cconfig.graph.xml.rb - creates a xml file from a cconfig [ruby] make.cconfig.from.xml.rb - creates a cconfig from a xml file [ruby] cinit-0.3pre15/contrib+tools/README.ruby000066400000000000000000000004161125633325400200000ustar00rootroot00000000000000The ruby tools for general cconfig [0] are written by René Nussbaumer [1]. You can find the documentation for them at [2]. [0]: http://nico.schotteli.us/papers/linux/cconfig/ [1]: http://killerfox.forkbomb.ch/ [2]: http://killerfox.forkbomb.ch/articles/cconfig/tools cinit-0.3pre15/contrib+tools/cconfig.graph.xml.rb000077500000000000000000000066751125633325400220140ustar00rootroot00000000000000#!/usr/bin/env ruby =begin Writes an XML-Tree for a cconfig directory Idea by Nico Schottelius aka telmich Implemented and (C) by René Nussbaumer aka KillerFox This script is written for the clinux-System and published under the terms of GPL 2.0 Version: 0.3 ChangeLog: Version 0.3 (René Nussbaumer): * Added support for binary files * Added sha1 checksum for binary files Version 0.2 (René Nussbaumer): * Changed checking order: symlink, directory, file. Because of a logical bug -> directory follows symlink so, when a symlink points to a directory no «link» element is created. Version 0.1 (René Nussbaumer): * Holy hack for directory scanning (needs to be optimized) * Hack for rexml to print out «lost» tags. This rexml sux. Todo: * Optimize scanning. * Use another xml library instead of rexml crap. Problem: Produce dependencies -> no std-lib Features: * Create a flat (no deepnes without directory) and 1:1 image of an cconfig directory =end require 'rexml/document' require 'base64' require 'digest/sha1' require 'filemagic' @version = '0.3' def determineTarget(entry) return 'external' if(!File.expand_path(entry).index(@initpath)) return 'link' if(FileTest.symlink?(entry)) return 'object' if(FileTest.directory?(entry)) return 'attribute' if(FileTest.file?(entry)) return 'unknown' # Should never be reached end def createTree(dir, parent) dir.each { |entry| next if(entry =~ /^(\.|\.\.)$/) if(FileTest.symlink?(entry)) e = parent.add_element('link') # Much fun with links e.add_attributes( { 'name' => entry, 'target' => determineTarget(File.readlink(entry)) } ) e.add_text(File.readlink(entry)) elsif(FileTest.directory?(entry)) e = parent.add_element('object') e.add_attribute('name', entry) # Bad, that we need to change the directory every time. oldPwd = Dir.pwd Dir.chdir(entry) createTree(Dir.new('.'), e) Dir.chdir(oldPwd) elsif(FileTest.file?(entry)) e = parent.add_element('attribute') e.add_attribute('name', entry) if(File.stat(entry).size?) # Yeah, we got one WITH content! W00h00, let's party. fm = FileMagic.new(FileMagic::MAGIC_MIME) if(fm.file(entry) =~ /executable/) e.add_attribute('type', 'binary') text = File.new(entry).read e.add_attribute('sha1', Digest::SHA1.hexdigest(text)) e.add_text(Base64.encode64(text)) else e.add_text(File.new(entry).read) end fm.close() end end } end if(!ARGV[0] || !FileTest.directory?(ARGV[0])) puts 'You need to specify a directory' Kernel.exit(-1) end doc = REXML::Document.new e = doc.add_element('cconfig') e.add_attribute('name', File.basename(ARGV[0])) e.add_attribute('version', @version) @initpath = File.expand_path(ARGV[0]) Dir.chdir(ARGV[0]) createTree(Dir.new('.'), doc.root) out = '' doc.write(out, 0, false, true) REXML::XMLDecl.new('1.0', 'utf-8').write($stdout) # This should automatically printed by rexml. Damn bugs. puts '' puts out # Workaround for a buggy rexml cinit-0.3pre15/contrib+tools/cinit-vis.pl000077500000000000000000000031121125633325400204010ustar00rootroot00000000000000#!/usr/bin/perl -w # (c) by Marcus Przyklink (downhill-clinux@burningchaos.org) # written for cinit and published under GPL # beautified a bit by Nico Schottelius # optimized by René Nussbaumer # Version: 0.1 use strict; use warnings; # # Variables for location and output # # cinit-directory my $path = "/etc/cinit/svc/"; # started profile my $starting_point = "init"; # the spaces for each level (integer: amount of spaces) my $space = 3; # marker for need my $need = "-->"; # marker for want my $want = "==>"; # # main function, recursively list the components of the cinit system # if (@ARGV) { if( $ARGV[0] =~ /-(h|-help)/ ) { print "Usage: " . __FILE__ . " without parameters for standard-use (check variables in file)\n"; print " Parameters:\n"; print " -h for this help\n"; print " profile-name for a profile\n"; exit(0); } else { $starting_point = $ARGV[0]; } } # # start first instance # sub get_deeper { my ($point, $tmp_counter, $need_want) = splice @_; print " " x ($space * $tmp_counter) . ($need_want ? $need : $want) . " " . $point . "\n"; opendir(DIR, "${path}${point}/needs") and my @next_need = sort grep(!/^\./, readdir(DIR)) and closedir(DIR); opendir(DIR, "${path}${point}/wants") and my @next_want = sort grep(!/^\./, readdir(DIR)) and closedir(DIR); for(@next_need) { get_deeper($_, $tmp_counter + 1, 1); } for(@next_want) { get_deeper($_, $tmp_counter + 1, 0); } } # # start first instance # get_deeper($starting_point, 0, 0); # # work done, go home # exit(0); cinit-0.3pre15/contrib+tools/cinit.graph.text.c000066400000000000000000000124711125633325400215010ustar00rootroot00000000000000/** (c) 2005 Peter Portmann (pp at bluewin.ch) cinit.graph.text.c This script is written for the clinux-System and published under the terms of GPL 2.0 Version: 0.2 ChangeLog: Version 0.2 (Peter Portmann): * Not assigned link destinies are marked by (!). * Not readable directories are marked by "directory not readable". Version 0.1 (Peter Portmann): * Print of the directory structure of the contained files and links without following the links. Todo: Features: */ //#include #include #include #include #include #include #include #include //#include "cinit.h" #include "error.h" #define FTW_F 1 /* file isn't a directory */ #define FTW_D 2 /* file is a directory */ #define FTW_DNR 3 /* not readable directory */ #define FTW_NS 4 /* unsuccesfully stat on this file */ #define MAX_CHAR 4096 /*********************************************************************** * cinit.graph.text - textual representation of the cinit directory */ #define CSERVICE_BANNER "cinit.graph.text - textual representatio of the cinit directory\n\n" #define USAGE_TEXT "\n\nUsage:\n\ncinit.graph.text \n" \ "\tpath\t- cinit installationpath\n" typedef int EACH_ENTRY(const char *, const struct stat *, int); typedef enum { FALSE=0, TRUE=1 } bool; static char dirpath[PATH_MAX]; static int depth = 0; static long int filecount = 0; static EACH_ENTRY each_entry; static int pp_ftw(char *, EACH_ENTRY *); static int each_getinfo(EACH_ENTRY *); /*********************************************************************** * pp_ftw: file tree walk */ static int pp_ftw(char *filepath, EACH_ENTRY *function) { int n; if(chdir(filepath) < 0) /* In angegebenen Pfad wechseln */ err_msg(FATAL_SYS, "can't change to %s", filepath); if(getcwd(dirpath, PATH_MAX) == 0) /* Absoluten Pfadnamen ermitteln */ err_msg(FATAL_SYS, "error using getcwd for %s", filepath); n = each_getinfo(function); return(n); } /*********************************************************************** * each_getinfo: get more info for each file. */ static int each_getinfo(EACH_ENTRY *function) { struct stat statpuff; struct dirent *direntz; DIR *dirz; int n; char *zgr; if(lstat(dirpath, &statpuff) < 0) return(function(dirpath, &statpuff, FTW_NS)); /* Error on stat */ if(S_ISDIR(statpuff.st_mode) == 0) return(function(dirpath, &statpuff, FTW_F)); /* no directory */ /* It's a directory. * Call function() for it. After that handel each file in the directory. */ if((dirz = opendir(dirpath)) == NULL) { /* Directory not readable */ closedir(dirz); return(function(dirpath, &statpuff, FTW_DNR)); } if((n = function(dirpath, &statpuff, FTW_D)) != 0) /* return the directorydirpath */ return(n); zgr = dirpath + strlen(dirpath); /* append slash to the dirpathname */ *zgr++ = '/'; *zgr = '\0'; while((direntz = readdir(dirz)) != NULL) { /* ignor . and .. */ if(strcmp(direntz->d_name, ".") && strcmp(direntz->d_name, "..")) { strcpy(zgr, direntz->d_name); /* append filename after slash */ depth++; if(each_getinfo(function) != 0) { /* Recursion */ depth--; break; } depth--; } } *(zgr-1) = '\0'; /* deleting evrything after the slash */ if(closedir(dirz) < 0) err_msg(WARNING, "closedir for %s failed", dirpath); return(n); } /*********************************************************************** * each_entry: handling each file and build the graph step by step. */ static int each_entry(const char *filepath, const struct stat *statzgr, int filetype) { struct stat statpuff; static bool erstemal=TRUE; int i; char link[MAX_CHAR]; filecount++; if(!erstemal) { for(i=1 ; i<=depth ; i++) printf("%4c|", ' '); printf("----%s", strrchr(filepath, '/')+1); } else { printf("%s", filepath); erstemal = FALSE; } switch(filetype) { case FTW_F: switch(statzgr->st_mode & S_IFMT) { case S_IFREG: break; case S_IFCHR: printf(" c"); break; case S_IFBLK: printf(" b"); break; case S_IFIFO: printf(" f"); break; case S_IFLNK: printf(" -> "); if(( i=readlink(filepath, link, MAX_CHAR)) != -1) printf("%.*s", i, link); if(stat(filepath, &statpuff) < 0) printf(" (!)"); break; case S_IFSOCK: printf(" s"); break; default: printf(" ?"); break; } printf("\n"); break; case FTW_D: printf("/\n"); break; case FTW_DNR: printf("/ directory not readable\n"); break; case FTW_NS: err_msg(WARNING_SYS, "Error using 'stat' on file %s", filepath); break; default: err_msg(FATAL_SYS, "Unknown Filetype (%d) by file %s", filetype, filepath); break; } return(0); } /*********************************************************************** * main: */ int main(int argc, char *argv[]) { if(argc != 2) usage(CSERVICE_BANNER, USAGE_TEXT); exit(pp_ftw(argv[1], each_entry)); } cinit-0.3pre15/contrib+tools/cinit.h000066400000000000000000000005651125633325400174240ustar00rootroot00000000000000/*********************************************************************** * * 2007 Nico Schottelius (nico-cinit //@\\ schottelius.org) * * part of cLinux/cinit * * Dummy header file to intgrate mini_printf and usage */ #ifndef CINIT_DUMMY_HEADER #define CINIT_DUMMY_HEADER void usage(char *banner, char *text); void mini_printf(char *str,int fd); #endif cinit-0.3pre15/contrib+tools/error.c000066400000000000000000000057071125633325400174450ustar00rootroot00000000000000/** (c) 2005 Peter Portmann (pp at bluewin.ch) error.c This script is written for the clinux-System and published under the terms of GPL 2.0 Version: 0.1 ChangeLog: Todo: Features: */ #include "error.h" #include #include #include #include #include #include #define MAX_CHAR 4096 int debug; /* Aufrufer von log_msg oder log_open muss debug setzen: 0, wenn interaktiv; 1, wenn Daemon-Prozess */ /*---- Lokale Routinen zur Abarbeitung der Argumentliste --------------------*/ static void msg_err(int sys_msg, const char *fmt, va_list az) { int fehler_nr = errno; char puffer[MAX_CHAR]; vsprintf(puffer, fmt, az); if (sys_msg) sprintf(puffer+strlen(puffer), ": %s ", strerror(fehler_nr)); fflush(stdout); /* fuer Fall, dass stdout und stderr gleich sind */ fprintf(stderr, "%s\n", puffer); fflush(NULL); /* alle Ausgabepuffer flushen */ return; } static void msg_log(int sys_msg, int prio, const char *fmt, va_list az) { int fehler_nr = errno; char puffer[MAX_CHAR]; vsprintf(puffer, fmt, az); if (sys_msg) sprintf(puffer+strlen(puffer), ": %s ", strerror(fehler_nr)); if (debug) { fflush(stdout); /* fuer Fall, dass stdout und stderr gleich sind */ fprintf(stderr, "%s\n", puffer); fflush(NULL); /* alle Ausgabepuffer flushen */ } else { strcat(puffer, "\n"); syslog(prio, puffer); } return; } /*---- Global aufrufbare Fehlerroutinen -------------------------------------*/ void err_msg(int kennung, const char *fmt, ...) { va_list az; va_start(az, fmt); switch (kennung) { case WARNING: case FATAL: msg_err(0, fmt, az); break; case WARNING_SYS: case FATAL_SYS: case DUMP: msg_err(1, fmt, az); break; default: msg_err(1, "Falscher Aufruf von err_msg...", az); exit(3); } va_end(az); if (kennung==WARNING || kennung==WARNING_SYS) return; else if (kennung==DUMP) abort(); /* core dump */ exit(1); } void log_msg(int kennung, const char *fmt, ...) { va_list az; va_start(az, fmt); switch (kennung) { case WARNING: case FATAL: msg_log(0, LOG_ERR, fmt, az); break; case WARNING_SYS: case FATAL_SYS: msg_log(1, LOG_ERR, fmt, az); break; default: msg_log(1, LOG_ERR, "Falscher Aufruf von log_msg...", az); exit(3); } va_end(az); if (kennung==WARNING || kennung==WARNING_SYS) return; exit(2); } /*---- log_open --------------------------------------------------------------- initialisiert syslog() bei einem Daemon-Prozess */ void log_open(const char *kennung, int option, int facility) { if (debug==0) openlog(kennung, option, facility); } cinit-0.3pre15/contrib+tools/error.h000066400000000000000000000007331125633325400174440ustar00rootroot00000000000000#ifndef ERROR_H #define ERROR_H /** (c) 2005 Peter Portmann (pp at bluewin.ch) error.h This script is written for the clinux-System and published under the terms of GPL 2.0 Version: 0.1 ChangeLog: Todo: Features: */ #define WARNING 0 #define WARNING_SYS 1 #define FATAL 2 #define FATAL_SYS 3 #define DUMP 4 void log_msg(int kennung, const char *fmt, ...); void err_msg(int kennung, const char *fmt, ...); #endif cinit-0.3pre15/contrib+tools/make.cconfig.from.xml.rb000077500000000000000000000145031125633325400225570ustar00rootroot00000000000000#!/usr/bin/env ruby =begin Create a cconfig directory based on a xml input. (C) 2005 by Ren Nussbaumer aka KillerFox This script is written for the clinux-System and published under the terms of GPL 2.0 Version: 0.3 ChangeLog: Version 0.3 (Ren Nussbaumer): * Added binary file support * Added sha1 checksum for binary files Version 0.2 (Ren Nussbaumer): * Added some commandline options * Added level so control the restrictivity of the program * Added more intelligence to the program, to detect internal broken dependcies. * Support debug-Levels. * Print statistic at the end of the programs about warnings and errors. Version 0.1 (Ren Nussbaumer): * Initial Todo: * Use an rexml alternative * Some cleanup * Optimize * Testing? Features: * Create a cconfig directory based on a xml =end require 'rexml/document' require 'getoptlong' require 'base64' require 'digest/sha1' @verbose = 0 @level = 1 @version = '0.3' @warnings = 0 @errors = 0 @checklist = Array.new def printMsg(prefix, msg) puts '%-12s %s' % [prefix + ':', msg] end def error(msg, fatal = 0) @errors += 1 fatal = 0 if(@level < 1) fatal = 255 if(@level > 1 && !fatal) printMsg(fatal != 0 ? 'PANIC' : 'ERROR', msg) Kernel.exit(-fatal) if(fatal != 0) end def warn(msg) error(msg, 1) if(@level > 1) @warnings += 1 printMsg('WARNING', msg) end def info(msg) printMsg('INFO', msg) end def debug(msg, verbosity = 1) if(@verbose >= verbosity) printMsg("DEBUG(#{verbosity})", msg) end end def createObject(name) error("#{name} already exists.", 1) if(FileTest.exists?(name)) begin Dir.mkdir(name) rescue error("Could not create directory #{name}: #{$!}. Abort.", 7) end debug("Object #{File.expand_path(name)} has been created.", 4) end def createAttribute(name, content = nil) warn("#{name} already exists. Overwrite.") if(FileTest.exists?(name)) begin file = File.new(name, 'w') file.print content if(content && !content.empty?) file.close debug("Attribute #{File.expand_path(name)} has been created", 4) rescue error("Could not create file #{name}: #{$!}. Skipped.") end end def createLink(name, target, type) warn("#{name} already exists. Overwrite.") if(FileTest.exists?(name)) error("Broken dependencies! Please take a look if #{target} exists on your system", 2) if(type == 'external' && !FileTest.exists?(target)) if(!FileTest.exists?(target) && type != 'external') #info("Possible break. But maybe the target #{target} does not yet exists. Checking later.") exptarget = File.expand_path(target) @checklist << exptarget debug("Adding #{target} to the list of internal dependcies to check.", 2) end begin error('You\'ve a system which does not support symbolic links. Abort.', 3) if(File.symlink(target, name) != 0) rescue error("Could not create symlink #{name} => #{target}: #{$!}.", 3) end debug("Link #{File.expand_path(name)} has been created", 4) end def doWork(elm) name = elm.name attrname = elm.attributes['name'] error("XML Tag with missing name attribute!", 5) if(!attrname) if(name =~ /(object|cconfig)/) if(name == 'cconfig') if(elm.attributes['version']) info("Found a version string: #{elm.attributes['version']}") warn("This XML is maybe incompatible with this programm. I'm a version #{@version} script. The XML is generated with a version #{elm.attributes['version']} script. Please update.") if(elm.attributes['version'] > @version) end end createObject(attrname) if(elm.has_elements?) pwd = Dir.pwd Dir.chdir(attrname) elm.each_element { |e| doWork(e) } Dir.chdir(pwd) end elsif(name == 'attribute') text = nil e = nil text = e.value if((e = elm.get_text)) if(text && elm.attributes['type'] && elm.attributes['type'] == 'binary') text = Base64.decode64(text) if(Digest::SHA1.hexdigest(text) != elm.attributes['sha1']) warn("SHA1 differs from file: #{Dir.pwd}#{attrname}") end end createAttribute(attrname, text) elsif(name == 'link') error("link-Tag without content.", 6) if(!elm.has_text?) error("link with missing target. Skipped.") if(!elm.attributes['target']) createLink(attrname, elm.get_text.value, elm.attributes['target']) end end puts "This is #{File.basename(__FILE__)} v#{@version} by Ren Nussbaumer" puts opts = GetoptLong.new( ['--verbose', '-v', GetoptLong::OPTIONAL_ARGUMENT], ['--level', '-l', GetoptLong::REQUIRED_ARGUMENT], ['--version', '-V', GetoptLong::NO_ARGUMENT] ) opts.each { |arg,value| case arg when '--verbose' @verbose += 1 value.each_byte { |x| if(x.chr == 'v') @verbose += 1 end } debug("Verbosity set to: #{@verbose}") when '--level' debug("Setting level to: #{value}", 3) case value when 'low' @level = 0 when 'normal' @level = 1 when 'paranoid' @level = 2 else warn('Unknown level: ' + value) end when '--version' Kernel.exit(0) else warn("Unknown option #{arg}#{value && !value.empty? ? ('with value ' + value) : ''}") end } if(!ARGV[0]) puts 'Need at least one argument' puts "Usage: #{__FILE__} " Kernel.exit(1) end filedesc = $stdin if(ARGV[0] != '-') filedesc = File.new(ARGV[0]) end doc = REXML::Document.new filedesc doWork(doc.root) if(!@checklist.empty?) info('Now checking all broken internal dependcies again') broken = 0 @checklist.each { |path| debug("Checking #{path}.", 2) if(!FileTest.exists?(path)) broken += 1 warn("Broken dependcies. #{path} does not exist. Please fix.") end } info('Looks good.') if(broken == 0) info('Bad, bad.') if(broken > 0) end info("Successed. #{@warnings} warnings, #{@errors} errors") cinit-0.3pre15/contrib+tools/mini_printf.c000077700000000000000000000000001125633325400257142../src/generic/mini_printf.custar00rootroot00000000000000cinit-0.3pre15/contrib+tools/usage.c000077700000000000000000000000001125633325400232702../src/generic/usage.custar00rootroot00000000000000cinit-0.3pre15/doc/000077500000000000000000000000001125633325400141105ustar00rootroot00000000000000cinit-0.3pre15/doc/.buildwarn000066400000000000000000000010571125633325400161030ustar00rootroot00000000000000 Welcome to the cinit ******************** Hints: ------ - Settings can be found in conf/* (also used for compiling) - Cinit configuration is normally found in /etc/cinit Documentation ------------- The documentation can be found in doc/: - doc/user/ contains documentation for users - doc/devel/ contains documentation for developers Please read doc/user/installing-cinit.text BEFORE installing. Building cinit -------------- "make all" - to build cinit "make install" - to install cinit, documentation and core tools cinit-0.3pre15/doc/Makefile000066400000000000000000000047751125633325400155650ustar00rootroot00000000000000# # Makefile stolen from ccollect # Nico Schottelius, Fri Jan 13 12:13:08 CET 2006 # A2X=a2x ASCIIDOC=asciidoc DOCBOOKTOTEXI=docbook2x-texi DOCBOOKTOMAN=docbook2x-man XSLTPROC=xsltproc XSL=/usr/share/xml/docbook/stylesheet/nwalsh/html/docbook.xsl # # Asciidoc will be used to generate other formats later # MANDOCS = man/cinit.text man/halt.kill.text man/poweroff.kill.text \ man/reboot.kill.text man/cmd.text USERDOCS = user/compiles.on.text user/configuring.cinit.text \ user/conf-system.text \ user/cross-compiling.text user/current-init-problems.text \ user/daemons.backgrounding.text user/dependencies.text \ user/example-directory-structure.text \ user/installing-cinit.text user/paths.text \ user/profiles.text user/README.text DEVELDOCS = devel/codingguideline.text DOCS = $(MANDOCS) $(USERDOCS) $(DEVELDOCS) # # Doku # HTMLDOCS = $(DOCS:.text=.html) DBHTMLDOCS = $(DOCS:.text=.htm) #TEXIDOCS = $(DOCS:.text=.texi) MANPDOCS = $(MANDOCS:.text=.man) DOCBDOCS = $(DOCS:.text=.docbook) DOC_ALL = $(HTMLDOCS) $(DBHTMLDOCS) $(TEXIDOCS) $(MANPDOCS) # # End user targets # help: @echo "----------- documentation make targets --------------" @echo "documentation: generate HTML, Texinfo and manpage" @echo "html: only generate HTML (via asciidoc/docbook/xsltproc)" @echo "htm: only generate HTML (via asciidoc)" @echo "info: only generate Texinfo" @echo "man: only generate manpages" @echo "pdf: only generate pdfs (requires: fop)" install: $(DOC_ALL) @echo "===> Copy " man/*.[0-9] "to the correct manpaths" # # Internal targets # html: $(HTMLDOCS) htm: $(DBHTMLDOCS) info: $(TEXIDOCS) man: $(MANPDOCS) documentation: $(DOC_ALL) # # Generic targets # # docbook gets .htm, asciidoc directly .html (or the other way round) %.html: %.docbook ${XSLTPROC} -o $@ ${XSL} $< %.htm: %.text ${ASCIIDOC} -n -o $@ $< %.docbook: %.text ${ASCIIDOC} -n -b docbook -o $@ $< %.texi: %.docbook ${DOCBOOKTOTEXI} --to-stdout $< > $@ %.mandocbook: %.text ${ASCIIDOC} -b docbook -d manpage -o $@ $< #%.man: %.mandocbook # ${DOCBOOKTOMAN} --to-stdout $< > $@ %.man: %.text ${A2X} -f manpage $< %.pdf: %.text ${A2X} -f pdf $< # # Distribution # clean distclean: rm -f $(DOC_ALL) rm -f man/*.texi man/*.xml man/*.[0-9] # # Be nice with the users and generate documentation for them # dist: distclean documentation cinit-0.3pre15/doc/README.text000066400000000000000000000020501125633325400157500ustar00rootroot00000000000000cinit/doc ========= Nico Schottelius 0.1, Initial Version from 2006-11-30 :Author Initials: NS This directory contains the cinit documentation. Files and directories in this directory ---------------------------------------- ancient ~~~~~~~ Old documents, only thought to irritate you. They are not interesting for most people and may contain obsoleted or wrong information. braindumps ~~~~~~~~~~ Files I used to make the situation clear to myself. They are not interesting for most people and may contain obsoleted or wrong information. devel ~~~~~ Developer related documents. Contains information for adding code, for developing external tools to cinit or code guidelines for writing patches to cinit. logs ~~~~ Logfiles or raw data dumps. Makefile ~~~~~~~~ The makefile used to generate the documentation. man ~~~ Manpages. README.text ~~~~~~~~~~~ This file user ~~~~ The most important part: Documentation for users (aka sysadmins, hackers, endusers?): Explains howto install, configure, use and debug cinit. cinit-0.3pre15/doc/ancient/000077500000000000000000000000001125633325400155315ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/Changelog000066400000000000000000000006341125633325400173460ustar00rootroot00000000000000Mo Okt 3 00:19:40 CEST 2005 *Changelog can now be found in git database (cg-log) Sun May 8 12:20:35 CEST 2005 *Changelog can now be found in monotone database (monotone log) Sat Apr 30 15:53:53 CEST 2005 * add socket code Tue Apr 26 15:29:53 CEST 2005 * removed is_cinit support, initial messaging framework Mon Apr 18 14:07:50 CEST 2005 * added is_cinit -> recognize if you are cinit or a fork cinit-0.3pre15/doc/ancient/README000066400000000000000000000006521125633325400164140ustar00rootroot00000000000000Ancient ======= Nico Schottelius 0.1, for cinit 0.3, Initial Version from 2006-06-02 These files may be incorrect, outdated, totally wrong or even trying to take over world dominance. Why are they still there? ------------------------- Just because to document the early days of cinit. If you are a software archaeologist in the year 2423, you'll be happy that I saved those files. cinit-0.3pre15/doc/ancient/TODO.lucky000066400000000000000000000021531125633325400173500ustar00rootroot0000000000000018:18 hey, ich hatte gerade ein wenig lust mich mit cinit zu befassen, hier also mein kleiner bug-report: in src/include fehlt cinit.h, (alles auf das aktuelle tarball bezogen), ich hab's aus pre9 genommen, hatte ich noch da, da git nicht wollte(Cannot get remote repository information.), ausserdem hast du _ statt - in doc/man/cinit.text verwendet bei der email, das mag docbook nicht, die beiden zeilen habe ich korrigiert, danch ging schon mal make all und auch make ins 18:35 und warum installiert er die man pages nicht mit? 07:20 so, kleiner zwischenbericht, das argv problem bei lvm gibt es mit pre10 nicht mehr, d.h. dass man auch kein shell-skript mehr braucht um lvm/luks-devices zu mounten :) 07:20 soweit sieht eig. alles gut aus 07:21 wenn das so bleibt, dann werd' ich dauerhaft auf cinit umsteigen :) 07:21 und wenn sich die gelegenheit bietet, dann stell ich cinit auch mal in der info-ag von unserer schule vor :) cinit-0.3pre15/doc/ancient/caveats000066400000000000000000000047521125633325400171120ustar00rootroot00000000000000-------------------------------------------------------------------------------- 'Geheimnisse' in German, Nico Schottelius, 2005-05-XX (Last Modified: 2005-06-11) -------------------------------------------------------------------------------- - Dependencies beginning with a '.' (dot) are ignored. So you can temporarily disable a dependency moving it to want/.name - Why is the name of the socket "coala"? Well, coala could mean 'cinit object abstract layer access', but perhaps it's a much simpler reason. - cinit will start a little bit faster if you omit non needed 'wants' and 'needs' dirs as they need to be scanned if they do not exist - Currently there is no support to react on 'ctr+alt+del': 1. It is not handled to switch on / off (Linux: See man 2 reboot and /proc/sys/kernel/ctrl-alt-del) 2. If the kernel handles it and sends signals to cinit (SIGINT on Linux) they will be ignored. There is no problem in implementing a handler for this signal, the only reason why it is not there (well, a template is in old/sig_special.c) is that nobody could tell me what would be the most senseful thing to handle ctrl-alt-del. If you can, I'll perhaps integrate it. 3. ctrl-alt-del is currently disabled under Linux within the service local-tuning/ctrl-alt-del - cinit ignores the Keyboard request Same thing with 'ctr-alt-del': SIGWINCH is sent, but I don't know what to do when recieving it. - cinit does not care about its pid nor does cinit care if it is already running in serv/cinit.c is a line calling run_init_svc(). If you call that only if getpid() == 1, cinit will behave like sysvinit and refuse to start if pid is not 1. Currently cinit has no chance to control whether it's started or not as /etc/cinit/tmp mounted again for every start. - cinit will sleep after respawing if ... a) the service did not terminate normally (!WIFEXITED(status)) b) the service did return a non-zero exit status - sleeping before rechecking if a service is finished can be optimised Currently run_svc() checks every SLEEP_RERUN seconds (default: 1), if the service it should start was finished by another instance of run_svc(). As run_svc() internally uses nanosleep() for sleeping, one could modify run_svc to use conf/sleep_rerun as a nanoseconds value. This would add most likely much often checking, but would result in faster results from run_svc. What's the best value for SLEEP_RERUN is currently unknown. cinit-0.3pre15/doc/ancient/cinit-doc/000077500000000000000000000000001125633325400174025ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/cinit-doc/author000066400000000000000000000000671125633325400206320ustar00rootroot00000000000000Nico Schottelius cinit-0.3pre15/doc/ancient/cinit-doc/availability000066400000000000000000000000431125633325400217740ustar00rootroot00000000000000cinit is currently Linux-specific. cinit-0.3pre15/doc/ancient/cinit-doc/examples000066400000000000000000000000571125633325400211450ustar00rootroot00000000000000See http://linux.schottelius.org/cinit/#config cinit-0.3pre15/doc/ancient/cinit-doc/files000066400000000000000000000003301125633325400204230ustar00rootroot00000000000000/sbin/cinit - the init system /sbin/cservice - control cinit /sbin/cinit.reboot (/sbin/reboot if non-existent before) /sbin/cinit.shutdown (/sbin/shutdown if non-existent before) /etc/cinit - configuration directory cinit-0.3pre15/doc/ancient/cinit-doc/long_description000066400000000000000000000005441125633325400226720ustar00rootroot00000000000000cinit is a fast executing, small and simple init with support for profiles. It minds dependencies (hard and soft, 'needs' and 'wants') and executes processes in parallel. And it has a simple configuration, which makes many shell-scripts unecessary (but you still could use them if you really want), which leads to better performance and less memory using. cinit-0.3pre15/doc/ancient/cinit-doc/meta/000077500000000000000000000000001125633325400203305ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/cinit-doc/meta/date000066400000000000000000000000131125633325400211620ustar00rootroot000000000000002005-08-21 cinit-0.3pre15/doc/ancient/cinit-doc/meta/man_section000066400000000000000000000000021125633325400225420ustar00rootroot000000000000008 cinit-0.3pre15/doc/ancient/cinit-doc/meta/name000066400000000000000000000000061125633325400211670ustar00rootroot00000000000000cinit cinit-0.3pre15/doc/ancient/cinit-doc/meta/short_description000066400000000000000000000000731125633325400240150ustar00rootroot00000000000000fast executing, small and simple init with profile-support cinit-0.3pre15/doc/ancient/cinit-doc/parameters000066400000000000000000000000261125633325400214660ustar00rootroot00000000000000cprofile: cinit-0.3pre15/doc/ancient/cinit-doc/path000066400000000000000000000000141125633325400202540ustar00rootroot00000000000000/sbin/cinit cinit-0.3pre15/doc/ancient/cinit-doc/see also000066400000000000000000000000441125633325400210160ustar00rootroot00000000000000http://linux.schottelius.org/cinit/ cinit-0.3pre15/doc/ancient/cinit-doc/synopsis000066400000000000000000000000151125633325400212100ustar00rootroot00000000000000/sbin/cinit cinit-0.3pre15/doc/ancient/cinit.commands000066400000000000000000000054401125633325400203650ustar00rootroot00000000000000-------------------------------------------------------------------------------- cinit commands, Nico Schottelius 2005-04-28 (Last Modified: 2005-06-11) -------------------------------------------------------------------------------- cinit allows communication through a socket (see ipc.thoughs for reasons). Sockets allow to find out the accessing uid, gid and pid (using SO_PEERCRED as socketoption). The communication-protocol is binary, the implementation can be found in comm/* mostly (clients use begin_msg() and server sigio() additonally). -------------------------------------------------------------------------------- Protocol overview -------------------------------------------------------------------------------- Any communication begins with a command. A command is a one byte unsigned char. Depending on the command, the communication has its own semantics. Commands are: (values can be found in cinit.h) CMD_START_SVC: I want to start a service. CMD_CHG_STATUS: I want to change the status of a service. CMD_STOP_SVC: Please shutdown a service. CMD_RESCUE: Kill everything, and spawn a sulogin shell. CMD_UPDATE: Hot-reboot system and reload cinit. CMD_HALT: Halt the system CMD_REBOOT: Reboot the system CMD_POWEROFF: Power-off the system -------------------------------------------------------------------------------- Detailled command-listing -------------------------------------------------------------------------------- CMD_START_SVC 1. int len; /* length of service name, including \0 */ 2. char *svc; /* name of the service, absolute pathname */ cinit returns: a) status of service b) fail CMD_CHG_STATUS: I want to change the status of a service. 0. int len; 1. char *svc; 2. char status; /* status: once: started successfully the service once. fail: tried to start once, but the service exit ungracefully respawn: I am on it, as soon it exists I'll restart! */ 2. pid_t pid /* the pid of the service, if started once or the pid of the service watcher, if respawning */ cinit returns: MSG_OK|MSG_FAIL (char) CMD_STOP_SVC: Please shutdown a service and its dependencies. 1. int len; /* length of service name, including \0 */ 2. char *svc; /* name of the service, absolute pathname */ cinit returns: Status of service (should be ST_OFF) The following commands do not return anything nor do they need any parameter: CMD_RESCUE: Kill everything, and spawn a sulogin shell. Irreversible. CMD_HALT: Halt the system. CMD_REBOOT: Reboot the system. CMD_POWEROFF: Power-off the system. CMD_UPDATE: Update cinit, hot-reboot the system. cinit-0.3pre15/doc/ancient/cservice-doc/000077500000000000000000000000001125633325400200775ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/cservice-doc/author000066400000000000000000000000671125633325400213270ustar00rootroot00000000000000Nico Schottelius cinit-0.3pre15/doc/ancient/cservice-doc/long_description000066400000000000000000000000721125633325400233630ustar00rootroot00000000000000cservice controls cinit. Please use cservice -h for help. cinit-0.3pre15/doc/ancient/cservice-doc/meta/000077500000000000000000000000001125633325400210255ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/cservice-doc/meta/date000066400000000000000000000000131125633325400216570ustar00rootroot000000000000002005-08-21 cinit-0.3pre15/doc/ancient/cservice-doc/meta/man_section000066400000000000000000000000021125633325400232370ustar00rootroot000000000000008 cinit-0.3pre15/doc/ancient/cservice-doc/meta/name000066400000000000000000000000111125633325400216600ustar00rootroot00000000000000cservice cinit-0.3pre15/doc/ancient/cservice-doc/meta/short_description000066400000000000000000000000731125633325400245120ustar00rootroot00000000000000fast executing, small and simple init with profile-support cinit-0.3pre15/doc/ancient/cservice-doc/parameters000066400000000000000000000000221125633325400221570ustar00rootroot00000000000000[-eaphru] [thilo] cinit-0.3pre15/doc/ancient/cservice-doc/path000066400000000000000000000000171125633325400207540ustar00rootroot00000000000000/sbin/cservice cinit-0.3pre15/doc/ancient/cservice-doc/see also000066400000000000000000000000441125633325400215130ustar00rootroot00000000000000http://linux.schottelius.org/cinit/ cinit-0.3pre15/doc/ancient/cservice-doc/synopsis000066400000000000000000000000151125633325400217050ustar00rootroot00000000000000/sbin/cinit cinit-0.3pre15/doc/ancient/extern/000077500000000000000000000000001125633325400170365ustar00rootroot00000000000000cinit-0.3pre15/doc/ancient/extern/README000066400000000000000000000001041125633325400177110ustar00rootroot00000000000000doc/extern/ Some things related to cinit from the outside world. cinit-0.3pre15/doc/ancient/extern/ipc.thoughts000066400000000000000000000050621125633325400214030ustar00rootroot00000000000000-------------------------------------------------------------------------------- Thoughts about different UNIX-IPC, Nico Schottelius, 2005-04-28 (Last Modified: 2005-06-11) -------------------------------------------------------------------------------- Howto cinit communicates with a) cinit-forks b) any other program a) cinit-forks a.1) shared memory Access could generally be done with shared memory. The problem with that is, that -lrt is required, which implicits -lpthread, which makes linking staticly problematic (at least for glibc). a.2) pipes A maximum of ~510 pipes could be used ( (1024-3)/2 ), 1024 is the maximum opened file deskriptors, minus 3 (stdin/stdout/stderr) already opened, divided by two, because two fds needed per client. Pipes cannot be used easily through forks of forks. a.3) fifos FIFOs are easy to use, but you would need to create two FIFOs for _every_ service, as with only two FIFOs we cannot reliable detect, _who_ is writting to us currently and who wants to read. The same limit as above is true for fifo, too: A maximum of ~510 services. a.4) system-v-ipc No documentation found nor tested. a.5) sockets Are indeed a very clean way. There's only one problem: bind() fails on read-only mounted devices: - The socket either does not exists and cannot be created - or the socket exists, but bind() refuses to reuse it (error: Address already in use) Imho bind() should even honour the socket-option SO_REUSEADDR, which allows to re-use a socket, if there's no other program bound to. As far as I can see, SO_REUSEADDR is only honoured, if socket is of type PF_INET (we use PF_UNIX) and POSIX does only specify how to check for support, but not that sockets have to be able to use SO_REUSEADDR (see posix.aardvark.bug.report). That way, we are forced to mount a temporarily filesystem on /etc/cinit/tmp and create the socket below this directory. This is not the clean and easy solution one would wish. Still, sockets seem to be the cleanest and most reliable way to have IPC for this situation. See socket(2), bind(2), listen(2), accept(2), socket(7) and unix(7) for help. b) any other program What you can do is to tell cinit to - reboot, - halt, - poweroff, - update itself (hot-reboot) - and to start a rescue mode (see using.rescue). Simple send cinit a signal, what to do: HUP: reboot USR1: halt USR2: rescue TERM: poweroff CONT: update See signal(2) and signal(7) for help and serv/sig_reboot.c for implementation. -------------------------------------------------------------------------------- cinit-0.3pre15/doc/ancient/extern/ipc.usenet.posting000066400000000000000000000030361125633325400225220ustar00rootroot00000000000000From: Nico Schottelius Subject: Unix IPC, socket/AF_UNIX; bind on r/o devices? Date: 09 May 2005 09:51:27 GMT To: comp.unix.programmer Hello! Situation: - everything mounted readonly (as when starting the system) - one process with n children, which may have n children (recursive) - all the children and children of children should be able to talk to the first parent Problem: - Using bind() will fail, because a) socket cannot created b) the existing socket cannot be reused Other possibilities not working: - shared memory is not an option, as one need -lrt, which needs -lpthread, which is problematic to link statically - pipes: handling the pipes from parent to child of child of child would be hard to program - socketpair: should be the same problematic as it's with pipes - fifos: one would have to create the fifos before and two fifos for each child; possible, but very unelegant; and one would have to memorize, which child is connected to which fifo; again possible, but somehow unelegant - signaling: one could implement communication with some kind of morse code with signals, but that won't be a good solution Questions: - Is there any way, case b) (socket already existing) can be solved in a way that I tell bind() to use an existing socket? - What would be the best solution to talk bidirectional to clients in this scenario? I appreciate any hint, as I really like the socket mechanism and would like to keep it. Thanks in advance, Nico cinit-0.3pre15/doc/ancient/extern/linux.kernel.eats.arguments000066400000000000000000000024471125633325400243450ustar00rootroot00000000000000-------------------------------------------------------------------------------- Linux, the kernel, eats arguments Nico Schottelius 2005-06-17 (Last Modified: 2005-06-17) -------------------------------------------------------------------------------- If you specify variable=value to the Linux kernel, the argument will NOT be passed to cinit. Here's the relevant code block from init/main.c of the Linux kernel: ------------------------------------------------------------------------------- From init(void * unused) the function run_init_process(char *init_filename) is called, which passes argv_init (char * argv_init[MAX_INIT_ARGS+2]) to init. First init_setup(char *str) resets all elements of the argv_init to NULL. The function unknown_bootoption(char *param, char *val) fills the argv_init array, but only with parameters, which have no value (val). The function parse_args calls unknown_bootoption with the unknown options. ------------------------------------------------------------------------------- This way the profile support in all cinit versions below cinit-0.1 will only work if you change conf/profile, because "cprofile=value" will not be given to cinit, because it's not treated as a command line option. The original value "cprofile=" is replaced by "cprofile:" as of cinit-0.1. cinit-0.3pre15/doc/ancient/extern/posix.aardvark.bug.report000066400000000000000000000033171125633325400240070ustar00rootroot00000000000000To: austin-review-l__AT__opengroup.org From: nico-posix__AT__schottelius.org Subject: Bug in TC2-d6 bind - bind a name to a socket Reply-To: austin-group-l__AT__opengroup.org Bug report from : Nico Schottelius , cLinux (Note that the reply-to line automatically redirects to austin-group-l__AT__opengroup.org for further discussion on bug reports) @ page 1 line 0 section bind - bind a name to a socket objection {-1} Problem: bind should 'assign a name to a socket', but in particular environments it will fail, where it could succeed. Long Description: When opening a new socket, with type PF_UNIX (sock = socket(PF_UNIX,SOCK_STREAM,0);) and one sets the socket option SO_REUSEADDR (setsockopt(sock, SOL_SOCKET, SO_REUSEADDR, &tmp, sizeof(tmp))), bind does not honour this setting. It is reported on irc channels, that SO_REUSEADDR is only supported on PF_INET sockets and that's what I would claim a bug. If a socket exists in the filesystem and no process is bound to it, bind wail fail anyway. This is especially problematic, when one is in an environment, which is pre-startup (like beeing init) and one wants to use sockets, but everything is mounted read-only. So, if bind() would honour the option, it would be able to bind() to a socket, which exists (as creating one on a read-only filesystem is not possible). Action: Proposal: Add better specification to either socket(7) or bind(2), which explains the behaviour of bind, when this option is set or even better: Specify, that bind should take care of this bit, also when using PF_UNIX. In general the socket(7) manpage should explain more in detail or at least reference other documents (unix(7)?), which explain what the option for a specific protocol does. cinit-0.3pre15/doc/ancient/fun-testing000066400000000000000000000003731125633325400177220ustar00rootroot00000000000000kind tot 17 ... Read path: / Read path: e Read path: t Read path: c Read path: / Read path: c Read path: i Read path: n Read path: i Read path: t Read path: / Read path: t Read path: e Read path: s Read path: t Read path: s Read path: v Read path: c cinit-0.3pre15/doc/ancient/how_it_works_internally000066400000000000000000000015011125633325400224300ustar00rootroot00000000000000The following is a very simple process structure of cinit internals: cinit-main starts \ |-> execute run_init_svc() | \ run_svc(CINIT_INIT); | | check status <-------------------\ | | set status = temp | | \ check dependencies | | | fork(run_svc()) for every WANT | | | run_svc() for every NEED / | / check if respawning { do .. while(repawn?) | \ yes: (remember: run_svc _must_ return!) | | msg_change_status(respawn) | | add watcher_signal handler to stop! (SIGTERM) | | fork(exec_svc) <--| | | waitpid(fork) | while(1) { ... } | \ sleep(WAIT_SECS) ---/ | | no: fork(exec_svc) | \ waitpid(fork) -> yes, wait! | | msg_change_status | / | / | -> while(1) | - listen to signals | - listen on socket cinit-0.3pre15/doc/ancient/init-idea-first000066400000000000000000000012701125633325400204440ustar00rootroot00000000000000- restarting/respawning touch respawn - dependencies a needs started b - clean multiply dependencies - start & stop dependencies start_depends stop_depends - parallel executation - start and stop commands start -> link start_param -> parameters, like minit stop -> link stop_param -> parameters, like minit if no stop command is available, try to kill the pid we started at stop /startup/ start_depends=gettys /shutdown/ stop_depends=power_off gettys/ start_depends=getty/1 start_depends=getty/2 start_depends=getty/3 start_depends=getty/4 ... getty/1/ start=/sbin/fgetty respawn power_off/ stop_depend=umount umount/ stop_depend= cinit-0.3pre15/doc/ancient/porting.to.other.os000066400000000000000000000017571125633325400213310ustar00rootroot00000000000000-------------------------------------------------------------------------------- Porting cinit to other operating systems, Nico Schottelius, 2005-06-02 -------------------------------------------------------------------------------- cinit is currently Linux-specific. It currently does not compile / work on other Unices, because we use O_ASYNC flag of open(2) which is _not_ a standard. This way we can act very elegant on incoming connections by our forks. If somebody finds a at least as elegant solution to act on incoming data which is more portable, I would be happy to recieve a diff -u. Additionally we currently do mount a temporarily filesystem on /etc/cinit/tmp, which allows us to create a socket, where nothing is mounted r/w yet. If a Unix has some kind of tmpfs, this can easily be changed to the appropriate value in conf/*tmp*. The O_ASYNC thing will perhaps become a compile option to cinit (via conf/socket_function for instance), so that using standard mechanism will be possible. cinit-0.3pre15/doc/ancient/removing.zombies000066400000000000000000000044261125633325400207570ustar00rootroot00000000000000-------------------------------------------------------------------------------- Removing Zombies, Nico Schottelius 2005-06-15 (Last Modified: 2005-06-15) -------------------------------------------------------------------------------- First of all, the definition of a zombie: ''Defunct ("zombie") process, terminated but not reaped by its parent.'' [Excerpt from ps(1)] ''In the case of a terminated child, performing a wait allows the system to release the resources associated with the child; if a wait is not performed, then terminated the child remains in a "zombie" state (see NOTES below). [...] NOTES A child that terminates, but has not been waited for becomes a "zom- bie". The kernel maintains a minimal set of information about the zombie process (PID, termination status, resource usage information) in order to allow the parent to later perform a wait to obtain information about the child. As long as a zombie is not removed from the system via a wait, it will consume a slot in the kernel process table, and if this table fills, it will not be possible to create further processes. If a parent process terminates, then its "zombie" children (if any) are adopted by init(8), which automati- cally performs a wait to remove the zombies.'' [Excerpt from waitpid(2)] So you can see, that if some process misbehaves and forgets about its children, we, cinit, will adopt it. In the first versions of cinit (cinit-0.0.1 <-> cinit-0.0.7) we ignored SIGCHLD. This way the zombies stayed in the system. Since cinit-0.0.8 we have sig_chld(), which removes the zombies. So far so good. Now let's remove this feature. Yes, you heard right. If cinit does not catch the zombies they will stay in the system. Yes, that's ugly. And that's how it should be. You should see, which software is broken and should contact the authors to fix it. To restore the 'old' behaviour of cinit, change generic/set_signals.c (ignore SIGCHLD) Makefile: remove serv/sig_child.c from modules list cinit in general will keep the behaviour of reaping the vestiges, which broken software left behind (as it is cleaner for the system to deallocate unused ressources). cinit-0.3pre15/doc/ancient/security000066400000000000000000000025151125633325400173260ustar00rootroot00000000000000-------------------------------------------------------------------------------- security, Nico Schottelius 2005-06-13 (Last Modified: 2005-06-14) -------------------------------------------------------------------------------- A little note about cinit security and how to exploit it: cinit trusts its socket, /etc/cinit/tmp/coala. If somebody not authorised has access to it, your system is taken over. Through this socket anybody with write access can: - shutdown, restart and power-off the host - spawn a local unprotected shell - execute anything as the user cinit runs (most likely root) Currently cinit does not care very much about the socket permissions. On my system this creates a socket with srwxr-x-rx permissions, which isi suitable for normal operation, which will not accept connect() by others than root. But you can also loosen the security and allow people from a specfic group to control your system: ei # chmod 770 /etc/cinit/tmp/coala ei # chown root:cinit /etc/cinit/tmp/coala Now everybody in the cinit group can control your system. Please think twice before doing that, as you read above, anyone from the cinit group may start a root shell on the initial console then! For extra parnoid settings you can do the following: ei # chmod 700 /etc/cinit/tmp/coala ei # chown root:root /etc/cinit/tmp/coala cinit-0.3pre15/doc/ancient/socket.poll_vs_o_async000066400000000000000000000024371125633325400221420ustar00rootroot00000000000000-------------------------------------------------------------------------------- Socket: poll(2) vs. O_ASYNC, Nico Schottelius 2005-06-22 (Last Modified: 2005-06-22) -------------------------------------------------------------------------------- 0. General problem 1. O_ASYNC 2. poll(2) 0. General problem cinit has to react, as soon as there's data on the socket. 1. O_ASYNC When you open a socket with O_ASYNC (or specify it with fcntl(2)) under Linux, your process recieves the SIGIO signal from the kernel, as soon as data is available. The problem is the handling of signals seems not to be serialised: The function, which is called on the SIGIO signal (called sigio() here) calls other functions. Those functions way recieve SIGIO while working, so the first data stream is not yet finished, though the next stream is beeing read. This gives very nice race-conditions, which are very nice to debug. 2. poll(2) poll(2) is a standard Unix-call (XPG4-UNIX), which waits a specific timeout (or infinite time if you specify a value less that zero) for the socket (or the fd in general) to be in a state where data is available to read (in fact poll can do much more, but we are not interested only in POLLIN and POLLPRI). While poll(2) seems to be a very bit slower than sigio it works reliable. cinit-0.3pre15/doc/ancient/thoughts.closed000066400000000000000000000041561125633325400205770ustar00rootroot00000000000000-------------------------------------------------------------------------------- Closed thoughts, Nico Schottelius, 2005-05-XX (Last Modified: 2005-06-14) -------------------------------------------------------------------------------- 1. using SIDs (service IDs) to communicated with external processes This was a very bad idea: The external program could exploit us by specifying an arbitary big SID (as the SID is simply the index of our service array). 2. using function pointers to handle messages Seems like it works fine. We have handlers for each message (do_*), which are called by client and server. The function pointer is simply to read or write, dependending if it is the client or the server. This way we don't need to rewrite communications parts. 3. Using different storage First all services were saved in a service array of the size MAX_SVC. This has been replaced by a double-linked list. Have a look at serv/list.c. 4. Using sockets for IPC (between cinit forks) Works very fine, though we have to mount a temporarily fs before. 5. Removing the maximum number of direct dependencies Is not planned, as it looks like the current number (32, see conf/max_deps) seems to be much more than needed. And if one really needs more, simply increase conf/max_deps. 6. Using a directory params with 1,2,3,4 for argv This would make substituting a single argument easier, but only if you know which one you have to change. This would add an additional dirent(), which would not replace the current read(), but add more open() and close()s. As this does not seem to make live easier for system administrators, this is not implemented. If you really like it, hack client/exec_svc.c 7. Using TCP/IP sockets This would be a very small change in the code, but would allow to control cinit over network. Since there is no authentication, this would be highly insecure. On the other hand, cinit could control the parallel start of many hosts, if they should become 'one' computer at the end. As this is not needed currently, it's not implemented. cinit-0.3pre15/doc/braindumps/000077500000000000000000000000001125633325400162545ustar00rootroot00000000000000cinit-0.3pre15/doc/braindumps/README.text000066400000000000000000000001621125633325400201160ustar00rootroot00000000000000DO NOT READ CONTENT IN THIS DIRECTORY. (or at least do not blame me, if you get really confused after reading it) cinit-0.3pre15/doc/braindumps/circular-dependencies.text000066400000000000000000000024561125633325400234210ustar00rootroot00000000000000What todo with circular dependencies? a needs b b needs a - try to start them? status a: is_starting status b: not_set a wants b, so a service starter for b starts status a: is_starting, waiting for b status b: is_starting service starter for b sees that a is needed service starter for b sees that a is already being started service starter for b begins to execute b status a: is_starting, waiting for b status b: is_starting, executing "on" service starter b finishes status a: is_starting, waiting for b status b: FAILED | RESPAWN | ONCE service a continues b successful: execute on b failed: register / print that we do not start, because b failed -> this would only catch possible deadlocks, if the dependency tree / status check is done dynamically -> in case of pre-building the dep-tree this situation must be concerned: - start both a and b? - or stop due to circular dependency? - Abort on detection of a circular dependency * possible without pre-calculating? - perhaps only with direct communication possible? * pre calculate - do not start that services? cinit-0.3pre15/doc/braindumps/converting-debian000066400000000000000000000011401125633325400215710ustar00rootroot00000000000000# If you would like to automatically convert a debian system, you could # use this script as a start point # # how it could look like # # create cinit base configuration # analyse enabled services level=$(awk -F: '/^id/ { print $2 }' /etc/inittab) rcdir="/etc/rc${level}.d/" initdir=/etc/init.d cd "$rcdir" for svc in *; do if [ -d "${debian_map_dir}/${svc}" ]; then echo "Adding $svc" else fi done # Also add existing services in /etc/init.d for ... if [ ! -e $rcdir/$svc ] if [ -d "${debian_map_dir}/${svc}" ]; then echo "Adding, but not enabling" fi fi done cinit-0.3pre15/doc/braindumps/converting-general000066400000000000000000000002011125633325400217610ustar00rootroot00000000000000kern=$(uname -s) case "${kern}" in $known_kern) $scriptdir/$kern ;; *) echo "Unknown system" ;; esac cinit-0.3pre15/doc/braindumps/creating-new-configurations000066400000000000000000000002411125633325400236070ustar00rootroot00000000000000scripts/create_baseconfig.sh # create base scripts/cinit.install.standard.dirs # create common categories - create fsck - set hostname - create getty(s) cinit-0.3pre15/doc/braindumps/messages.text000066400000000000000000000002431125633325400207700ustar00rootroot00000000000000This document describes the messages used between cinit and its "clients" (i.e. ccontrol, cservice, cinit.halt, ...): Signal messages --------------- As signals cinit-0.3pre15/doc/braindumps/possible_service_pre_calculation.text000066400000000000000000000013671125633325400257550ustar00rootroot00000000000000- start at * create a new service entry (if not exists) <--- * reads needs | - follow dependencies ------------------------ * only if service does not yet exist! | * read wants | - follow dependencies ------------------------ * only if service does not yet exist! * create - needed by entry in dependencies - needs entry in service - wanted by entry in dependencies - wants entry in service * record - (on,off)(,.env,.params)? - alternatively put that code into service starter * add services without further needs into a special "begin" structure to be reused at fireing of the services? cinit-0.3pre15/doc/braindumps/possible_service_status.text000066400000000000000000000010331125633325400241220ustar00rootroot00000000000000 - NOT_SET: this service has not yet been initialized - RESPAWNING: happily respawning - RESPAWN_DELAY: waiting delay before restarting * HINT: using alarm()? - senseful for single process service watcher * HINT: using nanosleep()? - senseful for per service process watcher - NEED_FAILED * add a (somehow terminated) list of services that failed? * use global status to checkout which services failed? - WANT_FAILED? * NOT NECESSARY, it is a simple want, we do not need it. cinit-0.3pre15/doc/braindumps/registering_needs_wants.text000066400000000000000000000016701125633325400241020ustar00rootroot00000000000000Each service has a list of services it - needs - is needed by - wants - is wanted by Each entry is a service pointer. The simplest list could look like this: service a: needs: b f g NULL So the needs pointer is NULL terminated: needs = realloc(count_links) -> how to get the count? 0x02 0x Better: A double linked list (like the main service list)? Could look like: service a: needs: *service *next *prev This design could also be used for wants. On the other hand, we've to register us at the needed/wanted service: service b: needed_by: *service *next *prev So each service needs four pointers: needs needed_by wants wanted_by And on each request both lists have to be modified! Example: Service "a" adds "b" as needed: - add "a" needs "b" - add "b" needed_by "a" cinit-0.3pre15/doc/braindumps/root-vm-testing000066400000000000000000000004301125633325400212520ustar00rootroot00000000000000[19:33] denkbrett:root% cat uml-mount.sh SDIR=$(dirname $0) DDIR=$(dirname $0)/root sudo mount "$SDIR/Debian-3.0r0.ext2" "$DDIR" -o loop,acl denkbrett# tar cfj ~nico/projekte/cinit/conf-vm-2007-03-05.tar.bz2 cinit denkbrett# chown -R nico cinit denkbrett# chown nico ../sbin cinit-0.3pre15/doc/braindumps/shutdown.text000066400000000000000000000050441125633325400210400ustar00rootroot00000000000000cinit - braindumps - shutdown ============================= Nico Schottelius v0.1, for cinit-0.3, 2007-01-11 :Author Initials: NS Just some braindumps. Do not read. Introduction ------------ Shutting down the system. When? ----- - reboot - halt - power off - further needed? How / What? ------------ - Stop services in the correct order * reuse the service tree / needs / needed_by! * call off, if existent * if respawning, send SIGTERM? - not if off is existent? * give some variables to off? - $RESPAWN_PID: if respawning - send SIGTERM to other apps? * or put that into special? special/post_svc_shutdown - call special/{halt,poweroff,reboot} * no, implemented that directly into cinit! - implement timely controlled shutdown: * cinit.shutdown forks (?) itself and waits, then sends a signal to cinit to initiate the shutdown process * create mappers for target OS - Linux - {free,net,open}bsd - others may contribute theirself - also implement poweroff * kill -TERM 1 - also implement reboot * kill -HUP 1 - also implement halt * kill -USR1 1 The implementation ----------------- x shutdown is initiated x disable communication (nobody can influence us anymore) x install special signal handler? - no. we do not care about zombies anymore, we are gone soon anyway - simply reset to the default - begin to shutdown services * where to start? * begin shutdown at the end of the tree, viewing/sorting it by the 'needed_by' -> where to begin sort? -> worst implementation: scan all services (easy for now) -> result: list of services, that noone needs :-) * stop those services and step above - stop a service, as soon as noone needs it anymore * check all needed_by links * more or less the inverted gen_svc_tree - how to shutdown a service * if existing, call off - if off does not exist: * if respawn: send sigterm to the process * also implement sigkill at this stage? - think we can delay it to the end - otherwise users can use off! - implement environment for off ($cinit_respawn_pid, $cinit_service_name) - do *NOT* care about the return value, we can't do anything for it anymore anyway - after all services are shutdown, kill all remaining services * SIGTERM * wait(defined_time_in_seconds) * SIGKILL - call the last command * to cleanup the system - umount -a (if needed) - swapoff (if needed) - sync (if needed) - switch off cinit-0.3pre15/doc/braindumps/sizes000066400000000000000000000002741125633325400173370ustar00rootroot00000000000000sysvinit: root 1 0.0 0.0 1944 648 ? Ss 02:12 0:00 init [2] cinit-0.3pre8-glibc-linux: compiler 25323 0.0 0.0 1564 392 pts/2 S+ 20:22 0:00 ./cinit cinit-0.3pre15/doc/changes/000077500000000000000000000000001125633325400155205ustar00rootroot00000000000000cinit-0.3pre15/doc/changes/0.3pre15000066400000000000000000000001531125633325400166170ustar00rootroot00000000000000Released: 2009-09-23 Changes: * Changed child handling (no function calls in sig_child handler anymore) cinit-0.3pre15/doc/changes/00-before-0.3pre15000066400000000000000000000102241125633325400202740ustar00rootroot00000000000000cinit-0.3pre14: 2008-03-17 - Added test-suite for cmd - Added support to shutdown services in cinit and cmd (without needs and wants) - Added linux-sysvinit wrapper for shutdown (See scripts/wrapper/linux-sysvinit/shutdown) - Rewrote most parts of cmd (to make it more beautiful) - Changed license to GPL 3.0 cinit-0.3pre13: 2007-09-26 - Added -V (get cmd version), -h (help), -p (get pid) to cmd - Cleaned up namemsage in msgq.h - Added global service lock - Splitted of svc.h to svc.h, svc-intern.h and svc-messages.h - Prepared logic splitoff from cinit_ipc_listen() - Fixed bug: fork() has a general race condition (see src/test/fork-latency.c) through use of global lock cinit-0.3pre12: 2007-09-06 - Added DESTDIR support - Added support to get service status via cmd: cmd -s * also supports relative paths to CINIT_DIR ("/etc/cinit") - Fixed git clone problem: hooks are needed for dumb git - Fixed bug: We did not wait for services to finsh, which we depend on being ran once. cinit-0.3pre11: 2007-09-01 - Added basic communication: * client binary "cmd" with argument -v returns cinit-version - Updated {halt,reboot,poweroff}.kill cinit-0.3pre10: - Fixed make install target - Added halt.kill, poweroff.kill and reboot.kill (including manpages!) - Fixed invalid comparision in core/cinit.c - Be verbose: Print what we execute - Updated documentation cinit-0.3pre9: 2007-05-15 - Implemented sleeping before respawn (static delay) - Report broken links on execution, but ignore empty services - Cleaned up message queue error reporting cinit-0.3pre8: 2007-04-06 - Updated and merged documentation: Codingstyle and Codingguide - Cleaned sigaction-code (fixes segfault on glibc) - Cleaned object listings - Added notifications at shutdown - Fixed status check cinit-0.3pre7: 2007-02-17 - Many code cleanups - Fixed glibc problem with sigaction (for details view src/core/set_signals.c) - Added general shutdown support (will *NOT* yet stop services, but still stop your system) cinit-0.3pre6: - Many code cleanups - Added user documentation and cleaned up documentation in general cinit-0.3pre5: - Finished new SIGCHLD handler - First cleanups for real release. - This version is the first 0.3pre version that can handle respawn! cinit-0.3pre4: - Re-implemented execution of services. - This version is the first 0.3pre version that COULD bootup your system! cinit-0.3pre3: - Finished execution all services via the reversed service tree. cinit-0.3pre2: - Finished generation of the dependency tree. cinit-0.3pre1: - cinit should now compile on mostly all unices - introduced much new code - THIS IS A DEVELOPER RELEASE, NOT USABLE IN PRODUCTION ENVIRONMENTS. cinit-0.2.1: (Bugfix release) - Fixed problem in contrib+tools/Makefile when installing - added many new scripts to convert sys-v-init, which are still early beta (see bin/cinit.merge.sysvinit-debian-sid) cinit-0.2: - Much more verbose error reporting - You can now also disable 'once ran' services, - You can restart services with csevice -r - Online speech in German is available - C_DELAY support - variable delay for sending SIGKILL after SIGTERM - First /etc/csys configuration example (wasserstoff) is available - a Mailing list was created - Added tools to analyze cinit configuration (cinit-vis.pl, cinit.graph.text.c) - Added tools to import and export configuration to XML (make.cconfig.from.xml.rb,cconfig.graph.xml.rb) - Removed unecessary signalling - Added many helper scripts to install services (cinit.install.service*) - Fixed many small bugs in old helper scripts (cinit.add.getty, cinit.get-conf, ...) - Added ccontrol, which allows to control cinit - Added update (-u) via ccontrol - Stripped cservice, which now "only" controls services - Removed swapoff from cinit code, should be handled by off - Much better error and processing descriptions - A bit more verbose reporting - Restructured run_svc, now with better error detection - Removed Kernel panic, when halting system cinit-0.3pre15/doc/devel/000077500000000000000000000000001125633325400152075ustar00rootroot00000000000000cinit-0.3pre15/doc/devel/Doxyfile000066400000000000000000000261011125633325400167150ustar00rootroot00000000000000# Doxyfile 1.5.6 #--------------------------------------------------------------------------- # Project related configuration options #--------------------------------------------------------------------------- DOXYFILE_ENCODING = UTF-8 PROJECT_NAME = cinit PROJECT_NUMBER = 0.3pre15 OUTPUT_DIRECTORY = /home/user/nico/oeffentlich/computer/projekte/cinit/doxygen CREATE_SUBDIRS = NO OUTPUT_LANGUAGE = English BRIEF_MEMBER_DESC = YES REPEAT_BRIEF = YES ABBREVIATE_BRIEF = "The $name class" \ "The $name widget" \ "The $name file" \ is \ provides \ specifies \ contains \ represents \ a \ an \ the ALWAYS_DETAILED_SEC = NO INLINE_INHERITED_MEMB = NO FULL_PATH_NAMES = YES STRIP_FROM_PATH = /home/user/nico/oeffentlich/computer/projekte/cinit/cinit/src STRIP_FROM_INC_PATH = SHORT_NAMES = NO JAVADOC_AUTOBRIEF = NO QT_AUTOBRIEF = NO MULTILINE_CPP_IS_BRIEF = NO DETAILS_AT_TOP = NO INHERIT_DOCS = YES SEPARATE_MEMBER_PAGES = NO TAB_SIZE = 3 ALIASES = OPTIMIZE_OUTPUT_FOR_C = YES OPTIMIZE_OUTPUT_JAVA = NO OPTIMIZE_FOR_FORTRAN = NO OPTIMIZE_OUTPUT_VHDL = NO BUILTIN_STL_SUPPORT = NO CPP_CLI_SUPPORT = NO SIP_SUPPORT = NO IDL_PROPERTY_SUPPORT = YES DISTRIBUTE_GROUP_DOC = NO SUBGROUPING = YES TYPEDEF_HIDES_STRUCT = NO #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- EXTRACT_ALL = YES EXTRACT_PRIVATE = YES EXTRACT_STATIC = YES EXTRACT_LOCAL_CLASSES = YES EXTRACT_LOCAL_METHODS = NO EXTRACT_ANON_NSPACES = NO HIDE_UNDOC_MEMBERS = NO HIDE_UNDOC_CLASSES = NO HIDE_FRIEND_COMPOUNDS = NO HIDE_IN_BODY_DOCS = NO INTERNAL_DOCS = NO CASE_SENSE_NAMES = YES HIDE_SCOPE_NAMES = NO SHOW_INCLUDE_FILES = YES INLINE_INFO = YES SORT_MEMBER_DOCS = YES SORT_BRIEF_DOCS = NO SORT_GROUP_NAMES = NO SORT_BY_SCOPE_NAME = NO GENERATE_TODOLIST = YES GENERATE_TESTLIST = YES GENERATE_BUGLIST = YES GENERATE_DEPRECATEDLIST= YES ENABLED_SECTIONS = MAX_INITIALIZER_LINES = 30 SHOW_USED_FILES = YES SHOW_DIRECTORIES = NO SHOW_FILES = YES SHOW_NAMESPACES = YES FILE_VERSION_FILTER = #--------------------------------------------------------------------------- # configuration options related to warning and progress messages #--------------------------------------------------------------------------- QUIET = NO WARNINGS = YES WARN_IF_UNDOCUMENTED = YES WARN_IF_DOC_ERROR = YES WARN_NO_PARAMDOC = NO WARN_FORMAT = "$file:$line: $text" WARN_LOGFILE = #--------------------------------------------------------------------------- # configuration options related to the input files #--------------------------------------------------------------------------- INPUT = /home/user/nico/oeffentlich/computer/projekte/cinit/cinit/src INPUT_ENCODING = UTF-8 FILE_PATTERNS = *.c \ *.cc \ *.cxx \ *.cpp \ *.c++ \ *.d \ *.java \ *.ii \ *.ixx \ *.ipp \ *.i++ \ *.inl \ *.h \ *.hh \ *.hxx \ *.hpp \ *.h++ \ *.idl \ *.odl \ *.cs \ *.php \ *.php3 \ *.inc \ *.m \ *.mm \ *.dox \ *.py \ *.f90 \ *.f \ *.vhd \ *.vhdl \ *.C \ *.CC \ *.C++ \ *.II \ *.I++ \ *.H \ *.HH \ *.H++ \ *.CS \ *.PHP \ *.PHP3 \ *.M \ *.MM \ *.PY \ *.F90 \ *.F \ *.VHD \ *.VHDL RECURSIVE = YES EXCLUDE = /home/user/nico/oeffentlich/computer/projekte/cinit/cinit/src/ancient/ \ /home/user/nico/oeffentlich/computer/projekte/cinit/cinit/src/test/ EXCLUDE_SYMLINKS = NO EXCLUDE_PATTERNS = EXCLUDE_SYMBOLS = EXAMPLE_PATH = EXAMPLE_PATTERNS = * EXAMPLE_RECURSIVE = NO IMAGE_PATH = INPUT_FILTER = FILTER_PATTERNS = FILTER_SOURCE_FILES = NO #--------------------------------------------------------------------------- # configuration options related to source browsing #--------------------------------------------------------------------------- SOURCE_BROWSER = YES INLINE_SOURCES = NO STRIP_CODE_COMMENTS = YES REFERENCED_BY_RELATION = YES REFERENCES_RELATION = YES REFERENCES_LINK_SOURCE = YES USE_HTAGS = NO VERBATIM_HEADERS = YES #--------------------------------------------------------------------------- # configuration options related to the alphabetical class index #--------------------------------------------------------------------------- ALPHABETICAL_INDEX = NO COLS_IN_ALPHA_INDEX = 5 IGNORE_PREFIX = #--------------------------------------------------------------------------- # configuration options related to the HTML output #--------------------------------------------------------------------------- GENERATE_HTML = YES HTML_OUTPUT = html HTML_FILE_EXTENSION = .html HTML_HEADER = HTML_FOOTER = HTML_STYLESHEET = HTML_ALIGN_MEMBERS = YES GENERATE_HTMLHELP = NO GENERATE_DOCSET = NO DOCSET_FEEDNAME = "Doxygen generated docs" DOCSET_BUNDLE_ID = org.doxygen.Project HTML_DYNAMIC_SECTIONS = NO CHM_FILE = HHC_LOCATION = GENERATE_CHI = NO CHM_INDEX_ENCODING = BINARY_TOC = NO TOC_EXPAND = NO DISABLE_INDEX = NO ENUM_VALUES_PER_LINE = 4 GENERATE_TREEVIEW = NONE TREEVIEW_WIDTH = 250 FORMULA_FONTSIZE = 10 #--------------------------------------------------------------------------- # configuration options related to the LaTeX output #--------------------------------------------------------------------------- GENERATE_LATEX = YES LATEX_OUTPUT = latex LATEX_CMD_NAME = latex MAKEINDEX_CMD_NAME = makeindex COMPACT_LATEX = NO PAPER_TYPE = a4wide EXTRA_PACKAGES = LATEX_HEADER = PDF_HYPERLINKS = YES USE_PDFLATEX = YES LATEX_BATCHMODE = NO LATEX_HIDE_INDICES = NO #--------------------------------------------------------------------------- # configuration options related to the RTF output #--------------------------------------------------------------------------- GENERATE_RTF = NO RTF_OUTPUT = rtf COMPACT_RTF = NO RTF_HYPERLINKS = NO RTF_STYLESHEET_FILE = RTF_EXTENSIONS_FILE = #--------------------------------------------------------------------------- # configuration options related to the man page output #--------------------------------------------------------------------------- GENERATE_MAN = YES MAN_OUTPUT = man MAN_EXTENSION = .3 MAN_LINKS = NO #--------------------------------------------------------------------------- # configuration options related to the XML output #--------------------------------------------------------------------------- GENERATE_XML = NO XML_OUTPUT = xml XML_SCHEMA = XML_DTD = XML_PROGRAMLISTING = YES #--------------------------------------------------------------------------- # configuration options for the AutoGen Definitions output #--------------------------------------------------------------------------- GENERATE_AUTOGEN_DEF = NO #--------------------------------------------------------------------------- # configuration options related to the Perl module output #--------------------------------------------------------------------------- GENERATE_PERLMOD = NO PERLMOD_LATEX = NO PERLMOD_PRETTY = YES PERLMOD_MAKEVAR_PREFIX = #--------------------------------------------------------------------------- # Configuration options related to the preprocessor #--------------------------------------------------------------------------- ENABLE_PREPROCESSING = YES MACRO_EXPANSION = NO EXPAND_ONLY_PREDEF = NO SEARCH_INCLUDES = YES INCLUDE_PATH = INCLUDE_FILE_PATTERNS = PREDEFINED = EXPAND_AS_DEFINED = SKIP_FUNCTION_MACROS = YES #--------------------------------------------------------------------------- # Configuration::additions related to external references #--------------------------------------------------------------------------- TAGFILES = GENERATE_TAGFILE = ALLEXTERNALS = NO EXTERNAL_GROUPS = YES PERL_PATH = /usr/bin/perl #--------------------------------------------------------------------------- # Configuration options related to the dot tool #--------------------------------------------------------------------------- CLASS_DIAGRAMS = NO MSCGEN_PATH = HIDE_UNDOC_RELATIONS = YES HAVE_DOT = YES DOT_FONTNAME = FreeSans DOT_FONTPATH = CLASS_GRAPH = YES COLLABORATION_GRAPH = YES GROUP_GRAPHS = YES UML_LOOK = NO TEMPLATE_RELATIONS = NO INCLUDE_GRAPH = YES INCLUDED_BY_GRAPH = YES CALL_GRAPH = NO CALLER_GRAPH = NO GRAPHICAL_HIERARCHY = YES DIRECTORY_GRAPH = YES DOT_IMAGE_FORMAT = png DOT_PATH = DOTFILE_DIRS = DOT_GRAPH_MAX_NODES = 50 MAX_DOT_GRAPH_DEPTH = 1000 DOT_TRANSPARENT = YES DOT_MULTI_TARGETS = NO GENERATE_LEGEND = YES DOT_CLEANUP = YES #--------------------------------------------------------------------------- # Configuration::additions related to the search engine #--------------------------------------------------------------------------- SEARCHENGINE = NO cinit-0.3pre15/doc/devel/README.text000066400000000000000000000006171125633325400170560ustar00rootroot00000000000000cinit/doc/devel =============== Nico Schottelius 0.1, Initial Version from 2006-07-09 :Author Initials: NS This directory contains cinit development documents. Introduction ------------ This file describes the related documents in the current directory. Who should read those documents? -------------------------------- (cinit-)developers. Content ------- cinit-0.3pre15/doc/devel/cinit-0.4.text000066400000000000000000000052431125633325400175260ustar00rootroot00000000000000cinit 0.4 - Redesign of cinit ============================================ Nico Schottelius 0.4.0, for cinit 0.4, Initial Version from 2006-03-11 :Author Initials: NS cinit 0.2 ran fine and the general project of developing a parallel executing init system is finished. With cinit 0.4 there are new aims to reach. Introduction ------------ . AIMS - portability: no Linux-dependency anymore - cleaner signal handling - better documentation so more people can use it Current problems ---------------- Temporary filesystem and socket problematic ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The mount(2) system call is os-specific. The temporary fs is os-specific. Signal handlers are not clean ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Race conditions when multiple signals arrive Reboot code is os specific ~~~~~~~~~~~~~~~~~~~~~~~~~~ serv/sig_reboot.c contains umount, remount hard coded. Solutions --------- Temporary filesystem and socket problematic ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Remove - the mount call - do not create an initial socket Wait until we recieve a signal, then we create a socket under the configured socket directory (see `conf/sockdir`). Signal handlers are not clean ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Reboot code is os specific ~~~~~~~~~~~~~~~~~~~~~~~~~~ Misc ~~~~ - Configuration /etc/cinit/config/ init -> link to initial service pre_boot pre_boot_args post_boot post_boot_args /etc/cinit/services/ /etc/cinit/profiles/ links to the starting services cinit - Internals ================= Nico Schottelius 0.1 for cinit-0.3, Initial version: So Feb 19 10:25:46 CET 2006 :Author Initials: NS Introduction ------------ This document describes the internals of cinit. It is thought to be read by developers. Child handler code in cinit-0.3 ------------------------------- In cinit versions <= cinit-0.2.1 the respawning services where handled by an extra child handler, which was a fork of cinit. This had some problems: - We allocated more memory than necessary, unecessary parts of cinit were copied - The SIG_CHILD-handler was not written very clean, in some versions it was completly missing. . So in `cinit-0.3` we changed it the following way: - no extra child handlers - handle everything in the SIG_CHILD handling function - when sig_child is recieved do: - check against respawn list - if it is a respawning service, [do the following in a seperate fork?] check whether it successfully stoped - if yes: restart immediatly - if no: sleep $sleep_time and then restart cinit-0.3pre15/doc/devel/cinit-status-translation.dia000066400000000000000000000117421125633325400226560ustar00rootroot00000000000000]msF_RUQyr-'ަvvNGD.!˺ں~P;A a%aH5Ds~?t5i6{sF>$q6Igo~/o_y2^|b6WonO_?<<<.M{4O^_<Ư 볷 L"wӫ"U<:gg,|o~bg˼^ΞkUĿ46\./{{SCR$lfǕn*ׇNWW0[kڲƏIg]6?>5A<.үWKˮ'`>ls8[rX*uY!ڻi $ !nvqZg{gd E)1a,YCX٥3Bwb0O8̋ ͧqa~Y+w7;|=zufŶķm6wجyK84ɗ_&Io~%cTST\]ujNzn3#E\n?h2-yUqگu ;7K Ke0(.s.,\,⪳G|,à `2"q1H6v!m5IE'rM՞,m mv7N;6^|r >vcX|I,Vaq, !o-;:\P!̩qҰ}j0OǛIvu0wCB.3Z3ւ`0^v|IFR L X]gY^\Z)/;G}[ʌ?+v;wxȞaExE yu}t+<jf.}oWsi/(fڬ I ."8;xOr6+/=X n٤d翾96–ϒtd3Xá/l$4XFňbIAkͬ-ڌk-~MtlaZ]!T,\|bp-!2j^P$V +D"*I9'.?"7͠ZM@ ݐә9]KPn|Kxn!ִJ(|MX8.:;1fL!8q~:.~=eaCE[(xVQP"Fll6N\AQuio`Aq0v (Af ({9&Dr"R̦%  O81w⤛rHs>◥{c2q[{7*AbHJ};G!Y%zJ(::Ru^Bŷdld2{ɎtI=_=V5PP>M4+*6OzC]0TRVֺ" MEuE-*۠<HuֱJЊMPpPls~eٞL@1U9oS|{H=W f/)VuEHU<'nԁ[̞laxD0 [@iPP$2>V&0G3l!l]xn8#;",ή)MɵZda ^pJSz\F.5Nlvmޚ;)EqxXWbfQb؈8Z!%ka~Ԋ0e=x[˿?t)Ev 0s+HčGD$)ZGu+㮵=֍SCp#\ﲐ;ހzBNjey[kW8 0XfA{1Dlu2z2c0֔^thfd`TmW5O0!e ͙="HrH_ .5^Fj&H,+Ƀ򭭶/Ѡ:Lǎz옢jHys.;FK6J@֘irGzeWNJC.BH@7Z[&q_F :Ǡ_D1:8ؐu9L-H12s7ceK0b?`-#;+Aڪ JQcG mҚCGsTJo@9L#>2YԜYQ3#_BX~kA+FL0/K8sY 9Y9jp w| 07 H:)Pp@CST$Ҭji%n2c)r[㦻BgaR~u% 0K%kSM!'nځ[Z: ?93&j :ڵVߩs}@ 6Yu'Zq"\HSpVNHhCΟ#b/$^DY {A!*0McEFk( 8.Xq2sy.!x-N AqhOYp:׮]`\9[8c'$ҞD\ & !lwIpB@..~J!mǐB_;;GUhbnNZN1)0FAalȴÂDu"Ě|iAOEv7ȓ'"<HIMb'yrVT)0Mt2h ^P2̣ R'g#LVp/=؞@WKń[GMV6О$ RNTpgWcPzaUv #ދꭵ~}{^u<4Zk;ZykG.kA`Fp-xH>6YW.94Yá6ðʚg4`90xg-; QOVD$Zpp1 0*a0+h{U)=u̪A;6Z}Fłpֵ2v(]+SS*rĬaD+FؘPu5-ȯ^XY[8]S)iBqW^\ySv(g؅qpJhc٥ņǻD4Zkޥ{ .Sp @KE =qܺv=q?ϏG-c E6kIa l[p,zXЕK?l| l dq琱nE72nN`%.uoR$;DZ.ID" ;Xc^]C%UyFÃI~ MsX /#0}N!:+o:⩳i]̐{5#m 7LҒi]CG3wԞ{U,xpӮ![mSv]1#̺V:v`59؟?nl6W}@L`}7V.-DO ']HxoWVlꃄTiRQߊ$7~q1-dC.*kT ٨M{io`QDA0Jƒ|V nDZGyq1m4dqyv(ߙ7cR)XʐCW\IЄ 1#i ECt M'%En ``ru|96DDZ]*ׯ tٷm}US1Ѹ#6$GnaHn:%WY>1^tmKEƄHpp&{ǿ_7/_O$|a۷ ܂lcinit-0.3pre15/doc/devel/cinit-status-translation.png000066400000000000000000001722331125633325400227100ustar00rootroot00000000000000PNG  IHDRf%sBITO pHYs IDATxw@?0"#`"P((|@ԏ{ԪbbjV묃Z⨶ Zō"( H}_ I+r OwQ4MbPG-](VWOͲS 1fGSlEKQTJJ ۅ4-Dh_DWWm۶m*7/_^RR-6o ٟ,j6.]yz&G4/'Np8vvv~ XmzoB6l ލ4dZ &&r…z[k-DCyۅ4-.M6͛'$$T[r7pu,;P3vFhLaaacǎ[Zޛ ::zZjӦͺu_] <.\dIIIÇ766r:t<3sLKKK~ꕕ%K?~ٙᘙ޽} τ{)FLL|Ç/޽V?߿?sN:7&&FҬuk4b% SַWNJEk-[(BC'[())iȑ|>޸qCN)׽{w]]N:gZ{͜9zhntuuLw裏 Z@Dfeܸq\y ܾ};&&&00P^D&\zUo޼3sLBȹsbbbbbbRRR) gtbbbw۷oرjB??޽;::zӦMׯizԨQڵ^xСvvvtӧOs\qϞ=SN۷ջ׊g\\٬Yٳm6]]]IQnAqa6PJ)][TEOPvvGt۶m<ѣGtJ###{{~iժU5#̽]k ;ŋyQJݹs>l˖-ݻwWl ͊q-YD^Dzzz_3wӧ}ID"XLZܿ_ȑ#|&%%Uk̿;B]]+өJgg碢"̷o*_X{͐?򊋋% f̘̺Fe SL@+UkE)[^Dhw\\_1߾}>ce:_|r%{r޽AޮLDXzdPثW/%ufeeq8% F4+<!-0zzz666QW- !111---ǎ;V!C|۷0`}Æ =y$///3f2ݹs'--/`*dXZZֵzZ1>ߪU+f\GG˗ʬۤ)I+dEv^|Ϗyhii٧O˗/K/SҥK=\L&EIv/!9#kN5JVJKKϗLs8UgoӦ̀-[&y699966V[ʴi!qrrٸN:<j,LŽV`_s:uDkX”$jxdH樉B^DjbX|A__cǎ]tIސcSkG7|sŁ>|x޼y;;\z>|ɓ'BaQQgMB>}*%l #{͐?<8`;vHJK`]B?|߿ԩS S~oe:U+es8?romkkj_ߺu˗QQQ /LqСCӧ{{{x"<.KN:x`c)(Z/HVZ}?C[۲eW_}Ѣ.>"Lŕ?af"rss;vWZ%  vQ"h*//^hȐ!6l&Ep-Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 " ˗/?{4M]οt_eFp] SXXlٲnݺ$$$]Y`'UеkÇ]  4Mܹfʕ<9(..ޱcITVH$9رlm@} "@D1cFAA<اO:5zjkkk>oaaj*ffnn)SLMM|#~Ø1c%ܼyHDCvv6ӎP(LLLTи4+Jo=66V^;6l700Xd f͚ٳYf+#99-..N{:͝;W%ss|%[~Abb"M>dg̘1eee!!!c;99u5''鬬,mm턄ӧO2iff^F\0ӌ KbvN<|Px!&j.fΜYQQ[P Vdd$EQueҥJ6?^XX(SLv%YrĈ| Meee&&&W\"Ǐ)z4.!sj[W,XLKG\.yADhn[7o],l޼9$$Ҳ%CCCurʾ}R+Y4;;ܜbff&4{+W>}Ot>ߦM陊W"Cu>|844455lGO>eNmHv]P+DhBKJJZś7o^~2 7nܸqeeeGɱr|oȐ!}˗8Xm:??Ç4.sj^zQxb:Bty2W%K*++ !2/P.W&T/ݽ{Wbcc!yyy|)summ &_ҥKSL3+(={L2Wv!yCIV155- B{{0BHee֭[ه "@zAV|2ϙ3G =zW:::;w644twwBPPХK|||:tPH]]]CC &0i\le…^^^~~~ӧO,?{?^E:u{VfC!ϳbzEuZjv-"4!)\XlAD&4zҸ@]ZhB%%%2/S,**JJ=P="@jժUPPP]8p 0MgϞJ.OQvڤU@0M GFF"Dhrvvv7nR?@1DPgg7nl޼Y |u֋/~}]T^rfffmڴ?~<D`ǟYRR2p@"zBDvھ~ڵc"  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "Ȁ2 "  "ȀjiKADv횛۹sj>ioo@DP'OX_zJa =PR{{g:ׯ_ѱ/-- l "<o…j ׯ/))5jZ(@_|wb@ aTGz c !'"JI޽{00*%H#b@=aTM2pb1F@$ "Cj f !33Cj 7ydP|ׯ_߱cÇmv- Ź~A !g&|laTJ&NcBٳ10#'Op8%!ٮZ{ 'eADUH |@JPCдj uMH|@JP+TH D=)@M "@w>` %Dhd  !"@cj|@J`"4F !"@h|@J` "4& V "@C5i>` %t_m###ގ ޽k``tU=y=\*ӧBfϞm۶& q X`Rk׮VZ͉٧VH$sرcU\L&oW/,,tvv޿Sӿ g͚u]l)Nj&BDPSWVbfN2Ԕ1"++:883[͛7 v BabbkK???r}f7ojdd$!w566d___###778yٳg^^^|>[n?ŬY={6k,[[`BȆ  ,,,,YBt]ݭ[jkۺ2=-._< U{"6"sN--ϟoذI%o>BᡚʃTZ˱Yŋ׽{w1.}3&77,$$_~|'']4<5})S4իרQ޿OӧO3224^kUNNN;wNHH(//1cF=hBpԩ%%%߿իɓi111̊w b̙3+**޾}+ k"''';;dHfssB(:tHɓ'ә---8PsW3}^K֕鑼lӳ5k0/bS8p!dڵMVZB>sXԛS ǩ2ǩ"xw҅y>|Xr<6߽{;fŎ;={)S,Zb(99?~P2ӧEeee1 !4M;99ڵK#LLL\BK}<~(XRqUUz||<hv횶viii=\.9i>x𠼏M61b<22!^ڂ jvZL.fg?zٽ~jRZǩrǩdWP%mll"##/}lviii7n3gMm۶t-8Y0T .<<<44ܼW^W\!Rijjͬbff&Y=((O666n<==iFzTUm"H$edd0;tPYYYA233UF-ٮ];f(BÇmlllmmw-'m])]|>xDõ-ZnݺDttKJJ>;vP[+^AәDuewٓYqTk7v ۸qƍWVV:z蜜+++.̗ g]|>L?|`jj*d5ImaaQPP|hkk ]]ݲ2f߈+UVVjkkBM 3A4CCz!ݑׯ_FGGՋŋ3k^K+**j푼% yH`` !dԩ-",\W|qZqL ~X,~捅c֬Y޽|||x<^<EPG UUUzzzP+$$Çyr֞0a/]4eʔjϺz{{Ϙ1_ٳg4.*yBʲ,Y2vX===wwB*++'+3_lܺuMzJ,4M3 iRR3_̌:tH^ kۺ2=m/bj8N9N%రdXfN(o߾6m0PAϙ3G =zX<}NΝ ݣt%:|622RWWp„ QWk򪒉3gμ}nǎ7^vͭ>>>2WP7FN8ھ~㕖""TK`|0&K('FDD Dh~gmA#ܹsOJJJٮCDm۶iiilW|rhlmmvy9`"Bpp۵@υlW 4lW+Bb kkk:011e,%%lW Xw߱]B3wD7- u2 "  "Ȁ|TTTlڴW^"?㓒T_h"DCKKkΝׯ_ߪ=UZZv#G<@ "4\.wҥUVUHؽ{wFFF݇ Rua@S4-+**T\ 0aË/JKK׭[GpSMP"h .mԩS5zꕕՎ;T_:HL !@= "FJIIIOOk$^:;;֭[$ !D$awzT^^zĉѣG3wzLKKprriر#e_~2euzzzNݻ߾}QH/&THXzueeĉc !/_$BCDM'mÇ+RSS8 9 ВI.[^^@SI$0s~' !H0 UUUCP/4@r ! @"W!@`4d RUU!i@~0M2@QIUU9N^^۵4ϟ;;;]EСC.]@0 !!!4Mck׮{%$$4 zѣǝ;wx<^^ztRvQF@1 BZ|7[ne~vtյҠbqdddii)mV< "@scǎ[n߿B@ݹs?~5YzuB.jbbbΝr/^l2f7D?iii+**z-۵ԙX,711a:366i5477|8$$СCffM6?U(,,ҥKJJʮ]>3Tmk zy!N[[{ϟ?}|||b1I.***>>^ ]MQQQ>|`MвܿiPv-P f`l-"BIYLE ",EՕBv...lR\~}[qtt\lYqq1!O>K.eӧEQ7nܐejj)YEz(//رc<@ P#zzz۷yG\oNO<٩S: zoݻwC8qbFFEJWi ??1cƼ{Bp޽bO>e%\|sΗ/_>>5OO<)5hiiq8fZGGiiiYYYfͲvuu S \qHHHeeerr)I% oius-//gN>MݻϞ=I L&(,,| #B~Z<4:Dh-`< {=!D>>S--ݻw7p\.+Vpvv_M6J?PehhzEK7dMoٲpӦM{~ett4&Lw^&A̰˗kaaajjѣwIl=JBDpR9xѣGeff}x<[qiӆRO .v+V6pׯa~~ٳLR(hdڴi*njɒ%4Myyy^Z)$MfddBסCoooBȄ T&"B{˗/{xx|I A/8)Yf-Z/066644OWZ_){{z~6_pG~ƪAOO믿xp144guxx%)ݔU׷CTUU[XXXXXٓ={Bڶm{ĉ$ ̩+WH2H4_pR㴴jw8qbvv;w2^CKKk֭[vmzzziiÇ?3sI5mذa%%%nffe˞ر]vUKKKVZ1B__ĉ'Oϖ4J#2-ZΝ;k\|N޳gرctb@sss d2BlllbqϞ=k6=ʢ%$$$$|Ϗ9UL\H33@pԩj1.\d7n$ܽ{~-lo٩Rڴi#o?0T  ֽ']Czz.x|A&PHy!ۅ1:2-F_pRjmm}!lݺuAj}u)> Vl9);n8==ɓ'nŋ۷o2e?Ɔ bq6vXGG]vl!p8I& ɓ'kii9rdҥ۷ox{{9+YWGGG@ӥիYf͝;We-4n; "@uI~aݺu:t7n2'eѽ$'5߼yڐ iG\9ѵk#G 6x]vڵu/]PN|||tuuٽ&%%`ddԷo_ccc Tdh~#"""""&Mv-PDGGGGGDŽklǏ?rHxx8|h!bIAAAVVs19sww'v˓TPPжm[zÉP5 ܿB@PDDE(zpRVI^^^̟7h=zp8۷ow֍r@bqXX!"ՒDC"ccc>}v!PgϞݺu+++B4ќ9s.Ta3f` вबa^&"4+W:99=yghr/_\h!dΝ[f вSp]Lj#xg͚53f}ӧOٳdҤIÇg͆в899n߾Z@ׯ_~ݻ]K3o>sNh+Fɓ'92331444~9{[jJKKvŋK\rOݽ{ B;t  n߾}޽/_4f͚3gK7Bw^YYv- _|Aqss+//gfj޼y666; Lhii 4(--XQ(77۷ Xݻ'Nhkk߼y"4Xo߲]N(..NKKחDLΝMLL]\\0rиZ{ 2$++K[[{ƍ3fr#lD'OZj믿5@]pa :<۵_#))i…;v={ٳ۶mQ1H|&0`Ϟ=ڵc4hZ.۷O>}ɒ%Gjjjjjoܸvi-Hv޼yC1bĒ%K(b.D̙34M'&&޻wdlUg7o,//ָMLL!{ҥ a!(lROm۶MKKff  "Ȁ2 "  "Ȁ2 "  "Ȁ2 " jիb*@8KP5DuC:998pr={ZT @]dff$%%u AuL8|~EE"pssKKKprrBP`t8011YbEzzG}v]*F8ΤI>}իW˖-ljMlPm۶MKK5k۵4={CرҥK'Nrlٳgo߾ 5ajC ZkŅ(%WY|˗ !zzz=zѣnS^|yȑA?Z@ "@sDh*<ܹǏUUU]zٳ_wppHLLlZՀicc>|РAFFF ֺufZWW U!DDhmVXXv޽{W~~>!D(.[lԨQ-iĉK.MHH`昛XZZZZZiF$z~!###33Lcc Ξ=UVV_bř3ghݻw;v,U@͔mۖ9HB'bUnݺձcGfy;;o&..N*-AZZڦM})^#F`ry󲲲TS-ADP#4MܹS[[beek׮JTA{թS)^AFDP&&&u 3gdVYjUUUjJP>>>./ttt:".ڷo/p?zZƟ:u""",YpTS yfoܸѷo߂w-22޽{#F8+۷o{zz*ƍ͛{5ׂ??~Q.Gäxzz~֭c5yJKKҾor4իW_UUu]wwwPG@l۶---}ҥlע̙Cŋٮ@Ma@\xlrrr򢣣%E0ӧAnz… 6] :BD0O&H~$޽[K6mùrJoCD$7n8peC[RRRVյkÇ7&@ ٳgyyv-j@\pA$Pb-*boo 5ΰa!ΝcI?NQѓBQTZZ'!4M2dҤI)S#Fdee1-dgg3 B!s#iSSXfwBf͚ٳYf+hS\]]߿̗ɾFFFnnnqqqW^mmm-,,VZ`_1;ٱ @dddB꺢MiӦ;wBF]RR; &0ˏ9煅R0huΝ;oݺ5%%e߾} ڬ… NzIO̔4M5K./^dNyɚ5k^8|p{ٙ̎aPg ";wN2~~~<OK;udhh>}JQǏSݻj- fΝ;|> [kZSNNNg=zpbu͏r4?^XXX.---(JGGj>qssQ|!!dڴig`̙3l2j(PHIMM(Wivvvzz:oӦM=*צy%|>3D"H$̩fd"<<<44400[n+W۷BUYYǫG+DM[n1F+`hhhccSmH$2e/\2ʊX,ჩ|]]ݲ2fZ;RkSD2WTTUVVjkkB/z7nܸqBCCG#ﶙ%%%ӹsgCCCww(H]]]CC &B6nx577Kb{522?~W\af~Xtivv-d:::lL={J @|__ߪ*h;wj* Z"9r$!d۶m8Kp[n jµ!##ɓFb PRRv9jF__o%,Xr4ʕ+G| F4OeeeΝ-[]F:s̨Q?~v9G[[?3h'OL4I,Z @"hO>dӣG/_N8_eQM5uԯJ$ 2dƍl/''/_Kn 2!"h7XB,ϛ7oĉlWbJ@ IDATƍ>|0t+W]ZCD`E-[ĉʕ+)X,>t萣ybEN>mddv]"4 s !`ȑÆ k$o޼y'N$&&BlmmwݿK GLL̢Enܸ<ӳGyy9F^^އ޾}իm۶Uu@Brr24"4q۶m14ݭ[~pDDQhL|mmm !h."@# $Btuu10L2@(4>f B\\ f޽{[[[] N4@ۿXXσb1@} "@#ۿ? Zj%f(3DhLL~?)@C!"@ݻ4"4j  04"4Hq ͂T|@J P MuV|@JP7  u(@YH vMH jѤ@RhfFoܸ*/^\~]@"&&fEEEE`-خ"4k"̙mX[l/ٮSΝkh>RRRnŋr#,,짟~(jԩ>>>MQQQlW++`hV>`GB:%}m۶4݆ZǏ#"p"(ңG/=ztĉUUUM!uPAJ@>PCP&M  D)@m!"=% 3DFL jQRCD:k`J@>PN )@ "@)% hDh%SAD5% h"Dh RBD!3% h&;4LJ0`ѣG4F1IN< I k"h(Dh|=zhӦ !d̘1lMBGG7q]%~СC-ӽ{_tV)p";wϧ(J2 ,ڵ*Pg-H$p8lKMMܹ|@;vP8jo޼:t@ .**b;;;/_< )S#Fdeeթo!66Vzgg{{{j;--m͚5|>ݺuujV ;y󓓓}}}$^ښ[XXZփ:g[[۟yÆ K,iYLɅVl "MÇ733JHHx.\8uǏ'M4}tfѣKJJ޽{gcc3a„:yܹӧO'&&V[1""~655Do޼9ҥKo ;i5jT.]/^o>f'OYիÇ}7nڴi)))|Iǎcbb#""duY(BH@@ۅZZZ999k׮ikk4~fG8X,~)EQYYY|BHffmڵKf%NNNwf:djj*...GUYyB%Sws܂fiNNNxǏ/,,烃Ν[s iVKBȖ-[.4EP ###a*++ !|>D"H$JMM(Jz4;;\6|/'$˕lV^57|455544df2) ֭ʕ++ׄÇryKֵ@,,, rss?)))@VVV\.Wwf㖪L[W$ɜ_QQWYYMaܸqƍ+++ =ztNN+_~ݫW//^X TlZ .../++^dرc-BHNNNdddlR7_(ۇB*++nʴU (sѥ3sСCP^% "JQu̙oߚ988رC*Oܹ;sElRkPyʜOQԩS?лwof9s##G*r… O_ UМP?h.]b W\>|xQQQrr2ӫ9s愆nٲn@"@iѣGtrrG!_D,ݻwVVV.++۷/Ň;wW "46mXYYٳG2۷o?EQ}!dݺu +VBf͚a*!"@g@S9P@!P&("^ "*XWQ U׶rm .ZE\X H$1ws Cy?L̼›9sfLbnn` !0̕+WR EHG:\Ct^"F8CPAA !yA@͛7BxgB Mx TEE%++  EHp ) !BS^ADFF`Ȑ!T@WN Ctj"Eaaa>|hј1cVX$~X@L2eر0@G~޽gϞEQgΜIEV)BRR҂ Z}ʕ+wIA$ɹs6`|>…:::׿pI}1%%"[l)--mx@ٳŋ$?~CWW޽{{UVV޽{tk{쉊j!|>)[qTQQQXXԃJuuy|={+ /_~i祈t_HRN:_wŋ;͛7ҍt7֭ &{6mGEEł OiŁG/lݺ V~wYY3gH4 ۧq޽GQ .]ԺljYYYT:DglllffFu,b=z>}:B(..X@wTXXغsssߟ@':!)6HOغa-p71BFFF__uͭuJ7Э0 C ۷/ՁĤuWYYuյ+յ-˗/AG$''hg3glݎ![]6EݻWKڴiB?~|ru8رc[ڲL@@_&Nb-Unee5gΜf=zhҤIrrr\n]ee%B6((ױ%£lvDDUV4obbZE4Uv͖+)) 8piiib[v.\}}} qF/uS:*Hnn9O?#毿ҍ݅rxڵ={JRﾻs(tU{{{kkׯ_^x177711qMT; U7nܪUׯ__[[;a„WVV<4U=G*_fM]]]AAAXXXmmСC?:X?׉'LMM>,EҨh <oĉ{߿DaĈ;v쐼e&eۮ" ߼ywwׯ3 euttLMMCCCGո… 322ÛjM222uS;Lrܼ<CӍVo-j٨-`tr h4СC?nggT ڡhH$CCC\VTK.%&&Θ1F|?Μ9Sf^|YvmOBaaaW\/! ~ܹs4֛7o\ٳb06lxu>}.]ÇV#ݨpwwa]]䇄YZZ0RuQ -&&&.]ze… Ν;'~L}ԨQqqq VʛA7mڴiӦ ǏgddhkkSWWWEE@.\]hG޽{ƍ)))ZZZܹs[єvލB Ǐx,Kdܽ{d޽{_~Ayxx>|xՒIVTBv𭢣G޿Xڦٳ'$$~Vpwwwrrnܸ 7F͘1cŊ#FhlwI0mmmmmm1?竩IRFm۶mRcpo߾}xzz2kDjѢE™ 222͖7Oܰaȑ#B֭DЕ+W$}~Z̴IWUU… Ε6nܸqFݳgϞ={jiiy0{ƍgtttΞ=aÆ$I6wԩvھ}PPPXrePPׯ[tSQ1L*o… 666bno;v :$y LigGvHGyyyDD͛7 2eŬJƏ/I.EHOO?s Zt)o:)((̙3G]]=55uMc{{ok877 >|xϯΛ*'I֦۷֭[ݓ0k׮khh7o.]Qϩ#LLL:NH vܹJ '-+6yfwAcqrr}TUU]]]9=&MTUU-*))eeeM:UYYW^/_722ju"ڶmb=˷lBY, B˗p!WWW?ΝyƕPQQFQ EWݾ}ׯ_"##A ٝh4m@SSꈀ5n ㏍SرcSNm4@Dٳ@@%%%[x >>:^xA tHׯFFs,:^WW`0JJJv3@333d+.kccӠǧESwHQ;Fg2mQ[wq!rrr#Fx hgfff-=DZtttz餽qC~tEŠ+pB;v+.@YYՁ%EC^^^{%&L1bHU]]B|||vv6|N[!5k/ uxP||<Ձ$n*(-RB~@:ŋ$IR )V!lLu,b=;v,ձ"Ej0M0!==]ժhA!!!4yA```߾})BHNVbq&OWOOϺ: Irٲeiii&&&AAAT@+_GoϞ=O<+CݻwǏǎ}A)ҧ=tO>?~͚5wޭ:.Іx<ӧOonllɓ^zm2.@{8pwܹaÆ[nݺ!ԿaÆUVVRܤ$c,߽{* Eh4 ڵqqqʯ_:4 MA(++abbbnn3A)mf!$|BuP@z9l0 Hh'AQH r^)D"@ E6lӧۭ v ""Mh#qqq (h"iYZZv.Ο?FK{=X[[xb|>_cmu;ta|Cc^</22(@wemmmUUUyf\XRRfUUUN ֮];f}}}#G y)?_TTa2x 355ů-[F:NNƒ-```accc##\訢b,XPQQyO~,XиoZYY:4..Ncǎ3 (\)e:th=##c̘1***x; /NJ0yyP]ܛ7onz4'''\|!׮]LKK OMM'Npqqip{ڴi_|III˹sL1;;7o ޽ۯ_8͛7o^r%))_d B$I''' wޥz{{#khhwޏ?9rqSG9w\IIׯ_%9#׹q_ xaEEŝ;w;vԩƗիW ;IӧO711)**us }Ձ{.;88Pedd(**^t˗/d ۲2Pnn.I ֜:u5kHѣGLL IN"I2)) =i>s\k׮+V$ٻw۷o 4ׯeeeAbbLqq1.N"Iܹs"/נAvލ_ MM͈IHuߗQMKV^^Ϝ9,Dٳ@@'Ghzzzǎ ԴAeee1fKKK6]TTu)@6vgggٳ~ƅܹmoopΝ|kkVp3CEEE>srrTTTzuuuX>} tttrss%9#׹Ϗ9RGG` IDAT_~VTﹹ0fO N{MW=UWW;;;ՋFIɓ/^}ĉsQSmmB6-,q{{{:< ??ٳFRTTp8%%%8K#NgXg@ff&~A$_g ӧs޽{Ɔ | vI$`=#׹A_x88w\S1?MMMP]]޽{[y EMTVVXb8p… jdd!477S(D}Qtuu!//d2=<<_AIg2w!{{r;;;i8AW^GVQQqwwo|y{q̙(eeeIΨ\!C^jرK,5PdA\rҥKGҕ!~-ݻoߦ::+Vٳ[@ E"@H R)D"@ E"@H R)D"@ E"@H Md/_={sLm#jjj쨎EjLÕ@W0E򊎎oeeeծPԨ>}2eÇ544 @g$P__/_(**[XXkjjS"&;;;!!!>>>111**?ա"'޾}!~6Mi`e,Xr/yٳ/_|%  @[l}6Ŋ ѹqƑ#GTTT#Y ^~yfK.9::RV?z(BÇTS򪭭: 3fpwwXp!IT󑉉ye޽oNu0@Q@;heqihhȵ.\xpggg)((222·"qܼ<222222jQ#W\l*fO׌[nZ[[_G޼yrgϞݠ\GaÆ飧tArg͚UpEEE/^sNBCC,-- pooh֧x.\(##h4ڣG,,,6nh``Я_7$QXXs'{n?'&5_zwð>Eٳ'Pţh۶m۸q/_Zݩپ}W{zzh u^^^B|./Z('w\3gΨ>~a㘛=q&^z ~M ;p85A)jtE)((̙3G]]=55uMc{{{@~Bpuu8p`UUUHHHMMM?,kΜ9222aaaAAAoU=q>_]]-<\NNNFTڵk~B͛K.-**j}hiiKVVKNNNNN=qDrrrrr;6lؠCu Ïq$Q`ffFn.kccӠnF.,//oʔ)x1uuu__%KQ,ٷo_uu5Au#2...L& GGGwȑɓ'N2%55u47lgϞwzTTСC?}DuP233\bffr/_>`PZ [^^ޢu@grKKKH.\H/LuDѣ_xadd & AӦMKHHDccc;R3? ɓ%K Ξ=Nu8Ǐ HJJʥKڨqgggCCØ(l۶s222VbN8>F?aݺuֻw:Χo߾w5|}}}#-߿!d1/[ tuua O}իW^-Zv-i}$Ilo߾TO&!!!!"áRnn.ުСCTN ޽h4ݻwT҉-Z!Ju h']3fHׯ[ZZ\g_~SǏ...I=z,\022Ju(&L'sN>ߺIuuux޾Ο{еkHcsqr~<oW^URRjP;#Fcǎζmn[k˗k׮߅(p:YZQQ' [np80Cў?^WWwnnڵ7nؼysPP^뗤 0@gffOĤ_~?~|pt@aaaFFF޾}UGlݻw._|8~ZRR"H^ii L "##?|bX)ُMh4%%Shszxx={v"Š 6%)YY?\.,$$vttѣӧKJJVXq:[[PuQQʕ+_^SSw%}}}67$spp(--y#GjS(,,l˖-^B-[,44d:uj޽ϟ?Gر?c0 ,nd``Gɓ'ǰe˖WTT(**._<((H255E}~[6lɓ~M8:ŋ:;;oذX:yyÇ?yd߾}+W0iύ޻H8*pvgt]cb]]݉'8ɓ</11!dll,c6.ѣLJv9p/_$ikkRRRR]]mgg+L>$䜜$Y,Çq/^צΝvTB222$I4hQQQ$Izzz:$I&%%iii8q4?uÇ7!))`$Y^^իյkB'No/ ",k]u5]QrBGu'rM.URwBx4p8xon>][yQ|+555==ϟ? GfBw?k%;::Λ7oҤI\.Ç ۷7nݪWPPѣ<< Pj@BϞ=mll|}}޽}Q\gќ9sbbbΝKL&BhAAA$I6YIIz0L3''G8rXj7l{ѹ$Zf*t\&Lwގ;6ol."lڴiݺurFF$Myy9dddAjjŋ(E}pae3}t,6==cǎϝ;wС6m7nh8Nvv/A'w턄˗SKGm۶#G[ ]*E={vhhŋ׭[A2|TWW:uH XYY_^MMmԨQ=zhp&Ӡ{zz߼y'OիFkZ@ (+++,,ģBuYYlǧ8??ٳF}iܹw޵!" --M)7Hpsssssvvv...nP!t֭~)77!иxŋdffREFF",XfIE\\ܝ;w&MLx<fܵkpAu++7n>}oaرUW-,,jjj.]f\.IG3gsPTTtȨQ\\\M¹?INNN¹6mTh4͛o޼xBnnn߾}w $l uuu bHIIy!.?tjϟ JW 0qqq),,,N:--lܸINkE@3cL8QXAKK \>/|۶muMBQ}͘1޽{ёUUU,qڴi~I__7]<<}Z"H~,X I/ i.`t:޹x/^@ݻvN</QEXjB~SGd@ ؾ},4hYqq1I|>t޼y_~-((3g>VJ!",$kulMr&d[OĈ)@ [?~X:77dPhhhOqxkh?;v29vI eddp@tzUUURRAxPrr2A[xLnnnFFKIY(Ik$I\rL&311QX_dl/ ̞=: 6mڄZ~}MM tbNJNNlydd?0:ٱNk]hQbbbVVVNN.nh"'.\)D%^D,MLL VGBIZC-[ݻwǏ˙l/;seB"i̚5ӧOxxM6Y7D$zhᔗ $#NgXxK/E)S8;;$Ta 3~z"jvVH4dddv؁ z PxxaönJu 3g4225k?-2׷(00UAAhȑK._߾}kllleeS∈лwbccy<‰jmUUUǎ;t萗Wmlvzz:~l/ @@wֺ4إ>}:_>""B]]ʕ+|餮}Y< ^g }}}=="""L~!22RNNАdm*++WXbTTT8Yؠƭݽ{w߾}ϟ˙{xxG>|XEE]^***tttTTT.k\`"x<^6U__?++`Q,F9F}6ձteWzE{vyͲ.]lMEx񢱱qZG IDATZ)Ĩ;w֭[  /`ՐB\4 EQRRziӊǏbŊ_RT2jԨSN1S>[ѣG{I||<ɴo2tJ AAA޽{d''|RWW'UTڄðaòKu,?B觟~jv'h)̦M?~lkk[\\rJ5mڴ#G0u*..~i@@!CL ^zellLutٺukii)t\ׯ_AϞ=gIwnFs]vݽ{722222bڮw˗?v4`pO>_ FyzzܹSMM@pppppps玗Wxx |n(''~@YgB"5L8qĉ/_~--***//e[^XX`mvp>jjj7nܔ)SFMn$$$dᑑ֭kv9;;{˖-(gϞ-Zh~[PPPXXئ5_|y3f"Buuucww… &믃={6u|>֬YO> )]VϞ=-/uϞ=Cl336Iٳg˗/7XK;??ƌ ڵkl6[c!u,[СCrrrvrtt:"*<866O><+QJR]… ܹϯ[RRѣ?>tЖ6)f;vӛ7o^xxx_d,//}ITTҞ={qtt|}O7lУGLZ"| 0{캺-[/͛7Lʕ+ v&++XWW믿6Ǐ'N ؘؤ nذaqqqk׎3F__?66633QEEb-XW+**dL&4-- !TRR UUUN+oٲE[[[UUG2Ex !X,"SN5HزeKmm>UIٜA$yyMMJ\nffV\\L$7557oׯ_ lll̙>}zAAI999$IںTWW{{{ّ$`0H,//US lv5Zh9Bĉ!&YXXHuhb.]B͘1@BϿ>Bh̘1>|hTGM$J/|CBBpabb NH|NJJJ""??~Aeee܌ EEK.}EXYdx"h4N722B5 !f)BFFNΝ)¢EBsΥ:o%\MMsssk "''GEEGn]]]QQQvvjϞ=뷖EĘ1c ,--lvQQޱcǂ555mllbbbB" H ?~ @7gΜSN!O8Aт[I"|AS^^^RR~NX,mm{ERQPP`hhrss{AQQє)SIl@-<#X]],н ̮0 !$ap @uV T0552douuuQQQ``ȑ#.]ZTTzmnn7N#""B޽x ,KVVB@@ (..!5)¢E<<@˗/̘1[V,XpQۮ"fggge!@1p@aaaa`` #iV:rȧOrrrrrr^xAU0uuurrrJkiiiii?d@ |xjj*!d#J(((~Z6 fϞ={xt!RSStgϨMՙeffRKx |}}) Ot W^]dINNBHYYyԨQFFF}Gmm3;rrrt:G/?F[KKKGG H/T>~'ڐ@}o.W]]]?i E>@}veHH% mܸq߾}$I޽{}:z ->}zyyQWEgϮ^}v>/++e S󼼼K^r!5rHsss333AUH[ddd'$$$%%x<]]#G76WW_B|>0@KݻwOOO!dccAΞ=200t@ :N#==}֬Yx|/>}UUU9BI $%%YXX صkHS SNI͖6ExꕜA>$-JJJ`w:~yEjkkSy󦪪*BxTQQ1`ϟ۹w>6mD :)r;ܹsm_CE-_{Rq5'!:oV>|ׯ_۳!333< u mxgϞW***ڿw -^^^-Xn߾M*O>ٳg[ߗ/_lNUKR45?ӓfN:5//!rl˗lɓ'aÆ>}![~-X!emmmUUUOQ?~(A'lYYYSNxAAANNNŰX7n03g={ehhJÑf[[[jooo;;;\գG>ܹsxt\III #--$W^EQ80zhП]))//oΝɉRQQ)((h}!Ku R(۷o߿~555yy[FGGGGyM4iƍ.\UEE411NӑDn=%%%>}Z^^ðt9::N<_m 233L& "S4"dee1fKKK6-\Imٲe޽?~v;icc#;#G5fS VÆ -++k~%K]w[l9pmӎBCΫZuC!իFKGAA^֔{zzGGG_~ =x𠨨hʔ)d[֭[x;ܻwͽ~MڳͭĉmQEE!Cڴ 2D^^@Z\\?Z~}UUձc:)NOOǯ߽{X,OVRR!]&LSѬYBx^B),,3ڴ((($''P4?)''ghhd2ܹ{}Ο?/''7c www>_@__ÇWVVXb8p… >G&M.''7puAAA-A?fq~UWW411`NWZ;;;lccSILϺA̲1ae999/ ?9~-#޽{ iii^^^n1wKS -\Raffv6B~~~ގҋ/rss[Ǐ\Aw|УGÇǏCۗB{l\\~!4~??<..}`0΍ "$*!<*33SuI ̚5KKK+11N'"mTNNرc]\\q'N055=|0foo?EEGGFGG ijj6{$vvv <8w$mv"7opٳg7(g`lذ! }c}[tixx8\.+4{좢/^Eg-UUU g}lJUKK,-ݻׯ_utt<<|%j@FFÇDSa"YoJ]]xuШ(|cԔf˗/~~~S b|իW]o߾zzz+Vh'f;t/xY'Jb…/F{ݻ7nܘ/%z$6^CC!$LEY޽IC1? _2;wC[q1󽼼Μ9ddd &''sΦy}&+UUU!RKN }!ޝ5q ? {IeQ Z(Z[Aֵ.V`*V++ ↨UQQTPds7LCgK9˦MFFFŷn*,,+S+^fAư0{433?6lPSSsq?O<"QIjIikkϜ96m‰˪Uƍ`ۼ/ 4Zn0̙3O>ݺukImH|]vIďؿ=z>|xҥAxzz^vm7oׯ߈#.\HP(yR<#h EP*SSSPQQ[(wi6e˖-[萐GG&(0j(Fz֬Y⎾F/_|߿ ݸqH$_KΝiܸq#~BH$R͠ȧKCkΜ9;vꫯ:%EM'EM޿odd$+S\CuJ~A6mZ>}֭[%8BCCu֝>}xС ^$D"ss.](xW\YjUCG%Ez &'_owǎk8pW\Yv-B(((K,!g۶mWzyylQ]]]UU%F;VLoD{]f B[nwiƽRS"(ullի%Il! `۶m[littt,XbŊ&NNNVVVqqqcǎON̍^5nUXYY#99!daa! רޗ͛7[666G?WrB|2ox/?~EM:E"QYYǏ=hkkǔH%/:Ǘ(FѣWӦMʪ~W}BB?~ HLOO8qb|5iw֬YK,֭j*<',,,//իvByyy]zU wXQQ0$$䫯n]Rk0A444ٳyWWW?~ﾓ_~_.]jՓ'OjkkʶlRSS#(MMͨݻwUTT8p`Ŋ[nՕsW- $;䰶9s8޷o͛7-Z4p@5J[[{ů_޼yׯwkkk.ȑ#5CHU5qrr4hPXX^&5++ ?۷/7.v)nNr9 \E7bt:=((h˖-/_ :*3x+MlVKUϕ+Wg_xJ<Y߮>uuu111߿gl6{Ȑ!A![[/ɓ999x,~p5cRg:99YZZ;zzzl6а7GAl/_q㆓ѤIl 營U7?P__ɓN; &;w.!!СCǏ>}z1˿H] GZt&ˊW(sssMM͢Zgֿ] S"sQPRR- Smۖ}z+ ݻwW-)H$211`=i)B.^9uT$I33/^dggK___wȴiwww9P~~~z`B(ÇxukK?^,ʱc6AO3+M">_gddhjjDt \Bq'|ݺuO> gr<w$۷iW z@Eh;xfΝ;nQXXZJOOW]Rjjj}"ug֭ʬCi MzO# BP<[nYYY-_|ҤI::: ͛7ƍ۵k.Qpfs mkxjHUUt:^Յ6coSYZZ>~% uɓ4)AgΜკ޽{{BB[lxmW^)2}"ҨȣGB[8p`ddH$:ujGy ϟs8(%ࠧ+Çѿ jB+$9g2o HWt;w.ac,--333) @y5H WT^ܹsh#P7j[ߨQx<^XXձfڿrr{ &&Ç Qpebb2ǟ>!dɒ5 (z?)s:Gi}"$l?t%C8qXȚYfOHx2T=]Uz{Ztit:]CC#55XZСC! rM"݋'O4p߮]B:::K,: ";xyy$I? -ڇϟ?M~Gcie"ݻwfffǏ.\O l'JΞ4i?FCCcРA7nuV~~~+JJJ>}(^O-ENH\x1|ahߎ=䶳:VF o<>~hjjbp@ON>G+++ggΝ;SBӯ]3ٞ={&NHu\~zٲe'O TEE97oJsvv8qVݼySrwy<^```3mݺu555˖-sww/qPS$IxÇϟG=zMa\)"hGGgڵx_TWVV&qss۰a*/hhcc{?ϟ?/((:j]$IYXXtuԨQxqʹi4mҥcǎ_,Y"bхJ:u%qnllcǎjj#Ћ$/_|e;Xݻ8p3,--lv>}44xjOaa@ : hjjlFq555M'H@/^#A܅?SvRu%HHMM%ЅA ZBЊ EPc#!##!T\\ ]ZjLܑ`bbR^^]Z w$D"BЊ EPoBк EP{gfXЅA\P(ruuuTA~ӳ… AAA%h-4͇󃼼>~ĉX ~JUPPp<|:"|}}]]]]]]ljjJuD,QW… Ϟ=>|8d JVWWuիW2jb݅ B7o'PA~]t eʚ>}{BÇ߿k~  w>xW\;wɓ'<ح[7C@ rڵk"K.:" _|1qDPRRRXXصklmmݻ׷o_@pE5P~,ĉ0zTTT̘1C$M0!++ 0nܸ#G Z#@ANd Jx7o|zzzT`0N:eggvZ@A60۷ۧrԎnLL͛|:TYB+zՁܹ~~~>Ձ EPQ`%ϟ?kiiQh) ϟ? B@uAZ7? Khԍ7,XǖWuqƵ*- """~Ν;/XQ+n311Ҳ[jUee%BsŊOOO n߾-~JJJ]p!!CCv.\Zɵk׼ Ο?/>$?f.@NNN5 7hHTKd rܹs„ |>_iD̙3>>>C Ӊ'\nzzz3LEGGG_^^^ .į322d_[[;rȞ={TVV:ugϞM$))o\.744믿\Z@N/|ҥw޼<7773g7t#۝bŢ:&{_|rwwhݻgllA5?~zJbbb Bʕ+E"IC]|9.:t%KOTB g3.917zfbАݵHsrW^ѣhH;LL:c~ѣ/^8a„Zs//B__x]]6mN{n֭G%I288xŊvvvgϞmvNNNֱW,'I^񀀀m۶mٲٍ֧`+Vddd("899YYYEDD ;fbbү_?17z ںhhh] ̛7zRuHܹƍfͪ:)ScӦMTA ?P}qС>}o@ť8::8qq7 RP2;֭[O<ׯ_PPPTTTjjj*e~===_z#wwwC@ $IRh __1c$$$B~|+WܱcP(%vvvF޿_˗t:2eJlllll,,X]Q]Iݲ2LWWw֭~7Mdff˗/I,//qCdVEٳg;uꔛuV;; $]]]=Op8qqquihh ѣٳgI YtzzEMMMXXX~ZQ}UUU!===Q'AAAX5AٳGuRR.߷o.LOOI)))t::33 *S eee!.+]]݄q,l* z`0qIC[zfm6|$˗/˩YF=zHSSS$5J)B3@%xKr~QPP`hhةS'cn{dmyyyAxxxUbx>>W^MNN~eQQѐ!Ce``  ;6@?ƃ"ݻwl6[6]^^^ZZ7ot&ieeUVVG%>ҒFH󣢢Ə_RRBF !!!'OxG-urZ|||͛'|}}bcc\jX0Eh_z%6mD qѢE|>-_|ҤI:::NNN 쳲\?~*))x"55NGGd)2  !Q]]ￇcX999V0D oSLɚ#5kVPPPNN8qY}}}8ṡlmmmll݋%%%ikk2 IDAT"I򫯾ݻ7ǻtd$2ÖwQ|!2ͨA߷o~S eee!.K$Éd޼yQƯ322455E"d뙙AIkhhSRRtzuuGh4Zyy9.?v옾[nCii7J^HCȽYUUBHOO@ >cccK'fffE^^A?bxbrrrg… !@sf4hР0rqѢE|>-_|ҤI:::{Ѹ]v5؛7oƍk.777EWRC4՝Ndd$Q)Bri--^z1}&''E8ppm۶8;;6l-i1))I[[֖`} 3g|f޽! \]]}}} [,!!-[_^R䍸]tXAH=tLITP-9s̙38@u,aʔ)| ձrrr"##o޼٫W/[[=zL8ĄTEneddXܹspvv6._ϟ?/ d@TRR2b.3cƌiӦ{.'''...33sРAO8p a.HO .rnnn ΝxE77|6Mu* +h\ra]]݃@`;wnȐ!B2Ak.^ήQ `ڀ@;'6tA0!" 044:)vC.\DR+1HCFB_^ዔǏ#F԰ ڡ)S5dܹR ByΝ; E R޽{ uUZZqIݻw?~XRB T?^]]xT_UU˗/eqH$Rr<.]$$$oΟ?ĄL8… ,+99yҤITǨ EN:7Ѱ0cc;w(?0u cc4 *U0bĈߟ>}ݝ MMÇOo2dѩ:HԴO><oRnܸquGGGJbSMNNN:::/^wԡ_lhhhXZZ CmݺUz @ RBEDD m&ՑzjЏ?%1yXiiΝ; E TGB011(M5-X`Hu$.Ç4h"#B~GBee%t!bCMII0aɓ'G}y\Hdxݺu1bW_%&&>:O>o޼ia%"PC_srrLf +Q}4 C]rᎄ7fff"}.P^^ӧ֪toЋ/#dxP#z ˚cƌsȑ#{왓SYYyԩ={iTBMo .]$'AAAϞ=ܹ3Lj_|!W^!^x!U>w\:bt2c $߾};zhabb2cƌ |ҥK\]]{ۯXݽGׯ_/))6m444rwww˙L͛7 ճaKKKCCCssuɼX,BXWW+Ιlll˝ڂ>}4"Ȭ'33˗$I?~4!Ɂ*:F,E ,,,Cnݺ}5k<bڵӦM:-###33ڵk7nٿBg0 ^|9 @N:!={v .GPnڴȨNgK,9sȳd֣' ?~f F޽cqqqgΜyBHGGT*Ep\;R@u߶!TVV3)@it&6e˖-[萐GGGWWWs g_ɯ!󣢢Ə_RRB4><55t͚5iii!&h f߱VI L&ɓ'cƌ|>աdoo߭[P~z33ϟ?Kboo(=88$ID"GGr\WWWX1c$I"Ȭ7o$IL&S$I]NCp!Ξ=_⿱;v쨪j쮃l2^jjj~~>^-tȑ555T EH+))AHBCCmllh4^K. #00$QF1N:$Ioܸݻ[JJJJfΜijjj``ХK9s!C0 ggg /^puuurr:thdd䌆}Μ9 {y)@Hu $ӧO#UDsQbh'O\WWzs?4mݺu;wT~jvz >$$$r]tUdPzyyϝ;w׮]r|xaaŋkjj|>~1cܹQwN:_666-M__󎎎x֊S]Q#@}g;wX,AK,UMU'l$cMpK޽{!d``0j(ۛ "I277͛gϞ믿!Cl޼yȐ!TGBh۶m .III~~~X˗/ 'O|1E&OK"$Ĩq!Aˣ0Vamm}B¡COrVYJv3fqQ-ZţGHÇSN%&&feeq\׵kר<==_Nvtt?~W_}f ӧOO8n׮]2`h)))#G^rڵkۨU)$YPPPRRۮ{:t(,,lƌm׊dٰj~Q|ի#""ڴgώ?.**~hӶTAm=g;su~;vCCCGS@4iґzhMn)UF!C8qN+9Jӕ:U EZESk[=A@ݻwݻw믿 CCCѣÇr111TL"Pi񩩩ޢhii>}zժUׯ6ITݤIY(z R)d2@ EZC2@P3ZZZT@)@Aut"@H*qqq2Ϟ=Sr<t"T׭[>JCEEE?( /?|ю(9HkȐ! ***ڻwԡ[VVV[ZZR[I9绸+-<RJ@/ EEEAZ:KVK޽{/ [BmT-@Pi#Fߑ B۷/u@:gX'OD$9zS"͛5o޼]Μ9!TZZb q+W𰵵MMMuppXzÇiK lIl(ȝ;w0@;w UI5Pl^044tvv޹sbiiiuClܸȈf_IG2;w4L$ !dff6|PDD>A<:eСYٳg;uꔛuV;; \pħyzzN8燇{{{r{{{$E"}IܴiS~iNz=I.wuu=z䋒'OfΜ9k,H$rvvjkk 飯d2o޼_߿H5fff|$Ǐ+~p s̩Ǡ"ABPT3tP]]]濺t">`={2tqGӧO (,,?!\.IuFFH$dšu$)S,X$ϟ?3GFѣGt:OիW I#&$;. h#G޻w!tm@Yf-ZGsٱcW_}pd1// q x!333ɓ ]]]P( i4Z|||TTT^^F+++~yĉ.]H>w7Pl\.d.]iQN=z6mZ>}֭[{\.b0F~ R#ܹcllӧ@ amm-U( CBB&O|Ϗ=KiiiIњ=g۷ӦMr力A˖-{===Ν;w!_bxUUU8Kx6ǯ7~󣢢Ə_RR(çONG(( W<ӧOЅ@!Pȗ B111{hh,K<+y?~D$%%)ϟB7մ$}k׮w>)GCq8;;˗ -[ҷo . Ν;ŋԺ:&p8ݻwmڵKr"H@D EFFJz+Wv5a„ɓ'i-:pɓBOի۷orr:::.YdC={Oo }?jdx}&9lذiӦ߶m[JJa,3LCC?@cHHHpuuuwwWA6}SSS Bu8C^ڃ'N ֭[_x1Bȑ#T::Hh>|PxuPAjаi>lddDa*5@h4;;;H[cA@|N쀺055o޼:СA@;KuP"a>|xܸqTGP"Э[LLLVZUYYoI۷bXIII .$dqppht___… |~*iF ׮]600wss;6|Ahkkܹsr9۷o;dtkk'O(*"ѝ9sgȐ!>}:qMOO&\hQCTk…uFFkkkGٳgϜSNٳI4$??sЯZrY  :tĉEEE9O߿ÇSRR\]]$̙x˗~ӡÇ:uj2k?AԔ@=??p޼yl6!R ͛tҹs犯|&M§ALLL~;v<Lf7G$͝;wɒ%+W%666ϗsgPЋ@ɓ)SHQdիW/[Mw&,,ԩSJ!333??o,2e ǻd!IqqqݻwW5|sp0R:boy4֭[k֬qppڵkSnj ?~D.wرf3۷8pJ~$7Gѽ{l6=hР&],))lF\fMEEE[g[lyqYY?UT^:P_;YfOk\̛ᐐŋ U)ullTlҊa,X@WWR8cǎf;u$ކʥԿ9NNN;f 4444lbbgϞ9;/>>>"%MsI&UWW۷FQ5hjjFEEM:dkhh?~|Ŋ{iŅnݻ:>uTssⴴ4=P)Ћ@G7n8o{q)-P uT hVGn[ctƶܜ1/2$SGؔEgy͹֊.3-C``GcXr~UN=4O}N̜9300PwWRM6'((yyy$< ܝ i_믿~ĉgz__1c4448p)x#ۗwoɓ?~رI&I] z/"^@山SSSzxBD\ZX,;^atOeܬV ޢ!%>h\***.O͍7(u!XwT\.u9讚???Ry= ]iG-Wd2Z[[#""pAq S`{.4'Otң7! 1LGnnn>Q.]L4)11>%%"CB%99j{H.&޽*++ ooo+BϞ=СCaaaf)6jvdtRWN8rHxxCrݻptb6fbʔ)aԨQ*J^mm F?| !DLLLVVVXXԥBcZ?Lj9r˗ 6lXqqq>}֭[{x܅ "ܹsFd2wRWtd2x:&O\[[k0Ǝ uE+VlܸqƍR?:Z"p ""p ""p ""p ""p5\~ĉRW"DŋRW"D$44tĉRW D$ @K]+D8@DDի)))~{*PH]8'$$U ===/_.IyۣI>Hvv…U?"畜=88X"zm-y%AT*KJJofӦM2L€G7t۷o{yy-Yd̘1aСR!X,&h4:SNݹsgHHԥBD͛SSSSLٹszΝoZVꊀRRRQ__i \mmIΟ??k֬ADGKK˄ Μ9g*--}ߟ u9D}l߾}… r -kײm۶ŋk426~`$}:tHI>p9-zjjj~'k "h4 !ƍ'u!芸8!d"&***Z!C]a0Ü8vWč7BCC&<.J+ ooo Ҡ A555I6p+vUlx7zӧK]@DٳgZWXXիǏ_jdsٟoizz̑Ç?fyĉ󦧧766vj.pԩ &>|>e2wTTTAAAA**,,w߻ "B_|MUUl~Ⱦ}._q(ʆ^}t㢢"[,S1>//oĈ 3ǿUUU{7K|j7n܌3wt8?[nZ,_~I_ %KX? QT;v;vϟ?mQ>!m\^^^]]RRR:5IgghiiIMMXts=Vϟnݺe˖566d Bզݿի'/)=a„+V<H@\r<11ݸtʕ+A :tѢEyyy=0˗gϞv011Ν;.\h;ښ#퍁;6k֬BOED nݺ%xϟcǎZP={`0YfC i3ܾ}[}>;UTeeeӦM :p@^^N{3$$$߿?((( +++77799k~>m-Z$>+WH] :'--2""AD+pϛ7 .ɓ۶mڳgB,[ٰaChhh>}zMMovkkիG)u9?[V(ou޽ TWWfddH]/ܣpC)))NBDFFFGG HZ-uij-++3LF֭[Jrڵ˖-RW pO[nȨz,mUh4m?=zݻ.aIwVWWg4Fd !FhFi0=<NryţgԔIENDB`cinit-0.3pre15/doc/devel/codingguideline.text000066400000000000000000000073471125633325400212610ustar00rootroot00000000000000Coding style ============ Nico Schottelius 0.1, for cinit, Initial version from 2006-11-13 :Author Initials: NS This document describes the coding style used in cinit. Indent ------ Indent the code by 3 spaces for each level. Indent variable names, so the names begin all at the same position. Use three spaces to place them. Whitespaces ----------- Where to put or avoid whitespaces (space or linefeed (lf)). Spaces ~~~~~~ - After closing brace "if(test) return 0;" - Spaces before and after '=', '>', '<', '==', '!='', '>=', '<=', '>>', '<<', '&', '&&', '|', '||' - After start of comment and before end of comment: '/* text */' After ')', ',' No spaces ~~~~~~~~~ - Within braces and code "(!test)", - Before braces "if(code)" - No space before ), so if '))', do not put a space after the first ')' Linebreaks ~~~~~~~~~~ This somehow includes the setting of braces (indirectly through (not) setting spaces. If ^^ Put the if, the braces and the opening curly brace on one line, put the closing one together with `else` and the new opening curly brace on one line: ------------------------------------------------------------------------------ if(...) { /* code */ } else { /* else: code */ } ------------------------------------------------------------------------------ While ^^^^^ ------------------------------------------------------------------------------ while(condition) { /* repeat */ } ------------------------------------------------------------------------------ Do-While ^^^^^^^^ ------------------------------------------------------------------------------ do { /* something */ } while(running); ------------------------------------------------------------------------------ Switch ^^^^^^ ------------------------------------------------------------------------------ switch(value) { case DO_SOMETHING: /* code */ break; default: break; } ------------------------------------------------------------------------------ Where to put curly braces ------------------------- Functions ~~~~~~~~~ Opening and closing curly braces are placed on a seperate row: ------------------------------------------------------------------------------ int func(int params) { body } ------------------------------------------------------------------------------ If, else, while, do-while ~~~~~~~~~~~~~~~~~~~~~~~~~ See above. Comments --------- where necessery, do not state the obvious in comments: /* this code increments tmp */ ++tmp; If there is more than one line containing a comment, try to adjust them so they look the same in width and position: ------------------------------------------------------------------------------ int illuminati = 23; /* do not want to comment that */ int the_answer_to_everything = 42; /* 42. */ [...] while(illuminati < the_answer_to_everything) { /* only try before them */ overtake_world(&self); /* overtake is complex */ } ------------------------------------------------------------------------------ Header ------- Put a header into each file, containing: - Date of file being put into existence (year is enough) - Name and e-mail (obfuscated if you want) of the author(s) - Description of the function - Copyright statement (if not included GPLv2 or later is assumed) Includes ~~~~~~~~ Include system headers first, then place own headers. Comment the includes, wherefore you added them. Example: ------------------------------------------------------------------------------ #include /* write */ #include "cinit.h> /* cinit_ipc_* */ ------------------------------------------------------------------------------ cinit-0.3pre15/doc/devel/communication.text000066400000000000000000000205241125633325400207650ustar00rootroot00000000000000cinit - communication ===================== Nico Schottelius 0.1 for cinit-0.3, Initial version: 2006-08-11 :Author Initials: NS This document describes the internal communication of cinit. It is thought to be read by developers. Introduction ------------ This document describes the messages used between cinit, cinit forks and other programs that want to talk to cinit. It does NOT describe the communication method, but only the messages sent (for the communication method read "ipc.text"). Document status ~~~~~~~~~~~~~~~ This document is still being written, it is not finished. About Messages -------------- Order ~~~~~ The client always initiates the communication. cinit will begin listening to messages directly after its start. Numbers ~~~~~~~ Can be found in include/cinit.h. Data ~~~~~ A message always conists of a predefined structure (see src/headers/comm.h). Can't use a structure, were missing the point that we cannot transfer dynamic length strings. Thus the protocol consists of: client(int) => cinit cinit(ini) => client => after that follows command specific data The byte order is host specific (may be little or big endian). STRUCTURE WITH STATIC SIZE. MSGRCV! IPC LAYER CREATES TRANSPORT! Type ~~~~ Messages are binary data. The messages ------------ The client always uses the same structure (struct msg_client) to contact cinit. This way cinit does not need to handle dynamic data structures. cinit in contrast delivers different data structures to its clients, depending on the question. The questions are issued by any type of client, the internal command used is noted in square brackets ([]). The answers are given by cinit. Question: Start a service (and its dependencies) [CMD_START_SVC] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command is issued either by a cinit fork or by an external client. cinit will start a fork, which tries to start the service and its dependencies. The client must provide cinit with the following information: . Name of the service to be started . Reason why to start it . eventually additional information (see below) The reason ^^^^^^^^^^ Can be one of: - RS_NONE (it's a manual start request) - RS_WANTS (a currently starting service wants to start this service) - RS_NEEDS (a currently starting service needs to start this service) If the reason is RS_WANTS or RS_NEEDS the client must supply the name of the service, which wants it to be started. Question: Start a service (nothing else) [CMD_START_SVC_ONLY] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will start a fork, which tries to start the service and which will report the status back. Question: Stop a service (and its dependencies) [CMD_STOP_SVC] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command is issued either by a cinit fork or by an external client. cinit will start a fork, which tries to stop the service and each service that 'needs' it. This function works recursively, thus also killing those services, that need the service that need the current service. Question: Stop a service (nothing else) [CMD_STOP_SVC_ONLY] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will start a fork, which tries to stop this service and which will report the status back. Question: Stop a service (plus 'needs' and 'wants') [CMD_STOP_SVC_WANTS] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Same as 'Stop a service (and its dependencies)', but also stop the services that want to have this service. This function works recursively, thus also killing those services, that 'need' or 'want' the service that 'need' or 'want' the current service. Question: What's the status of service XYZ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Code, length of service name, the service name (without \0). int, int, char[]; Question: Could you change the status? [CMD_CHG_STAT] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A cinit fork reports the new status of a service. Question: Could you start the rescue mode? [CMD_RESCUE] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will not give an answer to this question. cinit will stop all services, kill all other processes and after that spawn the rescue program. Question: Could you halt the system? [CMD_HALT] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will not give an answer to this question. cinit will stop all services, kill all other processes and after that halt the system. Question: Could you reboot the system? [CMD_REBOOT] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will not give an answer to this question. cinit will stop all services, kill all other processes and after that reboot the system. Question: Could you poweroff the system? [CMD_POWEROFF] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will not give an answer to this question. cinit will stop all services, kill all other processes and after that poweroff the system. If poweroff is not possible, the system will be halted. Question: Could you warmboot the system? [CMD_WBOOT] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will not give an answer to this question. cinit will stop all services, kill all other processes and after that restart itself and the bootup process. Question: Could you send information about a service? [CMD_INFO] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command may only be issued by an external client. cinit will respond with detailled information about the service to the client. Answer: Return short status of a service ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This answer is used as a response to: - Question: Start a service (and its dependencies) - Question: Start a service (nothing else) - Question: Stop a service (and its dependencies) - Question: Stop a service (nothing else) - Question: Stop a service (plus 'needs' and 'wants') - Question: Could you change the status? cinit only responds the status of the asked service. The structure send is "asw_sstatus", which only include a status byte. Answer: Return long status of a service ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This answer is used as a response to: - Question: Could you send information about a service? old Messages (to be transferred into this document) --------------------------------------------------- CMD_START_SVC: I want to start a service. CMD_CHG_STATUS: I want to change the status of a service. CMD_STOP_SVC: Please shutdown a service. CMD_RESCUE: Kill everything, and spawn a sulogin shell. CMD_UPDATE: Hot-reboot system and reload cinit. CMD_HALT: Halt the system CMD_REBOOT: Reboot the system CMD_POWEROFF: Power-off the system -------------------------------------------------------------------------------- Service status: -------------------------------------------------------------------------------- service status (cinit), Nico Schottelius 2005-09-29 (Last Modified: -) -------------------------------------------------------------------------------- There are service status and service returns. Service status is a status a service can have. A service return is a value from a function that describes what happened with the service. Status has ST_ prefix, return has RT_ prefix. See cinit.h for most up to date versions. ST_NEED_FAIL - this service will not be started, until the needs are started ST_FAIL - this service failed to start ST_UNSPEC - some unknown error. This should never happen. ST_ERR - ??? /* tried earlier, service failed, won't retry */ ST_SUCCESS - service was successfully started - senseful? ST_TMP - some instance is currently working on it ST_ONCE - executed once sucessfully ST_RESPAWN - service is running and respawning ST_TMPNOW 55 /* now you are on it - only for clients */ #define ST_OFF 56 /* Switching service off */ cinit-0.3pre15/doc/devel/configuring.text000066400000000000000000000005251125633325400204310ustar00rootroot00000000000000cinit/doc/devel/using-conf.text ================================ Nico Schottelius 0.1, Initial Version from 2006-07-28 :Author Initials: NS About conf/* and how to use the configurations. Introduction ------------ Who should read those documents? -------------------------------- Content ------- cinit-0.3pre15/doc/devel/cross-compiling.text000066400000000000000000000010471125633325400212270ustar00rootroot00000000000000TODO: - merge into "Cross compiling" cinit - Problems that may arise =============================== Nico Schottelius 0.1, for cinit 0.3, Initial Version from 2006-06-03 :Author Initials: NS Max open files OS dependent Installing cinit Introduction ------------ General sections, OS-specific, ... Installing ---------- From source ~~~~~~~~~~~ In General ^^^^^^^^^^ Download, edit conf/os to the os Cross-compiling ^^^^^^^^^^^^^^^ conf/os to destination os conf/cc conf/ld conf/cflags conf/ldflags cinit-0.3pre15/doc/devel/ipc.text000066400000000000000000000112651125633325400166750ustar00rootroot00000000000000IPC - in cinit and in general ============================= Nico Schottelius 0.1, Initial Version from 2006-07-09 :Author Initials: NS IPC - Inter process communication Introduction ------------ This document describes the IPC methods used and/or tested for cinit. It does not describe in detail, how the different methods work (this is already done many times, there's great documentation available online), but more the advantages and disadvantages (especially for an init system). What is IPC? ~~~~~~~~~~~~ IPC describes methods to communicate between different processes (programs). IPC as described by SUSV3 (The Single UNIX Specification Version 3) aka IEEE Std 1003.1, 2004 Edition aka POSIX only defines MSQ, SHM and Semaphores as IPC. This document also covers Sockets and FIFOs. What is not (yet) covered by this document? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Speed of different IPC methods, different behaviour on different unices. Why do you need IPC for an init system? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cinit IPC history + analysis ---------------------------- FIFOs ~~~~~ First in - first out File on the filesystem Always need two files for two way communication Hints ^^^^^ The first idea for IPC in cinit was to use two FIFOs, like minit does. Wrong assumption: runit also uses fifos, but two fifos for each services. That way more parallel transmissions is possible. You have to pay attention: Maximum number of opened files! (On Linux 2.6 this is 1024, which makes a maximum of 512 services. This limit is most likely never reached, but you have to keep it in mind). Sockets ~~~~~~~ Clean and beautiful. They allow easy two way communication. If you created a socket, fs is r/o, you cannot use it, although there is SO_REUSE. First method: Using memory mapped part (tmpfs). Second method: use interal communication (pipes!) and external after /etc/cinit/ becomes writable. Current IPC configuration -------------------------- - switchable (conf/ipc_method) - each ipc implementation needs: ipc.h -> for global variables and ipc specific things prefix variables with ipc_ int cinit_ipc_init(void); -> general initialization return 1 on success, 0 on failure int cinit_ipc_listen(void); -> begin to listen for messages int cinit_ipc_send(void *data) -> send data to a client Abstraction layer: cinit_ipc_* ------------------------------ You can choose or even reimplement ipc code for cinit. You only have to create a directory below src/ipc/ and create the following necessary functions: int cinit_ipc_init(void); ~~~~~~~~~~~~~~~~~~~~~~~~~ Initialise the IPC functions in cinit. int cinit_ipc_listen(void); ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Never ending looping function that listens for commands and passes the retrieved command to read_command(). other ~~~~~~ int cinit_ipc_sclose(void); /* fork of cinit come from outside! */ int cinit_ipc_ssend(void *data); /* send to a client from the server */ void cinit_ipc_destroy(void); /* destroy ipc handler in cinit */ cinit_get_data(int ident, int size, void *data) => read size bytes from client with ident /***************************************************************************** * Functions: in clients */ int cinit_ipc_logon(void); /* logon to init (client init) */ int cinit_ipc_connect(void); /* connect to init */ int cinit_ipc_csend(struct cinit_message *data); /* send to the server from a client */ -------------------------------------------------------------------------------- Messages: struct cinit_question qsn; struct cinit_answer asr; question: answer: int cinit_send_to(struct cinit_question *data, struct cinit_answer *res) -> return 0 on ipc errors -------------------------------------------------------------------------------- enable / disable services: - send svc - send flags - recv return: CINIT_ASW_SVC_STOPPED: successfully stopped the service CINIT_ASW_SVC_ERR: failed to stop the service CINIT_ASW_SVC_WANTS: wants failed CINIT_ASW_SVC_NEEDS: needs failed opt contains number of failed services retriev them from cinit after that -------------------------------------------------------------------------------- TO SORT: 1. message queues o clients schreiben rein o datenpaket gross genug fuer antwort? 2. shared memory o client kann direkt rauslesen, was gestartet werden muss o client kann direkt abhaengigkeiten starten, muss diese aber eintragen Ausprobieren: - Mutexe - Message Queues - Ideen: Message queue 1. Client geht auf die normale als id = pid (cast!) dann rueck via anderer queue cinit-0.3pre15/doc/devel/lists.text000066400000000000000000000010071125633325400172510ustar00rootroot00000000000000Lists in cinit-0.3 are generalized, all have the same general layout: - double linked - have 'prev' and 'next' as pointers Add an element to a list /--------------------------\ |<->first<->middle<->last<->| After insert: /-------------------------------\ |<->first<->middle<->last<->new<->| We alway have 'first'. Need to adjust: - new->prev = last (= first->next) - new->next = first - first->prev = new - first->prev->next (= last->next) = new cinit-0.3pre15/doc/devel/merging.other.initsystems.text000066400000000000000000000043701125633325400232630ustar00rootroot00000000000000TODO: - rewrite to asciidoc - implement a sample merge -------------------------------------------------------------------------------- Merging other init systems to cinit, Nico Schottelius, 2005-06-02 (Last Modified: 2005-06-11) -------------------------------------------------------------------------------- 1. Preamble 2. General to do 3. Create a script 1. Preamble There is no tool available to merge any existing init-system-configuration to cinit style. This is not because the author of cinit does not care about support for that. He simply he has a) no access to every init-system available b) not the time to analyze every init system He instead spends the time to improve and bugfix cinit. This does not mean that he does not accepts scripts, which do the work. In fact, creating and submitting a merge tool is much appreciated! 2. General to do 1. Choose your target init and possibly target platform: - sysvinit may be different on AIX, SuSE and Debian - /etc/rc may look different on each *BSD - Sometimes even same platforms differ in versions: SuSE 5.1 uses a different configuration then SuSE 9.0 So decide whether you want and can write a general merge tool or if you have to specialize. After deciding, name the script you want to write with the following syntax: cinit-merge.$init-$platform-$version $platform and $version (either both or only platform) can be omitted. Examples: cinit-merge.sysvinit-debian-3.0 cinit-merge.minit 2. Analyze how it works, detect the mechanism in it Your script has to detect if dependencies exist and resolve them. It has to take care of special configurations and possibly warn the user. 3. Create a script Now, after you learned how the old init system works, you can start creating the merge-script (naming see above). This merge script a) will perhaps not cover full old system (if so, warnings should be printed b) should try to avoid using old (shell)-scripts, as starting a shell for every service needed makes starting up slow c) will include some basic features, that are needed everytime on this platform (setting kernel configuration, hostname, etc) cinit-0.3pre15/doc/devel/optimising.cinit000066400000000000000000000016361125633325400204270ustar00rootroot00000000000000-------------------------------------------------------------------------------- optimising cinit, Nico Schottelius, 2005-06-09 (Last Modified: -) -------------------------------------------------------------------------------- 0. Warning 1. gcc options 2. striping 0. Warning Any optimisation may cause cinit (not just cinit, but any program) to fail and to do mysterious things instead of expected actions. 1. gcc options gcc knows of several optimisation flags. Mostly interesting is -Os for small size (this is btw broken on gcc-3.4.3 on x86!). One can also pass -Werror so that any warning makes the compile to fail. The current standard for cinit is: (see CFLAGS in the Makefile). 2. striping With strip(1) you can remove specific sections of object files. You have to find out, which ones you can remove safely (for instance with objdump(1)). The current standard for cinit is: (see STRIP in the Makefile) cinit-0.3pre15/doc/devel/testing-cinit-in-vm.text000066400000000000000000000004321125633325400217210ustar00rootroot00000000000000 m = manually a = automated m Install OS of your choice into KVM, including make, gcc, ssh and rsync m Startup VM a Transfer data to VM a Compile cinit on VM a Install cinit and configuration on VM m Configure bootloader to add cinit as alternative choice m Reboot and start cinit cinit-0.3pre15/doc/devel/testing.text000066400000000000000000000032331125633325400175730ustar00rootroot00000000000000-------------------------------------------------------------------------------- testing cinit in a User-Mode-Linux (uml), Nico Schottelius 2005-06-14 (Last Modified: 2005-06-14) -------------------------------------------------------------------------------- 1. Get an image you want to install cinit to 2. Compile an UML 3. change bin/cinit.uml.test to your needs 4. put a configuration (/etc/cinit) on to your image 5. ./bin/cinit.uml.test -> wait, your Linux starts with cinit enabled. If you omit 4, you'll see how cinit will fail without having its base directory. -------------------------------------------------------------------------------- Using a raw (x86) hd image: Access partition 1 via losetup: sudo losetup -o 32256 /dev/loop0 "$hierabs/debian-hd.img" linux ubd0=/dev/loop0 init=/sbin/cinit "$@" Offset was taken from fdisk: [19:22] denkbrett:emu# fdisk -l -u /dev/sda Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x1669c708 Device Boot Start End Blocks Id System /dev/sda1 63 19535039 9767488+ 83 Linux /dev/sda2 19535040 23438834 1951897+ 82 Linux swap / Solaris /dev/sda3 23438835 156296384 66428775 83 Linux ===> 63*512bytes spaeter beginnt sda1 [19:23] denkbrett:~% echo 512\*63 |bc -l 32256 Results in losetup -o 32256 /dev/loop0 ./debian-hd.img Scripts from the nsbin project (lo-*) can be used. It can be found at http://unix.schottelius.org/cgi-bin/gitweb.cgi. -------------------------------------------------------------------------------- cinit-0.3pre15/doc/gpl3-header000066400000000000000000000015551125633325400161340ustar00rootroot00000000000000/******************************************************************************* * * 2008 Nico Schottelius (nico-cinit at schottelius.org) * * This file is part of cinit. * cinit 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. * * cinit 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 cinit. If not, see . * * purpose_of_this_file_is_also_there_behind_the_big_header * */ cinit-0.3pre15/doc/logs/000077500000000000000000000000001125633325400150545ustar00rootroot00000000000000cinit-0.3pre15/doc/logs/2006-10-25.config.wasserstoff000066400000000000000000000010161125633325400216370ustar00rootroot00000000000000[17:12] wasserstoff:svc# pwd /etc/cinit/svc [17:12] wasserstoff:svc# ls init 17:12] wasserstoff:svc# mkdir getty [17:12] wasserstoff:svc# mkdir getty/2/ [17:12] wasserstoff:svc# cd getty/2 [17:12] wasserstoff:2# ln -s /sbin/getty on 17:12] wasserstoff:2# echo 38400 > on.params [17:13] wasserstoff:2# echo tty2 >> on.params [17:13] wasserstoff:2# cd ../../init [17:14] wasserstoff:init# mkdir needs [17:14] wasserstoff:init# cd needs [17:14] wasserstoff:needs# ln -s ../../getty/2 getty-2 [17:14] wasserstoff:needs# cinit-0.3pre15/doc/logs/2006-11-22.startup-with-debug000066400000000000000000000045001125633325400215630ustar00rootroot00000000000000[0:08] wasserstoff:cinit-0.3pre3% ./src/cinit cinit-0.3pre3: Booting from /etc/cinit/svc/init gen_tree::/etc/cinit/svc/init CAD::/etc/cinit/svc/init CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/getty:: gen_tree::/etc/cinit/svc/getty CAD::/etc/cinit/svc/getty CAD::NEW::/etc/cinit/svc/getty::/etc/cinit/svc/getty/2:: gen_tree::/etc/cinit/svc/getty/2 CAD::/etc/cinit/svc/getty/2 CAD::NEW::/etc/cinit/svc/getty/2::/etc/cinit/svc/local-tuning/keyboard-layout:: gen_tree::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/local-tuning/keyboard-layout START::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/getty/2 CAD::NEW::/etc/cinit/svc/getty::/etc/cinit/svc/getty/3:: gen_tree::/etc/cinit/svc/getty/3 CAD::/etc/cinit/svc/getty/3 CAD::NEW::/etc/cinit/svc/getty/3::/etc/cinit/svc/local-tuning/keyboard-layout:: CAD::/etc/cinit/svc/getty/3 CAD::/etc/cinit/svc/getty CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/local-tuning:: gen_tree::/etc/cinit/svc/local-tuning CAD::/etc/cinit/svc/local-tuning CAD::NEW::/etc/cinit/svc/local-tuning::/etc/cinit/svc/local-tuning/keyboard-layout:: CAD::/etc/cinit/svc/local-tuning CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/mount:: gen_tree::/etc/cinit/svc/mount CAD::/etc/cinit/svc/mount CAD::NEW::/etc/cinit/svc/mount::/etc/cinit/svc/mount/root:: gen_tree::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount/root START::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/network:: gen_tree::/etc/cinit/svc/network CAD::/etc/cinit/svc/network CAD::NEW::/etc/cinit/svc/network::/etc/cinit/svc/network/eth0:: respawn: /etc/cinit/svc/network/eth0 gen_tree::/etc/cinit/svc/network/eth0 CAD::/etc/cinit/svc/network/eth0 CAD::/etc/cinit/svc/network/eth0 START::/etc/cinit/svc/network/eth0 CAD::NEW::/etc/cinit/svc/network::/etc/cinit/svc/network/loopback:: gen_tree::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network/loopback START::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network CAD::/etc/cinit/svc/init ========> tree_exec() /etc/cinit/svc/local-tuning/keyboard-layout:::abhaengigkeiten gestartet, exec; add wants, needsdep_needs_wants_add::/etc/cinit/svc/local-tuning/keyboard-layout add: (/etc/cinit/svc/getty/2) cinit-0.3pre15/doc/logs/2006-11-30.startup-0.3pre5000066400000000000000000002116361125633325400206310ustar00rootroot00000000000000cinit-0.3pre4: Booting from /etc/cinit/svc/init gen_tree::/etc/cinit/svc/init CAD::/etc/cinit/svc/init CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/getty gen_tree::/etc/cinit/svc/getty CAD::/etc/cinit/svc/getty CAD::NEW::/etc/cinit/svc/getty::/etc/cinit/svc/getty/2 gen_tree::/etc/cinit/svc/getty/2 CAD::/etc/cinit/svc/getty/2 CAD::NEW::/etc/cinit/svc/getty/2::/etc/cinit/svc/local-tuning/keyboard-layout gen_tree::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/local-tuning/keyboard-layout START::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/getty/2 CAD::NEW::/etc/cinit/svc/getty::/etc/cinit/svc/getty/3 gen_tree::/etc/cinit/svc/getty/3 CAD::/etc/cinit/svc/getty/3 CAD::NEW::/etc/cinit/svc/getty/3::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/getty/3 CAD::/etc/cinit/svc/getty CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/local-tuning gen_tree::/etc/cinit/svc/local-tuning CAD::/etc/cinit/svc/local-tuning CAD::NEW::/etc/cinit/svc/local-tuning::/etc/cinit/svc/local-tuning/keyboard-layout CAD::/etc/cinit/svc/local-tuning CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/mount gen_tree::/etc/cinit/svc/mount CAD::/etc/cinit/svc/mount CAD::NEW::/etc/cinit/svc/mount::/etc/cinit/svc/mount/root gen_tree::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount/root START::/etc/cinit/svc/mount/root CAD::/etc/cinit/svc/mount CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/network gen_tree::/etc/cinit/svc/network CAD::/etc/cinit/svc/network CAD::NEW::/etc/cinit/svc/network::/etc/cinit/svc/network/eth0 respawn: /etc/cinit/svc/network/eth0 gen_tree::/etc/cinit/svc/network/eth0 CAD::/etc/cinit/svc/network/eth0 CAD::/etc/cinit/svc/network/eth0 START::/etc/cinit/svc/network/eth0 CAD::NEW::/etc/cinit/svc/network::/etc/cinit/svc/network/loopback gen_tree::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network/loopback START::/etc/cinit/svc/network/loopback CAD::/etc/cinit/svc/network CAD::NEW::/etc/cinit/svc/init::/etc/cinit/svc/test gen_tree::/etc/cinit/svc/test CAD::/etc/cinit/svc/test CAD::NEW::/etc/cinit/svc/test::/etc/cinit/svc/test/env gen_tree::/etc/cinit/svc/test/env CAD::/etc/cinit/svc/test/env CAD::/etc/cinit/svc/test/env START::/etc/cinit/svc/test/env CAD::/etc/cinit/svc/test CAD::/etc/cinit/svc/init ========> tree_exec() TEX::/etc/cinit/svc/local-tuning/keyboard-layout abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params DNWA::/etc/cinit/svc/local-tuning/keyboard-layout::/etc/cinit/svc/getty/2::(A)::::/etc/cinit/svc/getty/3::(A)::::/etc/cinit/svc/local-tuning::(A):: DNWA::/etc/cinit/svc/local-tuning/keyboard-layout TEX::/etc/cinit/svc/mount/root abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/mount/root/on CBA::/etc/cinit/svc/mount/root/on ORC:/etc/cinit/svc/mount/root/on.params DNWA::/etc/cinit/svc/mount/root::/etc/cinit/svc/mount::(A):: DNWA::/etc/cinit/svc/mount/root TEX::/etc/cinit/svc/network/eth0 abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/network/eth0/on CBA::/etc/cinit/svc/network/eth0/on ORC:/etc/cinit/svc/network/eth0/on.params DNWA::/etc/cinit/svc/network/eth0::/etc/cinit/svc/network::(A):: DNWA::/etc/cinit/svc/network/eth0 TEX::/etc/cinit/svc/network/loopback abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/network/loopback/on CBA::/etc/cinit/svc/network/loopback/on ORC:/etc/cinit/svc/network/loopback/on.params DNWA::/etc/cinit/svc/network/loopback::/etc/cinit/svc/network DNWA::/etc/cinit/svc/network/loopback TEX::/etc/cinit/svc/test/env abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/test/env/on CBA::/etc/cinit/svc/test/env/on DNWA::/etc/cinit/svc/test/env::/etc/cinit/svc/test::(A):: DNWA::/etc/cinit/svc/test/env TEX::/etc/cinit/svc/getty/2 ::/etc/cinit/svc/local-tuning/keyboard-layout /etc/cinit/svc/local-tuning/keyboard-layout: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/getty/2/on CBA::/etc/cinit/svc/getty/2/on DNWA::/etc/cinit/svc/getty/2::/etc/cinit/svc/getty::(A):: DNWA::/etc/cinit/svc/getty/2 TEX::/etc/cinit/svc/getty/3 ::/etc/cinit/svc/local-tuning/keyboard-layout /etc/cinit/svc/local-tuning/keyboard-layout: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/getty/3/on CBA::/etc/cinit/svc/getty/3/on ORC:/etc/cinit/svc/getty/3/on.params DNWA::/etc/cinit/svc/getty/3::/etc/cinit/svc/getty DNWA::/etc/cinit/svc/getty/3 TEX::/etc/cinit/svc/local-tuning ::/etc/cinit/svc/local-tuning/keyboard-layout /etc/cinit/svc/local-tuning/keyboard-layout: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/local-tuning/on CBA::/etc/cinit/svc/local-tuning/on CBA::/etc/cinit/svc/local-tuning/on /etc/cinit/svc/local-tuning/on: No such file or directory SC::Cleanup: reparenting DNWA::/etc/cinit/svc/local-tuning::/etc/cinit/svc/init::(A):: DNWA::/etc/cinit/svc/local-tuning TEX::/etc/cinit/svc/mount ::/etc/cinit/svc/mount/root /etc/cinit/svc/mount/root: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/mount/on CBA::/etc/cinit/svc/mount/on CBA::/etc/cinit/svc/mount/on /etc/cinit/svc/mount/on: No such file or directory SC::Cleanup: reparenting DNWA::/etc/cinit/svc/mount::/etc/cinit/svc/init DNWA::/etc/cinit/svc/mount TEX::/etc/cinit/svc/network ::/etc/cinit/svc/network/eth0 /etc/cinit/svc/network/eth0: <<16>> ::/etc/cinit/svc/network/loopback /etc/cinit/svc/network/loopback: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/network/on CBA::/etc/cinit/svc/network/on CBA::/etc/cinit/svc/network/on /etc/cinit/svc/network/on: No such file or directory SC::Cleanup: reparenting DNWA::/etc/cinit/svc/network::/etc/cinit/svc/init DNWA::/etc/cinit/svc/network TEX::/etc/cinit/svc/test ::/etc/cinit/svc/test/env /etc/cinit/svc/test/env: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/test/on CBA::/etc/cinit/svc/test/on CBA::/etc/cinit/svc/test/on /etc/cinit/svc/test/on: No such file or directory SC::Cleanup: reparenting DNWA::/etc/cinit/svc/test::/etc/cinit/svc/init DNWA::/etc/cinit/svc/test TEX::/etc/cinit/svc/getty ::/etc/cinit/svc/getty/2 /etc/cinit/svc/getty/2: <<4>> ::/etc/cinit/svc/getty/3 /etc/cinit/svc/getty/3: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/getty/on CBA::/etc/cinit/svc/getty/on CBA::/etc/cinit/svc/getty/on /etc/cinit/svc/getty/on: No such file or directory SC::Cleanup: reparenting DNWA::/etc/cinit/svc/getty::/etc/cinit/svc/init DNWA::/etc/cinit/svc/getty TEX::/etc/cinit/svc/init ::/etc/cinit/svc/getty /etc/cinit/svc/getty: <<4>> ::/etc/cinit/svc/local-tuning /etc/cinit/svc/local-tuning: <<4>> ::/etc/cinit/svc/mount /etc/cinit/svc/mount: <<4>> ::/etc/cinit/svc/network /etc/cinit/svc/network: <<4>> ::/etc/cinit/svc/test /etc/cinit/svc/test: <<4>> abhaengigkeiten gestartet, exec; add wants, needs ES::/etc/cinit/svc/init/on CBA::/etc/cinit/svc/init/on DNWA::/etc/cinit/svc/init DNWA::/etc/cinit/svc/init => cinit started. ORC:/etc/cinit/svc/test/env/on.params SFN: NULL ORC:/etc/cinit/svc/test/env/on.env ORC: 38400 tty3 ORC:/etc/cinit/svc/getty/3/on.env SFN: NULL CBA::/etc/cinit/svc/getty/3/on ORC:/etc/cinit/svc/getty/3/on.params ORC: 38400 tty3 ORC:/etc/cinit/svc/getty/3/on.env SFN: NULL ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL ORC:/etc/cinit/svc/init/on.params ORC:/etc/cinit/svc/getty/2/on.params ORC: -f -i eth0 ORC:/etc/cinit/svc/network/eth0/on.env SFN: NULL CBA::/etc/cinit/svc/network/eth0/on ORC:/etc/cinit/svc/network/eth0/on.params ORC: -f -i eth0 ORC:/etc/cinit/svc/network/eth0/on.env SFN: NULL ORC: test=Wunderbar es tut CBA::/etc/cinit/svc/test/env/on ORC:/etc/cinit/svc/test/env/on.params SFN: NULL ORC:/etc/cinit/svc/test/env/on.env ORC: test=Wunderbar es tut pre-test Wunderbar es tut post-test SC::/etc/cinit/svc/test/env::FAILED::::RESPAWN::ES::/etc/cinit/svc/test/env/on CBA::/etc/cinit/svc/test/env/on ORC:/etc/cinit/svc/test/env/on.params SFN: NULL ORC:/etc/cinit/svc/test/env/on.env ORC: test=Wunderbar es tut CBA::/etc/cinit/svc/test/env/on ORC:/etc/cinit/svc/test/env/on.params SFN: NULL ORC:/etc/cinit/svc/test/env/on.env ORC: test=Wunderbar es tut pre-test Wunderbar es tut post-test msgrcv: Interrupted system call ORC: lo 127.0.0.1 up ORC:/etc/cinit/svc/network/loopback/on.env SFN: NULL CBA::/etc/cinit/svc/network/loopback/on ORC:/etc/cinit/svc/network/loopback/on.params ORC: lo 127.0.0.1 up ORC:/etc/cinit/svc/network/loopback/on.env SFN: NULL ORC: -n -o remount,rw / ORC:/etc/cinit/svc/mount/root/on.env SFN: NULL CBA::/etc/cinit/svc/mount/root/on ORC:/etc/cinit/svc/mount/root/on.params ORC: -n -o remount,rw / ORC:/etc/cinit/svc/mount/root/on.env SFN: NULL ORC: 38400 tty2 ORC:/etc/cinit/svc/getty/2/on.env SFN: NULL CBA::/etc/cinit/svc/getty/2/on ORC:/etc/cinit/svc/getty/2/on.params ORC: 38400 tty2 ORC:/etc/cinit/svc/getty/2/on.env SFN: NULL udhcpc (v0.9.9-pre) started socket failed!: Operation not permitted SC::/etc/cinit/svc/network/eth0::FAILED::::RESPAWN::ES::/etc/cinit/svc/network/eth0/on CBA::/etc/cinit/svc/network/eth0/on ORC:/etc/cinit/svc/network/eth0/on.params ORC: -f -i eth0 ORC:/etc/cinit/svc/network/eth0/on.env SFN: NULL CBA::/etc/cinit/svc/network/eth0/on ORC:/etc/cinit/svc/network/eth0/on.params ORC: -f -i eth0 ORC:/etc/cinit/svc/network/eth0/on.env SFN: NULL udhcpc (v0.9.9-pre) started socket failed!: Operation not permitted msgrcv: Interrupted system call ORC: The initial service has been started. ORC:/etc/cinit/svc/init/on.env SFN: NULL CBA::/etc/cinit/svc/init/on ORC:/etc/cinit/svc/init/on.params ORC: The initial service has been started. ORC:/etc/cinit/svc/init/on.env SFN: NULL The initial service has been started. SC::/etc/cinit/svc/init::FAILED::::RESPAWN::ES::/etc/cinit/svc/init/on CBA::/etc/cinit/svc/init/on ORC:/etc/cinit/svc/init/on.params ORC: The initial service has been started. ORC:/etc/cinit/svc/init/on.env SFN: NULL CBA::/etc/cinit/svc/init/on ORC:/etc/cinit/svc/init/on.params ORC: The initial service has been started. ORC:/etc/cinit/svc/init/on.env SFN: NULL The initial service has been started. msgrcv: Interrupted system call SIOCSIFADDR: Permission denied SIOCSIFFLAGS: Permission denied SIOCSIFFLAGS: Permission denied Unknown server error ifconfig: `--help' gives usage information. SC::/etc/cinit/svc/network/loopback::FAILED::::RESPAWN::ES::/etc/cinit/svc/network/loopback/on CBA::/etc/cinit/svc/network/loopback/on ORC:/etc/cinit/svc/network/loopback/on.params ORC: lo 127.0.0.1 up ORC:/etc/cinit/svc/network/loopback/on.env SFN: NULL CBA::/etc/cinit/svc/network/loopback/on ORC:/etc/cinit/svc/network/loopback/on.params ORC: lo 127.0.0.1 up ORC:/etc/cinit/svc/network/loopback/on.env SFN: NULL SIOCSIFADDR: Permission denied SIOCSIFFLAGS: Permission denied SIOCSIFFLAGS: Permission denied Unknown server error ifconfig: `--help' gives usage information. msgrcv: Interrupted system call mount: only root can do that SC::/etc/cinit/svc/mount/root::FAILED::::RESPAWN::ES::/etc/cinit/svc/mount/root/on CBA::/etc/cinit/svc/mount/root/on ORC:/etc/cinit/svc/mount/root/on.params ORC: -n -o remount,rw / ORC:/etc/cinit/svc/mount/root/on.env SFN: NULL CBA::/etc/cinit/svc/mount/root/on ORC:/etc/cinit/svc/mount/root/on.params ORC: -n -o remount,rw / ORC:/etc/cinit/svc/mount/root/on.env SFN: NULL mount: only root can do that msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz LSP:: 32705: /etc/cinit/svc/init:1 (0) LSP:: 32705: /etc/cinit/svc/test/env:4 (32702) LSP:: 32705: /etc/cinit/svc/test:65 (0) LSP:: 32705: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32705: /etc/cinit/svc/network/eth0:16 (32700) LSP:: 32705: /etc/cinit/svc/network:65 (0) LSP:: 32705: /etc/cinit/svc/mount/root:4 (32699) LSP:: 32705: /etc/cinit/svc/mount:65 (0) LSP:: 32705: /etc/cinit/svc/local-tuning:65 (0) LSP:: 32705: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32705: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) LSP:: 32705: /etc/cinit/svc/getty/2:4 (32703) LSP:: 32705: /etc/cinit/svc/getty:65 (0) LSP:: 32706: /etc/cinit/svc/init:65 (0) LSP:: 32706: /etc/cinit/svc/test/env:4 (32702) LSP:: 32706: /etc/cinit/svc/test:65 (0) LSP:: 32706: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32706: /etc/cinit/svc/network/eth0:16 (32700) LSP:: 32706: /etc/cinit/svc/network:65 (0) LSP:: 32706: /etc/cinit/svc/mount/root:4 (32699) LSP:: 32706: /etc/cinit/svc/mount:65 (0) LSP:: 32706: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32706: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32706: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) LSP:: 32706: /etc/cinit/svc/getty/2:4 (32703) LSP:: 32706: /etc/cinit/svc/getty:65 (0) LSP:: 32707: /etc/cinit/svc/init:65 (0) LSP:: 32707: /etc/cinit/svc/test/env:4 (32702) LSP:: 32707: /etc/cinit/svc/test:65 (0) LSP:: 32707: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32707: /etc/cinit/svc/network/eth0:16 (32700) LSP:: 32707: /etc/cinit/svc/network:65 (0) LSP:: 32707: /etc/cinit/svc/mount/root:4 (32699) LSP:: 32707: /etc/cinit/svc/mount:4 (32706) LSP:: 32707: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32707: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32707: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) LSP:: 32707: /etc/cinit/svc/getty/2:4 (32703) LSP:: 32707: /etc/cinit/svc/getty:65 (0) LSP:: 32708: /etc/cinit/svc/init:65 (0) LSP:: 32708: /etc/cinit/svc/test/env:4 (32702) LSP:: 32708: /etc/cinit/svc/test:65 (0) LSP:: 32708: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32708: /etc/cinit/svc/network/eth0:16 (32700) LSP:: 32708: /etc/cinit/svc/network:4 (32707) LSP:: 32708: /etc/cinit/svc/mount/root:4 (32699) LSP:: 32708: /etc/cinit/svc/mount:4 (32706) LSP:: 32708: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32708: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32708: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) LSP:: 32708: /etc/cinit/svc/getty/2:4 (32703) LSP:: 32708: /etc/cinit/svc/getty:65 (0) LSP:: 32709: /etc/cinit/svc/init:65 (0) LSP:: 32709: /etc/cinit/svc/test/env:4 (32702) LSP:: 32709: /etc/cinit/svc/test:4 (32708) LSP:: 32709: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32709: /etc/cinit/svc/network/eth0:16 (32700) LSP:: 32709: /etc/cinit/svc/network:4 (32707) LSP:: 32709: /etc/cinit/svc/mount/root:4 (32699) LSP:: 32709: /etc/cinit/svc/mount:4 (32706) LSP:: 32709: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32709: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32709: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) LSP:: 32709: /etc/cinit/svc/getty/2:4 (32703) LSP:: 32709: /etc/cinit/svc/getty:65 (0) LSP:: 32702: /etc/cinit/svc/init:4 (32710) LSP:: 32702: /etc/cinit/svc/test/env:4 (32702) pid: 0, m_client LSP:: 32700: /etc/cinit/svc/init:4 (32710) LSP:: 32700: /etc/cinit/svc/test/env:16 (32717) LSP:: 32700: /etc/cinit/svc/test:4 (32708) LSP:: 32700: /etc/cinit/svc/network/loopback:4 (32701) LSP:: 32700: /etc/cinit/svc/network/eth0:16 (32700) pid: 0, m_client LSP:: 32710: /etc/cinit/svc/init:4 (32710) pid: 0, m_client LSP:: 32701: /etc/cinit/svc/init:16 (32719) LSP:: 32701: /etc/cinit/svc/test/env:16 (32717) LSP:: 32701: /etc/cinit/svc/test:4 (32708) LSP:: 32701: /etc/cinit/svc/network/loopback:4 (32701) pid: 0, m_client LSP:: 32699: /etc/cinit/svc/init:16 (32719) LSP:: 32699: /etc/cinit/svc/test/env:16 (32717) LSP:: 32699: /etc/cinit/svc/test:4 (32708) LSP:: 32699: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32699: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32699: /etc/cinit/svc/network:4 (32707) LSP:: 32699: /etc/cinit/svc/mount/root:4 (32699) pid: 0, m_client LSP::SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz 32698: /etc/cinit/svc/init:16 (32719) LSP:: 32698: /etc/cinit/svc/test/env:16 (32717) LSP:: 32698: /etc/cinit/svc/test:4 (32708) LSP:: 32698: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32698: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32698: /etc/cinit/svc/network:4 (32707) LSP:: 32698: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32698: /etc/cinit/svc/mount:4 (32706) LSP:: 32698: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32698: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32698: /etc/cinit/svc/local-tuning/keyboard-layout:4 (32698) pid: 0, m_client LSP:: 32728: /etc/cinit/svc/init:16 (32719) LSP:: 32728: /etc/cinit/svc/test/env:16 (32717) LSP:: 32728: /etc/cinit/svc/test:4 (32708) LSP:: 32728: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32728: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32728: /etc/cinit/svc/network:4 (32707) LSP:: 32728: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32728: /etc/cinit/svc/mount:4 (32706) LSP:: 32728: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32728: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32728: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32728) pid: 0, m_client LSP:: 32735: /etc/cinit/svc/init:16 (32719) LSP:: 32735: /etc/cinit/svc/test/env:16 (32717) LSP:: 32735: /etc/cinit/svc/test:4 (32708) LSP:: 32735: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32735: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32735: /etc/cinit/svc/network:4 (32707) LSP:: 32735: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32735: /etc/cinit/svc/mount:4 (32706) LSP:: 32735: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32735: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32735: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32735) pid: 0, m_client LSP:: 32742: /etc/cinit/svc/init:16 (32719) LSP:: 32742: /etc/cinit/svc/test/env:16 (32717) LSP:: 32742: /etc/cinit/svc/test:4 (32708) LSP:: 32742: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32742: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32742: /etc/cinit/svc/network:4 (32707) LSP:: 32742: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32742: /etc/cinit/svc/mount:4 (32706) LSP:: 32742: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32742: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32742: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32742) pid: 0, m_client LSP:: 32749: /etc/cinit/svc/init:16 (32719) LSP:: 32749: /etc/cinit/svc/test/env:16 (32717) LSP:: 32749: /etc/cinit/svc/test:4 (32708) LSP:: 32749: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32749: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32749: /etc/cinit/svc/network:4 (32707) LSP:: 32749: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32749: /etc/cinit/svc/mount:4 (32706) LSP:: 32749: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32749: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32749: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32749) pid: 0, m_client LSP:: 32756: /etc/cinit/svc/init:16 (32719) LSP:: 32756: /etc/cinit/svc/test/env:16 (32717) LSP:: 32756: /etc/cinit/svc/test:4 (32708) LSP:: 32756: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32756: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32756: /etc/cinit/svc/network:4 (32707) LSP:: 32756: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32756: /etc/cinit/svc/mount:4 (32706) LSP:: 32756: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32756: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32756: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32756) pid: 0, m_client LSP:: 32763: /etc/cinit/svc/init:16 (32719) LSP:: 32763: /etc/cinit/svc/test/env:16 (32717) LSP:: 32763: /etc/cinit/svc/test:4 (32708) LSP:: 32763: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 32763: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 32763: /etc/cinit/svc/network:4 (32707) LSP:: 32763: /etc/cinit/svc/mount/root:16 (32721) LSP:: 32763: /etc/cinit/svc/mount:4 (32706) LSP:: 32763: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 32763: /etc/cinit/svc/getty/3:4 (32704) LSP:: 32763: /etc/cinit/svc/local-tuning/keyboard-layout:16 (32763) pid: 0, m_client LSP:: 302: /etc/cinit/svc/init:16 (32719) LSP:: 302: /etc/cinit/svc/test/env:16 (32717) LSP:: 302: /etc/cinit/svc/test:4 (32708) LSP:: 302: /etc/ciSC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN:: msgrcv: Interrupted system call ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz nit/svc/network/loopback:16 (32720) LSP:: 302: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 302: /etc/cinit/svc/network:4 (32707) LSP:: 302: /etc/cinit/svc/mount/root:16 (32721) LSP:: 302: /etc/cinit/svc/mount:4 (32706) LSP:: 302: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 302: /etc/cinit/svc/getty/3:4 (32704) LSP:: 302: /etc/cinit/svc/local-tuning/keyboard-layout:16 (302) pid: 0, m_client LSP:: 312: /etc/cinit/svc/init:16 (32719) LSP:: 312: /etc/cinit/svc/test/env:16 (32717) LSP:: 312: /etc/cinit/svc/test:4 (32708) LSP:: 312: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 312: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 312: /etc/cinit/svc/network:4 (32707) LSP:: 312: /etc/cinit/svc/mount/root:16 (32721) LSP:: 312: /etc/cinit/svc/mount:4 (32706) LSP:: 312: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 312: /etc/cinit/svc/getty/3:4 (32704) LSP:: 312: /etc/cinit/svc/local-tuning/keyboard-layout:16 (312) pid: 0, m_client LSP:: 326: /etc/cinit/svc/init:16 (32719) LSP:: 326: /etc/cinit/svc/test/env:16 (32717) LSP:: 326: /etc/cinit/svc/test:4 (32708) LSP:: 326: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 326: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 326: /etc/cinit/svc/network:4 (32707) LSP:: 326: /etc/cinit/svc/mount/root:16 (32721) LSP:: 326: /etc/cinit/svc/mount:4 (32706) LSP:: 326: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 326: /etc/cinit/svc/getty/3:4 (32704) LSP:: 326: /etc/cinit/svc/local-tuning/keyboard-layout:16 (326) pid: 0, m_client LSP:: 333: /etc/cinit/svc/init:16 (32719) LSP:: 333: /etc/cinit/svc/test/env:16 (32717) LSP:: 333: /etc/cinit/svc/test:4 (32708) LSP:: 333: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 333: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 333: /etc/cinit/svc/network:4 (32707) LSP:: 333: /etc/cinit/svc/mount/root:16 (32721) LSP:: 333: /etc/cinit/svc/mount:4 (32706) LSP:: 333: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 333: /etc/cinit/svc/getty/3:4 (32704) LSP:: 333: /etc/cinit/svc/local-tuning/keyboard-layout:16 (333) pid: 0, m_client LSP:: 340: /etc/cinit/svc/init:16 (32719) LSP:: 340: /etc/cinit/svc/test/env:16 (32717) LSP:: 340: /etc/cinit/svc/test:4 (32708) LSP:: 340: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 340: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 340: /etc/cinit/svc/network:4 (32707) LSP:: 340: /etc/cinit/svc/mount/root:16 (32721) LSP:: 340: /etc/cinit/svc/mount:4 (32706) LSP:: 340: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 340: /etc/cinit/svc/getty/3:4 (32704) LSP:: 340: /etc/cinit/svc/local-tuning/keyboard-layout:16 (340) pid: 0, m_client LSP:: 347: /etc/cinit/svc/init:16 (32719) LSP:: 347: /etc/cinit/svc/test/env:16 (32717) LSP:: 347: /etc/cinit/svc/test:4 (32708) LSP:: 347: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 347: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 347: /etc/cinit/svc/network:4 (32707) LSP:: 347: /etc/cinit/svc/mount/root:16 (32721) LSP:: 347: /etc/cinit/svc/mount:4 (32706) LSP:: 347: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 347: /etc/cinit/svc/getty/3:4 (32704) LSP:: 347: /etc/cinit/svc/local-tuning/keyboard-layout:16 (347) pid: 0, m_client LSP:: 354: /etc/cinit/svc/init:16 (32719) LSP:: 354: /etc/cinit/svc/test/env:16 (32717) LSP:: 354: /etc/cinit/svc/test:4 (32708) LSP:: 354: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 354: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 354: /etc/cinit/svc/network:4 (32707) LSP:: 354: /etc/cinit/svc/mount/root:16 (32721) LSP:: 354: /etc/cinit/svc/mount:4 (32706) LSP:: 354: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 354: /etc/cinit/svc/getty/3:4 (32704) LSP:: 354: /etc/cinit/svc/local-tuning/keyboard-layout:16 (354) pid: 0, m_client LSP:: 372: /etc/cinit/svc/init:16 (32719) LSP:: 372: /etc/cinit/svc/test/env:16 (32717) LSP:: 372: /etc/cinit/svc/test:4 (32708) LSP:: 372: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 372: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 372: /etc/cinit/svc/network:4 (32707) LSP:: 372: /etc/cinit/svc/mount/root:16 (32721) LSP:: 372: /etc/cinit/svc/mount:4 (32706) LSP:: 372: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 372: /etc/cinit/svc/getty/3:4 (327SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz 04) LSP:: 372: /etc/cinit/svc/local-tuning/keyboard-layout:16 (372) pid: 0, m_client LSP:: 379: /etc/cinit/svc/init:16 (32719) LSP:: 379: /etc/cinit/svc/test/env:16 (32717) LSP:: 379: /etc/cinit/svc/test:4 (32708) LSP:: 379: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 379: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 379: /etc/cinit/svc/network:4 (32707) LSP:: 379: /etc/cinit/svc/mount/root:16 (32721) LSP:: 379: /etc/cinit/svc/mount:4 (32706) LSP:: 379: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 379: /etc/cinit/svc/getty/3:4 (32704) LSP:: 379: /etc/cinit/svc/local-tuning/keyboard-layout:16 (379) pid: 0, m_client LSP:: 386: /etc/cinit/svc/init:16 (32719) LSP:: 386: /etc/cinit/svc/test/env:16 (32717) LSP:: 386: /etc/cinit/svc/test:4 (32708) LSP:: 386: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 386: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 386: /etc/cinit/svc/network:4 (32707) LSP:: 386: /etc/cinit/svc/mount/root:16 (32721) LSP:: 386: /etc/cinit/svc/mount:4 (32706) LSP:: 386: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 386: /etc/cinit/svc/getty/3:4 (32704) LSP:: 386: /etc/cinit/svc/local-tuning/keyboard-layout:16 (386) pid: 0, m_client LSP:: 393: /etc/cinit/svc/init:16 (32719) LSP:: 393: /etc/cinit/svc/test/env:16 (32717) LSP:: 393: /etc/cinit/svc/test:4 (32708) LSP:: 393: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 393: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 393: /etc/cinit/svc/network:4 (32707) LSP:: 393: /etc/cinit/svc/mount/root:16 (32721) LSP:: 393: /etc/cinit/svc/mount:4 (32706) LSP:: 393: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 393: /etc/cinit/svc/getty/3:4 (32704) LSP:: 393: /etc/cinit/svc/local-tuning/keyboard-layout:16 (393) pid: 0, m_client LSP:: 400: /etc/cinit/svc/init:16 (32719) LSP:: 400: /etc/cinit/svc/test/env:16 (32717) LSP:: 400: /etc/cinit/svc/test:4 (32708) LSP:: 400: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 400: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 400: /etc/cinit/svc/network:4 (32707) LSP:: 400: /etc/cinit/svc/mount/root:16 (32721) LSP:: 400: /etc/cinit/svc/mount:4 (32706) LSP:: 400: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 400: /etc/cinit/svc/getty/3:4 (32704) LSP:: 400: /etc/cinit/svc/local-tuning/keyboard-layout:16 (400) pid: 0, m_client LSP:: 407: /etc/cinit/svc/init:16 (32719) LSP:: 407: /etc/cinit/svc/test/env:16 (32717) LSP:: 407: /etc/cinit/svc/test:4 (32708) LSP:: 407: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 407: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 407: /etc/cinit/svc/network:4 (32707) LSP:: 407: /etc/cinit/svc/mount/root:16 (32721) LSP:: 407: /etc/cinit/svc/mount:4 (32706) LSP:: 407: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 407: /etc/cinit/svc/getty/3:4 (32704) LSP:: 407: /etc/cinit/svc/local-tuning/keyboard-layout:16 (407) pid: 0, m_client LSP:: 414: /etc/cinit/svc/init:16 (32719) LSP:: 414: /etc/cinit/svc/test/env:16 (32717) LSP:: 414: /etc/cinit/svc/test:4 (32708) LSP:: 414: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 414: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 414: /etc/cinit/svc/network:4 (32707) LSP:: 414: /etc/cinit/svc/mount/root:16 (32721) LSP:: 414: /etc/cinit/svc/mount:4 (32706) LSP:: 414: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 414: /etc/cinit/svc/getty/3:4 (32704) LSP:: 414: /etc/cinit/svc/local-tuning/keyboard-layout:16 (414) pid: 0, m_client LSP:: 421: /etc/cinit/svc/init:16 (32719) LSP:: 421: /etc/cinit/svc/test/env:16 (32717) LSP:: 421: /etc/cinit/svc/test:4 (32708) LSP:: 421: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 421: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 421: /etc/cinit/svc/network:4 (32707) LSP:: 421: /etc/cinit/svc/mount/root:16 (32721) LSP:: 421: /etc/cinit/svc/mount:4 (32706) LSP:: 421: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 421: /etc/cinit/svc/getty/3:4 (32704) LSP:: 421: /etc/cinit/svc/local-tuning/keyboard-layout:16 (421) pid: 0, m_client LSP:: 428: /etc/cinit/svc/init:16 (32719) LSP:: 428: /etc/cinit/svc/test/env:16 (32717) LSP:: 428: /etc/cinit/svc/test:4 (32708) LSP:: 428: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 428: /etc/cinit/svc/network/eth0:16SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call (32718) LSP:: 428: /etc/cinit/svc/network:4 (32707) LSP:: 428: /etc/cinit/svc/mount/root:16 (32721) LSP:: 428: /etc/cinit/svc/mount:4 (32706) LSP:: 428: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 428: /etc/cinit/svc/getty/3:4 (32704) LSP:: 428: /etc/cinit/svc/local-tuning/keyboard-layout:16 (428) pid: 0, m_client LSP:: 435: /etc/cinit/svc/init:16 (32719) LSP:: 435: /etc/cinit/svc/test/env:16 (32717) LSP:: 435: /etc/cinit/svc/test:4 (32708) LSP:: 435: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 435: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 435: /etc/cinit/svc/network:4 (32707) LSP:: 435: /etc/cinit/svc/mount/root:16 (32721) LSP:: 435: /etc/cinit/svc/mount:4 (32706) LSP:: 435: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 435: /etc/cinit/svc/getty/3:4 (32704) LSP:: 435: /etc/cinit/svc/local-tuning/keyboard-layout:16 (435) pid: 0, m_client LSP:: 452: /etc/cinit/svc/init:16 (32719) LSP:: 452: /etc/cinit/svc/test/env:16 (32717) LSP:: 452: /etc/cinit/svc/test:4 (32708) LSP:: 452: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 452: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 452: /etc/cinit/svc/network:4 (32707) LSP:: 452: /etc/cinit/svc/mount/root:16 (32721) LSP:: 452: /etc/cinit/svc/mount:4 (32706) LSP:: 452: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 452: /etc/cinit/svc/getty/3:4 (32704) LSP:: 452: /etc/cinit/svc/local-tuning/keyboard-layout:16 (452) pid: 0, m_client LSP:: 459: /etc/cinit/svc/init:16 (32719) LSP:: 459: /etc/cinit/svc/test/env:16 (32717) LSP:: 459: /etc/cinit/svc/test:4 (32708) LSP:: 459: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 459: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 459: /etc/cinit/svc/network:4 (32707) LSP:: 459: /etc/cinit/svc/mount/root:16 (32721) LSP:: 459: /etc/cinit/svc/mount:4 (32706) LSP:: 459: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 459: /etc/cinit/svc/getty/3:4 (32704) LSP:: 459: /etc/cinit/svc/local-tuning/keyboard-layout:16 (459) pid: 0, m_client LSP:: 466: /etc/cinit/svc/init:16 (32719) LSP:: 466: /etc/cinit/svc/test/env:16 (32717) LSP:: 466: /etc/cinit/svc/test:4 (32708) LSP:: 466: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 466: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 466: /etc/cinit/svc/network:4 (32707) LSP:: 466: /etc/cinit/svc/mount/root:16 (32721) LSP:: 466: /etc/cinit/svc/mount:4 (32706) LSP:: 466: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 466: /etc/cinit/svc/getty/3:4 (32704) LSP:: 466: /etc/cinit/svc/local-tuning/keyboard-layout:16 (466) pid: 0, m_client LSP:: 473: /etc/cinit/svc/init:16 (32719) LSP:: 473: /etc/cinit/svc/test/env:16 (32717) LSP:: 473: /etc/cinit/svc/test:4 (32708) LSP:: 473: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 473: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 473: /etc/cinit/svc/network:4 (32707) LSP:: 473: /etc/cinit/svc/mount/root:16 (32721) LSP:: 473: /etc/cinit/svc/mount:4 (32706) LSP:: 473: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 473: /etc/cinit/svc/getty/3:4 (32704) LSP:: 473: /etc/cinit/svc/local-tuning/keyboard-layout:16 (473) pid: 0, m_client LSP:: 480: /etc/cinit/svc/init:16 (32719) LSP:: 480: /etc/cinit/svc/test/env:16 (32717) LSP:: 480: /etc/cinit/svc/test:4 (32708) LSP:: 480: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 480: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 480: /etc/cinit/svc/network:4 (32707) LSP:: 480: /etc/cinit/svc/mount/root:16 (32721) LSP:: 480: /etc/cinit/svc/mount:4 (32706) LSP:: 480: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 480: /etc/cinit/svc/getty/3:4 (32704) LSP:: 480: /etc/cinit/svc/local-tuning/keyboard-layout:16 (480) pid: 0, m_client LSP:: 487: /etc/cinit/svc/init:16 (32719) LSP:: 487: /etc/cinit/svc/test/env:16 (32717) LSP:: 487: /etc/cinit/svc/test:4 (32708) LSP:: 487: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 487: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 487: /etc/cinit/svc/network:4 (32707) LSP:: 487: /etc/cinit/svc/mount/root:16 (32721) LSP:: 487: /etc/cinit/svc/mount:4 (32706) LSP:: 487: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 487: /etc/cinit/svc/getty/3:4 (32704) LSP:: 487: /etc/cinit/svc/local-tuning/keyboard-layout:16 (487) pid: 0, mLoading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz _client LSP:: 494: /etc/cinit/svc/init:16 (32719) LSP:: 494: /etc/cinit/svc/test/env:16 (32717) LSP:: 494: /etc/cinit/svc/test:4 (32708) LSP:: 494: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 494: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 494: /etc/cinit/svc/network:4 (32707) LSP:: 494: /etc/cinit/svc/mount/root:16 (32721) LSP:: 494: /etc/cinit/svc/mount:4 (32706) LSP:: 494: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 494: /etc/cinit/svc/getty/3:4 (32704) LSP:: 494: /etc/cinit/svc/local-tuning/keyboard-layout:16 (494) pid: 0, m_client LSP:: 501: /etc/cinit/svc/init:16 (32719) LSP:: 501: /etc/cinit/svc/test/env:16 (32717) LSP:: 501: /etc/cinit/svc/test:4 (32708) LSP:: 501: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 501: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 501: /etc/cinit/svc/network:4 (32707) LSP:: 501: /etc/cinit/svc/mount/root:16 (32721) LSP:: 501: /etc/cinit/svc/mount:4 (32706) LSP:: 501: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 501: /etc/cinit/svc/getty/3:4 (32704) LSP:: 501: /etc/cinit/svc/local-tuning/keyboard-layout:16 (501) pid: 0, m_client LSP:: 510: /etc/cinit/svc/init:16 (32719) LSP:: 510: /etc/cinit/svc/test/env:16 (32717) LSP:: 510: /etc/cinit/svc/test:4 (32708) LSP:: 510: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 510: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 510: /etc/cinit/svc/network:4 (32707) LSP:: 510: /etc/cinit/svc/mount/root:16 (32721) LSP:: 510: /etc/cinit/svc/mount:4 (32706) LSP:: 510: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 510: /etc/cinit/svc/getty/3:4 (32704) LSP:: 510: /etc/cinit/svc/local-tuning/keyboard-layout:16 (510) pid: 0, m_client LSP:: 520: /etc/cinit/svc/init:16 (32719) LSP:: 520: /etc/cinit/svc/test/env:16 (32717) LSP:: 520: /etc/cinit/svc/test:4 (32708) LSP:: 520: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 520: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 520: /etc/cinit/svc/network:4 (32707) LSP:: 520: /etc/cinit/svc/mount/root:16 (32721) LSP:: 520: /etc/cinit/svc/mount:4 (32706) LSP:: 520: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 520: /etc/cinit/svc/getty/3:4 (32704) LSP:: 520: /etc/cinit/svc/local-tuning/keyboard-layout:16 (520) pid: 0, m_client LSP:: 533: /etc/cinit/svc/init:16 (32719) LSP:: 533: /etc/cinit/svc/test/env:16 (32717) LSP:: 533: /etc/cinit/svc/test:4 (32708) LSP:: 533: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 533: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 533: /etc/cinit/svc/network:4 (32707) LSP:: 533: /etc/cinit/svc/mount/root:16 (32721) LSP:: 533: /etc/cinit/svc/mount:4 (32706) LSP:: 533: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 533: /etc/cinit/svc/getty/3:4 (32704) LSP:: 533: /etc/cinit/svc/local-tuning/keyboard-layout:16 (533) pid: 0, m_client LSP:: 541: /etc/cinit/svc/init:16 (32719) LSP:: 541: /etc/cinit/svc/test/env:16 (32717) LSP:: 541: /etc/cinit/svc/test:4 (32708) LSP:: 541: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 541: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 541: /etc/cinit/svc/network:4 (32707) LSP:: 541: /etc/cinit/svc/mount/root:16 (32721) LSP:: 541: /etc/cinit/svc/mount:4 (32706) LSP:: 541: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 541: /etc/cinit/svc/getty/3:4 (32704) LSP:: 541: /etc/cinit/svc/local-tuning/keyboard-layout:16 (541) pid: 0, m_client LSP:: 548: /etc/cinit/svc/init:16 (32719) LSP:: 548: /etc/cinit/svc/test/env:16 (32717) LSP:: 548: /etc/cinit/svc/test:4 (32708) LSP:: 548: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 548: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 548: /etc/cinit/svc/network:4 (32707) LSP:: 548: /etc/cinit/svc/mount/root:16 (32721) LSP:: 548: /etc/cinit/svc/mount:4 (32706) LSP:: 548: /etc/cinit/svc/local-tuning:4 (32705) LSP:: 548: /etc/cinit/svc/getty/3:4 (32704) LSP:: 548: /etc/cinit/svc/local-tuning/keyboard-layout:16 (548) pid: 0, m_client LSP:: 555: /etc/cinit/svc/init:16 (32719) LSP:: 555: /etc/cinit/svc/test/env:16 (32717) LSP:: 555: /etc/cinit/svc/test:4 (32708) LSP:: 555: /etc/cinit/svc/network/loopback:16 (32720) LSP:: 555: /etc/cinit/svc/network/eth0:16 (32718) LSP:: 555: /etc/cinit/svc/network:4 (32707) LSP:: 555: /etc/cinit/svSC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz findkeymap: No such file or directory cannot open file Loading /usr/share/keymaps/i386/dvorak/dvorak.kmap.gz SC::/etc/cinit/svc/local-tuning/keyboard-layout::FAILED::::RESPAWN::ES::/etc/cinit/svc/local-tuning/keyboard-layout/on CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL CBA::/etc/cinit/svc/local-tuning/keyboard-layout/on ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.params ORC: dvorak ORC:/etc/cinit/svc/local-tuning/keyboard-layout/on.env SFN: NULL msgrcv: Interrupted system call cinit-0.3pre15/doc/man/000077500000000000000000000000001125633325400146635ustar00rootroot00000000000000cinit-0.3pre15/doc/man/cinit.text000066400000000000000000000027621125633325400167060ustar00rootroot00000000000000cinit(8) ======== Nico Schottelius NAME ---- cinit - fast executing, small and simple init with support for profiles SYNOPSIS -------- 'cinit' [cprofile:name_of_profile] DESCRIPTION ----------- Cinit is an init system. It normally gets started by the operating system (Linux, *BSD, ...) directly after the kernel has been loaded. Cinit uses parallel execution of services as far as possible. To ensure the correct boot order you need to specify which service 'needs' or 'wants' another service. The resulting dependency tree is used at startup to determine which service to start when. This may result in different boot orders depending on whether one service is one time faster or slower. Due to the dependencies this is not a problem, but allowed and wished per design. For more information refer to the texinfo or html documentation. OPTIONS ------- cprofile:name_of_profile:: If specified, cinit will start the named profile instead of the standard 'init' service BUGS ---- cinit is not tested nor documented very well currently. The porting to other OS is not finished yet (mainly missing system level binaries: shutdown, reboot, halt). Both is work in progress. AUTHOR ------ Nico Schottelius RESOURCES --------- Main web site: http://unix.schottelius.org/cinit/[] COPYING ------- Copyright \(C) 2006 Nico Schottelius. Free use of this software is granted under the terms of the GNU General Public License (GPL). cinit-0.3pre15/doc/man/cmd.text000066400000000000000000000032711125633325400163370ustar00rootroot00000000000000cmd(8) ====== Nico Schottelius NAME ---- cmd - cinit management and information tool SYNOPSIS -------- 'cmd' [-ed (i|w|n)] [-(p|s) ] [-v] DESCRIPTION ----------- cmd adds the management possibility to cinit(8). You can retrieve several information from cinit and change services. OPTIONS ------- -d:: Disable service (see below for required parameters) (NOT YET IMPLEMENTED) -e:: Enable service - i: Included all needs and wants - n: Exclude needs - w: Exclude wants (NOT YET IMPLEMENTED) -p:: Retrieve last process id (pid) for the specific service. For respawn services this is the pid of the running service. For services that are started only once it is the pid it had when running. (NOT YET IMPLEMENTED) -s:: Retrieve status of a service. Warning: Do not add trailing slash. Path can be specified absolute (/etc/cinit/svc/mount/root) or relative (mount/root). -v:: Get version of cinit. -V:: Get version of cmd. EXAMPLES -------- Get version:: [8:44] denkbrett:src# cmd -v Version of cinit: 0.3pre12 Get status:: [8:37] denkbrett:src# ./cmd -s mount/root Status of /etc/cinit/svc/mount/root is: 2001 EXIT STATUS ----------- Cmd returns 0 on success, 1 on user errors, 2 on communication errors and 3 on unknown reason errors. BUGS ---- Not everything is implemented. AUTHOR ------ Nico Schottelius RESOURCES --------- Main web site: http://unix.schottelius.org/cinit/[] COPYING ------- Copyright \(C) 2007 Nico Schottelius. Free use of this software is granted under the terms of the GNU General Public License Version 3 (GPLv3). cinit-0.3pre15/doc/man/cservice000066400000000000000000000024551125633325400164170ustar00rootroot00000000000000WARNING: cservice is not yet ready for cinit-0.3! -------------------------------------------------------------------------------- cservice, Nico Schottelius, 2005-06-10 (Last Modified: 2005-06-22) -------------------------------------------------------------------------------- cservice - control cinit cservice -[phearsu] -e - (ein) start a service (including all needed dependencies) -a - (aus) stop a respawing service, don't care about other services -r - reboot -h - halt -p - poweroff (on some systems the same as halt) -s - reScue mode - only a shell -u - update: hot reboot - shutdown system and execute /sbin/cinit A service may be specified either as relative or as absolute path. -h, -p, -r, -s and -u need the "Magic Word" to do their work: "thilo" -------------------------------------------------------------------------------- Some examples: cservice -e /etc/cinit/getty/8 # fire up getty/8 cd /etc/cinit/getty; cservice -a ./8 # shut down getty/8 cservice -h thilo # halt cservice -r thilo # reboot cservice -s thilo # rescue cservice -u thilo # update -------------------------------------------------------------------------------- cinit-0.3pre15/doc/man/halt.kill.text000066400000000000000000000015311125633325400174530ustar00rootroot00000000000000halt.kill(8) ============ Nico Schottelius NAME ---- halt.kill - Halts systems running cinit through a kill call SYNOPSIS -------- 'halt.kill' DESCRIPTION ----------- You normally halt your system through 'cmd'. If cmd is unavailable or the IPC system has problem there is still the possibilty to halt it through a signal. See 'src/include/signals.h' for more details which signals are used. OPTIONS ------- none:: No options are used, If you execute halt.kill, your system will be halted. AUTHOR ------ Nico Schottelius RESOURCES --------- Main web site: http://unix.schottelius.org/cinit/[] SEE ALSO --------- cmd(8) COPYING ------- Copyright \(C) 2007 Nico Schottelius. Free use of this software is granted under the terms of the GNU General Public License (GPL). cinit-0.3pre15/doc/man/poweroff.kill.text000066400000000000000000000016521125633325400203560ustar00rootroot00000000000000poweroff.kill(8) ================ Nico Schottelius NAME ---- poweroff.kill - Halts and powers off systems running cinit through a kill call SYNOPSIS -------- 'poweroff.kill' DESCRIPTION ----------- You normally poweroff your system through 'cmd'. If cmd is unavailable or the IPC system has problem there is still the possibilty to poweroff it through a signal. See 'src/include/signals.h' for more details which signals are used. OPTIONS ------- none:: No options are used, If you execute poweroff.kill, your system will be powered off. AUTHOR ------ Nico Schottelius RESOURCES --------- Main web site: http://unix.schottelius.org/cinit/[] SEE ALSO --------- cmd(8), halt.kill(8), reboot.kill(8) COPYING ------- Copyright \(C) 2007 Nico Schottelius. Free use of this software is granted under the terms of the GNU General Public License (GPL). cinit-0.3pre15/doc/man/reboot.kill.text000066400000000000000000000016161125633325400200210ustar00rootroot00000000000000reboot.kill(8) ============== Nico Schottelius NAME ---- reboot.kill - Reboots systems running cinit through a kill call SYNOPSIS -------- 'reboot.kill' DESCRIPTION ----------- You normally reboot your system through 'cmd'. If cmd is unavailable or the IPC system has problem there is still the possibilty to reboot it through a signal. See 'src/include/signals.h' for more details which signals are used. OPTIONS ------- none:: No options are used, If you execute reboot.kill, your system will be rebooted. AUTHOR ------ Nico Schottelius RESOURCES --------- Main web site: http://unix.schottelius.org/cinit/[] SEE ALSO --------- cmd(8), halt.kill(8), poweroff.kill(8) COPYING ------- Copyright \(C) 2007 Nico Schottelius. Free use of this software is granted under the terms of the GNU General Public License (GPL). cinit-0.3pre15/doc/todo/000077500000000000000000000000001125633325400150555ustar00rootroot00000000000000cinit-0.3pre15/doc/todo/0.3pre11000066400000000000000000000004631125633325400161540ustar00rootroot00000000000000Done: - cleanup ipc: merge cinit_ipc_logon() and cinit_ipc_connect()? => already done! - finish cmd in general, perhaps only including one command. [18:51] denkbrett:src# LANG=C cp cinit /sbin/cinit cp: cannot create regular file `/sbin/cinit': Text file busy => mv & cp! => documentation! cinit-0.3pre15/doc/todo/0.3pre12000066400000000000000000000026531125633325400161600ustar00rootroot00000000000000Wished release date: 6/7. September -------------------------------------------------------------------------------- Done: - begin to write documentation about client functions => noone needs that anyway. skip and concentrate on functions now. cleanup ipc! where to call !cinit_ipc_logon and !cinit_ipc_connect? -------------------------------------------------------------------------------- Add Hallo, Liebster Nico, wuerdest du die dazu durchringen "make install" und vllt. sogar "make install-test" in die cinit 0.3er branch aufnehmen? vlg Lucky ==> added make install in previous releases, make test maybe come back later again. - cleanup communication: put parts of comm.h into cinit.h => global exposure or define new structure in cinit.h? => removed comm.h - check svc path in cmd: if it's relative, add /etc/cinit/svc to it => added. - add update for git => so cloning does not fail! => added hook. Use http://www.opengroup.org/onlinepubs/009695399/basedefs/stdint.h.html => partly implemented - remove manual pid support, use the one supplied by msgctl() => ok. - there seems to be a race condition in the execution of the dependency tree: it happens that services that depend on mounted /proc, have needs on mount/proc are still exited before /proc is mounted. problem of cinit or of mount, exiting too early? guess the first one, so fix it :-) => missing check in svc_needs_status.c cinit-0.3pre15/doc/todo/0.3pre13000066400000000000000000000015741125633325400161620ustar00rootroot00000000000000Wished released date: 10./11. September -------------------------------------------------------------------------------- Done: - add get_svc_pid() - cleanup msgq.h: namespace! - cleanup cmd: add real usage, add -h for help - cleanup cinit_ipc_logon()! [already done before] - cleanup headers: ==> not yet needed. seems to make more sense, to have more than one exposed header. cinit.h gets to fast too big. so splitoff to: /* main */ /* ... */ - create libcinit.a/so and link against it => not need right now. - pre12 seems to have an IPC problem: Fix it. ==> problem with not finishing cinit startup - global symbol to track the connection to cinit in the client => cinit_ipc_cinit() - initalise ipc in the client (only once) => not really our problem, client should be able to remember whether she called us once or twice. cinit-0.3pre15/doc/todo/0.3pre13.race-condition000066400000000000000000000013731125633325400210540ustar00rootroot0000000000000009:49 < telmich> is it possible, that if I fork() and call _exit(0) in the child, that the _exit(0) is executed earlier than the fork() call returns in the parent? 09:49 < telmich> I'm having some race condition in cinit, where the pid is not yet updated in the service structure, and the child exited before and thus cinit does not update the service 09:49 < telmich> as being run 09:51 < telmich> rexy_: currently I'm thinking about implementing a lock before starting the fork() 09:51 < telmich> rexy_: thus cinit will react differently, if the starting function is still running 09:51 < telmich> rexy_: but I'm somehow confused, that fork() allows such race condition cinit-0.3pre15/doc/todo/0.3pre14000066400000000000000000000001151125633325400161510ustar00rootroot00000000000000Wished release date: 13. September - add support for shutting down services cinit-0.3pre15/doc/todo/0.3pre15000066400000000000000000000036271125633325400161650ustar00rootroot00000000000000Wished release date: 20. September - Add support for starting/stoping services via cmd - add support for additional information (like which services stopped when having dependencies) - if cinit has to stop / start others, how to report? - add strings to cinit internally to a buffer? -> or struct cinit_answer + status - add support to enable services - create some boot profiles - cinit.install.standard.dirs.argv - code check: * check needs: really started, after started or after finished starting? * wants: are they checked? - fix devel/codingguideline.text! - perhaps merge svc_need_status to svc_status cinit-communication: cinit_get_failed_needs(char *name, int *cnt); - add support for shutting down services on halt - cleanup msgq/cinit_ipc_listen.c - move logic out of the child handler: => use the new while()-loop in core/cinit.c! time() and co. are problematic in a child handler! introduce global list of services to execute => perhaps reuse already existing dependency-list? tree_exec(): check whether adding something to the dep list hurts => don't think so. expand / change ipc handler: make it return the message move while() loop to core/cinit.c in the while loop, the global dependency list should be empty. if it is not, we should start something. => chance cinit_ipc_listen() to use without while() loop => export logic to core/cinit.c - map status numbers to messages - Cleanup doc/user/NEW_using_cinit_freebsd => make a real document! - write / update manpage for cmd! - add sleep() support after service exited. -------------------------------------------------------------------------------- Done: - add minimal test-suite: cmd -s /etc/cinit/svc/init cmd -p /etc/cinit/svc/init cmd -v cmd -V - change to GPLv3? => ask Markus (cinit), Killerfox (cconfig) and Peter (cconfig) cinit-0.3pre15/doc/todo/0.3pre16000066400000000000000000000004031125633325400161530ustar00rootroot00000000000000Wished release date: 27. September - check porting code: * advise users to set conf/os * add uname -r | tr ... as make osconfig - check that all parts of cinit compile at least under: * linux, linux on 64bit * FreeBSD * NetBSD - cleanup output cinit-0.3pre15/doc/todo/0.3pre17000066400000000000000000000005731125633325400161640ustar00rootroot00000000000000Wished release date: 3. October "Code quality assurance release" - Fix bugs all outstanding bugs. - Give cinit some time, write some documentation and make pre17 the last pre of the 0.3 serie. - Give the code out to other developers, request explicit strong critics => So even "This could be in theory, if Mars is behind Pluto on Sunday evening" bugs are out. cinit-0.3pre15/doc/todo/0.3pre18000066400000000000000000000001571125633325400161630ustar00rootroot00000000000000- add support to manually set status of a service: cmd -s respawn, failed, once, ... - make get status = -g cinit-0.3pre15/doc/todo/0.3pre19000066400000000000000000000002041125633325400161550ustar00rootroot00000000000000- enable fast shutdown: - ignores services and jumps directly to conf/last - enable ultrafast shutdown - even skips conf/last cinit-0.3pre15/doc/todo/0.4000066400000000000000000000045121125633325400153030ustar00rootroot00000000000000-------------------------------------------------------------------------------- Clean service status messages: Ausgaben nach Beendigung vom Starten des Services. [ on ] %s + Ergebnis [ off ] %s -------------------------------------------------------------------------------- 16:13 < KillerFox> telmich: hast du eigentlich schon hooks in cinit? 20:07 < KillerFox> Vapier führt mal wieder Selbstgespräche. 23:39 < telmich> KillerFox: wozu? 23:42 < KillerFox> telmich: es wäre durchaus interessant, um z.B. sterbende Prozesse wieder zu starten und so. 23:42 < KillerFox> oder einen Hinweis per Mail zu verschicken. 23:43 < telmich> ahh, du meinst so benachrichtigungen von cinit an $prozess? 23:43 < KillerFox> jein 23:43 < KillerFox> du machst z.B. /etc/cinit/hooks/ 23:43 < KillerFox> darin gibts dann Scripte die bei bestimmten Ereignise aufgerufen werden. 23:43 < KillerFox> z.B. wenn ein Prozess stirbt 23:44 < KillerFox> du kannst dir natürlich auch überlegen, es auf Prozessebene herunter zu hacken 23:44 < telmich> ja, eher letzeres 23:44 < KillerFox> so könnte man auch ein paar nette Sachen machen. z.B. Aufräumarbeiten nachdem ein Prozess beendet wurde oder so 23:45 < KillerFox> telmich: ich finde beides Sinnvoller 23:45 < KillerFox> telmich: globale und lokale Hooks 23:45 < KillerFox> lokale überschreiben globale oder so 23:45 < telmich> oder laufen beide 23:45 < KillerFox> oder man kaskadiert sie. 23:45 < KillerFox> genau 23:46 < KillerFox> sinnvolle hooks: pre-start, start, post-start, pre-stop, stop, post-stop, crash 23:46 < KillerFox> oder sowas 23:47 < KillerFox> vielleicht fallen dir noch mehr ein. 23:48 < KillerFox> die Kommunikation könnte man dann wahlweise über Parameter oder Umgebungsvariablen lösen 23:48 < KillerFox> um z.B. mitzuteilen welcher Prozess gestoppt wurde 23:49 < KillerFox> z.B. wenn man in pre-stop je nach Bedingung den Stop-Vorgang abbrechen will. 23:49 < telmich> via ${ipc} => kommt darauf an, was implementiert ist; zZ ist es ja msgq 23:50 < telmich> ahh, so 23:50 < telmich> das waere noch recht trivial ueber pipes 23:50 < KillerFox> fifos/sockets, was auch immer. 23:50 < KillerFox> das müsste man dann mit einer Bibliothek lösen oder so 23:50 < telmich> ja, die ist auch im aufbau in libcinit/ cinit-0.3pre15/doc/todo/0.4.1000066400000000000000000000000531125633325400154360ustar00rootroot00000000000000- Generate automatic asciidoc from conf/* cinit-0.3pre15/doc/todo/long_list000066400000000000000000000005671125633325400170020ustar00rootroot00000000000000Code ---- Performance ~~~~~~~~~~~ - Perhaps replace malloc for path with static buffer? Compatibility ~~~~~~~~~~~~~ - create migration scripts Usage ~~~~~ - Aid in debugging cinit-configuration (check without reboot) - Integrate into OS package system Other ~~~~~ - add log support to shm - Check and clean doc/: Remove *TODO*+ROADMAP and leave behin doc/TODO (or ditz) cinit-0.3pre15/doc/user/000077500000000000000000000000001125633325400150665ustar00rootroot00000000000000cinit-0.3pre15/doc/user/FAQ000066400000000000000000000027441125633325400154270ustar00rootroot00000000000000-------------------------------------------------------------------------------- FAQ - Frequently asked questions, Nico Schottelius, 2005-06-05 (Last Modified: 2005-06-12) -------------------------------------------------------------------------------- Q: So, what's good in cinit? A: Fast executing, clean design, parallel execution, profile support, small binary size (~50KiB static against uclibc), easy configuration, just to name the main facts. Q: How do I start cinit? A: You don't start cinit directly, but your kernel does. Please have a look at your system documentation how to tell your kernel to load /sbin/cinit as init. You'll also find some examples in the README file. Q: What is /etc/cinit/init used for? A: The init service is not just a placeholder, it is the beginning of executing services. Q: /etc/cinit/init seems not to be used when I use profiles? A: That's true. When you select a profile, cinit will begin in this directory: "cprofile:home" will use /etc/cinit/home as starting point. Q: Why does it take so long before my getty is respawned? A: cinit only waits 5 seconds (see conf/sleep_svc), if a) a service didn't exit normally b) the service had a non-zero exit code So fixing the problem would mean fixing your getty / shell. Q: I am using a tarball from samples/ and there is no getty on tty1!? A: That's true, the first console is used for logging purpose in the examples. You still have six console (tty2-tty7) running getty. cinit-0.3pre15/doc/user/README.text000066400000000000000000000007071125633325400167350ustar00rootroot00000000000000cinit/doc/devel =============== Nico Schottelius 0.1, Initial Version from 2006-07-09 :Author Initials: NS This directory contains cinit user documents. Introduction ------------ This file describes the related documents in the current directory. Who should read those documents? -------------------------------- People using cinit. Content ------- hints.text: Some general hints tuning.text: Some tuning hints cinit-0.3pre15/doc/user/TODO000066400000000000000000000002301125633325400155510ustar00rootroot00000000000000All the content in this file is unsorted. Reading may harm you. Confdir: /etc/cinit/conf/ panic: /etc/cinit/conf/panic, /etc/cinit/conf/panic.params cinit-0.3pre15/doc/user/compiles.on.text000066400000000000000000000011741125633325400202250ustar00rootroot00000000000000cinit - known configurations cinit compiles on ============================================== Nico Schottelius 0.1, for cinit 0.3, Initial Version from 2006-12-08 :Author Initials: NS This document lists all the configuration known to me on that cinit compiles. If you compiled cinit with another configuration, drop a mail to nico-cinit-report [at] schottelius.org. The list -------- cinit is known to compile on: - x86-Linux-Debian-3.0-gcc-4-glibc-2.3.2 - x86-Linux-Debian-3.0-gcc-3.4.3-glibc-2.3.5 - ppc-Linux-Gentoo-2004.3-gcc-3.4.3-glibc-2.3.5 - ppc-Linux-Gentoo-2004.3-gcc-3.4.3-uclibc-0.9.27 cinit-0.3pre15/doc/user/conf-system.text000066400000000000000000000021451125633325400202450ustar00rootroot00000000000000The conf/ system ================= Nico Schottelius 0.1, for cinit 0.3, Initial version from 2006-12-08 :Author Initials: NS This documentes describes the configuration system used by cinit. What is the conf/ system? ------------------------- The conf/ system is the configuration system for the cinit build. The first line of each file below conf/ is a configuration value with the name of the file: ---------------------------------------------------------------------- [9:00] hydrogenium:cinit-0.3pre6% head -n 1 conf/cc gcc ---------------------------------------------------------------------- This means that the variable "cc" has the value "gcc". What is the reason for conf/? ----------------------------- I needed a small and simple configuration system, which may be included in the full build process. Is conf/ also usable for other projects? ---------------------------------------- In its current state conf/ is just a prototype, with which I experiement a lot. But it is possible that the future aim is to provide a simele configuration and autoconfiguraton mechanism. cinit-0.3pre15/doc/user/configuring.cinit.text000066400000000000000000000253311125633325400214170ustar00rootroot00000000000000cinit - Configuring =================== Nico Schottelius 0.1, for cinit 0.3, Initial version from 2005-05-28 :Author Initials: NS This documentes describes how to configure cinit. You should already have cinit installed, otherwise read "cinit - Installing" first. General configuration layout ---------------------------- Cinit uses the <<>> configuration syntax, which means that the configuration is kept as simple as possible. The following sections will show you what that means. The cinit configuration consists of - a special configuration directory - and the service definitions. Paths ----- Normally the configuration is kept below '/etc/cinit' (though you can change this before compiling in conf/cinit_dir). The full description of the path layout of cinit and how to change it can be found in 'paths.text'. Conf ---- The special configuration directory is normally called `conf/` (defined at compile-time in `conf/c_confdir`). For all executables into this directory apply the same rules as mentioned below in "Execution: on and off": Appened .params specifies parameters, appended .env specifies environment. conf/last ~~~~~~~~~ This is the last part that will be executed. After it has finished, cinit will halt, power-off or reboot your machine. You can use it for whatever task to accomplish (as most things of cinit), but the idea behind it is to use it for cleaning up things that are not covered by the off parts of the services. This maybe swapoff (although this is an unecessary call before poweroff, imho and even if needed this could be handled within the off part of the same services that enabled it) or `umount -a` for everything manually mounted and not unmounted yet. conf/sleep_before_kill ~~~~~~~~~~~~~~~~~~~~~~ This file contains just one line: The number of seconds to sleep after SIGTERM was sent to every remaining process before sending SIGKILL to all processes. If this file is unreadable or not existent, cinit will fall back to the value compiled in (which was specified at build time in conf/sleep_kill). Services -------- cinit is service based. Other init systems use shell scripts (for instance /etc/rc, /etc/init.d/rc as starters and /etc/rc*.d/* as "service definitions"). 'current-init-problems.text' explains why cinit does *not* use nor recommends the use of shell scripts. A service is simply a directory. This directory contains information about - what should be started when starting the service - what should be started when stoping the service - what dependencies the service has - whether to restart it, when it exits Full service definition ~~~~~~~~~~~~~~~~~~~~~~~ . A service consists of - a base directory (like /etc/cinit/svc/mount/root/) - dependency configuration (`needs` and `wants`) - start/stop programs (`on` and `off`) - respawn flag (`respawn`) Base directory ^^^^^^^^^^^^^^ You can create the base directory everywhere below /etc/cinit/svc. You may and it is recommened to create a directory structure (see 'example-directory-structure.text'). Dependencies ^^^^^^^^^^^^ The subdirectories - `wants` - and `needs` contain the dependencies for the service. Read 'dependencies.text' for more information. Respawning ^^^^^^^^^^^ If you create the empty file 'respawn' (adjustable via conf/c_respawn) the service will be restarted after it exits. -------------------------------------------------------------------------------- # Tell cinit to respawn the eth0.udhcpc service touch /etc/cinit/svc/network/eth0.udhcpc -------------------------------------------------------------------------------- Execution: on and off ^^^^^^^^^^^^^^^^^^^^^ When a service starts, the file `on` in the service directory is executed. It is ok, if this file is not existing. When a service stops, the file `off` in the service directory is executed. The file with the extension `.params` is used to specify the arguments to pass. Each line contains exactly one parameter. The file with the extension `.env` is used to specify the environment to pass. Each line contains exactly one variable definition in the form 'variable=value'. . The following six files are possibly used on starting/stoping: - ./on (the program called on startup) - ./on.params (the parameters to pass to the program, see conf/c_params) - ./on.env (the environment to pass to the program, see conf/c_env) - ./off (the program called when shutting down the service) - ./off.params (the parameters to pass to the program) - ./on.env (the environment to pass to the program) Some examples: ---------------------------------------------------------------------- /etc/cinit/svc/init: ./wants -> services it wants ./needs -> services it needs ---------------------------------------------------------------------- A more or less normal service without dependencies: ---------------------------------------------------------------------- /etc/cinit/testsvc: on -> link to program on.param -> parameters to program respawn -> restart it ---------------------------------------------------------------------- A service with all options used: ---------------------------------------------------------------------- /etc/cinit/fullsvc: on -> program to start when switching on on.params -> parameters to pass to start program on.env -> environment to pass to start program respawn -> respawn service off -> program to start when switching off off.params -> parameters to pass to stop program off.env -> environment to pass to stop program wants/* -> services it wants before starting (non-critical ones) needs/* -> links to needed services (critical!) before starting ---------------------------------------------------------------------- Profiles -------- Profiles allow you to define different startup scenarios and select those before bootup. Read 'profiles.text' for more information about profiles. The profile support was added in cinit-0.0.6. Service execution order ------------------------ The first service executed is '/etc/cinit/svc/init'. If a profile is selected '/etc/cinit/svc/`profilename`' is used instead. Cinit builds a full service dependency tree through the `wants` and `needs` of the first service and its dependencies (recursively). After the tree is generated, cinit begins to start the services at the end of the tree. These services have no `needs`. If you manage to create circular dependencies your system will not startup. You can verify the correctness your configuration with the script `cinit.check.config`. Hints ----- Service executing / parameters ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The on and off files can and should be links to the programs you want to execute instead of a shell script. This way you save yourself the overhead of loading a shell. The speed enhancement is very big if you have shells like bash installed as /bin/sh (which is *not* senseful anyway, I would recommend dash or ksh for /bin/sh). The on.params and off.params files could also be links to system configuration: Assume the service is called local-tuning/keyboard. The service could look like this: ---------------------------------------------------------------------- on -> /bin/loadkeys on.params -> /etc/sys/keyboard.mapping And /etc/sys/keyboard.mapping would contain only the string "dvorak" (or "de-latin1" or "sg-latin1" or ...). ---------------------------------------------------------------------- Daemons ~~~~~~~~ Daemons are programs that go away to the background (using fork()) after start). The fork-away strategy seems to be some illness introduced by traditional init systems, that are dependent on the fact, that a process exits on startup. cinit in contrast remembers the process ID (pid) of the services it restarts (those with `respawn` enabled). So when the daemon fork()s away and the parent process exits it looks to cinit like the watched service died and cinit will restart it. Happily, most processes can be taught not to go to background. Some processes even do that by default and very less are broken that one cannot tell them not to background. A list of known processes that are normally used in respawn processes can be found in 'daemons.backgrounding.text'. If your process is not listed in `daemons.backgrounding.text', check the documentation of your daemon program, if may have a switch to disable forking. But, with a small hack it is even possible to respawn those broken processes: We start a program, that - starts the daemon, - monitors the pidfile of the daemon, - waits until that pid does not exist anymore - and then exits. Such a program is included into the cinit source tarball, though I do not recommend using it. The better way is to implement non forking mode into your process. The name of the program (actually a shell script) is 'cinit.wait.for.daemon'. You can use it as the `on` part of a service and add - the pidfile, - the process binary - and the process parameters to `on.params`. Thus the service could look like: ---------------------------------------------------------------------- svc-broken-daemon/ on -> /sbin/cinit.wait.for.daemon on.params: /var/run/apache.pid /usr/packages/apache-2.0.51/bin/httpd -DSSL ---------------------------------------------------------------------- (This is not a so good example, because Apache supports non-forking mode). Be aware: This is just a hack, first try to avoid backgrounding and you won't need this hack! Logging ~~~~~~~ Currently there's no special logging support. When a process writes to stdout, it will be displayed on the same stdout cinit is connected to. In newer versions cinit (perhaps cinit-0.4) will also support logging stdout and stderr of a service. How to migrate your old init-system configuration to cinit ---------------------------------------------------------- This is highly dependent on your actual system, your system configuration and your own ideas. Cinit is able to replace all other init systems I know about. So the only question is "How to do it?". There are some hints on how to migrate to cinit in general and also some os specific help in the file 'migrating-init-systems.text', Debugging the configuration ---------------------------- Use `ls -lR /etc/cinit` or one of the tools found in contrib+tools/. Examples -------- Currently there are some example configurations available at http://unix.schottelius.org/cinit/samples/cinit-0.3/, sorted by host on which they are created. In near future, there will also be a file name configuration.example.text, which will lead you to a sample configuration. References ---------- + [[[cconfig]]] http://nico.schotteli.us/papers/linux/cconfig/ cinit-0.3pre15/doc/user/cross-compiling.text000066400000000000000000000001041125633325400210770ustar00rootroot00000000000000conf/os to destination os conf/cc conf/ld conf/cflags conf/ldflags cinit-0.3pre15/doc/user/current-init-problems.text000066400000000000000000000112071125633325400222410ustar00rootroot00000000000000Currently available init systems and their problems =================================================== Nico Schottelius 0.1, for cinit 0.3, Initial version from 2006-12-11 :Author Initials: NS This document describes some other init systems, especially the "traditional" ones and describes their problems. Introduction ------------- some history, sysv, bsd, minit, runit, initng, cinit, upstart Implementations --------------- List of current implementations as of 2006-12-12. Linux Sys-V-Init ~~~~~~~~~~~~~~~~ Debian Sid /etc/inittab "First script" /etc/init.d/rcS (specified /etc/init.d/rcS: Bourne shell script text executable Runlevels: 0-6, different states -------------------------------------------------------------------------------- [9:51] hydrogenium:cinit-0.3pre6% /sbin/runlevel N 2 -------------------------------------------------------------------------------- Depending on runlevel, the init calls /etc/init.d/rc $runlevel. This is manually configured in /etc/inittab /etc/init.d/rc: Bourne shell script text executable /etc/init.d/rc Calls symlinks in /etc/rc?.d. Each runlevel a directory: -------------------------------------------------------------------------------- [9:51] hydrogenium:cinit-0.3pre6% ls -ld /etc/rc*.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc0.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc1.d drwxr-xr-x 3 root root 4096 2006-12-01 16:56 /etc/rc2.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc3.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc4.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc5.d drwxr-xr-x 2 root root 4096 2006-12-01 16:56 /etc/rc6.d drwxr-xr-x 2 root root 4096 2006-11-28 23:17 /etc/rcS.d -------------------------------------------------------------------------------- rlmanager: sys-v-init hack ~~~~~~~~~~~~~~~~~~~~~~~~~~ rlmanager: one script to be executed, sources simply configuration Gentoo Linux ~~~~~~~~~~~~ no content yet BSD init ~~~~~~~~ Analyzed on FreeBSD. /etc/rc /etc/rc.d/ system services /usr/local/etc/rc.d/ user installed services Scripts may use values from /etc/rc.conf to check whether they should be started or not. runit ~~~~~ Three stages: Script1, dependencies, Script3 Initng ~~~~~~ no content yet minit ~~~~~ Focus on being small. Needs libowfat. Log support through pipe. Problems overview ----------------- Scripts ~~~~~~~ Scripts are slow. Startup time. Execution time. Unecessary overhead. Sequential startup ~~~~~~~~~~~~~~~~~~ In the 'old' init systems there is no support of parallel execution. So if one services hangs at startup, the whole system has to wait (for instance a dhcp request). In the worst case this may result in a non-booting system. Systems with dependencies can start the gettys for login before, in parallel to or even after blocking services are started. The fact, that they *are* started means you can interact with the system, you can end looping or blocking services. So sequential startup may not only be the reason for a pretty slow system, but also for an unmaintainable one. Unecessary services ~~~~~~~~~~~~~~~~~~~ Many implementations try to do whatever-is-possible on boot, trying to cover every possible and impossible situation. Portmap without any program that needs it. Starting all installed services per default (Debian) vs. let the user choose what to start (Gentoo). Nicht entfernte Altlasten ab und zu. No dependencies ~~~~~~~~~~~~~~~ Systems without dependencies may result in a chaos state after booting up. Only soft dependencies ~~~~~~~~~~~~~~~~~~~~~~~ The dependencies are used, but because of soft dependencies, services may be started although their dependency is missing. Parallel init system debugging ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In contrast to the old init systems, parallel executing init systems are much harder to debug. If the starting init systems does not have proper logging / reporting to the user (like cinit-0.2 has), the user may never find out, what happened and why. Parallel / dependency checking init system with variable boot order ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The boot order may be different each time you boot and is dependent on the success or failure of services. This way you can never tell exactly how and in which order they are executed. On multiprocessor machines, where processes may be truely executed in parallel, there is no order anymore, but there are n orders on n processors. To solve this issue, init systems which support parallel execution should ship with some testing tools, that simulate a startup. cinit will ship with such a tool in cinit-0.4. References ---------- no content yet cinit-0.3pre15/doc/user/daemons.backgrounding.text000066400000000000000000000060051125633325400222370ustar00rootroot00000000000000cinit - Daemons backgrounding ============================= Nico Schottelius 0.1, for cinit 0.3, Initial versinon from 2005-06-12 This document describes the backgrounding process and how to disable it. Definition ----------- A daemon is a program which runs in the background. Running in the background means you cannot access the process directly (like you can press a key in a shell). Daemons and cinit ------------------ cinit normally watches system services and restarts them (`respawn` flag in the configuration). If the process goes to background, cinit cannot control it directly anymore. List of daemons and non-forking parameters ------------------------------------------- The following daemons / servers are known to avoid backgrounding easily: - acpid [x86 power management]: -f (undocumentated but works) - apache [webserver]: -DFOREGROUND - asterisk [pbx]: -f - bind [dns server/caching]: -f - cardmgr [pcmcia/cardbus]: -f - cron (vixie) [schedular]: -f - cupsd [printer server]: -f or -F - dhclient [dhcp client]: -d - dhcp3 (isc) [dhcp server]: -f - distccd [compile server]: normal behaviour - dnsmasq [dhcp/tfpt/dns]: -k - dovecot [imap/pop3 server]: -F - fam [file alteration monitor]:-f - fcron [schedular]: -f - frox [ftp proxy]: "NoDetach" in config - freeradius [radiusd]: -f - gdm [display manager]: -nodaemon - hybrid [irc server]: -foreground - icecast2 [sound streamer]: normal behaviour - mini-lpd [printer server]: normal behaviour - metalog [log server]: normal behaviour - monotone [vcs]: normal behaviour - mpd [music server]: --no-daemon - nessusd ["security server"]: normal behaviour - ntpd [time server]: -n - nylon [socks proxy]: -f (prints output to terminal) - oidentd [identd server]: -i - oops [http proxy]: normal behaviour - openpbx [pbx]: -f - openssh [ssh server]: -D - openvpn [vpn server]: normal behaviour - pbbuttonsd [power management]:normal behaviour - portmap [portmapper]: -f - proftpd [ftp server]: -n - qmail [mta]: normal behaviour - rsync ["file server"]: --no-detach - silcd ["secure chat server"]: -F, --foreground - slapd [ldap]: -d - snmpd [snmp daemon]: -f - stunnel [ssl wrapper]: "foreground = yes" in config - svnserve [vcs]: --foreground - syslogd [log server]: -n - syslog-ng [log server]: -F - tcpserver [super server]: normal behaviour - udhcpc [dhcp client]: normal behaviour - vsftpd [ftp server]: normal behaviour (or: config: background=no) - xinetd [super server]: -dontfork Problematic daemons ------------------- Those are the daemons that do not offer the possibility (as of release 0.2): - atd (no switch, no configuraton option) - inetd (some variants) - nscd (no switch, no configuraton option) cinit-0.3pre15/doc/user/debugging.configuration000066400000000000000000000024321125633325400216130ustar00rootroot00000000000000-------------------------------------------------------------------------------- Debugging your init configuration, Nico Schottelius 2005-06-17 (Last Modified: 2005-06-17) -------------------------------------------------------------------------------- As writing an init configuration is not the easiest thing, here are some problems (P) and debugging hints (H): P: There's no output! H: If you don't start a service which outputs something there won't be any, cinit starts up silently. P: Service XYZ seems not to work? H: Try the following in your shell: cd /etc/cinit/the-service; ./on "$(on.params)" If that succeeds it has perhaps something missing which should have been started before. H: Create a test-service, which contains the following: on: link to /bin/echo on.params: "A test string" (with or without the quotes) Now add the test-service to the needs directory of service XYZ. If you see output the next time, the service is started. Otherwise you forgot to make another service dependent on service XYZ. P: How can I test if a non-outputting service successfully started? H: Create another service, which depends on your service and make it echo something. P: Does that profile support really work? H: Try that: cprofile:NONEXISTENT and you'll see. cinit-0.3pre15/doc/user/dependencies.text000066400000000000000000000045631125633325400204320ustar00rootroot00000000000000cinit - Dependencies ==================== Nico Schottelius 0.1, for cinit 0.3, Initial Version from 2005-12-13 :Author Initials: NS This document describes the different dependency types of cinit. Dependencies in general ----------------------- Each service may have two types (non-exclusive) types of dependencies: The so called `needs` or `wants`. These are directories below the service directory and contain symbolic links to the dependencies. The name of the link can be freely chosen. An example: The service '/etc/cinit/svc/getty/2' needs the service '/etc/cinit/svc/local-tuning/keyboard-layout': -------------------------------------------------------------------------------- [21:35] hydrogenium:needs# cd /etc/cinit/svc/getty/2/needs [21:35] hydrogenium:needs# ls -l insgesamt 0 lrwxrwxrwx 1 root root 37 2006-10-26 17:51 keyboard-layout -> ../../../local-tuning/keyboard-layout [21:35] hydrogenium:needs# cd keyboard-layout/ [21:35] hydrogenium:keyboard-layout# pwd -P /etc/cinit/svc/local-tuning/keyboard-layout -------------------------------------------------------------------------------- (Warning: This is an incomplete example, it misses at least `mount/root` as dependency) This service could additionally want something else, too. It is also possible that a service only `wants` another service or that a service has no dependencies. Absolute versus relative links ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cinit does not care whether a link is relative or absolute. And as far as I can see it does not make any difference to usability. In general, it seems to be a little bit 'easier' to use relative links when manually configuring cinit ('ln -s ../../../service' versus 'ln -s /etc/cinit/svc/category/service'), but easier readable when analysing them (with `ls -l'). The two types ------------- needs ~~~~~ `Needs` are the 'hard dependencies': If a services fails to start that is linked in the `needs` directory, the service will not be started. wants ~~~~~ `Wants` are the 'soft dependencies': cinit will try to start the dependencies found in `wants` before the service, but the service will also be started, indenpendend of success of the dependencies. Circular dependency problem ---------------------------- If you manage to create circular dependencies cinit will fall into an endless loop. Use `cinit.check.config` to verify your configuration. cinit-0.3pre15/doc/user/example-directory-structure.text000066400000000000000000000112661125633325400234750ustar00rootroot00000000000000cinit - Example directory structure =================================== Nico Schottelius 0.1, for cinit 0.3, Initial Version from 2005-12-12 :Author Initials: NS This document describes a tested directory hierarchy that you could adapt for your setup. But this is no need, you are free to design your own layout and/or improve this one. Main idea --------- The main reason for this layout is that all services directly located in /etc/cinit/svc/ would create a not-so-easy maintainable chaos. Categories ---------- When thinking about grouping some parts together, there came some categories to my mind: - init: This must be there. It is no real choice (well, working with profiles is an alternative) - we need to mount things - things that are used to 'configure' my local system - network connectivity - services only locally reachable - services remote reachable - something that let me login With these requirements the following categories (=directories) were created: getty ~~~~~ Gettys are those little and nice programs that allow you to login. As we normally want to have more than one it seems to be senseful to create a category for it. For the creation of the getty services itself, an extremly simply scheme is used: Simply create service