From 2f191c302fed4463b1192d2595184a65411adf25 Mon Sep 17 00:00:00 2001 From: Unit 193 Date: Sun, 22 Apr 2018 15:17:42 -0400 Subject: New upstream version 3.0.07-1 --- LICENSE.txt | 674 ++ README.txt | 376 + inxi | 31942 ++++++++++++++++++++++++++++--------------------------- inxi.1 | 1375 +-- inxi.1.gz | Bin 13303 -> 0 bytes inxi.changelog | 784 ++ 6 files changed, 18635 insertions(+), 16516 deletions(-) create mode 100644 LICENSE.txt create mode 100644 README.txt delete mode 100644 inxi.1.gz diff --git a/LICENSE.txt b/LICENSE.txt new file mode 100644 index 0000000..9cecc1d --- /dev/null +++ b/LICENSE.txt @@ -0,0 +1,674 @@ + 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. + + {one line to give the program's name and a brief idea of what it does.} + Copyright (C) {year} {name of author} + + This program is free software: you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation, either version 3 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program. If not, see . + +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: + + {project} Copyright (C) {year} {fullname} + 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 +. diff --git a/README.txt b/README.txt new file mode 100644 index 0000000..5443b0b --- /dev/null +++ b/README.txt @@ -0,0 +1,376 @@ +README for inxi - a command line system information tool + +The new Perl inxi is now here! File all issue reports with the master +branch. All support for versions prior to 3.0 is now ended, sorry. + +Make sure to update to the current inxi from the master branch before +filing any issue reports. The code in pre 2.9 versions literally no +longer exists in inxi 3. Bugs from earlier versions cannot be solved +in the new version since the pre 2.9 and the 2.9 and later versions +are completely different internally. + +inxi strives to support the widest range of operating systems and +hardware, from the most simple consumer desktops, to the most advanced +professional hardware and servers. + +The issues you post help maintain or expand that support, and are +always appreciated since user data and feedback is what keeps inxi +working and supporting the latest or not so latest hardware and +operating systems. + +See the BSD section below for qualifications re BSDs, and OSX in +particular. + +===================================================================== +MASTER BRANCH: + +This is the only supported branch, and the current latest commit is +the only supported 'release'. There are no 'releases' of inxi beyond +the current commit to master. All past commits are not supported. + +git clone https://github.com/smxi/inxi --branch master --single-branch + +OR direct fast and easy install: +wget -Nc https://github.com/smxi/inxi/raw/master/inxi + +OR easy to remember shortcut (which redirects to github): +wget -Nc https://smxi.org/inxi +wget -Nc smxi.org/inxi + +'Tagging' is purely a formality that certain distros can't figure out +how to do without, that's all. A tag is a pointer to a commit, and has +no further meaning. + +NOTE: Just because github calls tagged commits 'Releases' does not +mean they are releases! I can't change the words on the tag page. +They are tagged commmits, period. I did not want to use tags precisely +to avoid the idea that inxi has any release that exists that is other +than it's current master version, but I decided that it was less pain +to add tags than to argue this point any further. + +===================================================================== +DEVELOPMENT BRANCH: +All active development is now done on the inxi-perl branch (pinxi): + +git clone https://github.com/smxi/inxi --branch inxi-perl --single-branch + +OR direct fast and easy install: +wget -Nc https://github.com/smxi/inxi/raw/inxi-perl/pinxi + +OR easy to remember shortcut (which redirects to github): +wget -Nc https://smxi.org/pinxi +wget -Nc smxi.org/pinxi + +Once new features have been debugged, tested, and are stable, they +will move to the master branch. + +===================================================================== +LEGACY BRANCH: +If you'd like to look at or check out the Gawk/Bash version of inxi, +you can find it here, at the inxi-legacy branch (binxi): + +git clone https://github.com/smxi/inxi --branch inxi-legacy --single-branch + +OR direct fast and easy install: +wget -Nc https://github.com/smxi/inxi/raw/inxi-legacy/binxi + +OR easy to remember shortcut (which redirects to github): +wget -Nc https://smxi.org/binxi + +This version will not be maintained, and it's unlikely that any time +will be spent on it in the future, but it is there in case it's of +use or interest to anyone. + +===================================================================== +SUPPORT INFO: + +Do not ask for basic help that reading the inxi -h / --help menus, or +man page would show you, and do not ask for features to be added that +inxi already has. Also do not ask for support if your distro won't +update its inxi version, some are bad about that. + +DOCUMENTATION: https://smxi.org/docs/inxi.htm +(smxi.org/docs/ is easier to remember, and is one click away from +inxi.htm). The one page wiki on github is only a pointer to the real +resources. + +https://github.com/smxi/inxi/tree/inxi-perl/docs +Contains specific Perl inxi documentation, of interest mostly to +developers. Includes internal inxi tools, values, configuration items. +Also has useful information about Perl version support, including the +list of Core modules that _should_ be included in a distribution's +core modules, but which are unfortunately sometimes removed. + +HTML MAN PAGE: https://smxi.org/docs/inxi-man.htm +INXI OPTIONS PAGE: http://smxi.org/docs/inxi-options.htm +NOTE: These may not always be up to date, but generally track the most +recent inxi commits. + +ISSUES: https://github.com/smxi/inxi/issues +No issues accepted for non current inxi releases. See below for more on +that. Unfortunately as of 2.9, no support or issues can be accepted for +older inxi's because inxi 2.9 (Perl) and newer is a full rewrite, and +legacy inxi is not being supported since our time here on earth is +finite (plus of course, one reason for the rewrite was to never have +to work with Gawk->Bash again!). + +SUPPORT FORUMS: https://techpatterns.com/forums/forum-33.html +This is the best place to place support issues that may be complicated. + +If you are developer, use: +DEVELOPER FORUMS: https://techpatterns.com/forums/forum-32.html + +SOURCE VERSION CONTROL: https://github.com/smxi/inxi +MAIN BRANCH: master +DEVELOPMENT BRANCHES: inxi-perl, one, two +inxi-perl is the dev branch, the others are rarely if ever used. inxi +itself has the built in feature to be able to update itself from +anywhere, including these branches, which is very useful for development +and debugging on various user systems. + +PULL REQUESTS: Please talk to me before starting to work on patches of +any reasonable complexity. inxi is hard to work on, and you have to +understand how it works before submitting patches, unless it's a trivial +bug fix. Please: NEVER even think about looking at or using previous +inxi commits, previous to the current master version, as a base for a +patch. If you do, your patch / pull request will probably be rejected. +Developers, get your version from the inxi-perl branch, pinxi, otherwise +you may not be current to actual development versions. inxi-perl pinxi +is always equal to or ahead of master branch inxi. + +Man page updates, doc page updates, etc, of course, are easy and will +probably be accepted, as long as they are properly formatted and +logically coherent. + +inxi releases early, and releases often, when under development. + +PACKAGERS: inxi has one and only one 'release', and that is the current +commit to master branch (plus pinxi inxi-perl branch, of course, but +those should never be packaged). + +===================================================================== +ABOUT INXI - CORE COMMITMENT TO LONG TERM STABILITY + +inxi is a command line system information tool. It was forked from the +ancient and mindbendingly perverse yet ingenius infobash, by locsmif. + +That was a buggy, impossible to update or maintain piece of software, +so the fork fixed those core issues, and made it flexible enough to +expand the utility of the original ideas. Locmsif has given his thumbs +up to inxi, so don't be fooled by legacy infobash stuff you may see +out there. + +inxi is lower case, except when I create a text header here in a file +like this, but it's always lower case. Sometimes to follow convention +I will use upper case inxi to start a sentence, but i find it a bad +idea since invariably, someone will repeat that and type it in as the +command name, then someone will copy that, and complain that the +command: Inxi doesn't exist... + +The primary purpose of inxi is for support, and sys admin use. inxi +is used widely for forum and IRC support, which is I believe it's most +common function. + +If you are piping output to paste or post (or writing to file), inxi +now automatically turns off color codes, so the old suggestion to +use -c 0 to turn off colors is no longer required. + +inxi should always show you your current system state, as far as +possible, and should be more reliable than your own beliefs about +what is in your system, ideally. In other words, the goal in inxi +is to have it be right more than it is wrong about any system that +it runs on. And not to rely on non current system state data if at +all possible. Some things, like memory/ram data, rely on radically +unreliable system self reporting based on OEM filling out data +correctly, which doesn't often happen, so in those cases, you want to +confirm things like ram capacity with a reputable hardware source, +like crucial.com, which has the best ram hardware tool I know of. + +The core mission of inxi is to always work on all systems all the +time. Well, all systems with the core tools inxi requires to operate +installed. Ie, not Android, yet. What this means is this: you can +have a 10 year old box, or probably 15, not sure, and you can install +today's inxi on it, and it will run. It won't run fast, but it will +run. I test inxi on a 200 MHz laptop from about 1998 to keep it +honest. That's also what was used to optimize the code at some +points, since differences appear as seconds, not 10ths or 100ths +of seconds on old systems like that. + +inxi is being written, and tested, on Perl as old as 5.08, and will +work on any system that runs Perl 5.08 or later. Pre 2.9.0 Gawk/Bash +inxi will also run on any system no matter how old, within reason, +so there should be no difference. + +===================================================================== +BSD SUPPORT + +Real BSDs: +BSD support is not as complete as GNU/Linux support due to the fact +some of the data simply is not available, or is structured in a way +that makes it unique to each BSD. This fragmentation makes supporting +BSDs far more difficult than it should be in the 21st century. The +BSD support in inxi is an ongoing process, with more features being +added as new data sources and types are discovered. + +All BSD issue reports unless trivial and obvious will require 1 of +two things: + +1. a full --debug 21 data dump so I don't have to spend days trying +to get the information I need to resolve the issue file by painful +file from the issue poster. This is only the start of the process, +and realistically requires 2. to complete it. + +2. direct SSH access to at least a comparable live BSD version/system, +that is, if the issue is on a laptop, access has to be granted to the +laptop, or a similar one. + +Option 2 is far preferred because in terms of my finite time on this +planet of ours, the fact is, if I don't have direct (or SSH) access, +I can't get much done, and the little I can get done will take 10 to +1000x longer than it should. That's my time spent (and sadly, with +BSDs, largely lost), not yours. + +I decided I have to adopt this much more strict policy with BSDs +after wasting untold hours on trying to get good BSD support, only +to see that support break a few years down the road as the data inxi +relied in changed structure or syntax, or the tools changed, or +whatever else makes the BSDs such a challenge to support. In the end, +I realized, the only BSDs that are well supported are ones that I have +had direct access to for debugging and testing. + +I will always accept patches that are well done, if they do not break +GNU/Linux, and extend BSD support, or add new BSD features, and follow +the internal inxi logic, and aren't too long. inxi sets initial internal +flags to identify that it is a BSD system vs a GNU/Linux system, and +preloads some data structures for BSD use, so make sure you understand +what inxi is doing before you get into it. + +OSX: +Do not insult real BSDs by calling OSX a BSD. OSX is the least +Unix-like operating system I've ever seen that claims to be a Unix, +its tools are mutated, it's data randomly and non-standardly organized, +and it totally fails to respect the 'spirit' of Unix, even though it +might pass some random tests that certify a system as a 'Unix'. + +If you want me to use my time on OSX features or issues, you have to +pay me, because Apple is all about money, not freedom (that's what +the 'free' in 'free software' is referring to, not cost), and I'm not +donating my finite time in support of non-free operating systems. + +===================================================================== +INXI FEATURES AND FUNCTIONALITY + +inxi's functionality continues to grow over time, but it's also +important to understand that each core new feature usually requires +about 30 days work to get it stable. So new features are not trivial +things, nor is it acceptable to submit a patch that works only on your +personal system. One inxi feature (-s, sensors data), took about +2 hours to get working in the alpha test on the local dev system, but +then to handle the massive chaos that is actual user sensors output +and system variations, it took several rewrites and about 30 days to +get somewhat reliable for about 98% or so of inxi users. So if your +patch is rejected, it's likely because you have not thought it through +adequately, have not done adequate testing cross system and +platform, etc. + +===================================================================== +INXI RELEASE/SUPPORT/ISSUES/BUGS INFORMATION: + +Important: the only version of inxi that is supported is the latest +current master branch release. No issue reports or bug reports will be +accepted for anything other than current master branch. No merges, +attempts to patch old code from old releases, will be considered or +accepted. If you are not updated to the latest inxi, do not file a +bug report since it's probably been fixed ages ago. If your distro +isn't packaging a current inxi, then file a bug report with them, not +here. The only valid working code base for inxi is the current +release of inxi. + +Distributions should never feel any advantage comes from using old +inxi releases because inxi has as a core promise to you, the end user, +that it will NEVER require new tools to run. New tools may be required +for a new feature, but that will always be handled internally by inxi, +and will not cause any operational failures. This is a promise, and I +will never as long as I run this project violate that core inxi +requirement. Old inxi is NOT more stable than current inxi, it's just +old, and lacking in bug fixes and features. For pre 2.9 releases, it's +also significantly slower, and with fewer features. + +inxi is a rolling release codebase, just like Debian Sid, Gentoo, or +Arch Linux are rolling release GNU/Linux distributions, with no +'release points'. + +Your distro not updating inxi ever, then failing to show something +that is fixed in current inxi is not a bug, and please do not post it +here. File the issue with your distro, not here. Updating inxi in a +package pool will NEVER make anything break or fail, period. It has no +version based dependencies, just software, like Perl 5.xx, lspci, etc. +There is never a valid reason to not update inxi in a package pool of +any distro in the world (with one single known exception, the Slackware +based Puppy Linux release, which ships without the full Perl language. +The Debian based one works fine). + +Sys Admin type inxi users always get the first level of support. ie, +convince us you run real systems and networks, and your issue shoots +to the top of the line. As do any real bugs. Failure to supply +requested debugger data will lead to a distinct lack of interest on +our part to help you with a bug. ie, saying, oh, x doesn't work, +doesn't cut it, unless it's obvious why. + +===================================================================== + +INXI VERSION NUMBERING: + +inxi uses 'semantic' version numbering, where the version numbers +actually mean something. + +The version number follows these guidelines: +Using example 3.2.28-6 + +The first digit(s), "3", is a major version, and almost never changes. +Only a huge milestone, or if inxi reaches 3.9.xx, when it will simply +move up to 4.0.0 just to keep it clean, would cause a change. + +The second digit(s), "2", means a new real feature has been added. +Not a tweaked existing feature, an actual new feature, which usually +also has a new argument option letter attached. The second number goes +from 0 to 9, and then rolls over the first after 9. It could also be +adding a very complicated expansion of existing features, like Wayland. +It depends. + +The third, "28", is for everything small, can cover bug fixes, tweaks +to existing features to add support for something, pretty much anything +where you want the end user to know that they are not up to date. The +third goes from 0 to 99, then rolls over the second. + +The fourth, "6", is extra information about certain types of inxi +updates. I don't usually use this last one in master branch, but you +will see it in branches one,two, inxi-perl, inxi-legacy since that is +used to confirm remote test system patch version updates. + +The fourth number, when used, will be alpha-numeric, a common version +would be, in say, branch one: 2.2.28-b1-02, in other words, a branch 1 +release, version 2. + +In the past, now and then the 4th, or 'patch', number, was used in +trunk/master branches of inxi, but I've pretty much stopped doing that +because it's confusing. + +inxi does not use the fiction of date based versioning because that +imparts no useful information to the end user, when you look at say, +2.2.28, and you last had 2.2.11, you can know with some certainty that +inxi has no major new features, just fine tunings and bug fixes. And +if you see one with 2.3.2, you will know that there is a new feature, +almost, but not always, linked to one or more new line output items. +Sometimes a fine tuning can be quite significant, sometimes it's a +one line code fix. + +A move to a new full version number, like the rewrite of inxi to Perl, +would reflect in first version say, 2.9.01, then after a period of +testing, where most little glitches are fixed, a move to 3.0.0. These +almost never happen. I do not expect for example version 4.0 to ever +happen after the 3.0 release of early 2018, unless so many new +features are added that it actually hits 3.9, then it would roll +over to 4. + +### EOF ### diff --git a/inxi b/inxi index f36c6dc..92926b5 100755 --- a/inxi +++ b/inxi @@ -1,697 +1,124 @@ -#!/usr/bin/env bash -######################################################################## -SELF_NAME='inxi' -# don't quote the following, parsers grab these too -SELF_VERSION=2.3.56 -SELF_DATE=2018-01-17 -SELF_PATCH=00 -######################################################################## -#### SPECIAL THANKS -######################################################################## -#### Special thanks to all those in #lsc and #smxi for their tireless -#### dedication helping test inxi modules. -######################################################################## -#### ABOUT INXI -######################################################################## -#### inxi is a fork of infobash 3.02, the original bash sys info tool by locsmif -#### As time permits functionality improvements and recoding will occur. -#### -#### inxi, the universal, portable, system information tool for irc. -#### Tested with Irssi, Xchat, Konversation, BitchX, KSirc, ircII, -#### Gaim/Pidgin, Weechat, KVIrc and Kopete. -#### Original infobash author and copyright holder: -#### Copyright (C) 2005-2007 Michiel de Boer a.k.a. locsmif -#### inxi version: Copyright (C) 2008-2018 Harald Hope -#### Additional features (C) Scott Rogers - kde, cpu info -#### Further fixes (listed as known): Horst Tritremmel -#### Steven Barrett (aka: damentz) - usb audio patch; swap percent used patch -#### Jarett.Stevens - dmidecde -M patch for older systems with the /sys -#### -#### Current project home page/wiki/git: https://github.com/smxi/inxi -#### Documentation/wiki pages can be found at https://smxi.org/docs/inxi.htm -#### Project forums: http://techpatterns.com/forums/forum-33.html -#### IRC support: irc.oftc.net channel #smxi -#### Version control: -#### * https://github.com/smxi/inxi -#### * git: git pull https://github.com/smxi/inxi master -#### * For basic version, no gz files, much smaller, do: -#### git clone https://github.com/smxi/inxi --branch master-plain --single-branch -#### * source repository url: https://github.com/smxi/inxi -#### -#### 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 . -#### -#### If you don't understand what Free Software is, please read (or reread) -#### this page: http://www.gnu.org/philosophy/free-sw.html -#### -#### But the main thing about Free Software is that its' about the freedom -#### of the individual user, not the corporations that try to coopt it. This -#### grows easy to forget when people confuse freedom with open source. -######################################################################## -#### -#### PACKAGE NAME NOTES -#### * Package names in (...) are the Debian Squeeze package name. Check your -#### distro for proper package name by doing this: which -#### then find what package owns that application file. Or run --recommends -#### which shows package names for Debian/Ubuntu, Arch, and Fedora/Redhat/Suse -#### -#### DEPENDENCIES -#### * bash >=3.0 (bash); df, readlink, stty, tr, uname, wc (coreutils); -#### gawk (gawk); grep (grep); lspci (pciutils); ps; find (findutils); -#### perl (Modules: [HTTP::Tiny IF NO wget/curl/fetch/ftp]; Net::FTP; File::Find); -#### * Also the proc filesystem should be present and mounted for Linux -#### * Some features, like -M and -d will not work, or will work incompletely, -#### if /sys is missing -#### -#### Apparently unpatched bash 3.0 has arrays broken; bug reports: -#### http://ftp.gnu.org/gnu/bash/bash-3.0-patches/bash30-008 -#### http://lists.gnu.org/archive/html/bug-bash/2004-08/msg00144.html -#### Bash 3.1 for proper array use -#### -#### Arrays work in bash 2.05b, but "grep -Em" does not -#### -#### RECOMMENDS (Needed to run certain features, listed by option) -#### -A - for output of usb audio information: lsusb (usbutils) -#### -Ax -Nx - for audio/network module version: modinfo (module-init-tools) -#### -Dx - for hdd temp output (root only default): hddtemp (hddtemp) -#### For user level hdd temp output: sudo (sudo) -#### Note: requires user action for this feature to run as user (edit /etc/sudoers file) -#### -G - full graphics output requires: glxinfo (mesa-utils); xdpyinfo (X11-utils); -#### xrandr (x11-xserver-utils) -#### -i - IP information, local/wan - ip (iproute) legacy, not used if ip present: ifconfig (net-tools) -#### -I - uptime (procps, check Debian if changed) -#### -Ix - view current runlevel while not in X window system (or with -x): runlevel (sysvinit) -#### -m - all systems, dmidecode, unless someone can find a better way. -#### -M - for older systems whose kernel does not have /sys data for machine, dmidecode (dmidecode) -#### -o - for unmounted file system information in unmounted drives (root only default): file (file) -#### Note: requires user action for this feature to run as user (edit /etc/sudoers file) -#### For user level unmounted file system type output: sudo (sudo) -#### -s For any sensors output, fan, temp, etc: sensors (lm-sensors) -#### Note: requires setup of lm-sensors (sensors-detect and adding modules/modprobe/reboot, -#### and ideally, pwmconfig) prior to full output being available. -#### -S For desktop environment, user must be in X and have xprop installed (in X11-utils) -#### -xx@14 - it really helps to have 'tree' installed on Linux systems with /sys for -#### debugger data collection, that creates a very useful map of /sys. -######################################################################## -#### BSD Adjustments -#### * sed -i '' form supported by using SED_I="-i ''". -#### * Note: New BSD sed supports using -r instead of -E for compatibility with gnu sed -#### However, older, like FreeBSD 7.x, does not have -r so using SED_RX='-E' for this. -#### * Gnu grep options can be used if the function component is only run in linux -#### These are the options that bsd grep does not support that inxi uses: -m -o -#### so make sure if you use those to have them in gnu/linux only sections. -#### It appears that freebsd uses gnu grep but openbsd uses bsd grep, however. -#### * BSD ps does not support --without-headers option, and also does not support --sort