Publish on Δευ 12 Αυγ 2024 10:25:32 πμ EEST

Salix-OS · Aug 12, 2024 · 092f7f8 · 092f7f8
1 parent a00fcff
commit 092f7f8
Show file tree

Hide file tree

Showing 17 changed files with 554 additions and 92 deletions.
diff --git a/index.html b/index.html
@@ -106,6 +106,27 @@
         <div id="content" class="content">
           <section id="posts" class="posts">
     <article class="post">
+  <header class="post-header">
+    <h1 class="post-title"><a class="post-link" href="/post/new-docs-site/">New Documentation Site</a></h1>
+    <div class="post-meta">
+      <span class="post-time"> 2024-08-12 </span>
+
+    </div>
+  </header>
+
+  <div class="post-content">
+    <div class="post-summary">
+      I&rsquo;ve been wanting to do this for a long time. I first started working on it five years ago!
+A bit of history first… When we were trying to build the Salix presence on the web, we knew we had to have at least three things:
+A main landing page A support forum A documentation project For the forum, we had settled on phpbb, which seemed to be the most feature-rich option.
+    </div>
+    <div class="read-more">
+      <a href="/post/new-docs-site/" class="read-more-link">Read more...</a>
+    </div>
+  </div>
+</article>
+
+    <article class="post">
   <header class="post-header">
     <h1 class="post-title"><a class="post-link" href="/post/salix-on-gemini/">Salix is on Gemini</a></h1>
     <div class="post-meta">
@@ -184,29 +205,6 @@ <h1 class="post-title"><a class="post-link" href="/post/just-a-little-teaser/">J
   </div>
 </article>
 
-    <article class="post">
-  <header class="post-header">
-    <h1 class="post-title"><a class="post-link" href="/post/are-we-there-yet/">Are We There Yet?</a></h1>
-    <div class="post-meta">
-      <span class="post-time"> 2022-02-15 </span>
-
-    </div>
-  </header>
-
-  <div class="post-content">
-    <div class="post-summary">
-      Short answer: No.
-Somewhat longer answer: Not yet, but we&rsquo;re getting there. There&rsquo;s still lot&rsquo;s of things to do, but there will be an alpha release soon (hopefully).
-Really long answer:
-It has been almost two weeks now that Slackware 15.0 has been released (yay!) and there are now regular inquiries on IRC and in the forums concerning the release of Salix 15.0.
-So, no, Salix 15.0 is not ready yet.
-    </div>
-    <div class="read-more">
-      <a href="/post/are-we-there-yet/" class="read-more-link">Read more...</a>
-    </div>
-  </div>
-</article>
-
     </section>
 
   <nav class="pagination">

diff --git a/page/2/index.html b/page/2/index.html
@@ -106,6 +106,29 @@
         <div id="content" class="content">
           <section id="posts" class="posts">
     <article class="post">
+  <header class="post-header">
+    <h1 class="post-title"><a class="post-link" href="/post/are-we-there-yet/">Are We There Yet?</a></h1>
+    <div class="post-meta">
+      <span class="post-time"> 2022-02-15 </span>
+
+    </div>
+  </header>
+
+  <div class="post-content">
+    <div class="post-summary">
+      Short answer: No.
+Somewhat longer answer: Not yet, but we&rsquo;re getting there. There&rsquo;s still lot&rsquo;s of things to do, but there will be an alpha release soon (hopefully).
+Really long answer:
+It has been almost two weeks now that Slackware 15.0 has been released (yay!) and there are now regular inquiries on IRC and in the forums concerning the release of Salix 15.0.
+So, no, Salix 15.0 is not ready yet.
+    </div>
+    <div class="read-more">
+      <a href="/post/are-we-there-yet/" class="read-more-link">Read more...</a>
+    </div>
+  </div>
+</article>
+
+    <article class="post">
   <header class="post-header">
     <h1 class="post-title"><a class="post-link" href="/post/preparing-for-15.0/">Preparing for 15.0</a></h1>
     <div class="post-meta">
@@ -184,26 +207,6 @@ <h1 class="post-title"><a class="post-link" href="/post/new-blog/">New blog site
   </div>
 </article>
 
-    <article class="post">
-  <header class="post-header">
-    <h1 class="post-title"><a class="post-link" href="/post/our-new-extra-repository/">Our new extra repository</a></h1>
-    <div class="post-meta">
-      <span class="post-time"> 2016-10-09 </span>
-
-    </div>
-  </header>
-
-  <div class="post-content">
-    <div class="post-summary">
-      You might have noticed that just before the Salix Xfce 14.2RC1 release a new repository, named extra-14.2 has appeared in our servers. This has been enabled by default in the 14.2RC1 and 14.2RC2 releases and will be also available in the final 14.2 release.
-This new repository is present for both i486 and x86_64 architectures and its purpose it to include packages built from SlackBuilds found at slackbuilds.org. At this moment, it&rsquo;s not that full, only about 20 packages are included in it.
-    </div>
-    <div class="read-more">
-      <a href="/post/our-new-extra-repository/" class="read-more-link">Read more...</a>
-    </div>
-  </div>
-</article>
-
     </section>
 
   <nav class="pagination">

diff --git a/page/3/index.html b/page/3/index.html
@@ -106,6 +106,26 @@
         <div id="content" class="content">
           <section id="posts" class="posts">
     <article class="post">
+  <header class="post-header">
+    <h1 class="post-title"><a class="post-link" href="/post/our-new-extra-repository/">Our new extra repository</a></h1>
+    <div class="post-meta">
+      <span class="post-time"> 2016-10-09 </span>
+
+    </div>
+  </header>
+
+  <div class="post-content">
+    <div class="post-summary">
+      You might have noticed that just before the Salix Xfce 14.2RC1 release a new repository, named extra-14.2 has appeared in our servers. This has been enabled by default in the 14.2RC1 and 14.2RC2 releases and will be also available in the final 14.2 release.
+This new repository is present for both i486 and x86_64 architectures and its purpose it to include packages built from SlackBuilds found at slackbuilds.org. At this moment, it&rsquo;s not that full, only about 20 packages are included in it.
+    </div>
+    <div class="read-more">
+      <a href="/post/our-new-extra-repository/" class="read-more-link">Read more...</a>
+    </div>
+  </div>
+</article>
+
+    <article class="post">
   <header class="post-header">
     <h1 class="post-title"><a class="post-link" href="/post/our-sbo-mirrors/">Our SBo mirrors</a></h1>
     <div class="post-meta">
@@ -184,25 +204,6 @@ <h1 class="post-title"><a class="post-link" href="/post/kernel-decisions/">Kerne
   </div>
 </article>
 
-    <article class="post">
-  <header class="post-header">
-    <h1 class="post-title"><a class="post-link" href="/post/the-gksu-problem/">The gksu problem</a></h1>
-    <div class="post-meta">
-      <span class="post-time"> 2013-11-13 </span>
-
-    </div>
-  </header>
-
-  <div class="post-content">
-    <div class="post-summary">
-      We had a real problem with ktsuss/gksu while developing for 14.1. It seems that newer versions of the shadow package, and certainly the one that is included in Slackware 14.1, don&rsquo;t allow su to be executed in any other way except directly from a terminal. That means that su cannot be executed as a subprocess from inside ktsuss or the original gksu anymore and these become effectively useless. This is a critical issue for us, because if we don&rsquo;t fix it, almost nothing in the System part of the menu would actually work.
-    </div>
-    <div class="read-more">
-      <a href="/post/the-gksu-problem/" class="read-more-link">Read more...</a>
-    </div>
-  </div>
-</article>
-
     </section>
 
   <nav class="pagination">

diff --git a/page/4/index.html b/page/4/index.html
@@ -106,6 +106,25 @@
         <div id="content" class="content">
           <section id="posts" class="posts">
     <article class="post">
+  <header class="post-header">
+    <h1 class="post-title"><a class="post-link" href="/post/the-gksu-problem/">The gksu problem</a></h1>
+    <div class="post-meta">
+      <span class="post-time"> 2013-11-13 </span>
+
+    </div>
+  </header>
+
+  <div class="post-content">
+    <div class="post-summary">
+      We had a real problem with ktsuss/gksu while developing for 14.1. It seems that newer versions of the shadow package, and certainly the one that is included in Slackware 14.1, don&rsquo;t allow su to be executed in any other way except directly from a terminal. That means that su cannot be executed as a subprocess from inside ktsuss or the original gksu anymore and these become effectively useless. This is a critical issue for us, because if we don&rsquo;t fix it, almost nothing in the System part of the menu would actually work.
+    </div>
+    <div class="read-more">
+      <a href="/post/the-gksu-problem/" class="read-more-link">Read more...</a>
+    </div>
+  </div>
+</article>
+
+    <article class="post">
   <header class="post-header">
     <h1 class="post-title"><a class="post-link" href="/post/how-much-of-slackware-is-in-salix/">How much of Slackware is in Salix</a></h1>
     <div class="post-meta">

diff --git a/post/index.html b/post/index.html
@@ -110,6 +110,17 @@
         <h2 class="archive-year">2024</h2>
       </div>
 
+    <div class="archive-post">
+      <span class="archive-post-time">
+        08-12
+      </span>
+      <span class="archive-post-title">
+        <a href="/post/new-docs-site/" class="archive-post-link">
+          New Documentation Site
+        </a>
+      </span>
+    </div>
+
     <div class="archive-post">
       <span class="archive-post-time">
         08-06
@@ -222,20 +233,6 @@ <h2 class="archive-year">2018</h2>
           New blog site
         </a>
       </span>
-    </div>
-      <div class="collection-title">
-        <h2 class="archive-year">2016</h2>
-      </div>
-
-    <div class="archive-post">
-      <span class="archive-post-time">
-        10-09
-      </span>
-      <span class="archive-post-title">
-        <a href="/post/our-new-extra-repository/" class="archive-post-link">
-          Our new extra repository
-        </a>
-      </span>
     </div></section>
 
 <nav class="pagination">

diff --git a/post/index.xml b/post/index.xml
@@ -6,7 +6,18 @@
     <description>Recent content in Posts on The Salix Blog</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en</language>
-    <lastBuildDate>Tue, 06 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.salixos.org/post/index.xml" rel="self" type="application/rss+xml" />
+    <lastBuildDate>Mon, 12 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.salixos.org/post/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>New Documentation Site</title>
+      <link>https://blog.salixos.org/post/new-docs-site/</link>
+      <pubDate>Mon, 12 Aug 2024 00:00:00 +0000</pubDate>
+
+      <guid>https://blog.salixos.org/post/new-docs-site/</guid>
+      <description>I&amp;rsquo;ve been wanting to do this for a long time. I first started working on it five years ago!
+A bit of history first… When we were trying to build the Salix presence on the web, we knew we had to have at least three things:
+A main landing page A support forum A documentation project For the forum, we had settled on phpbb, which seemed to be the most feature-rich option.</description>
+    </item>
+
     <item>
       <title>Salix is on Gemini</title>
       <link>https://blog.salixos.org/post/salix-on-gemini/</link>