move website out to its own repo

LICENSE

@@ -0,0 +1,661 @@
+                    GNU AFFERO GENERAL PUBLIC LICENSE
+                       Version 3, 19 November 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU Affero General Public License is a free, copyleft license for
+software and other kinds of works, specifically designed to ensure
+cooperation with the community in the case of network server software.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+our General Public Licenses are 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.
+
+  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.
+
+  Developers that use our General Public Licenses protect your rights
+with two steps: (1) assert copyright on the software, and (2) offer
+you this License which gives you legal permission to copy, distribute
+and/or modify the software.
+
+  A secondary benefit of defending all users' freedom is that
+improvements made in alternate versions of the program, if they
+receive widespread use, become available for other developers to
+incorporate.  Many developers of free software are heartened and
+encouraged by the resulting cooperation.  However, in the case of
+software used on network servers, this result may fail to come about.
+The GNU General Public License permits making a modified version and
+letting the public access it on a server without ever releasing its
+source code to the public.
+
+  The GNU Affero General Public License is designed specifically to
+ensure that, in such cases, the modified source code becomes available
+to the community.  It requires the operator of a network server to
+provide the source code of the modified version running there to the
+users of that server.  Therefore, public use of a modified version, on
+a publicly accessible server, gives the public access to the source
+code of the modified version.
+
+  An older license, called the Affero General Public License and
+published by Affero, was designed to accomplish similar goals.  This is
+a different license, not a version of the Affero GPL, but Affero has
+released a new version of the Affero GPL which permits relicensing under
+this license.
+
+  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 Affero 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. Remote Network Interaction; Use with the GNU General Public License.
+
+  Notwithstanding any other provision of this License, if you modify the
+Program, your modified version must prominently offer all users
+interacting with it remotely through a computer network (if your version
+supports such interaction) an opportunity to receive the Corresponding
+Source of your version by providing access to the Corresponding Source
+from a network server at no charge, through some standard or customary
+means of facilitating copying of software.  This Corresponding Source
+shall include the Corresponding Source for any work covered by version 3
+of the GNU General Public License that is incorporated pursuant to the
+following paragraph.
+
+  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 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 work with which it is combined will remain governed by version
+3 of the GNU General Public License.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU Affero 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 Affero 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 Affero 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 Affero General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU Affero 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 Affero General Public License for more details.
+
+    You should have received a copy of the GNU Affero General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If your software can interact with users remotely through a computer
+network, you should also make sure that it provides a way for users to
+get its source.  For example, if your program is a web application, its
+interface could display a "Source" link that leads users to an archive
+of the code.  There are many ways you could offer source, and different
+solutions will be better for different programs; see section 13 for the
+specific requirements.
+
+  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 AGPL, see
+<https://www.gnu.org/licenses/>.

Makefile

@@ -7,19 +7,22 @@ SHELL := sh
 KAMA ?= ../kama
 PKGS ?= ../kama-packages
 
-.PHONY: iso install recipe-check clean
+.PHONY: rootfs install live-init recipe-check clean
 
-iso:
+rootfs:
 	sh scripts/build-root.sh
-	sh iso/build-iso.sh
 
 install:
 	sh installer/install.sh
 
+# syntax-check the live init (what boots you into the installer)
+live-init:
+	sh -n live/init && echo "OK  live/init"
+
 recipe-check:
 	@for f in $(PKGS)/*.sh; do \
 		sh -n "$$f" && echo "OK  $$f" || echo "FAIL $$f"; \
 	done
 
 clean:
-	rm -rf iso/work /tmp/keru
+	rm -rf /tmp/keru

README.md

@@ -1,11 +1,12 @@
-# Keru OS
+# Keru OS <sub>ける</sub>
 
 An independent, source-only Linux distribution built around one idea: you
-don't install a system, you *craft* one.
+don't install a system, you *craft* one — **ける・けいとうてき** (keru keitō-teki): a
+system assembled the way you want it.
 
-This repository holds the **operating system itself** — the installer, the ISO
+This repository is the **operating system itself** — the installer, the
-build tooling, the profile system, and the build pipeline. The two things Keru
+profile system, and the build pipeline. The two things Keru leans on live in
-depends on live in their own repositories:
+their own homes:
 
 - **[kama](https://github.com/AstralZX/kama)** — the package manager (a shell script)
 - **[kama-packages](https://github.com/AstralZX/kama-packages)** — the recipe repository
@@ -15,61 +16,62 @@ depends on live in their own repositories:
 Every package on Keru is built from source by **Kama**, a deliberately small
 package manager that simply runs the commands in each recipe. No binary
 packages, no opaque package machinery. The whole system — toolchain included —
-is compiled from original source, and the install image is assembled by hand
+is compiled from original source. What you run, you built.
-rather than with a stock tool like archiso.
 
-Runit handles services. The standard Linux kernel drives the hardware.
+Nothing is fixed. Nothing you didn't ask for is forced on you.
-`nmtui` manages networking. Nothing you didn't ask for ends up on the disk.
 
-## The differentiator: craft your system at install time
+Read the full **philosophy** in [docs/PHILOSOPHY.md](docs/PHILOSOPHY.md).
+
+## The differentiator: everything is swappable
 
 Keru's installer is a TUI that walks you through designing your exact machine
-*before* it ever boots:
+*before* it ever boots. Every major component is selectable:
 
-- **init system** — Runit (default), s6, OpenRC, systemd
+- **init system** — Runit (default), s6, OpenRC, systemd, busybox init, and more
-- **C library** — glibc or musl
+- **C library** — glibc, musl, uClibc-ng, and more
-- **filesystem** — ext4, btrfs, xfs, zfs, f2fs
+- **filesystem** — ext4, btrfs, xfs, zfs, f2fs, jfs, reiserfs, swap, and more
-- **kernel** — linux, linux-lts, linux-hardened
+- **kernel** — linux, linux-lts, linux-hardened, linux-cachyos, and more
+- **privilege elevation** — doas, sudo, opendoas, su
+- **kernel parameters, locale, clock, keymap** — all configurable
 
-Swappable at install time, fixed at first boot. The system that lands on your
+Every init, every libc, every filesystem, everything. The selections are made
-disk is precisely the one you chose.
+during install and fixed at first boot. The system that lands on your disk is
+precisely the one you chose.
+
+Keru is stable on the combinations it offers you. If you push past what's
+proven — an untested libc/init pair, an unmaintained filesystem — the
+installer **warns** you the combination is unstable, then gets out of your way.
+You're never blocked, only told the truth.
+
+## How installation works
+
+The ISO carries **only the installer** — nothing else. There is no prebuilt
+base image on the disk. Boot it and the live init (`live/init`) starts the
+installer immediately — no shell prompt, you just make your choices and it
+builds. The installer connects to the network, then fetches and builds
+whatever you selected (init system, kernel, libc, filesystem tooling, and
+tools) on the fly.
+
+A working **network connection is therefore a hard requirement** for
+installing Keru. The installer checks connectivity and offers in-installer
+network setup (wireless via `nmtui`/`wifi-menu`, or Ethernet/DHCP) before the
+build begins.
 
 ## Repository layout
 
 ```
-installer/     TUI installer — writes make.conf from your choices
+installer/     TUI installer — auto-starts on boot, writes make.conf from your choices
-iso/           from-scratch ISO build tooling (xorriso + squashfs + syslinux)
 profile/       make.conf template (the swappables + build flags)
 scripts/       build pipeline: build-root, mkfs-root, common helpers
-docs/          design docs + the recipe format spec
+live/          live-ISO init — boots straight into the installer
+docs/          philosophy + design docs + the recipe format spec
 ```
 
-## Building
+## Release
 
-The three repos should sit next to each other (or point at each other via
+Keru OS is currently in development. The first installable release, **0.1**,
-`KAMA_DIR` / `PKGS_DIR` / `PKGDIR`):
+will ship as a bootable ISO — no source builds, no manual tooling required.
-
+It will be made available here when it's ready.
-```
-~/dev/
-├── KeruOS/
-├── kama/
-└── kama-packages/
-```
-
-Then, from `KeruOS/`:
-
-```sh
-make install       # run the TUI installer
-# or, headlessly:
-sh scripts/build-root.sh            # build a rootfs into /tmp/keru/root
-make iso                            # assemble an install image
-```
-
-Requires the sibling `kama` and `kama-packages` repos to be present.
-
-## Status
-
-Design + scaffolding. Nothing is building end-to-end yet.
 
 ## License
 

docs/DESIGN.md

@@ -1,19 +0,0 @@
-# design/index
-
-This directory holds the working design for Keru OS. The code is scaffolding
-and not yet functional end-to-end.
-
-## What exists
-
-- `recipe-format.md` — the Kama recipe format (easy/advanced tiers)
-- `README.md` (repo root) — project identity + layout
-
-## Open design questions
-
-- **Bootstrapping toolchain**: chicken-and-egg — the first compiler must be
-  obtained somehow. Options: a documented one-time bootstrap from a binary
-  seed, or a multi-stage rebuild (host -> minimal -> full). Not yet decided.
-- **No dependency resolver**: how upgrades/rebuilds are handled for a system
-  that's "built once at install." Currently framed as install-time-only.
-- **Cache artifacts vs. rebuilds**: whether the build cache stores binaries
-  for fast re-install or always recompiles.

docs/PHILOSOPHY.md

@@ -0,0 +1,109 @@
+# Keru OS — Philosophy
+
+Keru is a source-only Linux distribution built on one governing principle:
+
+> **The OS is a choice, not a conclusion.**
+
+Most distros ship a decision someone else already made for you — a default
+init, a default libc, a default filesystem. You inherit it and live with it.
+Keru refuses that premise. Every foundational component is a *variable you
+resolve at install time*, not a fixed value baked into the distribution.
+Every init, every libc, every filesystem, every kernel, every
+privilege-elevation tool — all selectable, none forced.
+
+## Anti-opinionated, not opinionated
+
+Keru is not opinionated. It is **anti-opinionated**. An opinionated distro
+picks a stack and defends it — *"you get s6 and XFS whether you like it or
+not."* Keru is the direct rejection of that. It holds **no opinion** about
+which init, libc, filesystem, or daemon you should run, because that decision
+belongs to you, not to the distribution.
+
+The distro's only opinion is that you have to form one. After that, it shuts
+up and builds exactly what you chose.
+
+## Only what you asked for
+
+The install medium carries **nothing but the installer**. There is no prebuilt
+base image, no hidden bloat, no background assumptions. You pick your system,
+Keru fetches it and compiles it from source, and the disk reflects exactly
+that and nothing more. What gets built is defined by what you chose — not by
+what maintainers decided you should have.
+
+## Control without complexity
+
+This is the deliberate bet, and the thing that separates Keru from a
+Gentoo-skin. The package manager, **Kama**, is a shell script. It reads a
+`make.conf` and runs recipe commands. No dependency solver. No package
+database. No compiled manager machinery.
+
+> "Sure, the package manager is in shell, and that compromises performance —
+> but it's still faster than many package managers people actually use, and
+> the real cost of a build is the compiler, not the meta-machinery around it."
+
+The dependency model is AUR-style ephemeral: build tools are fetched,
+compiled, and removed once they've served, so they never accumulate. The
+richness lives in the recipes and the profile, not in the machinery. Keru is
+the position that package managers became more complex than the packages they
+manage, and that the simple version is the right one.
+
+> "A package manager doesn't need a resolver to be honest. It needs to be
+> legible — you can read every decision it makes, because every decision is a
+> script or a line in make.conf you can see and change."
+
+## Squared with reality
+
+Building every init, every libc, every filesystem from source at install time
+requires a working network connection, and the installer is honest about that:
+connectivity is a hard gate, and network setup happens inside the installer.
+This is what makes "everything is swappable" real rather than aspirational.
+The power to choose anything comes from the fact that nothing is prebuilt —
+you fetch exactly the parts you picked.
+
+> "You give up the convenience of a prebuilt system so the system you get is
+> exactly the one you designed. Speed-to-install is traded for
+> fit-to-request. If you want fast and prebaked, a binary distro is right
+> there. If you want your machine, this is the one."
+
+## Stability: guaranteed on what's offered, never enforced on you
+
+Keru's promise is that **the system won't break** — but honestly scoped: it
+won't break **on the combinations it offers you**. That is what the installer
+means by offering a choice: each option in `install.sh` is one Keru has proven
+builds and boots. The offered set is curated *so that* it doesn't break.
+
+Choice multiplies the test surface — six inits, four libcs, seven filesystems,
+five kernels, and so on produce over a thousand possible systems. Guaranteeing
+every one of them is only honest if it's *enforced by curation*: Keru offers
+what works.
+
+But the user is never locked out of going further. If you pick something that
+isn't yet proven — a libc and init never tested together, an unmaintained
+filesystem, an exotic kernel pair — Keru does **not** stop you. It **warns
+you** the combination is unstable and lets you proceed.
+
+> "Stability is a guarantee about what we offer, not a jail around the edge of
+> it. If you want to push into the unproven, we tell you the truth and get out
+> of your way."
+
+So the full definition, in one line:
+
+> **The system won't break for any choice Keru offers you; for anything beyond
+> that, Keru warns and steps aside — you stay in control, never blocked.**
+
+## Agreement on choice, not agreement on opinion
+
+The through-line across Keru's lineage is clear: TOML packages, then a
+50-line build DSL, then plain shell. And from *opinionated dogma* — "you get
+s6 and XFS whether you like it or not" — to *anti-opinionated anything-goes*.
+Keru keeps the from-scratch purity while rejecting the fixed dogmas outright.
+
+> "We don't tell you which init to worship or which filesystem to trust. We
+> tell you that you have to choose — and then we build exactly that."
+
+The philosophy in one line:
+
+> **A system should be exactly what you chose it to be — selected at install,
+> built from source, nothing forced and nothing you didn't ask for.**
+
+And in two words: **anti-opinionated by design.**

installer/install.sh

@@ -1,70 +1,126 @@
 #!/usr/bin/env sh
-# keru-install — the Keru OS TUI installer
+# keru-install — Keru OS installer. Runs from the live ISO, walks you
-#
+# through your choices, writes make.conf, then builds your system.
-# Walks you through crafting your exact system, then writes make.conf and
-# kicks off the build. Everything is swappable here, at install time, and
-# locked in when you boot.
-#
-# Designed to run from the Keru live ISO. Backed by dialog/whiptail if
-# present; falls back to plain prompted input. All shell, no magic.
 
 set -eu
 
 . "$(dirname "$0")/../scripts/common.sh"
 
-# ---- defaults (mirror profile/make.conf) --------------------------------
 OUT="${MAKE_CONF_OUT:-/tmp/keru/make.conf}"
-DROP="/tmp/keru"
+mkdir -p /tmp/keru
-mkdir -p "$DROP"
 
-# ---- menu helpers -------------------------------------------------------
+# show a menu of options, remember the pick in $CHOICE
-pick() { # prompt, array-of-labels, defaults -> writes choice to $CHOICE
+pick() {
-    local prompt="$1"; shift
+    prompt="$1"; shift
-    local default="$1"; shift
+    default="$1"; shift
     CHOICE="$default"
-    if command -v dialog >/dev/null 2>&1; then
-        local args=()
-        local i=0
-        for opt in "$@"; do
-            args+=("$i" "$opt")
-            i=$((i+1))
-        done
-        local sel
-        sel=$(dialog --stdout --no-cancel --menu "$prompt" 15 60 8 \
-                  --default-item "$default" "${args[@]}") || true
-        CHOICE=$(eval "printf '%s' \"\${$((sel+1)):-\$default}\"" 2>/dev/null || printf '%s' "$default")
-    else
     printf '%s\n' "== $prompt =="
-        local n=1
+    n=0
     for opt in "$@"; do
-            printf '  %s) %s\n' "$n" "$opt"
         n=$((n+1))
+        printf '  %s) %s\n' "$n" "$opt"
     done
     printf 'Select [%s]: ' "$default"
     read -r sel
-        [ -n "$sel" ] && CHOICE=$(eval "printf '%s' \"\${$sel}\"") || CHOICE="$default"
+    case "$sel" in
+        ''|*[!0-9]*) CHOICE="$default" ;;
+        *)
+            if [ "$sel" -ge 1 ] && [ "$sel" -le "$n" ]; then
+                i=0
+                for opt in "$@"; do
+                    i=$((i+1))
+                    [ "$i" -eq "$sel" ] && { CHOICE="$opt"; break; }
+                done
+            else
+                CHOICE="$default"
+            fi
+            ;;
+    esac
+}
+
+require_network() {
+    ok=0
+    for host in 1.1.1.1 github.com; do
+        if command -v ping >/dev/null 2>&1 && ping -c1 -W2 "$host" >/dev/null 2>&1; then
+            ok=1; break
+        fi
+    done
+    if [ "$ok" = "0" ]; then
+        if command -v nc >/dev/null 2>&1 && nc -z -w5 github.com 443 >/dev/null 2>&1; then
+            ok=1
+        elif [ -e /dev/tcp ] && (exec 3<>/dev/tcp/github.com/443) >/dev/null 2>&1; then
+            ok=1
+        fi
+    fi
+    [ "$ok" = "1" ]
+}
+
+configure_network() {
+    if command -v nmtui >/dev/null 2>&1; then
+        nmtui >/dev/null 2>&1
+    else
+        warn "nmtui not available — bring up the network yourself, then continue"
     fi
 }
 
-# ---- swappable selections ------------------------------------------------
+banner "Keru OS — network required"
+info "the ISO only carries the installer."
+info "the system you choose (init, libc, fs, kernel, tools) is fetched and"
+info "built from the network during installation. a connection is required."
+
+while ! require_network; do
+    warn "network: not connected"
+    read -r -p "Connect to the network now (runs nmtui)? [Y/n] " cfg
+    case "$cfg" in
+        n|N|no) die "a network connection is required to install Keru" ;;
+        *) configure_network ;;
+    esac
+done
+msg "network: connected"
+
 banner "Keru OS — craft your system"
 
-pick "Init system" runit  runit s6 openrc systemd
+pick "Init system" runit  runit s6 openrc systemd busybox-init sysvinit dinit shepherd
 INIT="$CHOICE"
 
-pick "C library" glibc glibc musl
+pick "C library" glibc glibc musl uclibc-ng
 LIBC="$CHOICE"
 
-pick "Filesystem" ext4 ext4 btrfs xfs zfs f2fs
+pick "Filesystem" ext4 ext4 ext2 ext3 btrfs xfs zfs f2fs jfs reiserfs
 TARGET_FS="$CHOICE"
 
-pick "Kernel" linux linux linux-lts linux-hardened
+pick "Kernel" linux linux linux-lts linux-hardened linux-cachyos linux-zen
 KERNEL="$CHOICE"
 
-pick "Network tools" nmtui networkmanager nmtui connman
+pick "Privilege elevation (sudo alternative)" doas doas sudo opendoas su
+SUDO="$CHOICE"
+
+pick "Network tools" nmtui nmtui networkmanager connman systemd-networkd
 NET="$CHOICE"
 
-# ---- assemble make.conf ------------------------------------------------
+warn_unstable() {
+    unstable=0
+    case "$LIBC:$INIT" in
+        uclibc-ng:*|musl:systemd)
+            warn "$LIBC + $INIT: not yet proven to build and boot together"
+            unstable=1 ;;
+    esac
+    case "$LIBC:$KERNEL" in
+        musl:linux-zen|uclibc-ng:*)
+            warn "$LIBC + $KERNEL: not yet proven to build and boot together"
+            unstable=1 ;;
+    esac
+    case "$TARGET_FS" in
+        zfs) warn "zfs + $LIBC: needs kernel module + ZFS userspace, not yet proven"
+             unstable=1 ;;
+        reiserfs) warn "reiserfs is unmaintained and has no stable future"
+               unstable=1 ;;
+    esac
+    [ "$unstable" = "1" ] && warn "this combination is unstable. Keru won't stop you — build at your own risk."
+}
+
+warn_unstable
+
 msg "writing $OUT"
 cat > "$OUT" <<EOF
 # Generated by keru-install — hand-tune then rebuild if you like.
@@ -72,6 +128,7 @@ INIT=$INIT
 LIBC=$LIBC
 TARGET_FS=$TARGET_FS
 KERNEL=$KERNEL
+SUDO=$SUDO
 NET=$NET
 LICENSE_ACCEPT=(*)
 EOF

iso/build-iso.sh

@@ -1,51 +0,0 @@
-#!/usr/bin/env sh
-# build-iso.sh — assemble a Keru OS ISO from the built rootfs and kernel
-#
-# From-scratch approach (no archiso): we lay out the classic isohybrid
-# structure manually, squash the rootfs, and generate the ISO with xorriso +
-# isolinux/syslinux (or syslinux's isohybrid). This is the LFS/Debian-live
-# style path.
-#
-# Requires on the build host: xorriso, squashfs-tools, syslinux/isolinux.
-
-set -eu
-. "$(dirname "$0")/common.sh"
-
-ROOT="${ROOT:-/tmp/keru/root}"       # target rootfs (from make.conf)
-ISO_OUT="${ISO_OUT:-$KERU_ROOT/iso/keru-$(date +%Y%m%d).iso}"
-WORK="$KERU_ROOT/iso/work"
-ISOIMG="$WORK/isolinux"
-
-info "building Keru ISO -> $ISO_OUT"
-[ -d "$ROOT" ] || die "rootfs not found at $ROOT (run build-root.sh first)"
-
-have xorriso || die "xorriso not installed"
-have mksquashfs || die "squashfs-tools not installed"
-
-rm -rf "$WORK"; mkdir -p "$ISOIMG"
-info "generating isolinux config"
-cp /usr/lib/syslinux/bios/isolinux.bin "$ISOIMG/" || true
-cp /usr/lib/syslinux/bios/ldlinux.c32 "$ISOIMG/" || true
-cat > "$ISOIMG/isolinux.cfg" <<'EOF'
-UI vesamenu.c32
-DEFAULT keru
-LABEL keru
-    LINUX /boot/vmlinuz-keru
-    INITRD /boot/initramfs-keru.img
-    APPEND root=live:LABEL=KERU_LIVE toram quiet
-EOF
-
-info "packing rootfs into squashfs"
-mksquashfs "$ROOT" "$WORK/keru.sfs" -noappend -comp xz
-
-info "writing ISO (isohybrid)"
-xorriso -as mkisofs \
-    -o "$ISO_OUT" \
-    -V KERU_LIVE \
-    -b isolinux/isolinux.bin \
-    -c isolinux/boot.cat \
-    -no-emul-boot -boot-load-size 4 -boot-info-table \
-    -isohybrid-mbr /usr/lib/syslinux/bios/isohdpfx.bin \
-    "$WORK"
-
-info "done: $ISO_OUT"

live/init

@@ -0,0 +1,61 @@
+#!/bin/sh
+# Keru live ISO init — jumps straight into the installer.
+#
+# The live ISO carries only the installer. On boot this script:
+#   1. mounts the virtual filesystems
+#   2. attaches the read-only installer root (squashfs, plain initramfs, or
+#      an unattached block device)
+#   3. execs installer/install.sh on the console — so you boot, choose, and it
+#      crafts and installs the system. No shell prompt in the way.
+#   4. if the installer exits (e.g. you declined to build), drops to an
+#      emergency shell instead of leaving you stranded.
+#
+# Ultra-minimal by design: /bin/sh is busybox. No init system in the live env.
+
+# ---- console -----------------------------------------------------------
+# Redirect the console early so messages land where you can see them.
+CONSOLE="${console:-/dev/tty1}"
+exec <"$CONSOLE" >"$CONSOLE" 2>"$CONSOLE"
+
+# ---- virtual filesystems ----------------------------------------------
+mount -t proc     proc /proc 2>/dev/null
+mount -t sysfs    sys  /sys  2>/dev/null
+mount -t devtmpfs dev  /dev  2>/dev/null || (mkdir -p /dev && mount -t tmpfs dev /dev 2>/dev/null)
+mkdir -p /dev/pts /dev/shm
+mount -t devpts   devpts /dev/pts 2>/dev/null
+mount -t tmpfs    tmpfs  /dev/shm  2>/dev/null
+
+# ---- locate the installer root ----------------------------------------
+# Where the installer payload lives. Tried in order:
+#   1. $root — whatever the kernel booted (a squashfs / overlay already handled
+#      by an initramfs that then hands off here).
+#   2. a squashfs node named *.sfs on a known device (label=KERU).
+#   3. nothing — the installer is already on the root we're running from.
+case "${root:-}" in
+    /dev/*)
+        # re-mount as the boot-time root: cannot pivot here, so use it directly
+        /bin/busybox mount -o move / "$root" 2>/dev/null || true
+        ;;
+    '')
+        for _dev in /dev/disk/by-label/KERU*; do
+            [ -e "$_dev" ] || continue
+            _node="$(readlink -f "$_dev")"
+            mount "$_node" /squash 2>/dev/null || continue
+            INSTALLER=/squash
+            break
+        done
+        ;;
+esac
+INSTALLER="${INSTALLER:-/}"
+
+# ---- launch the installer ---------------------------------------------
+if [ -e "$INSTALLER/installer/install.sh" ]; then
+    printf '\n[ keru ] booting installer...\n'
+    cd "$INSTALLER" && exec /bin/sh "$INSTALLER/installer/install.sh"
+fi
+
+# If we land here the installer is missing or returned. Never strand someone:
+# fall back to an interactive rescue shell.
+printf '\n[ keru ] installer not found or exited.\n'
+printf '[ keru ] dropping to an emergency shell. (installer path: %s)\n' "$INSTALLER"
+exec /bin/sh

profile/make.conf

@@ -9,23 +9,28 @@
 ## ---------------------------------------------------------------------------
 
 # Which init system gets installed
-#   runit  (default) | s6 | openrc | systemd
+#   runit (default) | s6 | openrc | systemd | busybox-init | sysvinit | dinit | shepherd
 INIT=runit
 
 # Which libc the toolchain and packages build against
-#   glibc (default) | musl
+#   glibc (default) | musl | uclibc-ng
 LIBC=glibc
 
 # Which filesystem the target root is formatted as
-#   ext4 (default) | btrfs | xfs | zfs | f2fs
+#   ext4 (default) | ext2 | ext3 | btrfs | xfs | zfs | f2fs | jfs | reiserfs | swap
 TARGET_FS=ext4
 
 # Which kernel you want built
-#   linux (sane default) | linux-lts | linux-hardened
+#   linux (default) | linux-lts | linux-hardened | linux-cachyos | linux-zen
 KERNEL=linux
 
+# Which privilege-elevation tool gets installed
+#   doas (default) | sudo | opendoas | su
+SUDO=doas
+
 # Base package set pulled into every install
-BASE_PACKAGES=(base toolchain kernel runit nmtui openssh)
+# (kernel, init, sudo, and net are selected separately below)
+BASE_PACKAGES=(base toolchain openssh)
 
 # Locale / clock / keymap applied to the target
 LOCALE=en_US.UTF-8
@@ -46,8 +51,8 @@ LDFLAGS="-s"
 JOBS=$(nproc)
 MAKEFLAGS="-j$JOBS"
 
-# Mirrors for source tarballs
+# Mirror for source tarballs (unset: fetch straight from upstream)
-SOURCE_MIRROR="https://mirror.keru.org/sources"
+# SOURCE_MIRROR="https://mirror.example.org/sources"
 
 # Where the new target root lives on the build host
 ROOT=/tmp/keru/root

scripts/build-root.sh

@@ -23,7 +23,7 @@ KAMA="$KAMA_DIR/kama"
 [ -d "$PKGS_DIR" ] || die "kama-packages repo not found at $PKGS_DIR (set PKGS_DIR)"
 
 info "building Keru rootfs into $ROOT"
-info "profile: init=$INIT libc=$LIBC fs=$TARGET_FS kernel=$KERNEL"
+info "profile: init=$INIT libc=$LIBC fs=$TARGET_FS kernel=$KERNEL sudo=$SUDO"
 
 # stage 0 — bootstrap toolchain
 info "stage 0: bootstrap toolchain (gcc binutils glibc/musl)"
@@ -38,9 +38,11 @@ for p in "${BASE_PACKAGES[@]}"; do
 done
 
 # stage 2 — kernel + init + swappables
-info "stage 2: kernel + init"
+info "stage 2: kernel + init + sudo + net"
 PKGDIR="$PKGS_DIR" "$KAMA" make "$KERNEL" || die "kernel build failed"
 PKGDIR="$PKGS_DIR" "$KAMA" make "$INIT"   || die "init build failed ($INIT)"
+PKGDIR="$PKGS_DIR" "$KAMA" make "$SUDO"   || die "sudo tool build failed ($SUDO)"
+PKGDIR="$PKGS_DIR" "$KAMA" make "$NET"    || die "net tool build failed ($NET)"
 
 # stage 3 — fstab/mkinitramfs for the chosen FS
 info "stage 3: finalize $TARGET_FS root"

scripts/common.sh

@@ -1,4 +1,4 @@
-# common.sh — shared helpers for Keru scripts (installer, iso, kama)
+# common.sh — shared helpers for Keru scripts (installer, build pipeline)
 PREFIX="\033[1;35m[ keru ]\033[0m"
 msg()  { printf '%b %s\n' "$PREFIX" "$*"; }
 info() { printf '%b \033[1;34m==>\033[0m %s\n' "$PREFIX" "$*"; }