</p>
<ol>
<li><strong class="strong">2024 and earlier</strong>: <a href="documents/checksum/kevin_day/2017/kevin_day-76E903396DAD0A83.public" class="link download">Kevin Day 76E903396DAD0A83</a> (<a href="documents/checksum/kevin_day/2017/kevin_day-76E903396DAD0A83.public.sha256" class="link download">SHA256</a>) (<a href="documents/checksum/kevin_day/2017/kevin_day-76E903396DAD0A83.public.asc" class="link download">GPG</a>).</li>
- <li><strong class="strong">2023 and later</strong>: <a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public" class="link download">Kevin Day 02E939B8F7EFE597</a> (<a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public.sha256" class="link download">SHA256</a>) (<a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public.asc" class="link download">GPG</a>).</li>
+ <li><strong class="strong">2023 to 2024</strong>: <a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public" class="link download">Kevin Day 02E939B8F7EFE597</a> (<a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public.sha256" class="link download">SHA256</a>) (<a href="documents/checksum/kevin_day/2023/kevin_day-02E939B8F7EFE597.public.asc" class="link download">GPG</a>).</li>
+ <li><strong class="strong">2023 to 2027</strong>: <a href="documents/checksum/kevin_day/2025/kevin_day-02E939B8F7EFE597.public" class="link download">Kevin Day 02E939B8F7EFE597</a> (<a href="documents/checksum/kevin_day/2025/kevin_day-02E939B8F7EFE597.public.sha256" class="link download">SHA256</a>) (<a href="documents/checksum/kevin_day/2025/kevin_day-02E939B8F7EFE597.public.asc" class="link download">GPG</a>).</li>
</ol>
<p class="p">
The key identified by <strong class="strong">76E903396DAD0A83</strong> is authenticated via the key identified by <strong class="strong">02E939B8F7EFE597</strong>.
This also utilizes older and less trusted algorithms.
</p>
<p class="p">
- The key identified by <strong class="strong">02E939B8F7EFE597</strong> is authenticated via the key identified by <strong class="strong">76E903396DAD0A83</strong>.
+ The key identified by <strong class="strong">02E939B8F7EFE597</strong> for the <strong class="strong">2023 to 2024</strong> year range is authenticated via the key identified by <strong class="strong">76E903396DAD0A83</strong>.
This key has been created near the start of 2023 and will be used until such time a replacement comes about.
This follows the newer practice of signing using subkeys, making the master key unavailable.
- This key utilizes newer algorithms.
+ This key utilizes algorithms available as of 2024.
+ </p>
+ <p class="p">
+ The key identified by <strong class="strong">02E939B8F7EFE597</strong> for the <strong class="strong">2023 to 2027</strong> year range is authenticated via its own key.
+ This key has is the same as the <strong class="strong">2023 to 2024</strong>, but has the year extended.
</p>
<p class="p">
These public keys should be downloaded imported into your own key chain to perform integrity checking and authentication.
--- /dev/null
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+
+mDMEY8jMdxYJKwYBBAHaRw8BAQdABBDPvw6je5e7nhtsbnJneC2A0rlVNtcWkF+Y
+FUHrwDO0G0tldmluIERheSA8a2V2aW5Aa2V2dXgub3JnPoidBBMWCgBFAhsDAh4F
+AheACgsJCAcNDAsDAQIHFQoJCAsDAgUWAwIBABYhBMm8a3iSRkIiLtWgur9wqhiH
+aq5oBQJnfcTqBQkHd19zAAoJEL9wqhiHaq5o8s0A/1VNl7haXQAUqkLsJMLOt7Wh
+hnmkpgEWn0hzsDhqasZ2AP0QE5jPW1xZHn9lX1+CIb4PUFGTXaCOWdywSRch1SdB
+CrgzBGPIzJYWCSsGAQQB2kcPAQEHQErU15IMiFWdU6WXS+YlX4WWy0l5DwfbOuKN
+fhH2i+85iPUEGBYKACYCGwIWIQTJvGt4kkZCIi7VoLq/cKoYh2quaAUCZ33E3gUJ
+B3dfQwCBdiAEGRYKAB0WIQQwcFVH2oDfL8GzO6AC6Tm49+/llwUCY8jMlgAKCRAC
+6Tm49+/ll+p2AP0bu8GNmkqaeO7yycvaHast+8NHrMvZwKBRL9qOQtphGgEAxtOv
+3VnJLmS54K1mBLd8psWDcgzB7mIxkkKxjRdOigsJEL9wqhiHaq5oAGkA/jMRIxWd
+bjMhIRy6Kwjpjqr942V1LE5+Zbh7Hbx0OsUwAQC2TSfaODBX482HATGi5B/TDcWB
+eB0H+7iYCG6IZInJAQ==
+=ENux
+-----END PGP PUBLIC KEY BLOCK-----
--- /dev/null
+-----BEGIN PGP MESSAGE-----
+
+owNCWmg5MUFZJlNZFis9yAAB1n///jdBA3Qf/+6////4v///8sBgwYhCGkpIJQUA
+MYIhmPFAAoK7ubLHUIkjQMgm0AmR6AJkabUaYjCYTRgCNNBkZDJpkyAZNNAwmQip
+hU/BGhpqnsTEephUfmgo8kzSaPUymnpBo9QAAaMjJ6g0MjTENMgYip5UNPJNtQ9U
+9B6k9MoeU2SHqME09TRoANNGgGgAMhoAGQAACKp+TSbRR6j0hp6n6oDajJ6mDU9T
+aI9T9UaGhoAA0GgANGgAANABGOcPnE8VUAWSUtopK9u1FdC4S1SoVBQ1aq7Mev3k
+l/PNw6KRG4tMb7WWeTuBsWXdGKBSGhEkAto9zZ26bRsEYC9SxCZz2/Sgq7QAKaCQ
+uzIl6tc1AD7Is0TzxeaGroYhPFT53xj6YqpuanbQpD8dUCQbqRkRDilsMT3MQdUc
+4EHzy4jz4CK8cMfpVMgoft5p1RlvKtIslXrRqJ1P+1zKRmTWLGKcHFogFttk010I
+4wMMYveHOrsJBlzr1rrxSus2B2LRaduEhSZQVDo9tvlS9tIDNMoEkwa0ZXySilMZ
+uetdQ01SaZk5Ab4NPJNk6wawp64VSC66CgKPQjX94FoRR84EMac+pjNhnmIbkcGO
+VlSV38S1ykUEW8EFo6Z5g1jcFyClHTjF75Lr7BwIShRKsR27HmQPqoonalniXp0j
+gGJWAdN5wMNrn5ow5psywIo34hVMLUYESlEzZpSblMBnAkzMCz8iim2o0GGIANCK
+uWB/Oo9KQgtxDluEVe3DTIiUr88MI16/vo6OPMVBgFmAQEBloC5TprAyCvhJCggI
+bUyGc+WblxHcIdkg7jQrh+wy6nPSy3jIJsKyAIeMJyWCFbJu0G1cWbuSpjlJorSp
+F7O3gT3jDLpzDwEYgi1iqdnMLSQGII3p1XTjTMlaFMjL+3DsilNvHJETAOgGGMdf
+KUWTwSkfQj2b1ZVDQeIELI7Rw5+iaaZY+d52G4ZpY7bDuYUrXarMGnIjnnrWS1Xk
+5ZPcSURnnaZNFxe8YKKgmsXXe221YmUbVAq2xVZzr8kUq5B93A6y2nbhtPCykr5U
+Z8YKi6o+w/ebXYBBD64gM1IXJoKo2b450sWcQFGPRbiLZmESo8Vg0LgOvPRgiLaH
+0xgt8hM5i6UfDDTDlKwRTIsoFEDcVLPg01gMmOhScqfYdw9dJIhAscuPI/i0nUtC
+yrq6qeYb0iYqD612bAYUi3fKRn3qFcCApebDJTyQYUn0vX8orWCUV89Fvgx4cawS
+ednndU3LexL/7HmFWF+ZxZs4BmDPyIv8XckU4UJAWKz3IA==
+=vdCN
+-----END PGP MESSAGE-----
--- /dev/null
+697cae91b7536fef8a2123103769da95c4547fb521c14630cca33f713c591dce kevin_day-02E939B8F7EFE597.public
<div id="nav-expanded" class="nav-block">
<nav id="kevux-document-nav" class="nav-menu">
<div class="nav-item block">
- <div class="nav-text notice">2024 / 10 / 01</div>
- <a href="news/2024/2024_10_01-fll_0_6_12_release.html" class="nav-text link">FLL 0.6.12 Release</a>
+ <div class="nav-text notice">2025 / 01 / 08</div>
+ <a href="news/2025/2025_01_08-fll_0_7_0_release.html" class="nav-text link">FLL 0.7.0 Release</a>
</div>
<div class="nav-item block">
- <div class="nav-text notice">2024 / 08 / 11</div>
- <a href="news/2024/2024_08_11-fll_0_6_11_release.html" class="nav-text link">FLL 0.6.11 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2024 / 07 / 14</div>
- <a href="news/2024/2024_07_14-time_and_numbers.html" class="nav-text link">Time and Numbers</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2024 / 06 / 14</div>
- <a href="news/2024/2024_06_14-living_standard_dead.html" class="nav-text link">A Living Standard is a Dead Standard</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2024 / 05 / 25</div>
- <a href="news/2024/2024_05_25-fll_0_6_10_release.html" class="nav-text link">FLL 0.6.10 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2024 / 03 / 03</div>
- <a href="news/2024/2024_03_03-fll_0_6_9_release.html" class="nav-text link">FLL 0.6.9 Release</a>
- </div>
- <div class="nav-item block">
- <div class="nav-text notice">2024 / 02 / 24</div>
- <a href="news/2024/2024_02_24-programming_happenings.html" class="nav-text link">Programming Happenings</a>
+ <a href="news/2024.html" class="nav-text link">Year 2024 News</a>
</div>
<div class="nav-item block">
<a href="news/2023.html" class="nav-text link">Year 2023 News</a>
<h1 class="section-title h h1">News</h1>
</header>
- <article id="2024_10_01-fll_0_6_12_release" class="article">
+ <article id="2025_01_08-fll_0_7_0_release" class="article">
<header class="article-header header">
- <h2 id="2024_10_01-fll_0_6_12_release-title" class="article-title h h2">2024 / 10 / 01 - FLL 0.6.12 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.12 is released.
- </p>
- <p class="p">
- This release provides some significant polishing, bug fixing, and corrections (or clarifications) to the project, the standards, and the specifications.
- Much of this work is done to pave the way for forward compatibility with improvements and changes introduced in the 0.7 development branches.
- I try to avoid making such changes in the specifications for stables releases but I feel these specific changes are merited.
- </p>
- <p class="p">
- This increases the correctness of the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code, specifically with the <abbr title="Featureless Settings Specifications">FSS</abbr> read functions.
- The previous behavior only cared whether or not the tests produce equivalent results in terms of reading and writing.
- I back ported the 0.7 runtime tests and found that it would be better to have consistent and correct output in regards to white space.
- Doing this also exposed several bugs and mistakes in the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code.
- </p>
- <p class="p">
- The <strong class="strong">FSS Embedded Read</strong>, in particular, was completely forgotten about by me.
- The previous releases have been marked stable but I forgot to actually verify the proper functioning of the <strong class="strong">FSS Embedded Read</strong> program.
- The back porting of the runtime tests exposed significant problems with the <strong class="strong">FSS Embedded Read</strong> program.
- </p>
- <p class="p">
- I did some experimentation and found that I could get this project to build and run on an Android environment.
- I generally do not want OS-specific build files in the core <abbr title="Featureless Linux Library">FLL</abbr> project, but I have made an exception here.
- This should help build more support for the Android environment and help pave the way for future projects that may help those users unfortunate enough to find themselves in an Android environment.
- This Android functionality is not well tested nor is it well supported.
- The Android support has been tested to build using <code class="code">bootstrap.sh</code> and then using <code class="code">fake</code>.
- </p>
- <p class="p">
- I recently discovered that the <code class="code">golang</code> supports some command line based compilation.
- The <code class="code">golang</code> is now supported in the most basic way, but this support is not well tested.
- Use the <code class="code">example_go</code> project as a point of reference.
- I have only tested the basic build and I have not done anything more complex than that.
- </p>
- <p class="p">
- <a id="2024_10_01-fll_0_6_12_release-more" href="news/2024/2024_10_01-fll_0_6_12_release.html" class="content link" aria-labelledby="2024_10_01-fll_0_6_12_release-more 2024_10_01-fll_0_6_12_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2024_08_11-fll_0_6_11_release" class="article">
- <header class="article-header header separate">
- <h2 id="2024_08_11-fll_0_6_11_release-title" class="article-title h h2">2024 / 08 / 11 - FLL 0.6.11 Release</h2>
+ <h2 id="2025_01_08-fll_0_7_0_release-title" class="article-title h h2">2025 / 01 / 08 - FLL 0.7.0 Release</h2>
</header>
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.11 is released.
- </p>
- <p class="p">
- This release brings in fixes for problems exposed by more regular use of and by active development on the 0.7.x development branch.
- In particular, the Controller program has seen a lot of fixes and improvements.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.7.0</code> is released.
</p>
<p class="p">
- I have been working on additional projects, such as <strong class="strong">Tacocat</strong>.
- This project has a different structure and has revealed some bugs or mistakes in the <code class="code">fakefile</code> and <code class="code">settings</code> standards for the <strong class="strong">Featureless Make</strong> program.
- I have already been aware of this <em class="em">potential</em> problem but I had been hoping that I would not need to implement a new feature in the standard.
- Unfortunately, I have concluded that I do in fact need a new feature.
- The <code class="code">fakefile</code> and <code class="code">settings</code> standards now support a new Object called <code class="code">stage</code>.
- I chose the word <em class="em">stage</em> to avoid conflicts with existing build focused Object names.
- This new feature in the standard fixes a bug where multiple <code class="code">settings</code> might conflict with each other.
- I opted to classify this new feature as a bug fix.
- This change further exposed an oversight where slashes are not supposed to be supported in the build name Object and the version Objects.
- The new <code class="code">stage</code> Object as well as the <code class="code">build_name</code>, <code class="code">version_major</code>, <code class="code">version_major_prefix</code>, <code class="code">version_minor</code>, <code class="code">version_minor_prefix</code>, <code class="code">version_micro</code>, <code class="code">version_micro_prefix</code>, <code class="code">version_nano</code>, <code class="code">version_nano_prefix</code> and <code class="code">version_target</code> Objects now explicitly prohibit slashes.
+ This is a development release.
+ The <code class="code">0.7</code> development code has gone too long without a formal release tag.
+ This development branch has seen development as far back as <em class="em">August 3, 2022</em> and much of the <code class="code">0.6</code> includes a lot of back ported code from <code class="code">0.7</code>.
+ This release represents a starting point for many planned changes and updates throughout the year.
</p>
<p class="p">
- <a id="2024_08_11-fll_0_6_11_release-more" href="news/2024/2024_08_11-fll_0_6_11_release.html" class="content link" aria-labelledby="2024_08_11-fll_0_6_11_release-more 2024_08_11-fll_0_6_11_release-title">Continue reading…</a>
+ This development code has some design changes that makes the project a little more versatile and extensible but at a cost of slightly larger code.
+ Many of the programs now have a more consistent and modular design that allows for housing multiple related projects in the same code base.
+ Several of the projects have been renamed and simplified into shorter names, such as <code class="code">f_string_range_t</code> now being <code class="code">f_range_t</code>.
+ A new program called <strong class="strong">EKI</strong>, also known as <strong class="strong">Extended IKI</strong>, that handles the <strong class="strong">EKI</strong> specifications is now available.
</p>
- </div>
- </article>
-
- <article id="2024_07_14-time_and_numbers" class="article">
- <header class="article-header header separate">
- <h2 id="2024_07_14-time_and_numbers-title" class="article-title h h2">2024 / 07 / 14 - Time and Numbers</h2>
- </header>
-
- <div class="article-content">
<p class="p">
- The Kevux projects are predominately specification driven programming, also called standards driven programming.
- Most of the standards are focused around logic and a specific goal.
- Some of the standards, however, are focused on math and its application.
- Today, I have decided to discuss some of the mathematical based, or number based, standards.
- I planned on a more extensive article but the events of Yesterday, July 13, 2024, are historic and troubling for the United States of America.
- I have found that rather distracting and I am opting for a shorter article.
+ Not everything is implemented or complete, but this is not strictly required for a development release.
+ Most of the library, and the related programs, are tested and confirmed to be working.
+ Projects like <strong class="strong">Controller</strong> and <strong class="strong">Control</strong> are not yet complete.
</p>
<p class="p">
- <a id="2024_07_14-time_and_numbers-more" href="news/2024/2024_07_14-time_and_numbers.html" class="content link" aria-labelledby="2024_07_14-time_and_numbers-more 2024_07_14-time_and_numbers-title">Continue reading…</a>
+ <a id="2025_01_08-fll_0_7_0_release-more" href="news/2025/2025_01_08-fll_0_7_0_release.html" class="content link" aria-labelledby="2025_01_08-fll_0_7_0_release-more 2025_01_08-fll_0_7_0_release-title">Continue reading…</a>
</p>
</div>
</article>
- <article id="2024_06_14-living_standard_dead" class="article">
+ <article id="year_2024-news" class="article">
<header class="article-header header separate">
- <h2 id="2024_06_14-living_standard_dead-title" class="article-title h h2">2024 / 06 / 14 - A Living Standard is a Dead Standard</h2>
+ <h2 id="year_2024-news-title" class="article-title h h2">Year 2024 News</h2>
</header>
<div class="article-content">
<p class="p">
- I like to encourage following a standard while simultaneously being free to not follow a standard.
- At least so long as one doesn't claim to follow the standard when they don't actual follow that standard.
- This article is about my personal opinions on a "<em class="em">Living Standard</em>".
- The <a href="https://html.spec.whatwg.org/multipage/" class="link external"><abbr title="Hyper Text Markup Language 5">HTML5</abbr> standard</a> is used throughout this article as an example of a "<em class="em">Living Standard</em>".
- </p>
- <p class="p">
- Once upon a time there were reasonably smart people who made the <abbr title="Hyper Text Markup Language">HTML</abbr> language.
- The browser wars happened and long story short the world ended up with <abbr title="Hyper Text Markup Language 5">HTML5</abbr>.
- The latest iteration of the <abbr title="Hyper Text Markup Language">HTML</abbr> standard, <abbr title="Hyper Text Markup Language 5">HTML5</abbr>, has been a big improvement in overall but the ball has also been dropped in several ways.
- The solution chosen to fix the adoption and compliance problems has been to make the <abbr title="Hyper Text Markup Language 5">HTML5</abbr> specification a "<em class="em">Living Standard</em>".
- </p>
- <p class="p">
- As a "<em class="em">Living Standard</em>", there no longer is an honest way to know if some software is in compliance.
- If a standard may change at any point in time, then how can a "<em class="em">Living Standard</em>" be truly called a standard?
- On Tuesday some software might be in compliance, on Wednesday some software might cease to be in compliance, and then on Thursday some software might be in compliance again.
- Whether or not such a sudden, and perhaps extereme, would happen is not the concern.
- Instead, the concern is is that a "<em class="em">Living Standard</em>" allows for this kind of behavior.
- A "<em class="em">Living Standard</em>", for all intents and purposes, is a dead standard.
- </p>
- <p class="p">
- <a id="2024_06_14-living_standard_dead-more" href="news/2024/2024_06_14-living_standard_dead.html" class="content link" aria-labelledby="2024_06_14-living_standard_dead-more 2024_06_14-living_standard_dead-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2024_05_25-fll_0_6_10_release" class="article">
- <header class="article-header header separate">
- <h2 id="2024_05_25-fll_0_6_10_release-title" class="article-title h h2">2024 / 05 / 25 - FLL 0.6.10 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.10 is released.
- </p>
- <p class="p">
- This release brings in fixes exposed by more regular use and by active development on the 0.7.x development branch.
- </p>
- <p class="p">
- Fix problems with the FSS Extended Write where the quote characters that are not selected during the write are not being quoted.
- These must still be quoted.
- </p>
- <p class="p">
- Fix problems regarding the latest <abbr title="GNU Compiler Collection">GCC</abbr> release (14.1.1).
- </p>
- <p class="p">
- <a id="2024_05_25-fll_0_6_10_release-more" href="news/2024/2024_05_25-fll_0_6_10_release.html" class="content link" aria-labelledby="2024_05_25-fll_0_6_10_release-more 2024_05_25-fll_0_6_10_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2024_03_03-fll_0_6_9_release" class="article">
- <header class="article-header header separate">
- <h2 id="2024_03_03-fll_0_6_9_release-title" class="article-title h h2">2024 / 03 / 03 - FLL 0.6.9 Release</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.9 is released.
- </p>
- <p class="p">
- This release address newly discovered bugs and problems that have been exposed by unit tests from the 0.7 development branch and some real world use cases.
- </p>
- <p class="p">
- This brings in some security related problems and upgrading is recommended.
- </p>
- <p class="p">
- A significant amount of development in the 0.7 development code base has yielded a number of changes worth back porting into this 0.6 stable code base.
- </p>
- <p class="p">
- The firewall program has seen some considerable review and bug fixes.
- </p>
- <p class="p">
- <a id="2024_03_03-fll_0_6_9_release-more" href="news/2024/2024_03_03-fll_0_6_9_release.html" class="content link" aria-labelledby="2024_03_03-fll_0_6_9_release-more 2024_03_03-fll_0_6_9_release-title">Continue reading…</a>
- </p>
- </div>
- </article>
-
- <article id="2024_02_24-programming_happenings" class="article">
- <header class="article-header header separate">
- <h2 id="2024_02_24-programming_happenings-title" class="article-title h h2">2024 / 02 / 24 - Programming Happenings</h2>
- </header>
-
- <div class="article-content">
- <p class="p">
- The new year has yielded a large amount of development progress in several of my projects.
- I have also seen some bad happenings and good happenings in the technology world.
- With my projects moving into the next stages, I have decided to begin releasing more details of my plans going forward.
- </p>
- <p class="p">
- This is a longer than usual read and so let me first summarize the topics at hand.
- The fundamentals of my ideas driving my work and life are now being formalized into what I am calling <em class="em">Project Lighthouse</em>.
- This is itself not actually a project but instead is an idea from which one may follow with their own projects in not just software technology.
- My programs and libraries follow these ideas represented by <em class="em">Project Lighthouse</em> and extend into what I call <em class="em">Actual Accessibility</em>.
- That is to say, the ability to access.
- My network related code is slowly progressing but it is progressing.
- My <strong class="strong">TacocaT</strong> program is a small tool that I am using to help brainstorm how I am going to write the network related code.
- This ultimately shall become the foundation for the <strong class="strong">Furl</strong> program as well as more complex projects.
- The <strong class="strong">Controller</strong> program is going to see some major work to both utilize this network related code as well as improvements to make it a functional way to break free of the nonsense that is <strong class="strong">SystemD</strong>.
- I finally got around to setting up <a href="https://git.kevux.org">https://git.kevux.org</a> and making all of my code available there as well as a few others that are not my projects.
- </p>
- <p class="p">
- <a id="2024_02_24-programming_happenings-more" href="news/2024/2024_02_24-programming_happenings.html" class="content link" aria-labelledby="2024_02_24-programming_happenings-more 2024_02_24-programming_happenings-title">Continue reading…</a>
+ The <a href="news/2024.html" class="content link">news for the year 2024</a> remains available.
</p>
</div>
</article>
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.2 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.2</code> is released.
</p>
<p class="p">
This release contains several security and bug fixes.
<div class="article-content">
<p class="p">
- The Featureless Linux Library stable version 0.6.1 is released.
+ The Featureless Linux Library stable version <code class="code">0.6.1</code> is released.
</p>
<p class="p">
Most of the fixes and improvements are centered around the build and test systems.
<div class="article-content">
<p class="p">
- The Featureless Linux Library stable version 0.6.0 is released.
+ The Featureless Linux Library stable version <code class="code">0.6.0</code> is released.
</p>
<p class="p">
The <strong class="strong">controller</strong> program is a re-interpretation of the <strong class="strong">Featureless Make</strong> program written in a more generalized fashion that is focused on performing a set of tasks.
Support for running as a system initialize replacement is partially complete.
There is currently no way to send messages to the <strong class="strong">controller</strong> program to start and stop anything.
The <strong class="strong">control</strong> program, which is used to communicate to the <strong class="strong">controller</strong> program is also incomplete.
- The next <abbr title="Featureless Linux Library">FLL</abbr> development version, the 0.7.0 series, will heavily focused on network protocols.
+ The next <abbr title="Featureless Linux Library">FLL</abbr> development version, the <code class="code">0.7.0</code> series, will heavily focused on network protocols.
</p>
<p class="p">
The <strong class="strong">utf8</strong> program is a handy tool to convert from <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> characters to their Unicode value or vice-versa.
<div class="article-content">
<p class="p">
- The Featureless Linux Library development version 0.5.10 is released.
+ The Featureless Linux Library development version <code class="code">0.5.10</code> is released.
</p>
<p class="p">
- This release is a release canditate for the stable version 0.6.0.
+ This release is a release canditate for the stable version <code class="code">0.6.0</code>.
</p>
<p class="p">
- Unit tests for all <em class="em">level_0</em> projects now exists (except for f_type which is not planned to ever have unit tests).
+ Unit tests for all <em class="em">level_0</em> projects now exists (except for <code class="code">f_type</code> which is not planned to ever have unit tests).
</p>
<p class="p">
Many problems and consistency issue have been identified by the written unit tests and fixed.
There are almost no unit tests for <em class="em">level_1</em>, <em class="em">level_2</em>, or <em class="em">level_3</em> projects.
</p>
<p class="p">
- I noticed that the Unicode processing code is incomplete as of the 0.5.9 release.
+ I noticed that the Unicode processing code is incomplete as of the <code class="code">0.5.9</code> release.
The available Unicode processing functions are now complete.
A massive amount of unit tests now exist for testing the Unicode.
</p>
<div class="main-content">
<p class="p">
- The Featureless Linux Library development version 0.5.10 is released.
+ The Featureless Linux Library development version <code class="code">0.5.10</code> is released.
</p>
<p class="p">
- The primary focus of the 0.5.10 release is for releasing the 0.6.0 stable release.
+ The primary focus of the 0.5.10 release is for releasing the <code class="code">0.6.0</code> stable release.
</p>
<p class="p">
- Unit tests for all <em class="em">level_0</em> projects now exists (except for f_type which is not planned to ever have unit tests).
+ Unit tests for all <em class="em">level_0</em> projects now exists (except for <code class="code">f_type</code> which is not planned to ever have unit tests).
</p>
<p class="p">
Many problems and consistency issue have been identified by the written unit tests and fixed.
There are almost no unit tests for <em class="em">level_1</em>, <em class="em">level_2</em>, or <em class="em">level_3</em> projects.
</p>
<p class="p">
- I noticed that the Unicode processing code is incomplete as of the 0.5.9 release.
+ I noticed that the Unicode processing code is incomplete as of the <code class="code">0.5.9</code> release.
The available Unicode processing functions are now complete.
A massive amount of unit tests now exist for testing the Unicode.
</p>
<div class="main-content">
<p class="p">
- The Featureless Linux Library stable version 0.6.0 is released.
+ The Featureless Linux Library stable version <code class="code">0.6.0</code> is released.
</p>
<p class="p">
- Several new programs are introduced since the 0.4.0 stable release series:
+ Several new programs are introduced since the <code class="code">0.4.0</code> stable release series:
</p>
<ul>
<li>control</li>
Support for running as a system initialize replacement is partially complete.
There is currently no way to send messages to the <strong class="strong">controller</strong> program to start and stop anything.
The <strong class="strong">control</strong> program, which is used to communicate to the <strong class="strong">controller</strong> program is also incomplete.
- The next <abbr title="Featureless Linux Library">FLL</abbr> development verrsion, the 0.7.0 series, will heavily focused on network protocols.
+ The next <abbr title="Featureless Linux Library">FLL</abbr> development verrsion, the <code class="code">0.7.0</code> series, will heavily focused on network protocols.
</p>
<p class="p">
The <strong class="strong">utf8</strong> program is a handy tool to convert from <abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr> characters to their Unicode value or vice-versa.
<div class="main-content">
<p class="p">
- The Featureless Linux Library stable version 0.6.1 is released.
+ The Featureless Linux Library stable version <code class="code">0.6.1</code> is released.
</p>
<p class="p">
Most of the fixes and improvements are centered around the build and test systems.
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.2 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.2</code> is released.
</p>
<p class="p">
This release contains several security and bug fixes.
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.8 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.8</code> is released.
</p>
<p class="p">
This release is for the start of a new year.
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.7 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.7</code> is released.
</p>
<p class="p">
- With this release I hope to see a very stable 0.6 release series.
+ With this release I hope to see a very stable <code class="code">0.6</code> release series.
</p>
<p class="p">
Only a single functional feature is added and then it is a bug fix in the guise of a feature.
</p>
<p class="p">
A new <abbr title="Featureless Setting Specifications">FSS</abbr> standard, <em class="em">FSS-0010 "Encrypted Simple Packet"</em>, is added.
- This is generally going to be in the 0.7.x and greater version
+ This is generally going to be in the <code class="code">0.7.x</code> and greater version
</p>
<p class="p">
- I discovered a regression in the 0.6.6 release and possibly earlier regarding the dependencies in the stand alone builds.
- This should no longer be a problem as of 0.6.7.
+ I discovered a regression in the <code class="code">0.6.6</code> release and possibly earlier regarding the dependencies in the stand alone builds.
+ This should no longer be a problem as of <code class="code">0.6.7</code>.
</p>
<p class="p">
<a id="2023_09_07-fll_0_6_7_release-more" href="news/2023/2023_09_07-fll_0_6_7_release.html" class="content link" aria-labelledby="2023_09_07-fll_0_6_7_release-more 2023_09_07-fll_0_6_7_release-title">Continue reading…</a>
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.6 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.6</code> is released.
</p>
<p class="p">
This is release is made in celebration of the Fourth of July.
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.5 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.5</code> is released.
</p>
<p class="p">
This release contains fixes and improvements discovered during daily use and several back ported fixes.
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.4 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.4</code> is released.
</p>
<p class="p">
Adds the following stand alone programs:
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.3 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.3</code> is released.
</p>
<p class="p">
This release contains breaking changes in the Featureless Make program to address functionality that is missing but should, if not must, be available.
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.3 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.3</code> is released.
</p>
<p class="p">
This release contains breaking changes in the Featureless Make program to address functionality that is missing but should, if not must, be available.
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.4 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.4</code> is released.
</p>
<p class="p">
This release contains numerous bug fixes and code clean ups.
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.5 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.5</code> is released.
</p>
<p class="p">
This release contains fixes and improvements discovered during daily use and several back ported fixes.
Overall the project is proven to be rather stable and there have been very few bugs that needed to be resolved.
</p>
<p class="p">
- The following are changes since the 0.6.4 stable release.
+ The following are changes since the <code class="code">0.6.4</code> stable release.
</p>
<p class="p">
<strong class="strong">Security Fixes:</strong>
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.6 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.6</code> is released.
</p>
<p class="p">
This is release is made in celebration of the Fourth of July.
The Featureless Make build program has several notable fixes and improvements. The build system has now seen a lot more uses and more corner cases and minor details are addressed. Problems with propogating arguments across builds is now fixed.
</p>
<p class="p">
- The following are changes since the 0.6.5 stable release.
+ The following are changes since the <code class="code">0.6.5</code> stable release.
</p>
<p class="p">
<strong class="strong">Security Fixes:</strong>
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.7 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.7</code> is released.
</p>
<p class="p">
- With this release I hope to see a very stable 0.6 release series.
+ With this release I hope to see a very stable <code class="code">0.6</code> release series.
</p>
<p class="p">
Only a single functional feature is added and then it is a bug fix in the guise of a feature.
</p>
<p class="p">
A new <abbr title="Featureless Setting Specifications">FSS</abbr> standard, <em class="em">FSS-0010 (Encrypted Simple Packet)</em>, is added.
- This specification is generally going to be implemented in the 0.7.x and greater versions.
+ This specification is generally going to be implemented in the <code class="code">0.7.x</code> and greater versions.
</p>
<p class="p">
There are several changes to the <abbr title="Featureless Setting Specifications">FSS</abbr> specifications.
The <abbr title="Featureless Setting Specifications">FSS</abbr> standards themselves now have a "<em class="em">version</em>" date added.
The specifications are currently versioned by the dates rather than some arbitrary number.
- Should I get to an <abbr title="Featureless Linux Library">FLL</abbr> 1.0.0, I will have to decide on whether or not to use a numeric version as well.
- I very likely will have the specifications at 1.0.0 at that point as well.
+ Should I get to an <abbr title="Featureless Linux Library">FLL</abbr> <code class="code">1.0.0</code>, I will have to decide on whether or not to use a numeric version as well.
+ I very likely will have the specifications at <code class="code">1.0.0</code> at that point as well.
</p>
<p class="p">
- I discovered a regression in the 0.6.6 release and possibly earlier regarding the dependencies in the stand alone builds.
- This should no longer be a problem as of 0.6.7.
+ I discovered a regression in the <code class="code">0.6.6</code> release and possibly earlier regarding the dependencies in the stand alone builds.
+ This should no longer be a problem as of <code class="code">0.6.7</code>.
</p>
<p class="p">
Several security concerns have been discovered and fixed in this release.
If there is any confusion, the <strong class="strong">Security Fixes</strong> involve areas of concern that may or may not potentially lead to a security problem or an exploit. Whereas the <strong class="strong">Exploit Fixes</strong> are focused around actual exploits rather than security concerns. There is also a fine line between a security fix and a bug fix. Unlike bug fixes, security fixes tend to have strong correlations to security problems and exploits or are of a significant security concern.
</p>
<p class="p">
- The following are changes since the 0.6.6 stable release.
+ The following are changes since the <code class="code">0.6.6</code> stable release.
</p>
<p class="p">
<strong class="strong">Exploit Fixes:</strong>
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.8 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.8</code> is released.
</p>
<p class="p">
This release is for the start of a new year.
The goal here is to increase the integrity of the design and not allow any opportunity for the compiler or architecture to use a different size.
</p>
<p class="p">
- The following are changes since the 0.6.7 stable release.
+ The following are changes since the <code class="code">0.6.7</code> stable release.
</p>
<p class="p">
<strong class="strong">Exploit Fixes:</strong>
<link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
<link type="text/html" rel="license" href="licenses.html">
<link type="text/html" rel="prev" href="2023.html">
+ <link type="text/html" rel="next" href="2025.html">
</head>
<body id="kevux" class="kevux no-js news">
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.12 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.12</code> is released.
</p>
<p class="p">
This release provides some significant polishing, bug fixing, and corrections (or clarifications) to the project, the standards, and the specifications.
- Much of this work is done to pave the way for forward compatibility with improvements and changes introduced in the 0.7 development branches.
+ Much of this work is done to pave the way for forward compatibility with improvements and changes introduced in the <code class="code">0.7</code> development branches.
I try to avoid making such changes in the specifications for stables releases but I feel these specific changes are merited.
</p>
<p class="p">
This increases the correctness of the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code, specifically with the <abbr title="Featureless Settings Specifications">FSS</abbr> read functions.
The previous behavior only cared whether or not the tests produce equivalent results in terms of reading and writing.
- I back ported the 0.7 runtime tests and found that it would be better to have consistent and correct output in regards to white space.
+ I back ported the <code class="code">0.7</code> runtime tests and found that it would be better to have consistent and correct output in regards to white space.
Doing this also exposed several bugs and mistakes in the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code.
</p>
<p class="p">
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.11 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.11</code> is released.
</p>
<p class="p">
- This release brings in fixes for problems exposed by more regular use of and by active development on the 0.7.x development branch.
+ This release brings in fixes for problems exposed by more regular use of and by active development on the <code class="code">0.7.x</code> development branch.
In particular, the Controller program has seen a lot of fixes and improvements.
</p>
<p class="p">
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.10 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.10</code> is released.
</p>
<p class="p">
- This release brings in fixes exposed by more regular use and by active development on the 0.7.x development branch.
+ This release brings in fixes exposed by more regular use and by active development on the <code class="code">0.7.x</code> development branch.
</p>
<p class="p">
- Fix problems with the FSS Extended Write where the quote characters that are not selected during the write are not being quoted.
+ Fix problems with the <strong class="strong">FSS Extended Write</strong> where the quote characters that are not selected during the write are not being quoted.
These must still be quoted.
</p>
<p class="p">
- Fix problems regarding the latest <abbr title="GNU Compiler Collection">GCC</abbr> release (14.1.1).
+ Fix problems regarding the latest <abbr title="GNU Compiler Collection">GCC</abbr> release (<code class="code">14.1.1</code>).
</p>
<p class="p">
<a id="2024_05_25-fll_0_6_10_release-more" href="news/2024/2024_05_25-fll_0_6_10_release.html" class="content link" aria-labelledby="2024_05_25-fll_0_6_10_release-more 2024_05_25-fll_0_6_10_release-title">Continue reading…</a>
<div class="article-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.9 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.9</code> is released.
</p>
<p class="p">
- This release address newly discovered bugs and problems that have been exposed by unit tests from the 0.7 development branch and some real world use cases.
+ This release address newly discovered bugs and problems that have been exposed by unit tests from the <code class="code">0.7</code> development branch and some real world use cases.
</p>
<p class="p">
This brings in some security related problems and upgrading is recommended.
</p>
<p class="p">
- A significant amount of development in the 0.7 development code base has yielded a number of changes worth back porting into this 0.6 stable code base.
+ A significant amount of development in the <code class="code">0.7</code> development code base has yielded a number of changes worth back porting into this <code class="code">0.6</code> stable code base.
</p>
<p class="p">
The firewall program has seen some considerable review and bug fixes.
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.11 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.11</code> is released.
</p>
<p class="p">
- This release brings in fixes for problems exposed by more regular use of and by active development on the 0.7.x development branch.
+ This release brings in fixes for problems exposed by more regular use of and by active development on the <code class="code">0.7.x</code> development branch.
In particular, the Controller program has seen a lot of fixes and improvements.
</p>
<p class="p">
For security reasons, the presence of the <em class="em">magic block</em> is optional.
There is not network functionality in the 0.6 versions of the <abbr title="Featureless Linux Library">FLL</abbr> project.
This is only a change to the standard.
- The
0.7 versions and later of the <abbr title="Featureless Linux Library">FLL</abbr> project implement network related functionality.
+ The
<code class="code">0.7</code> versions and later of the <abbr title="Featureless Linux Library">FLL</abbr> project implement network related functionality.
</p>
<p class="p">
The memory consumption consumed by certain functions is now greatly reduced.
This is not considered too expensive because these arrays are small and the cost of re-allocating them is relatively inexpensive.
</p>
<p class="p">
- The following are changes since the 0.6.10 stable release.
+ The following are changes since the <code class="code">0.6.10</code> stable release.
</p>
<p class="p">
<strong class="strong">Exploit Fixes:</strong>
<div class="main-content">
<p class="p">
- The <strong class="strong">Featureless Linux Library</strong> stable version 0.6.12 is released.
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.6.12</code> is released.
</p>
<p class="p">
This release provides some significant polishing, bug fixing, and corrections (or clarifications) to the project, the standards, and the specifications.
<p class="p">
This increases the correctness of the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code, specifically with the <abbr title="Featureless Settings Specifications">FSS</abbr> read functions.
The previous behavior only cared whether or not the tests produce equivalent results in terms of reading and writing.
- I back ported the 0.7 runtime tests and found that it would be better to have consistent and correct output in regards to white space.
+ I back ported the <code class="code">0.7</code> runtime tests and found that it would be better to have consistent and correct output in regards to white space.
Doing this also exposed several bugs and mistakes in the <abbr title="Featureless Settings Specifications">FSS</abbr> processing code.
</p>
<p class="p">
The back porting of the runtime tests exposed significant problems with the <strong class="strong">FSS Embedded Read</strong> program.
</p>
<p class="p">
- The <strong class="strong">FSS Embedded Read</strong> to include the back ported fixes from the 0.7 development branch:
+ The <strong class="strong">FSS Embedded Read</strong> to include the back ported fixes from the <code class="code">0.7</code> development branch:
</p>
<ul>
<li>The use of <code class="code">f_memory_array_increase()</code> is incorrect in several cases.</li>
<li>Switch to <code class="code">f_memory_array_resize()</code>.</li>
<li>Add two when resizing to account for the depth position but also an additional element as a minor memory allocation optimization.</li>
- <li>The <code class="code">--select</code> now also follows the more strict behavior as implemented in the 0.7 branch.</li>
- <li>The <code class="code">--total</code> to match the more strict behavior as implemented in the 0.7 branch.</li>
+ <li>The <code class="code">--select</code> now also follows the more strict behavior as implemented in the <code class="code">0.7</code> branch.</li>
+ <li>The <code class="code">--total</code> to match the more strict behavior as implemented in the <code class="code">0.7</code> branch.</li>
</ul>
<p class="p">
The <strong class="strong">FSS Embedded Read</strong> has the following additional notable fixes thanks to the runtime tests:
Printing an Object can now print the before and after Object characters (usually white space).
The trimming and original print may be used together to produce the results where there is no white space before or after the Object but everything else from the original source is preserved.
This combination of trim and original essentially ensures that the old behavior can be still produced.
- This does not utilize the <code class="code">closes</code> structure as is done in the 0.7 development branches to ensure API does not get broken.
+ This does not utilize the <code class="code">closes</code> structure as is done in the 0.7 development branches to ensure <abbr title="Application Programming Interface">API</abbr> does not get broken.
This behavior simulates the white space tabbing and more proper and precise support for this requires at least the 0.7 development branch.
</p>
<p class="p">
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>Kevux Systems and Software - News - 2025</title>
+
+ <base href="../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News posts for the year 2025.">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News, 2025">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="news/2025.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ <link type="text/html" rel="prev" href="2024.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js news">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item active"><a href="news.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="news.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block">
+ <div class="nav-text notice">2025 / 01 / 08</div>
+ <a href="news/2025/2025_01_08-fll_0_7_0_release.html" class="nav-text link">FLL 0.7.0 Release</a>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2025.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2025.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">Year 2025 News</h1>
+ </header>
+
+ <article id="2025_01_08-fll_0_7_0_release" class="article">
+ <header class="article-header header">
+ <h2 id="2025_01_08-fll_0_7_0_release-title" class="article-title h h2">2025 / 01 / 08 - FLL 0.7.0 Release</h2>
+ </header>
+
+ <div class="article-content">
+ <p class="p">
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.7.0</code> is released.
+ </p>
+ <p class="p">
+ This is a development release.
+ The <code class="code">0.7</code> development code has gone too long without a formal release tag.
+ This development branch has seen development as far back as <em class="em">August 3, 2022</em> and much of the <code class="code">0.6</code> includes a lot of back ported code from <code class="code">0.7</code>.
+ This release represents a starting point for many planned changes and updates throughout the year.
+ </p>
+ <p class="p">
+ This development code has some design changes that makes the project a little more versatile and extensible but at a cost of slightly larger code.
+ Many of the programs now have a more consistent and modular design that allows for housing multiple related projects in the same code base.
+ Several of the projects have been renamed and simplified into shorter names, such as <code class="code">f_string_range_t</code> now being <code class="code">f_range_t</code>.
+ A new program called <strong class="strong">EKI</strong>, also known as <strong class="strong">Extended IKI</strong>, that handles the <strong class="strong">EKI</strong> specifications is now available.
+ </p>
+ <p class="p">
+ Not everything is implemented or complete, but this is not strictly required for a development release.
+ Most of the library, and the related programs, are tested and confirmed to be working.
+ Projects like <strong class="strong">Controller</strong> and <strong class="strong">Control</strong> are not yet complete.
+ </p>
+ <p class="p">
+ <a id="2025_01_08-fll_0_7_0_release-more" href="news/2025/2025_01_08-fll_0_7_0_release.html" class="content link" aria-labelledby="2025_01_08-fll_0_7_0_release-more 2025_01_08-fll_0_7_0_release-title">Continue reading…</a>
+ </p>
+ </div>
+ </article>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
--- /dev/null
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <title>News - 2025/01/08 - FLL 0.7.0 Release</title>
+
+ <base href="../../">
+
+ <meta charset="UTF-8">
+ <meta name="author" content="Kevin Day">
+ <meta name="description" content="News post on 2025/01/08.">
+ <meta name="keywords" content="Kevin Day, Kevux, FLL, Featureless, Linux, Library, Distribution, Open-Source, News, 2025">
+ <meta name="viewport" content="width=device-width, initial-scale=1.0">
+
+ <link type="text/css" rel="stylesheet" media="all" href="css/kevux.css">
+ <link type="text/css" rel="stylesheet" media="only screen" href="css/kevux-screen.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px)" href="css/kevux-screen-desktop.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:500px)" href="css/kevux-screen-mobile.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:1201px)" href="css/kevux-screen-large.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:501px) and (max-device-width:1200px)" href="css/kevux-screen-normal.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (min-device-width:251px) and (max-device-width:500px)" href="css/kevux-screen-small.css">
+ <link type="text/css" rel="stylesheet" media="only screen and (max-device-width:250px)" href="css/kevux-screen-tiny.css">
+ <link type="text/css" rel="stylesheet" media="only print" href="css/kevux-print.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:landscape)" href="css/kevux-print-landscape.css">
+ <link type="text/css" rel="stylesheet" media="only print and (orientation:portrait)" href="css/kevux-print-portrait.css">
+
+ <link rel="canonical" href="news/2025/2025_01_08-fll_0_7_0_release.html">
+ <link type="image/x-icon" rel="icon" href="images/kevux.ico">
+ <link type="image/x-icon" rel="shortcut" href="images/kevux.ico">
+ <link type="text/html" rel="license" href="licenses.html">
+ <link type="text/html" rel="prev" href="news/2025/2025_01_08-fll_0_7_0_release.html">
+ </head>
+
+ <body id="kevux" class="kevux no-js news">
+ <div role="banner" class="header-block">
+ <header class="header-section header">
+ <div class="header-site">Kevux Systems and Software</div>
+ </header>
+
+ <div class="nav-block">
+ <nav id="kevux-site-nav" class="nav-menu">
+ <div class="nav-item active"><a href="news.html" class="nav-text link">News</a></div>
+ <div class="nav-item"><a href="distributions.html" class="nav-text link">Distributions</a></div>
+ <div class="nav-item"><a href="fll.html" class="nav-text link">FLL</a></div>
+ <div class="nav-item"><a href="projects.html" class="nav-text link">Projects</a></div>
+ <div class="nav-item"><a href="documentation.html" class="nav-text link">Documentation</a></div>
+ </nav>
+ </div>
+ </div>
+
+ <div class="content-block">
+ <div id="nav-expanded" class="nav-block">
+ <nav id="kevux-document-nav" class="nav-menu">
+ <div class="nav-item block back">
+ <a href="news/2025.html" class="nav-text link back">Back</a>
+ </div>
+ <div class="nav-item block highlight unlink">
+ <div class="nav-text notice">2025 / 01 / 08</div>
+ <div class="nav-text unlink">FLL 0.7.0 Release</div>
+ </div>
+ <div class="nav-item block ellipses">
+ <a href="news/2025/2025_01_08-fll_0_7_0_release.html#nav-expanded" class="nav-text link open" title="Expand Menu">…</a>
+ <a href="news/2025/2025_01_08-fll_0_7_0_release.html" class="nav-text link close">Collapse Menu</a>
+ </div>
+ </nav>
+ </div>
+
+ <div role="document" class="main-block">
+ <main class="main">
+ <header class="section-header header">
+ <h1 class="section-title h h1">2025 / 01 / 08 - FLL 0.7.0 Release</h1>
+ </header>
+
+ <div class="main-content">
+ <p class="p">
+ The <strong class="strong">Featureless Linux Library</strong> stable version <code class="code">0.7.0</code> is released.
+ </p>
+ <p class="p">
+ This is a development release.
+ The <code class="code">0.7</code> development code has gone too long without a formal release tag.
+ This development branch has seen development as far back as <em class="em">August 3, 2022</em> and much of the <code class="code">0.6</code> includes a lot of back ported code from <code class="code">0.7</code>.
+ This release represents a starting point for many planned changes and updates throughout the year.
+ </p>
+ <p class="p">
+ This development code has some design changes that makes the project a little more versatile and extensible but at a cost of slightly larger code.
+ Many of the programs now have a more consistent and modular design that allows for housing multiple related projects in the same code base.
+ Several of the projects have been renamed and simplified into shorter names, such as <code class="code">f_string_range_t</code> now being <code class="code">f_range_t</code>.
+ A new program called <strong class="strong">EKI</strong>, also known as <strong class="strong">Extended IKI</strong>, that handles the <strong class="strong">EKI</strong> specifications is now available.
+ </p>
+ <p class="p">
+ Not everything is implemented or complete, but this is not strictly required for a development release.
+ Most of the library, and the related programs, are tested and confirmed to be working.
+ Projects like <strong class="strong">Controller</strong> and <strong class="strong">Control</strong> are not yet complete.
+ </p>
+ <p class="p">
+ Many of the stand alone builds are not created yet, however, a few core programs have the stand alone build provided.
+ The stand alone build settings will be created later on as they simply do not need to be ready just yet.
+ It is much easier to configure the stand alone build settings once the <abbr title="Application Programming Interface">API</abbr> has stabilized more.
+ The programs have improved support for the <em class="em">programs as libraries</em> design.
+ </p>
+ <p class="p">
+ This development release helps pave the way for focusing on external projects like <strong class="strong">TacocaT</strong> and <strong class="strong">Kevux Tools</strong>.
+ There will be a huge focus on network related functionality, which is what is needed to help wrap up <strong class="strong">Controller</strong> and <strong class="strong">Control</strong>.
+ The <strong class="strong">Featureless Make</strong> and the <strong class="strong">Controller</strong> programs will likely see updates to their specifications which will result in new features added to the <code class="code">0.7</code> code.
+ The <strong class="strong">IKI Read</strong> and <strong class="strong">IKI Write</strong> are seeing additional changes as the project and its websites will eventually be templated out into a structure based around the <strong class="strong">IKI</strong> and <strong class="strong">EKI</strong> specifications.
+ </p>
+ <p class="p">
+ Ideally, by the end of the year or the start of the next year the may be a <code class="code">0.8.0</code> release.
+ When that happens, the <code class="code">0.9</code> development will be on hold for a while because that development cycle will be focused on design improvements, performance iprovements, and stabilization of all of the standards, specifications, improved error handling, and <abbr title="Application Programming Interfaces">APIs</abbr>.
+ Therefore, the <code class="code">0.8</code> could be considered a <code class="code">1.0</code> release candidate.
+ The development of the <code class="code">0.7</code> will therefore be focused on making a production ready product.
+ </p>
+ <p class="p">
+ Check out the project on the <a href="fll.html#release" class="link"><abbr title="Featureless Linux Library">FLL</abbr> release</a> page.
+ </p>
+ <p class="p">
+ The project is built like a tool chest.
+ Individuals who are unfamiliar with the project should have an easier time trying out the pre-packaged <a href="https://sourceforge.net/projects/fll/files/FLL-0.7/0.7.0/monolithic/" class="link external">monolithic sources</a>.
+ These <a href="https://sourceforge.net/projects/fll/files/FLL-0.7/0.7.0/programs/" class="link external">programs</a>, by default, are designed to build against a library built using the monolithic source tree.
+ </p>
+ <p class="p">
+ The <strong class="strong">stand alone</strong> sources for the several programs can be found <a href="https://sourceforge.net/projects/fll/files/FLL-0.7/0.7.0/stand_alone/" class="link external">pre-packaged at Sourceforge</a>.
+ </p>
+ <p class="p">
+ <strong class="strong">Kevin Day</strong>
+ </p>
+ </div>
+ </main>
+ </div>
+ </div>
+ </body>
+</html>
projects / kevux.org-website / commitdiff