diff --git a/docs/index.txt b/docs/index.txt
index 9d8097a..6635bc7 100644
--- a/docs/index.txt
+++ b/docs/index.txt
@@ -60,26 +60,30 @@ News
[RSS Feed](/news.xml) | [See all news](/news.html)
-### Jun 17 2020
+Jun 17 2020
+--------------------------------------------------------------------------------
A new rootfs tarball including the changes to the core is released and can be
found on the downloads page.
-### May 26 2020
+May 26 2020
+--------------------------------------------------------------------------------
An initial version for binary package management is released.
It can be found on the [GitHub page].
[GitHub page]: https://github.com/CarbsLinux/kiss-bin
-### May 19 2020
+May 19 2020
+--------------------------------------------------------------------------------
A rootfs tarball targeting the i686 architecture has
been released. It can be found on the [downloads page]
[downloads page]: https://dl.carbslinux.org/releases/i686
-### May 10 2020
+May 10 2020
+--------------------------------------------------------------------------------
A GCC 10.1.0 change causes a kernel panic for kernels built
with GCC 10.1. This issue can be resolved by applying this
@@ -87,7 +91,8 @@ with GCC 10.1. This issue can be resolved by applying this
[patch]: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22
-### Apr 27 2020
+Apr 27 2020
+--------------------------------------------------------------------------------
A new rootfs tarball has been released! You can
see it on !
diff --git a/docs/mailing-lists.html b/docs/mailing-lists.html
index 63476bc..c74f9ae 100644
--- a/docs/mailing-lists.html
+++ b/docs/mailing-lists.html
@@ -2,7 +2,7 @@
Mailing Lists | Carbs Linux
-
+
diff --git a/docs/news.html b/docs/news.html
index 92271d0..9ad57c9 100644
--- a/docs/news.html
+++ b/docs/news.html
@@ -2,7 +2,7 @@
news | Carbs Linux
-
+
diff --git a/docs/news.txt b/docs/news.txt
index 3a6ed12..91b1ce8 100644
--- a/docs/news.txt
+++ b/docs/news.txt
@@ -1,12 +1,12 @@
Jun 17 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball including the changes to the core is released and can be
found on the downloads page.
May 26 2020
------------
+--------------------------------------------------------------------------------
An initial version for binary package management is released.
It can be found on the [GitHub page].
@@ -14,7 +14,7 @@ It can be found on the [GitHub page].
[GitHub page]: https://github.com/CarbsLinux/kiss-bin
May 19 2020
------------
+--------------------------------------------------------------------------------
A rootfs tarball targeting the i686 architecture has
been released. It can be found on the [downloads page]
@@ -22,7 +22,7 @@ been released. It can be found on the [downloads page]
[downloads page]: https://dl.carbslinux.org/releases/i686
May 10 2020
------------
+--------------------------------------------------------------------------------
A GCC 10.1.0 change causes a kernel panic for kernels built
with GCC 10.1. This issue can be resolved by applying this
@@ -31,7 +31,7 @@ with GCC 10.1. This issue can be resolved by applying this
[patch]: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22
Apr 27 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball has been released! You can
see it on !
@@ -39,18 +39,18 @@ see it on !
**EDIT:** A new bug fix release has been made.
Apr 10 2020
------------
+--------------------------------------------------------------------------------
IRC channel can now be accessed from `#carbslinux` at freenode!
Apr 06 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball has been released. See the
[downloads](https://dl.carbslinux.org) page
Apr 05 2020
------------
+--------------------------------------------------------------------------------
Carbs Linux repositories will be hosted only on Github. Commits will be
pushed there, and not the repository. You have until
@@ -65,7 +65,7 @@ repository directory.
Feb 18 2020
------------
+--------------------------------------------------------------------------------
A new tarball is released. It can be found on .
@@ -77,7 +77,7 @@ changes on Busybox.
Feb 14 2020
------------
+--------------------------------------------------------------------------------
**IMPORTANT!** Carbs-init update to be released on 17th of February
will require manual intervention. I am holding this update back so
@@ -130,7 +130,7 @@ This is a Quality of Life update.
Feb 13 2020
------------
+--------------------------------------------------------------------------------
Runit is now released on the core repository! You can now replace
busybox-init with runit-init. You can also replace the busybox runit
@@ -138,7 +138,7 @@ utilities with the actual runit. This will reduce the dependency on
busybox greatly.
Jan 28 2020
------------
+--------------------------------------------------------------------------------
Web Server is now on a Carbs Linux server. It is not complete yet,
but I will be adding a little more for the intended functionality.
@@ -150,20 +150,20 @@ UPDATE2: downloads are back again.
Jan 22 2020
------------
+--------------------------------------------------------------------------------
Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating
this web server to my Carbs Linux server!
Jan 15 2020
------------
+--------------------------------------------------------------------------------
sinit has been taken to `core`, and is now officially supported
Jan 13 2020
------------
+--------------------------------------------------------------------------------
**Busybox update reqires manual intervention**
@@ -183,13 +183,13 @@ I have moved runit and logging utilities from the busybox-init package to the bu
package, which is the cause of these conflicts.
Jan 10 2020
------------
+--------------------------------------------------------------------------------
carbs-rootfs-20200110.tar.xz was [released](//dl.carbslinux.org/releases)
Jan 09 2020
------------
+--------------------------------------------------------------------------------
Happy new year, everyone! I am back after some long silence. I was unable to commit for a
while, but I have pulled some new updates from the KISS repository, added some of my own.
@@ -204,19 +204,19 @@ Important things are,
Dec 18 2019
------------
+--------------------------------------------------------------------------------
carbs-rootfs-20191218.tar.xz was [released](//dl.carbslinux.org/releases)
Dec 17 2019
------------
+--------------------------------------------------------------------------------
Installation instruction are now complete. A review would be greatly appreciated!
Dec 15 2019
------------
+--------------------------------------------------------------------------------
Carbs Linux Wiki is now available to be edited and updated by the users go
to the [wiki](//carbslinux.org/wiki) to obtain more information.
@@ -225,14 +225,14 @@ to the [wiki](//carbslinux.org/wiki) to obtain more information.
Dec 12 2019
------------
+--------------------------------------------------------------------------------
Busybox and Busybox-init has been seperated into two different packages.
This is for adding standalone runit/runit-init to the repositories.
Dec 10 2019
------------
+--------------------------------------------------------------------------------
First alpha release was made. See the [downloads page](//dl.carbslinux.org/releases).
diff --git a/docs/news.xml b/docs/news.xml
index b481bc4..4ca82dd 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -9,71 +9,87 @@
a simple busybox linux distribution
https://carbslinux.org
-Jun Wed 2020 14:00
+Jun Sat 2020 20:00
-20200617.news
+Jun 17 2020Wed, 17 Jun 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A new rootfs tarball including the changes to the core is released and can be
+<h2>Jun 17 2020</h2>
+
+<p>A new rootfs tarball including the changes to the core is released and can be
found on the downloads page.</p>
-20200526.news
+May 26 2020Tue, 26 May 2020Cem Keylan
https://carbslinux.org/index.html
-<p>An initial version for binary package management is released.
+<h2>May 26 2020</h2>
+
+<p>An initial version for binary package management is released.
It can be found on the <a href="https://github.com/CarbsLinux/kiss-bin">GitHub page</a>.</p>
-20200519.news
+May 19 2020Tue, 19 May 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A rootfs tarball targeting the i686 architecture has
+<h2>May 19 2020</h2>
+
+<p>A rootfs tarball targeting the i686 architecture has
been released. It can be found on the <a href="https://dl.carbslinux.org/releases/i686">downloads page</a></p>
-20200510.news
+May 10 2020Sun, 10 May 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A GCC 10.1.0 change causes a kernel panic for kernels built
+<h2>May 10 2020</h2>
+
+<p>A GCC 10.1.0 change causes a kernel panic for kernels built
with GCC 10.1. This issue can be resolved by applying this
<a href="https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22">patch</a> to your kernel sources.</p>
-20200427.news
+Apr 27 2020Mon, 27 Apr 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A new rootfs tarball has been released! You can
+<h2>Apr 27 2020</h2>
+
+<p>A new rootfs tarball has been released! You can
see it on <a href="https://dl.carbslinux.org/releases">https://dl.carbslinux.org/releases</a>!</p>
<p><strong>EDIT:</strong> A new bug fix release has been made.</p>
-20200410.news
+Apr 10 2020Fri, 10 Apr 2020Cem Keylan
https://carbslinux.org/index.html
-<p>IRC channel can now be accessed from <code>#carbslinux</code> at freenode!</p>
+<h2>Apr 10 2020</h2>
+
+<p>IRC channel can now be accessed from <code>#carbslinux</code> at freenode!</p>
-20200406.news
+Apr 06 2020Mon, 06 Apr 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A new rootfs tarball has been released. See the
+<h2>Apr 06 2020</h2>
+
+<p>A new rootfs tarball has been released. See the
<a href="https://dl.carbslinux.org">downloads</a> page</p>
-20200405.news
+Apr 05 2020Sun, 05 Apr 2020Cem Keylan
https://carbslinux.org/index.html
-<p>Carbs Linux repositories will be hosted only on Github. Commits will be
+<h2>Apr 05 2020</h2>
+
+<p>Carbs Linux repositories will be hosted only on Github. Commits will be
pushed there, and not the repository. You have until
May 4, 2020 Monday to switch your remotes to <a href="https://github.com/CarbsLinux/repository">https://github.com/CarbsLinux/repository</a>.
The git repository will continue to be served until then (without additional
@@ -86,11 +102,13 @@ repository directory.</p>
</code></pre>
-20200218.news
+Feb 18 2020Tue, 18 Feb 2020Cem Keylan
https://carbslinux.org/index.html
-<p>A new tarball is released. It can be found on <a href="https://dl.carbslinux.org">https://dl.carbslinux.org</a>.</p>
+<h2>Feb 18 2020</h2>
+
+<p>A new tarball is released. It can be found on <a href="https://dl.carbslinux.org">https://dl.carbslinux.org</a>.</p>
<p><strong>edit:</strong> I have removed the tarball because of a bootstrapping issue.
I will be re-adding it later today.</p>
@@ -99,11 +117,13 @@ I will be re-adding it later today.</p>
changes on Busybox.</p>
-20200214.news
+Feb 14 2020Fri, 14 Feb 2020Cem Keylan
https://carbslinux.org/index.html
-<p><strong>IMPORTANT!</strong> Carbs-init update to be released on 17th of February
+<h2>Feb 14 2020</h2>
+
+<p><strong>IMPORTANT!</strong> Carbs-init update to be released on 17th of February
will require manual intervention. I am holding this update back so
people can see it before they update their system (even though the
update will show the same message as this). The rationale for the
@@ -154,21 +174,25 @@ and constantly testing those init providers, a huge nightmare for me.
This is a Quality of Life update.</p>
-20200213.news
+Feb 13 2020Thu, 13 Feb 2020Cem Keylan
https://carbslinux.org/index.html
-<p>Runit is now released on the core repository! You can now replace
+<h2>Feb 13 2020</h2>
+
+<p>Runit is now released on the core repository! You can now replace
busybox-init with runit-init. You can also replace the busybox runit
utilities with the actual runit. This will reduce the dependency on
busybox greatly.</p>
-20200128.news
+Jan 28 2020Tue, 28 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p>Web Server is now on a Carbs Linux server. It is not complete yet,
+<h2>Jan 28 2020</h2>
+
+<p>Web Server is now on a Carbs Linux server. It is not complete yet,
but I will be adding a little more for the intended functionality.
Downtimes can be expected.</p>
@@ -177,26 +201,32 @@ Downtimes can be expected.</p>
<p>UPDATE2: downloads are back again.</p>
-20200122.news
+Jan 22 2020Wed, 22 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p>Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating
+<h2>Jan 22 2020</h2>
+
+<p>Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating
this web server to my Carbs Linux server!</p>
-20200115.news
+Jan 15 2020Wed, 15 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p>sinit has been taken to <code>core</code>, and is now officially supported</p>
+<h2>Jan 15 2020</h2>
+
+<p>sinit has been taken to <code>core</code>, and is now officially supported</p>
-20200113.news
+Jan 13 2020Mon, 13 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p><strong>Busybox update reqires manual intervention</strong></p>
+<h2>Jan 13 2020</h2>
+
+<p><strong>Busybox update reqires manual intervention</strong></p>
<p>The new busybox package conflicts with the pre-update busybox-init. That’s why
you should rebuild and install <code>busybox-init</code> before doing the update.</p>
@@ -215,18 +245,22 @@ $ kiss u
package, which is the cause of these conflicts.</p>
-20200110.news
+Jan 10 2020Fri, 10 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p>carbs-rootfs-20200110.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
+<h2>Jan 10 2020</h2>
+
+<p>carbs-rootfs-20200110.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
-20200109.news
+Jan 09 2020Thu, 09 Jan 2020Cem Keylan
https://carbslinux.org/index.html
-<p>Happy new year, everyone! I am back after some long silence. I was unable to commit for a
+<h2>Jan 09 2020</h2>
+
+<p>Happy new year, everyone! I am back after some long silence. I was unable to commit for a
while, but I have pulled some new updates from the KISS repository, added some of my own.
This week I will be changing/adding some things.</p>
@@ -240,43 +274,53 @@ This week I will be changing/adding some things.</p>
</ul>
-20191218.news
+Dec 18 2019Wed, 18 Dec 2019Cem Keylan
https://carbslinux.org/index.html
-<p>carbs-rootfs-20191218.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
+<h2>Dec 18 2019</h2>
+
+<p>carbs-rootfs-20191218.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
-20191217.news
+Dec 17 2019Tue, 17 Dec 2019Cem Keylan
https://carbslinux.org/index.html
-<p>Installation instruction are now complete. A review would be greatly appreciated!</p>
+<h2>Dec 17 2019</h2>
+
+<p>Installation instruction are now complete. A review would be greatly appreciated!</p>
-20191215.news
+Dec 15 2019Sun, 15 Dec 2019Cem Keylan
https://carbslinux.org/index.html
-<p>Carbs Linux Wiki is now available to be edited and updated by the users go
+<h2>Dec 15 2019</h2>
+
+<p>Carbs Linux Wiki is now available to be edited and updated by the users go
to the <a href="//carbslinux.org/wiki">wiki</a> to obtain more information.</p>
<p><strong>February 2020 EDIT:</strong> Changed link for wiki</p>
-20191212.news
+Dec 12 2019Thu, 12 Dec 2019Cem Keylan
https://carbslinux.org/index.html
-<p>Busybox and Busybox-init has been seperated into two different packages.
+<h2>Dec 12 2019</h2>
+
+<p>Busybox and Busybox-init has been seperated into two different packages.
This is for adding standalone runit/runit-init to the repositories.</p>
-20191210.news
+Dec 10 2019Tue, 10 Dec 2019Cem Keylan
https://carbslinux.org/index.html
-<p>First alpha release was made. See the <a href="//dl.carbslinux.org/releases">downloads page</a>.</p>
+<h2>Dec 10 2019</h2>
+
+<p>First alpha release was made. See the <a href="//dl.carbslinux.org/releases">downloads page</a>.</p>
diff --git a/docs/people.html b/docs/people.html
index 7e9cfe1..dac1b57 100644
--- a/docs/people.html
+++ b/docs/people.html
@@ -2,7 +2,7 @@
People | Carbs Linux
-
+
diff --git a/docs/rss.xml b/docs/rss.xml
index ba63e5e..5788d02 100644
--- a/docs/rss.xml
+++ b/docs/rss.xml
@@ -9,7 +9,7 @@
a simple busybox linux distribution
https://carbslinux.org
-Jun Wed 2020 14:00
+Jun Sat 2020 20:00June NewspostWed, 17 Jun 2020
diff --git a/docs/style.css b/docs/style.css
new file mode 100644
index 0000000..d3de079
--- /dev/null
+++ b/docs/style.css
@@ -0,0 +1,115 @@
+/* Cem Keylan (C) 2019 */
+
+:root {
+ --color0: #0A1E2B;
+ --color1: #5C5B6F;
+ --color2: #9B506D;
+ --color3: #C34266;
+ --color4: #7B9BB7;
+ --color5: #BF6790;
+ --color6: #6a9faf;
+ --color7: #A676D2;
+ --color8: #8b8288;
+ --color9: #5C5B6F;
+ --color10: #9B506D;
+ --color11: #C34266;
+ --color12: #4E708D;
+ --color13: #BF6790;
+ --color14: #528899;
+ --color15: #c7bac3;
+ --fg: #0a1e2b;
+ --bg: #ffffff;
+ --altbg: #bf6790;
+ --link: #bf6790;
+ --linkalt: #4e708d;
+}
+
+
+html {
+ background-color: var(--bg);
+ font-family: sans-serif;
+ color: var(--fg);
+ padding-bottom: 100px;
+ -webkit-text-size-adjust: 100%;
+ -ms-text-size-adjust: 100%;
+ -ms-overflow-style: scrollbar;
+ -webkit-tap-highlight-color: transparent;
+}
+.header {
+ text-align: center;
+}
+.header strong{
+ color: var(--color5)
+}
+.header a{
+ text-decoration: none;
+ text-align: center;
+ color: var(--fg);
+ margin-left: 10px;
+ margin-right: 10px;
+}
+.header a:hover{
+ text-decoration: none;
+ text-align: center;
+ color: var(--linkalt);
+ margin-left: 10px;
+ margin-right: 10px;
+}
+.border {
+ padding-top: 1%;
+ border-bottom: solid 2px;
+ color: var(--fg);
+}
+a {
+ text-decoration: none;
+ font-weight: bold;
+ color: var(--link);
+}
+a:hover {
+ text-decoration: underline;
+ font-weight: bold;
+ color: var(--linkalt);
+}
+.post-title {
+ text-align: center;
+}
+ul li::before {
+ color: var(--color4);
+}
+body {
+ width: 80%;
+ max-width: 1050px;
+ margin-left: auto;
+ margin-right: auto;
+ margin-top: 20px;
+ overflow: none;
+ padding-right: 10px;
+ padding-left: 10px;
+ color: var(--fg);
+}
+code {
+ color: var(--fg);
+ content: "> ";
+}
+p,tr,td,table { color: var(--fg); }
+h1 {
+ color: var(--color7);
+ font-weight: bolder;
+}
+h2 {
+ color: var(--color4);
+ font-weight: bold;
+}
+h3 {
+ color: var(--fg);
+ font-weight: bold;
+}
+.footer {
+ text-align: center;
+}
+
+pre { margin-left: 2em; }
+blockquote {
+ border-left: 1px solid var(--color6);
+ font-style: italic;
+}
diff --git a/docs/wiki/boot/module-management.html b/docs/wiki/boot/module-management.html
deleted file mode 100644
index a77685d..0000000
--- a/docs/wiki/boot/module-management.html
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
-Module Management | Carbs Linux
-
-
-
-
-
-
Carbs Linux - a simple busybox linux distribution
-
-
Module Management
-
-
With busybox-init, a module can be loaded at boot by adding such a line to your inittab
-
-
::once:/bin/modprobe module-name
-
-
-
With sinit, a module can be loaded from your /etc/rc.local file. Add this to your file
-
-
diff --git a/docs/wiki/boot/module-management.txt b/docs/wiki/boot/module-management.txt
deleted file mode 100644
index 96256c1..0000000
--- a/docs/wiki/boot/module-management.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Module Management
-=================
-
-With **busybox-init**, a module can be loaded at boot by adding such a line to your `inittab`
-
- ::once:/bin/modprobe module-name
-
-
-With **sinit**, a module can be loaded from your `/etc/rc.local` file. Add this to your file
-
- /bin/modprobe module-name
-
-
diff --git a/docs/wiki/index.html b/docs/wiki/index.html
deleted file mode 100644
index 10843fb..0000000
--- a/docs/wiki/index.html
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
-Wiki | Carbs Linux
-
-
-
-
-
-
Carbs Linux - a simple busybox linux distribution
-
-
Wiki
-
-
Welcome to the Carbs Linux wiki! This wiki is open for access, and can be edited
-freely by anyone who wants to contribute.
-
-
diff --git a/docs/wiki/index.txt b/docs/wiki/index.txt
deleted file mode 100644
index 3d64de9..0000000
--- a/docs/wiki/index.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-Wiki
-================================================================================
-
-Welcome to the Carbs Linux wiki! This wiki is open for access, and can be edited
-freely by anyone who wants to contribute.
-
-If you want to make a contribution, go to
-
-Content
---------------------------------------------------------------------------------
-
-* [Module Management](boot/module-management.html)
-* [Switching to Sinit](init/switching-to-sinit.html)
-* [Install](install.html)
-* [X-keymaps](keymaps/X-keymaps.html)
-* [Keymaps in TTY](keymaps/keymaps.html)
-* [Service Management](system/service-management.html)
diff --git a/docs/wiki/init/switching-to-sinit.html b/docs/wiki/init/switching-to-sinit.html
deleted file mode 100644
index 775e01c..0000000
--- a/docs/wiki/init/switching-to-sinit.html
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
-Switching to Sinit | Carbs Linux
-
-
-
-
-
-
Carbs Linux - a simple busybox linux distribution
-
-
Switching to Sinit
-
-
Carbs Linux runs busybox-init by default. You can switch to
-anything else you desire, but only busybox-init and sinit are
-officially supported. Switching to sinit is extremely easy, you
-can be up and running within minutes. The only “hard” requirement
-is an environment you will be chrooting in. So, let’s begin!
-
-
Preparing your environment
-
-
From your other environment, download the kiss-chroot utility
-and make it executable.
-
-
$ wget https://dl.getkiss.org/kiss-chroot
-$ chmod +x kiss-chroot
-
-# From your environment start the chroot
-$ kiss-chroot /mnt
-
-
-
Removing busybox-init
-
-
Now that we are in chroot environment, let’s remove busybox-init.
-
-
$ kiss r busybox-init
-
-
-
Installing and configuring sinit
-
-
Build and install sinit
-
-
$ kiss b sinit
-$ kiss i sinit
-
-
-
Open up your /etc/init/rc.conf now and uncomment
-the variables regarding SINIT. You are ready now.
-
-
If you edited your inittab, make sure you reflect your changes
-on the /etc/init/sinit-launch-services.boot file.
-
-
Finishing up
-
-
If all of the above is done, simply exit the chroot and reboot.
-Sinit should be functioning without any issues.
-
-
diff --git a/docs/wiki/init/switching-to-sinit.txt b/docs/wiki/init/switching-to-sinit.txt
deleted file mode 100644
index 3bee312..0000000
--- a/docs/wiki/init/switching-to-sinit.txt
+++ /dev/null
@@ -1,51 +0,0 @@
-
-Switching to Sinit
-==================
-
-Carbs Linux runs `busybox-init` by default. You can switch to
-anything else you desire, but only busybox-init and sinit are
-officially supported. Switching to sinit is extremely easy, you
-can be up and running within minutes. The only "hard" requirement
-is an environment you will be chrooting in. So, let's begin!
-
-
-Preparing your environment
---------------------------
-
-From your other environment, download the kiss-chroot utility
-and make it executable.
-
- $ wget https://dl.getkiss.org/kiss-chroot
- $ chmod +x kiss-chroot
-
- # From your environment start the chroot
- $ kiss-chroot /mnt
-
-Removing busybox-init
----------------------
-
-Now that we are in chroot environment, let's remove busybox-init.
-
- $ kiss r busybox-init
-
-
-Installing and configuring sinit
---------------------------------
-
-Build and install sinit
-
- $ kiss b sinit
- $ kiss i sinit
-
-Open up your `/etc/init/rc.conf` now and uncomment
-the variables regarding SINIT. You are ready now.
-
-If you edited your inittab, make sure you reflect your changes
-on the `/etc/init/sinit-launch-services.boot` file.
-
-
-Finishing up
-------------
-
-If all of the above is done, simply exit the chroot and reboot.
-Sinit should be functioning without any issues.
diff --git a/docs/wiki/install.html b/docs/wiki/install.html
deleted file mode 100644
index e9c882b..0000000
--- a/docs/wiki/install.html
+++ /dev/null
@@ -1,337 +0,0 @@
-
-
-
-Install | Carbs Linux
-
-
-
-
-
-
Carbs Linux - a simple busybox linux distribution
-
-
Installation Instructions
-
-
This post will guide you step-by-step in order to install
-Carbs Linux. It is not complete yet.
-
-
Downloading and Getting Ready to Chroot
-
-
Installing Carbs Linux is the same as installing most
-rootfs distributions, such as Gentoo, or Void Linux.
-
-
Requirements
-
-
You simply need a Live Linux ISO. Gentoo would be the best
-as programs you will require will be already there. Get the
-ISO, boot it and set up your network.
-
-
Required Programs:
-
-
-
tar
-
wget
-
xz
-
-
-
-
Rest of the instructions assume that you have set all of these
-up, and will continue on.
-
-
Download
-
-
First, we need to download the rootfs tarball. In your terminal
-type
You need to extract the tarball to your mounted partition
-
-
$ tar xvpf carbs-rootfs-20191210.tar.xz -C /mnt
-
-
-
Chroot
-
-
Chroot into Carbs Linux
-
-
$ ./kiss-chroot /mnt
-
-
-
Enable repository signing (Highly Recommended)
-
-
This step is optional, but very highly recommended
-(I cannot stress out the amount I am recommending this).
-This ensures you are receiving updates from Carbs Linux
-and not some other source.
-
-
Install GnuPG
-
-
It is also a great time to learn how to use your new
-package manager, KISS! You simply build and install
-the package
-
-
$ kiss build gnupg1
-$ kiss install gnupg1
-
-
-
Import my key
-
-
Import my public key (cem@ckyln.com)
-
-$ gpg --recv-key 4356EE08A364CE09
-
-Create a .gnupg directory if it doesn't exist
-
-$ mkdir -p /root/.gnupg
-
-Trust my public key
-
-$ echo trusted-key 0x4356ee08a364ce09 >> /root/.gnupg/gpg.conf
-
-
-
Enable signature verification
-
-
Git has a built in signature verification feature.
-You can go to the repository directory and enable it
-
-
$ cd /var/db/kiss/repo
-$ git config merge.verifySignatures true
-
-
-
Installing Important Tools
-
-
Since Carbs gives you one of the most minimal base,
-you might need to apply some add-ons to your system.
-
-
Update packages
-
-
It might be a good idea to update your packages before
-installing new packages. This ensure compatibility.
-
-
$ kiss update
-
-
-
Filesystems
-
-
Currently, e2fsprogs and dosfstools are supported,
-as they are the most-used filesystems.
-
-
Support for ext2, ext3, and ex4
-
-$ kiss build e2fsprogs
-$ kiss install e2fsprogs
-
-Support for dosfstools
-
-$ kiss build dosfstools
-$ kiss install dosfstools
-
-
-
Device management
-
-
$ kiss build eudev
-$ kiss install eudev
-
-
-
Wireless
-
-
wpa_supplicant
-
-
$ kiss build wpa_supplicant
-$ kiss install wpa_supplicant
-
-
-
eiwd (WIP)
-
-
$ kiss build eiwd
-$ kiss install eiwd
-
-
-
dhcpcd
-
-
$ kiss build dhcpcd
-$ kiss install dhcpcd
-
-
-
Shells
-
-
Carbs Linux comes preinstalled with busybox ash, but other shells
-can be found on the repository
-
-
Install bash
-
-$ kiss build bash
-$ kiss install bash
-
-Install zsh
-
-$ kiss build zsh
-$ kiss install zsh
-
-Install Plan9 rc-shell
-
-$ kiss build 9base
-$ kiss install 9base
-
-
-
Install the Kernel
-
-
IMPORTANT: If you have GCC 10.x on your system, you need to apply
-this patch to your kernel sources. Otherwise your kernel will panic
-during the boot stage.
-
-
Next step is installing the kernel, which might sound as a challenge
-you should download and extract the kernel tarball first.
-
-
$ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz
-
-Let's move the sources to /usr/src
-
-$ mv linux-5.5.tar.xz /usr/src
-$ tar xf linux-5.5.tar.xz
-$ cd linux-5.5
-
Currently, default init for Carbs Linux is sinit, but
-busybox-init is also supported. You can also change this yourself.
-
-
To install init, you have to
-
-
$ kiss b sinit
-$ kiss i sinit
-
-
-
This will also fetch busybox-init as its dependency.
-
-
Enabling other repositories
-
-
There are other repositories out there that might be of your
-interest. The Official Repositories come with community and testing
-repositories that are not enabled by default. You could also want to
-add the Kiss Linux community repository, or someone’s personal kiss
-repository.
-
-
Obtaining repositories
-
-
Obtaining a repository is as simple as a git clone. You can do it
-with Cem’s personal repository as an example, but any other repository
-will be the same.
-
-
# Clone the repository to your desired location
-# Optionally add "--depth 1" to save precious disk space
-
-$ git clone --depth 1 git://git.ckyln.com/kiss-repository /var/db/kiss/cem-repository
-
-
-
That’s it, you have obtained a new repository!
-
-
Adding a repository to your KISS_PATH
-
-
Now that we have obtained Cem’s repository, we can add it to our KISS_PATH!
-
-
We need to edit /etc/profile.d/kiss_path.sh for this, but you
-can also change your KISS_PATH from your shellrc.
-
-
Add the full path to the repository, in this case
-/var/db/kiss/cem-repository/cem to the variable
-and add a : before/after it.
-
-
diff --git a/docs/wiki/install.txt b/docs/wiki/install.txt
deleted file mode 100644
index 81f87d1..0000000
--- a/docs/wiki/install.txt
+++ /dev/null
@@ -1,309 +0,0 @@
-
-Installation Instructions
-=========================
-
-This post will guide you step-by-step in order to install
-Carbs Linux. It is not complete yet.
-
-
-Downloading and Getting Ready to Chroot
----------------------------------------
-
-Installing Carbs Linux is the same as installing most
-rootfs distributions, such as Gentoo, or Void Linux.
-
-
-### Requirements
-
-You simply need a Live Linux ISO. Gentoo would be the best
-as programs you will require will be already there. Get the
-ISO, boot it and set up your network.
-
-**Required Programs:**
-
-* tar
-* wget
-* xz
-
-Rest of the instructions assume that you have set all of these
-up, and will continue on.
-
-
-### Download
-
-
-First, we need to download the rootfs tarball. In your terminal
-type
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz
-
-
-### Check the integrity of the tarball
-
-While optional, it is highly recommended to check the integrity
-of the tarball.
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sha256sum
- $ sha256sum -c carbs-rootfs-20191210.tar.xz.sha256sum
-
-
-### Check the signatures
-
-While optional, it is highly recommended to check the signature
-of the tarball
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sig
-
- Import the public key of release@carbslinux.org
-
- $ gpg --recv-keys FF484BDFEFCEF8FF
-
- $ gpg --verify carbs-rootfs-20191210.tar.xz.sig
-
-### Download Kiss Linux Chroot Helper
-
- $ wget https://dl.getkiss.org/kiss-chroot
-
- Make the script executable
-
- $ chmod +x kiss-chroot
-
-### Extract the rootfs tarball
-
-You need to extract the tarball to your mounted partition
-
- $ tar xvpf carbs-rootfs-20191210.tar.xz -C /mnt
-
-Chroot
-------
-Chroot into Carbs Linux
-
- $ ./kiss-chroot /mnt
-
-### Enable repository signing (Highly Recommended)
-
-This step is optional, but very highly recommended
-(I cannot stress out the amount I am recommending this).
-This ensures you are receiving updates from Carbs Linux
-and not some other source.
-
-**Install GnuPG**
-
-It is also a great time to learn how to use your new
-package manager, KISS! You simply build and install
-the package
-
- $ kiss build gnupg1
- $ kiss install gnupg1
-
-**Import my key**
-
-
- Import my public key (cem@ckyln.com)
-
- $ gpg --recv-key 4356EE08A364CE09
-
- Create a .gnupg directory if it doesn't exist
-
- $ mkdir -p /root/.gnupg
-
- Trust my public key
-
- $ echo trusted-key 0x4356ee08a364ce09 >> /root/.gnupg/gpg.conf
-
-**Enable signature verification**
-
-
-Git has a built in signature verification feature.
-You can go to the repository directory and enable it
-
- $ cd /var/db/kiss/repo
- $ git config merge.verifySignatures true
-
-### Installing Important Tools
-
-Since Carbs gives you one of the most minimal base,
-you might need to apply some add-ons to your system.
-
-**Update packages**
-
-It might be a good idea to update your packages before
-installing new packages. This ensure compatibility.
-
- $ kiss update
-
-**Filesystems**
-
-
-Currently, e2fsprogs and dosfstools are supported,
-as they are the most-used filesystems.
-
- Support for ext2, ext3, and ex4
-
- $ kiss build e2fsprogs
- $ kiss install e2fsprogs
-
- Support for dosfstools
-
- $ kiss build dosfstools
- $ kiss install dosfstools
-
-**Device management**
-
- $ kiss build eudev
- $ kiss install eudev
-
-**Wireless**
-
-**wpa_supplicant**
-
- $ kiss build wpa_supplicant
- $ kiss install wpa_supplicant
-
-**eiwd (WIP)**
-
- $ kiss build eiwd
- $ kiss install eiwd
-
-**dhcpcd**
-
- $ kiss build dhcpcd
- $ kiss install dhcpcd
-
-**Shells**
-
-Carbs Linux comes preinstalled with busybox ash, but other shells
-can be found on the repository
-
- Install bash
-
- $ kiss build bash
- $ kiss install bash
-
- Install zsh
-
- $ kiss build zsh
- $ kiss install zsh
-
- Install Plan9 rc-shell
-
- $ kiss build 9base
- $ kiss install 9base
-
-
-### Install the Kernel
-
-**IMPORTANT:** If you have GCC 10.x on your system, you need to apply
-this [patch] to your kernel sources. Otherwise your kernel will panic
-during the boot stage.
-
-Next step is installing the kernel, which might sound as a challenge
-you should download and extract the kernel tarball first.
-
- $ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz
-
- Let's move the sources to /usr/src
-
- $ mv linux-5.5.tar.xz /usr/src
- $ tar xf linux-5.5.tar.xz
- $ cd linux-5.5
-
-[patch]: https://dl.carbslinux.org/distfiles/linux-gcc-10-bootfix.patch
-
-**Configure the Kernel**
-
-You can check
-to learn more about kernel configuration. Overall, [Gentoo Wiki](https://wiki.gentoo.org)
-is a good place to learn about kernel configuration related to
-your hardware.
-
-**Build and install the kernel**
-
-The rest of it is simple, build the kernel with
-`make` and install it with `make install`
-
-### Bootloader
-
-The default bootloader is GRUB (GRand Unified Bootloader).
-
-Build and install GRUB
-
- $ kiss b grub
- $ kiss i grub
-
- Install efibootmgr as well if your
- system requires it
-
- $ kiss b efibootmgr
- $ kiss i efibootmgr
-
-
-**Setup GRUB**
-
- For BIOS:
- $ grub-install --target=i386-pc /dev/sdX
-
- For UEFI:
- $ grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=CarbsLinux
-
- $ grub-mkconfig -o /boot/grub/grub.cfg
-
-
-### Install init
-
-Currently, default init for Carbs Linux is `sinit`, but
-busybox-init is also supported. You can also change this yourself.
-
-To install init, you have to
-
- $ kiss b sinit
- $ kiss i sinit
-
-This will also fetch busybox-init as its dependency.
-
-
-### Enabling other repositories
-
-There are other repositories out there that might be of your
-interest. The Official Repositories come with community and testing
-repositories that are not enabled by default. You could also want to
-add the Kiss Linux community repository, or someone's personal kiss
-repository.
-
-**Obtaining repositories**
-
-Obtaining a repository is as simple as a git clone. You can do it
-with Cem's personal repository as an example, but any other repository
-will be the same.
-
- # Clone the repository to your desired location
- # Optionally add "--depth 1" to save precious disk space
-
- $ git clone --depth 1 git://git.ckyln.com/kiss-repository /var/db/kiss/cem-repository
-
-That's it, you have obtained a new repository!
-
-Adding a repository to your KISS_PATH
-
-Now that we have obtained Cem's repository, we can add it to our KISS\_PATH!
-
-We need to edit `/etc/profile.d/kiss_path.sh` for this, but you
-can also change your KISS\_PATH from your shellrc.
-
-Add the full path to the repository, in this case
-`/var/db/kiss/cem-repository/cem` to the variable
-and add a `:` before/after it.
-
-It must be looking like this.
-
- export KISS_PATH=/var/db/kiss/repo/core:/var/db/kiss/repo/extra:/var/db/kiss/repo/xorg:/var/db/kiss/cem-repository/cem
-
-Update your shell variables by doing `. /etc/profile.d/kiss_path.sh` so you can
-immediately access the repository packages
-
-
-More
-----
-
-You should now be able to boot into you Carbs Linux installation.
-To learn more, you can visit the [wiki](//carbslinux.org/wiki)
diff --git a/docs/wiki/keymaps/X-keymaps.html b/docs/wiki/keymaps/X-keymaps.html
deleted file mode 100644
index 960ba5c..0000000
--- a/docs/wiki/keymaps/X-keymaps.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
-X-keymaps | Carbs Linux
-
-
-
-
-
-
Unlike most other distributions out there
-Carbs Linux does not come preinstalled with console
-keys. You probably won’t be using more than
-two either. There are two ways of using keymaps
-
-
diff --git a/docs/wiki/keymaps/keymaps.txt b/docs/wiki/keymaps/keymaps.txt
deleted file mode 100644
index 89a7e8c..0000000
--- a/docs/wiki/keymaps/keymaps.txt
+++ /dev/null
@@ -1,52 +0,0 @@
-
-Installing and Using Keymaps
-============================
-
-Unlike most other distributions out there
-Carbs Linux does not come preinstalled with console
-keys. You probably won't be using more than
-two either. There are two ways of using keymaps
-
-Installing the "bkeymaps" package
----------------------------------
-
-You can get the `bkeymaps` package from the
-[KISS community repository](https://github.com/kisslinux/community).
-
-Build and install `bkeymaps`.
-
- -> kiss b bkeymaps
- -> kiss i bkeymaps
-
-Now you can find the keymaps in `/usr/share/bkeymaps`.
-
-
-Downloading the keymaps you require
------------------------------------
-
-*This will assume that you are using the us keyboard layout*
-
-You firstly will need to go to
-and download the keymap you need
-
-Loading keymap, doing it on login/boot
---------------------------------------
-
-- Run `loadkmap < file` to load the keymap.
-
-**Load keymap at login**
-
-If you want to load a keymap at login, you can
-add the command above to your `.profile` file.
-
-**Load keymap at boot**
-
-You can also load keymap during boot. You should edit
-`/lib/init/rc.boot` file and add something like
-
- # assuming you are using trq as your keymap
- log "Setting keymap to trq..."; {
- loadkmap < /path/to/trq.bmap
- }
-
-to your main function.
diff --git a/docs/wiki/system/service-management.html b/docs/wiki/system/service-management.html
deleted file mode 100644
index da639fb..0000000
--- a/docs/wiki/system/service-management.html
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
-Service Management | Carbs Linux
-
-
-
-
-
-
Carbs Linux - a simple busybox linux distribution
-
-
Carbs Linux uses busybox-runit by default, but the repository additionally has the
-original runit and sysmgr. You can install either with kiss b runit; kiss i runit
-or kiss b sysmgr; kiss i sysmgr.
-
-
runit
-
-
Enabling a Service
-
-
ln -sf /etc/sv/acpid /var/service
-
-
-
Disabling a Service
-
-
unlink /var/service/acpid
-
-
-
Starting a Service
-
-
sv start acpid
-
-
-
Stopping a Service
-
-
sv stop acpid
-
-
-
For more information refer to the sv --help output. Also check out the sv(8)
-manual page if you have installed the runit package.
-
-
sysmgr
-
-
sysmgr is POSIX-sh service supervisor written by me. Its usage resembles
-runit. The biggest difference is that sysmgr uses service files instead
-of directories with run scripts inside.
-
-
svctl
-
-
svctl is the equivalant of sv for sysmgr. You can run the above commands for
-runit and use svctl instead of sv. Those would be as follows.
-
-
Enabling a Service
-
-
ln -sf /etc/sysmgr/acpid /var/sysmgr
-
-
-
Disabling a Service
-
-
unlink /var/sysmgr/acpid
-
-
-
Starting a Service
-
-
svctl start acpid
-
-
-
Stopping a Service
-
-
svctl stop acpid
-
-
-
Switching from runit
-
-
Switching from runit is fairly easy. You can run the following commands to get
-started with sysmgr.
-
-
# Create the directories if you haven't yet
-mkdir -p /var/sysmgr /etc/sysmgr
-
-# Copy all of the run scripts to /etc/sysmgr
-set -- /etc/sv/*
-for service; do cp "$service/run" "/etc/sysmgr/${service##*/}" ; done
-
-# Link all enabled services
-set -- /var/service/*
-for service; do ln -sf /etc/sysmgr/${service##*/} /var/sysmgr ; done
-
-
-
diff --git a/docs/wiki/system/service-management.txt b/docs/wiki/system/service-management.txt
deleted file mode 100644
index 2133ea5..0000000
--- a/docs/wiki/system/service-management.txt
+++ /dev/null
@@ -1,81 +0,0 @@
-
-Carbs Linux uses `busybox-runit` by default, but the repository additionally has the
-original `runit` and `sysmgr`. You can install either with `kiss b runit; kiss i runit`
-or `kiss b sysmgr; kiss i sysmgr`.
-
-runit
-=====
-
-**Enabling a Service**
-
- ln -sf /etc/sv/acpid /var/service
-
-**Disabling a Service**
-
- unlink /var/service/acpid
-
-**Starting a Service**
-
- sv start acpid
-
-**Stopping a Service**
-
- sv stop acpid
-
-For more information refer to the `sv --help` output. Also check out the `sv(8)`
-manual page if you have installed the `runit` package.
-
-
-sysmgr
-======
-
-[sysmgr] is POSIX-sh service supervisor written by me. Its usage resembles
-`runit`. The biggest difference is that `sysmgr` uses service files instead
-of directories with run scripts inside.
-
-
-svctl
------
-
-`svctl` is the equivalant of `sv` for sysmgr. You can run the above commands for
-`runit` and use `svctl` instead of `sv`. Those would be as follows.
-
-
-**Enabling a Service**
-
- ln -sf /etc/sysmgr/acpid /var/sysmgr
-
-**Disabling a Service**
-
- unlink /var/sysmgr/acpid
-
-**Starting a Service**
-
- svctl start acpid
-
-**Stopping a Service**
-
- svctl stop acpid
-
-
-Switching from runit
---------------------
-
-Switching from `runit` is fairly easy. You can run the following commands to get
-started with `sysmgr`.
-
-
- # Create the directories if you haven't yet
- mkdir -p /var/sysmgr /etc/sysmgr
-
- # Copy all of the run scripts to /etc/sysmgr
- set -- /etc/sv/*
- for service; do cp "$service/run" "/etc/sysmgr/${service##*/}" ; done
-
- # Link all enabled services
- set -- /var/service/*
- for service; do ln -sf /etc/sysmgr/${service##*/} /var/sysmgr ; done
-
-
-
-[sysmgr]: https://github.com/cemkeylan/sysmgr
diff --git a/src/blog/index.md b/src/blog/index.md
index ac2c84b..501c8e4 100644
--- a/src/blog/index.md
+++ b/src/blog/index.md
@@ -5,6 +5,7 @@ This is the Carbs Linux Blog Index. You can find every post here. [RSS Feed]
[RSS Feed]: /rss.xml
+
* Jun 17 2020 - [June Newspost](20200617.html)
* May 28 2020 - [kiss 2.0.0 and overall changes](20200528.html)
* May 08 2020 - [The Relation of Carbs and KISS](20200508.html)
diff --git a/src/index.md b/src/index.md
index 9d8097a..6635bc7 100644
--- a/src/index.md
+++ b/src/index.md
@@ -60,26 +60,30 @@ News
[RSS Feed](/news.xml) | [See all news](/news.html)
-### Jun 17 2020
+Jun 17 2020
+--------------------------------------------------------------------------------
A new rootfs tarball including the changes to the core is released and can be
found on the downloads page.
-### May 26 2020
+May 26 2020
+--------------------------------------------------------------------------------
An initial version for binary package management is released.
It can be found on the [GitHub page].
[GitHub page]: https://github.com/CarbsLinux/kiss-bin
-### May 19 2020
+May 19 2020
+--------------------------------------------------------------------------------
A rootfs tarball targeting the i686 architecture has
been released. It can be found on the [downloads page]
[downloads page]: https://dl.carbslinux.org/releases/i686
-### May 10 2020
+May 10 2020
+--------------------------------------------------------------------------------
A GCC 10.1.0 change causes a kernel panic for kernels built
with GCC 10.1. This issue can be resolved by applying this
@@ -87,7 +91,8 @@ with GCC 10.1. This issue can be resolved by applying this
[patch]: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22
-### Apr 27 2020
+Apr 27 2020
+--------------------------------------------------------------------------------
A new rootfs tarball has been released! You can
see it on !
diff --git a/src/news.md b/src/news.md
index 3a6ed12..91b1ce8 100644
--- a/src/news.md
+++ b/src/news.md
@@ -1,12 +1,12 @@
Jun 17 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball including the changes to the core is released and can be
found on the downloads page.
May 26 2020
------------
+--------------------------------------------------------------------------------
An initial version for binary package management is released.
It can be found on the [GitHub page].
@@ -14,7 +14,7 @@ It can be found on the [GitHub page].
[GitHub page]: https://github.com/CarbsLinux/kiss-bin
May 19 2020
------------
+--------------------------------------------------------------------------------
A rootfs tarball targeting the i686 architecture has
been released. It can be found on the [downloads page]
@@ -22,7 +22,7 @@ been released. It can be found on the [downloads page]
[downloads page]: https://dl.carbslinux.org/releases/i686
May 10 2020
------------
+--------------------------------------------------------------------------------
A GCC 10.1.0 change causes a kernel panic for kernels built
with GCC 10.1. This issue can be resolved by applying this
@@ -31,7 +31,7 @@ with GCC 10.1. This issue can be resolved by applying this
[patch]: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22
Apr 27 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball has been released! You can
see it on !
@@ -39,18 +39,18 @@ see it on !
**EDIT:** A new bug fix release has been made.
Apr 10 2020
------------
+--------------------------------------------------------------------------------
IRC channel can now be accessed from `#carbslinux` at freenode!
Apr 06 2020
------------
+--------------------------------------------------------------------------------
A new rootfs tarball has been released. See the
[downloads](https://dl.carbslinux.org) page
Apr 05 2020
------------
+--------------------------------------------------------------------------------
Carbs Linux repositories will be hosted only on Github. Commits will be
pushed there, and not the repository. You have until
@@ -65,7 +65,7 @@ repository directory.
Feb 18 2020
------------
+--------------------------------------------------------------------------------
A new tarball is released. It can be found on .
@@ -77,7 +77,7 @@ changes on Busybox.
Feb 14 2020
------------
+--------------------------------------------------------------------------------
**IMPORTANT!** Carbs-init update to be released on 17th of February
will require manual intervention. I am holding this update back so
@@ -130,7 +130,7 @@ This is a Quality of Life update.
Feb 13 2020
------------
+--------------------------------------------------------------------------------
Runit is now released on the core repository! You can now replace
busybox-init with runit-init. You can also replace the busybox runit
@@ -138,7 +138,7 @@ utilities with the actual runit. This will reduce the dependency on
busybox greatly.
Jan 28 2020
------------
+--------------------------------------------------------------------------------
Web Server is now on a Carbs Linux server. It is not complete yet,
but I will be adding a little more for the intended functionality.
@@ -150,20 +150,20 @@ UPDATE2: downloads are back again.
Jan 22 2020
------------
+--------------------------------------------------------------------------------
Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating
this web server to my Carbs Linux server!
Jan 15 2020
------------
+--------------------------------------------------------------------------------
sinit has been taken to `core`, and is now officially supported
Jan 13 2020
------------
+--------------------------------------------------------------------------------
**Busybox update reqires manual intervention**
@@ -183,13 +183,13 @@ I have moved runit and logging utilities from the busybox-init package to the bu
package, which is the cause of these conflicts.
Jan 10 2020
------------
+--------------------------------------------------------------------------------
carbs-rootfs-20200110.tar.xz was [released](//dl.carbslinux.org/releases)
Jan 09 2020
------------
+--------------------------------------------------------------------------------
Happy new year, everyone! I am back after some long silence. I was unable to commit for a
while, but I have pulled some new updates from the KISS repository, added some of my own.
@@ -204,19 +204,19 @@ Important things are,
Dec 18 2019
------------
+--------------------------------------------------------------------------------
carbs-rootfs-20191218.tar.xz was [released](//dl.carbslinux.org/releases)
Dec 17 2019
------------
+--------------------------------------------------------------------------------
Installation instruction are now complete. A review would be greatly appreciated!
Dec 15 2019
------------
+--------------------------------------------------------------------------------
Carbs Linux Wiki is now available to be edited and updated by the users go
to the [wiki](//carbslinux.org/wiki) to obtain more information.
@@ -225,14 +225,14 @@ to the [wiki](//carbslinux.org/wiki) to obtain more information.
Dec 12 2019
------------
+--------------------------------------------------------------------------------
Busybox and Busybox-init has been seperated into two different packages.
This is for adding standalone runit/runit-init to the repositories.
Dec 10 2019
------------
+--------------------------------------------------------------------------------
First alpha release was made. See the [downloads page](//dl.carbslinux.org/releases).
diff --git a/src/news.xml b/src/news.xml
new file mode 100644
index 0000000..4ca82dd
--- /dev/null
+++ b/src/news.xml
@@ -0,0 +1,326 @@
+
+
+
+Carbs Linux
+a simple busybox linux distribution
+https://carbslinux.org
+
+Jun Sat 2020 20:00
+
+Jun 17 2020
+Wed, 17 Jun 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jun 17 2020</h2>
+
+<p>A new rootfs tarball including the changes to the core is released and can be
+found on the downloads page.</p>
+
+
+May 26 2020
+Tue, 26 May 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>May 26 2020</h2>
+
+<p>An initial version for binary package management is released.
+It can be found on the <a href="https://github.com/CarbsLinux/kiss-bin">GitHub page</a>.</p>
+
+
+May 19 2020
+Tue, 19 May 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>May 19 2020</h2>
+
+<p>A rootfs tarball targeting the i686 architecture has
+been released. It can be found on the <a href="https://dl.carbslinux.org/releases/i686">downloads page</a></p>
+
+
+May 10 2020
+Sun, 10 May 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>May 10 2020</h2>
+
+<p>A GCC 10.1.0 change causes a kernel panic for kernels built
+with GCC 10.1. This issue can be resolved by applying this
+<a href="https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22">patch</a> to your kernel sources.</p>
+
+
+Apr 27 2020
+Mon, 27 Apr 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Apr 27 2020</h2>
+
+<p>A new rootfs tarball has been released! You can
+see it on <a href="https://dl.carbslinux.org/releases">https://dl.carbslinux.org/releases</a>!</p>
+
+<p><strong>EDIT:</strong> A new bug fix release has been made.</p>
+
+
+Apr 10 2020
+Fri, 10 Apr 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Apr 10 2020</h2>
+
+<p>IRC channel can now be accessed from <code>#carbslinux</code> at freenode!</p>
+
+
+Apr 06 2020
+Mon, 06 Apr 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Apr 06 2020</h2>
+
+<p>A new rootfs tarball has been released. See the
+<a href="https://dl.carbslinux.org">downloads</a> page</p>
+
+
+Apr 05 2020
+Sun, 05 Apr 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Apr 05 2020</h2>
+
+<p>Carbs Linux repositories will be hosted only on Github. Commits will be
+pushed there, and not the repository. You have until
+May 4, 2020 Monday to switch your remotes to <a href="https://github.com/CarbsLinux/repository">https://github.com/CarbsLinux/repository</a>.
+The git repository will continue to be served until then (without additional
+commits).</p>
+
+<p>You can switch your remote by executing the following command on your
+repository directory.</p>
+
+<pre><code>git remote set-url origin https://github.com/CarbsLinux/repository
+</code></pre>
+
+
+Feb 18 2020
+Tue, 18 Feb 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Feb 18 2020</h2>
+
+<p>A new tarball is released. It can be found on <a href="https://dl.carbslinux.org">https://dl.carbslinux.org</a>.</p>
+
+<p><strong>edit:</strong> I have removed the tarball because of a bootstrapping issue.
+I will be re-adding it later today.</p>
+
+<p><strong>edit 2:</strong> I have added a tarball (20200219) to reflect my recent
+changes on Busybox.</p>
+
+
+Feb 14 2020
+Fri, 14 Feb 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Feb 14 2020</h2>
+
+<p><strong>IMPORTANT!</strong> Carbs-init update to be released on 17th of February
+will require manual intervention. I am holding this update back so
+people can see it before they update their system (even though the
+update will show the same message as this). The rationale for the
+update is explained below the intervention.</p>
+
+<pre><code># There is an explanation for each init
+# You only need to follow the instructions
+# for your own init-system
+
+## busybox-init
+# If you did not edit your inittab simply
+# move inittab.new to inittab
+-> mv /etc/inittab.new /etc/inittab
+
+# If you did edit your inittab you can use
+# a simple sed command to remove the necessary lines
+-> sed -i '/getty/d;/runsvdir/d' /etc/inittab
+
+
+## runit
+# same as busybox-init, if you did not edit
+# /etc/runit/2 move 2.new to 2
+-> mv /etc/runit/2.new /etc/runit/2
+
+# else
+-> vim /etc/runit/2
+# open your 2 file and remove the for loop containing
+# getty commands. If you are using runit, it is recommended
+# to comment out /etc/init/runit.boot
+
+## sinit/minit
+# If you did not edit your {sinit-,}launch-services.boot
+# you can simply remove it.
+-> rm -f /etc/init/launch-services.boot /etc/init/sinit-launch-services.boot
+
+# This should leave you without any issues, and you can safely reboot.
+</code></pre>
+
+<p>Carbs-init update is to make sure init systems do not clash, and do
+not have to use different files. This is a sensible update both for
+the user user and for the maintainer side.</p>
+
+<p>To give an example, before this update busybox-init was managing getty
+through <code>inittab</code>, runit was managing through <code>/etc/runit/2</code>, and
+minit/sinit were launching from <code>/etc/init/launch-services.boot</code>. This
+is a configuration nightmare for everyone, and since I am maintaining
+and constantly testing those init providers, a huge nightmare for me.
+This is a Quality of Life update.</p>
+
+
+Feb 13 2020
+Thu, 13 Feb 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Feb 13 2020</h2>
+
+<p>Runit is now released on the core repository! You can now replace
+busybox-init with runit-init. You can also replace the busybox runit
+utilities with the actual runit. This will reduce the dependency on
+busybox greatly.</p>
+
+
+Jan 28 2020
+Tue, 28 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 28 2020</h2>
+
+<p>Web Server is now on a Carbs Linux server. It is not complete yet,
+but I will be adding a little more for the intended functionality.
+Downtimes can be expected.</p>
+
+<p>UPDATE: ssl is now working.</p>
+
+<p>UPDATE2: downloads are back again.</p>
+
+
+Jan 22 2020
+Wed, 22 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 22 2020</h2>
+
+<p>Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating
+this web server to my Carbs Linux server!</p>
+
+
+Jan 15 2020
+Wed, 15 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 15 2020</h2>
+
+<p>sinit has been taken to <code>core</code>, and is now officially supported</p>
+
+
+Jan 13 2020
+Mon, 13 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 13 2020</h2>
+
+<p><strong>Busybox update reqires manual intervention</strong></p>
+
+<p>The new busybox package conflicts with the pre-update busybox-init. That’s why
+you should rebuild and install <code>busybox-init</code> before doing the update.</p>
+
+<pre><code># Do a kiss update first (but don't actually update it yet), or manually pull the git repository
+$ kiss u # Cancel this operation after it asks for you to confirm the update
+
+# Install the busybox-init package
+$ kiss b busybox-init && kiss i busybox-init
+
+# Continue your update as you normally would.
+$ kiss u
+</code></pre>
+
+<p>I have moved runit and logging utilities from the busybox-init package to the busybox
+package, which is the cause of these conflicts.</p>
+
+
+Jan 10 2020
+Fri, 10 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 10 2020</h2>
+
+<p>carbs-rootfs-20200110.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
+
+
+Jan 09 2020
+Thu, 09 Jan 2020
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Jan 09 2020</h2>
+
+<p>Happy new year, everyone! I am back after some long silence. I was unable to commit for a
+while, but I have pulled some new updates from the KISS repository, added some of my own.
+This week I will be changing/adding some things.</p>
+
+<p>Important things are,</p>
+
+<ul>
+<li>Carbs-init was updated to 0.3.</li>
+<li>I will be adding an implementation of suckless.org’s <a href="//core.suckless.org/sinit">sinit</a> as <code>carbs-sinit</code></li>
+<li>Carbs Repository was added to <a href="//repology.org/repository/carbs">repology.org</a></li>
+<li>A new rootfs tarball will be coming up tomorrow.</li>
+</ul>
+
+
+Dec 18 2019
+Wed, 18 Dec 2019
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Dec 18 2019</h2>
+
+<p>carbs-rootfs-20191218.tar.xz was <a href="//dl.carbslinux.org/releases">released</a></p>
+
+
+Dec 17 2019
+Tue, 17 Dec 2019
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Dec 17 2019</h2>
+
+<p>Installation instruction are now complete. A review would be greatly appreciated!</p>
+
+
+Dec 15 2019
+Sun, 15 Dec 2019
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Dec 15 2019</h2>
+
+<p>Carbs Linux Wiki is now available to be edited and updated by the users go
+to the <a href="//carbslinux.org/wiki">wiki</a> to obtain more information.</p>
+
+<p><strong>February 2020 EDIT:</strong> Changed link for wiki</p>
+
+
+Dec 12 2019
+Thu, 12 Dec 2019
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Dec 12 2019</h2>
+
+<p>Busybox and Busybox-init has been seperated into two different packages.
+This is for adding standalone runit/runit-init to the repositories.</p>
+
+
+Dec 10 2019
+Tue, 10 Dec 2019
+Cem Keylan
+https://carbslinux.org/index.html
+<h2>Dec 10 2019</h2>
+
+<p>First alpha release was made. See the <a href="//dl.carbslinux.org/releases">downloads page</a>.</p>
+
+
+
diff --git a/src/rss.xml b/src/rss.xml
new file mode 100644
index 0000000..5788d02
--- /dev/null
+++ b/src/rss.xml
@@ -0,0 +1,392 @@
+
+
+
+Carbs Linux
+a simple busybox linux distribution
+https://carbslinux.org
+
+Jun Sat 2020 20:00
+
+June Newspost
+Wed, 17 Jun 2020
+Cem Keylan
+https://carbslinux.org/blog/20200617.html
+<h1>June Newspost</h1>
+
+<p>This will be an active month for Carbs as major changes to the base and the
+package manager will be coming up.</p>
+
+<h2>Statically linking the base</h2>
+
+<p>For the past couple of weeks I have been trying to simplify the base and
+statically link the core (mostly binaries rather than libraries). I usually see
+some people extremely opposed to static linking as I also see the opposite on
+people.</p>
+
+<p>I believe that binaries on the core should always be linked statically. This
+ensures that an SONAME bump to <code>libObscure.so</code> will not break the core
+functionality of your system, forcing you to use external resources to recover
+from such an issue. As long as you can compile, use core utilities, edit text,
+and access the web, you can solve any given issue on your system.</p>
+
+<p>However, I don’t think that removing shared libraries is sensible either. Not
+every piece of software out there is good quality enough to be statically
+linked.</p>
+
+<h2>Major changes on the core repository</h2>
+
+<p>There have been drastic changes to the core repository and the base rootfs this
+month (with more on the way). Right now changes are as follows.</p>
+
+<h3>Removed from Core</h3>
+
+<ul>
+<li><code>git</code></li>
+<li><code>libressl</code></li>
+<li><code>grub</code></li>
+<li><code>bison</code></li>
+<li><code>dhcpcd</code></li>
+<li><code>ubase</code></li>
+</ul>
+
+
+<h3>Added to Core</h3>
+
+<ul>
+<li><code>bearssl</code>, as a <code>libressl</code> replacement</li>
+<li><code>byacc</code>, as a <code>bison</code> replacement</li>
+</ul>
+
+
+<h3>Statically linked</h3>
+
+<ul>
+<li><code>kiss</code></li>
+<li><code>neatvi</code></li>
+<li><code>mandoc</code></li>
+<li><code>byacc</code></li>
+<li><code>m4</code></li>
+<li><code>e2fsprogs</code></li>
+<li><code>make</code></li>
+<li><code>pkgconf</code></li>
+<li><code>sbase</code></li>
+<li><code>libnl</code></li>
+<li><code>wpa_supplicant</code></li>
+<li><code>bearssl</code></li>
+</ul>
+
+
+<h2>Making the wiki available offline</h2>
+
+<p>Soon, all documentation regarding Carbs Linux will be avaialable to be installed
+from the core repository in a <code>carbs-docs</code> package along with its own document
+crawler. Currently, the documentation regarding the installation process is a
+little outdated which will also receive some important updates.</p>
+
+<h2>ISO image for Carbs</h2>
+
+<p>I am thinking of releasing an ISO image in order to provide a standardized
+environment for installation along with installation helper tools in the spirit
+of <code>arch-install-scripts</code>. Let’s see how that’s going to play out.</p>
+
+
+kiss 2.0.0 and overall changes
+Thu, 28 May 2020
+Cem Keylan
+https://carbslinux.org/blog/20200528.html
+<h1>kiss 2.0.0 and overall changes</h1>
+
+<p>Carbs Linux kiss version 2.0.0 has been released which introduces
+rsync repositories.</p>
+
+<p>Git is no longer a mandatory dependency for the package manager,
+every git source on the core repository has been replaced with
+https sources (sbase, sinit), and rootfs tarballs will no longer
+ship with git. Repositories in the upcoming tarball will be rsync
+repositories.</p>
+
+<p>Git is now on the <code>extra</code> repository and is still (optionally)
+used in the package manager.</p>
+
+<p>The idea behind this change is size reductions and increased
+speed with rsync. As I said on the previous post, git repositories
+get larger and larger over the time span. Currently my personal
+copy of the git repository is around 77MB and I have forked KISS
+Linux (as a shallow copy) around December. Obviously, I have commits
+that I ommitted. I tend to create commits I dislike, which I change
+with ‘git reset –soft HEAD^’, which doesn’t actually remove the
+commits, etc. A user will have a repository much smaller than mine.</p>
+
+<p>This is a precaution with the added bonuses of speed and dropping a
+mandatory dependency.</p>
+
+<p>You can see the rest of the changelog <a href="https://github.com/CarbsLinux/kiss/blob/master/CHANGELOG.md">here</a>.</p>
+
+<h2>Binary Repositories</h2>
+
+<p>A few days ago, I have also published <a href="https://github.com/CarbsLinux/kiss-bin">kiss-bin</a>, a first version
+for managing binary repositories. Currently, there are some caveats
+that I’ll be fixing along the way. I decided not to include this
+in the package manager natively as managing the source based and
+binary based packages together adds levels of complexity that we
+do not want. Instead, this is an extension for kiss which sources
+the package manager as a library. I hope to see it being adopted
+by others interested on the matter as well.</p>
+
+<p>That’s about it.</p>
+
+<p>Cheers,
+Cem</p>
+
+
+The Relation of Carbs and KISS
+Fri, 08 May 2020
+Cem Keylan
+https://carbslinux.org/blog/20200508.html
+<h1>The Relation of Carbs and KISS</h1>
+
+<p><strong>Date:</strong> May 08 2020</p>
+
+<p>Since I have forked KISS, I have received many questions
+that can be summarized as “Why?”. I have realized that I
+never truly answered this question. That’s the reason I am
+writing this post, to give some background on Carbs, and
+some differences between KISS Linux and Carbs Linux for
+anyone who may be wondering. Perhaps I could make this a
+“FAQ” page later on.</p>
+
+<h2>History</h2>
+
+<p>I had the idea of creating my own Linux distribution since
+the May of 2019. Back then, I had my own <a href="https://linuxfromscratch.org">Linux from Scratch</a>
+build, and I wanted to slim it down my own way and replace
+the software (with musl,sbase,etc.). The name Carbs Linux
+was in my mind since then. I wanted to write my own package
+manager, but I wasn’t satisfied with anything I had built.</p>
+
+<p>I had written some incomplete package managers (all named <code>fat</code>)
+and I quickly threw them into the trash can, where they
+honestly belonged. I would want to share them with you for
+laughs, but my hard-drive got wiped and I have a problem
+of not doing an “initial commit” until a program I write
+is in a usable state.</p>
+
+<p>I have obtained the ‘carbslinux.org’ domain name in September
+2019, but then life got on the way, and I stopped for a long
+time.</p>
+
+<p>One day on Reddit, I saw Dylan’s post on <a href="https://reddit.com/r/unixporn">r/unixporn</a> about
+KISS, and I really thought that it was interesting. Here is
+my <a href="https://www.reddit.com/r/unixporn/comments/ducd34/sowm_kiss_d/f7lua7x">comment</a> to Dylan on that post. I checked out the package
+manager and the repository. The packaging system was extremely
+clean and well-thought. I decided to give it a go and fork
+KISS.</p>
+
+<h2>Differences between KISS and Carbs</h2>
+
+<p>Now, I still baffle when people ask me this question. My
+intention was never to create a distribution with specific
+differences between KISS. My intention was being my own
+BDFL of a distribution I maintain. There are lots of
+differences between the main repositories, but they are subtle
+and not worth talking about. I personally never even installed
+KISS Linux on my system. So Carbs, isn’t something like a
+downstream fork of KISS, it is just a distribution that was
+initially based on KISS.</p>
+
+<p>I try to contribute as much as I can to KISS Linux. I think
+that it is a brilliant distribution, and it was a great starting
+point for Carbs. I am really grateful to Dylan and all the
+other contributors.</p>
+
+<h2>What I’m working on now</h2>
+
+<p>Currently I have a few projects that I’m working on for Carbs.
+These are,</p>
+
+<p>A BSD port for Carbs. For a while, I have been working on BSD
+compatibility on my fork of the <a href="https://github.com/carbslinux/kiss">package manager</a>. I have tested,
+without any more issues, on OpenBSD and FreeBSD. The biggest
+issues remaining are choosing a vendor for BSD, packaging the
+BSD source, and providing a minimal base (like busybox for BSD).
+If you aren’t familiar with BSD, it has a single source code
+for all of the utilities (kernel, command line programs, etc.).
+Contributions (even chipping in ideas) are very welcome.</p>
+
+<p>Adding binary package distribution support natively to the package
+manager. Biggest issue in small/old computers are compile times.
+This feature is for the bigger packages such as webkit, clang,
+llvm that take a considerable amount of time. Some computers
+with low memories cannot even compile firefox/webkit.</p>
+
+<p>Adding rsync repository support to the package manager. This
+is not a current issue, but rather a futureproofing. As time
+passes, distribution repositories grow larger. KISS and Carbs
+are young distributions without this problem right now. But
+in something like 5 years, this size will presumably increase
+to hundreds of megabytes. At that point it will be pointless
+to have the repository sources unless you specifically need them.</p>
+
+<h2>What’s up with all the init/service daemons?</h2>
+
+<p>If you have ever checked the <a href="https://github.com/carbslinux/repository">repository</a>, you may have noticed
+that there are lots of init/service related packages. I have had
+my fair share of time with all of them, and it is an area that I
+am really interested in. I have even written my own <a href="https://github.com/cemkeylan/shinit">init daemon</a>
+and <a href="https://github.com/cemkeylan/sysmgr">service supervisor</a>. I maintain all those packages on KISS
+Community Repository as well with the exception of busybox. Those
+are, <code>busybox init/runit</code>, <code>runit</code>, <code>sinit</code>, and <code>sysmgr</code>. I would
+definitely recommend checking out <code>shinit</code> and <code>sysmgr</code>.</p>
+
+<h2>Why I don’t publicize Carbs</h2>
+
+<p>There are a couple of reasons I don’t publicize Carbs a lot.</p>
+
+<p>KISS is the better alternative in terms of support and community.
+I work on maintaining this distribution just as hard as Dylan,
+but in the end, Carbs is based on his original hard work, and I
+believe that he deserves the recognition more than I do.</p>
+
+<p>Since I cannot answer questions like “What is the difference?”, I
+prefer staying as the silent sibling project of KISS Linux. Plus,
+there is no point in dividing the newly-emerging community in half.</p>
+
+<p>That’s not because I don’t have ideas for the future of Carbs, I
+do. I just think that I will deserve the recognition once those
+above lists are checked.</p>
+
+<p>I think that’s about it, if you have questions you can send me a
+mail, ping me on IRC (my handle is <code>merakor</code>), and I will be happy
+to answer. Maybe your question fits this post, and I can update it
+to thoroughly give an explanation.</p>
+
+<p>Cheers,
+Cem</p>
+
+
+Outsource Repository Concept
+Fri, 10 Apr 2020
+Cem Keylan
+https://carbslinux.org/blog/20200410.html
+<h1>Outsource Repository Concept</h1>
+
+<p>In April 3rd, I have added submodule support for Carbs
+Linux’s fork of <code>kiss</code>. Now, from that sentence, it really
+doesn’t sound exciting at all. But in reality, it opens a
+path to lots of creative output, and a better way to manage
+multi-user repositories (such as KISS Community).</p>
+
+<p>When managing a repository of submodules, the repository
+maintainer’s only job is to deal with adding packages.
+A package maintainer doesn’t have to wait for the repository
+maintainer to update their packages, as they are only making
+the changes to their own repositories.</p>
+
+<p>This way, an end-user can also track from their preferred
+maintainers, and do that with the tidyness of a single repository
+in their <code>KISS_PATH</code>.</p>
+
+<p>Carbs Linux now has an outsource repository for some packages.
+Firefox and its dependencies have been purged from the main repository,
+but can be found on it.</p>
+
+<p><a href="https://github.com/CarbsLinux/outsource">https://github.com/CarbsLinux/outsource</a></p>
+
+
+Roadmap for Carbs
+Mon, 06 Apr 2020
+Cem Keylan
+https://carbslinux.org/blog/20200406.html
+<h1>Roadmap for Carbs</h1>
+
+<p>It has been a busy week. There are lots of changes in
+direction, and more to come. I want to talk a little
+about all of them.</p>
+
+<h2>Carbs Linux Server Going Down</h2>
+
+<p>It became harder to maintain and pay for the server, and I will be
+shutting it down in May. I am currently in the phase of
+carrying over everything to <a href="https://github.com/CarbsLinux">Github</a>. The repository and the
+website is served on Github now. I have also moved the <a href="https://github.com/CarbsLinux/wiki/wiki">Wiki</a>
+to Github and anyone can edit it there. There are some outdated
+posts that I will be fixing around this week.</p>
+
+<p>I am not quite sure where to store the downloads page now. But I
+will be switching that to a new source as well. (Maybe Source Forge?)</p>
+
+<p>I feel a little sad for switching, but serving on Github is faster,
+cheaper, and hassle-free.</p>
+
+<h2>Forking KISS</h2>
+
+<p>I had a personal fork of KISS, which I enjoyed thoroughly. I didn’t
+intend to make it the default when I started it, but it has matured
+enough to be so. The package manager can now be found on <a href="https://github.com/CarbsLinux/kiss">this repository</a>.
+See it for the added changes.</p>
+
+<p>This will be a change for the better, as I can develop the package
+manager as it fits my views.</p>
+
+<h2>Small Changes on the Website</h2>
+
+<p>I have made some small changes on the website. The build is not dependent
+on Plan9 utilities anymore. It was fun messing around with <code>rc</code> and <code>mk</code>,
+but they are quite limited compared to POSIX shell.</p>
+
+<p>RSS feeds are finally working as intended, both for the <a href="https://carbslinux.org/news.xml">news</a> section, and
+the <a href="https://carbslinux.org/rss.xml">blog</a> secion.</p>
+
+<p>You can see every page’s <code>.txt</code> output at the end of the page by clicking
+‘View Page Source’. Meanwhile, I will be updating some pages to be a little
+more ‘human-readable’.</p>
+
+<h2>Outsources Repository</h2>
+
+<p>I have opened an <code>outsource</code> repository, which I will be pushing this week.
+I will add a new post when I am ready to push it. I think it will be interesting,
+it will also make more sense about the changes I have added to the package
+manager. The now empty repository, can be found <a href="https://github.com/CarbsLinux/outsource">here</a>!</p>
+
+<h2>New Tarball</h2>
+
+<p>Finally, I have released a new tarball today, which can be obtained from the
+<a href="https://dl.carbslinux.org/releases">downloads page</a>.</p>
+
+<p>I am planning to add more of these update posts as I’m feeling better about
+the website structure overall.</p>
+
+<p>- Cem</p>
+
+
+Switching to New Website
+Tue, 28 Jan 2020
+Cem Keylan
+https://carbslinux.org/blog/20200128.html
+<h1>Switching to New Website</h1>
+
+<p><strong>Date:</strong> Jan 28 2020</p>
+
+<p>In case you haven’t seen it before, this website
+was powered by <a href="http://werc.cat-v.org">werc</a>. And
+even though I liked it really much, it was too
+powerful for a small website like this.</p>
+
+<p>So I have decided to reimplement this website with
+my own static generation scripts. The source will
+probably be on <a href="https://carbslinux.org/git/website/log.html">https://carbslinux.org/git/website/log.html</a>
+when I decide to publish the website.</p>
+
+<p>The generation requires Plan9 programs, although
+I have used them just for my enthusiasm. I have built
+the site with a combination of mk (instead of make), rc,
+and POSIX sh. I am not yet exactly familiar with rc,
+but I will replace the shell scripts when I feel like
+I can.</p>
+
+
+
diff --git a/src/style.css b/src/style.css
new file mode 100644
index 0000000..d3de079
--- /dev/null
+++ b/src/style.css
@@ -0,0 +1,115 @@
+/* Cem Keylan (C) 2019 */
+
+:root {
+ --color0: #0A1E2B;
+ --color1: #5C5B6F;
+ --color2: #9B506D;
+ --color3: #C34266;
+ --color4: #7B9BB7;
+ --color5: #BF6790;
+ --color6: #6a9faf;
+ --color7: #A676D2;
+ --color8: #8b8288;
+ --color9: #5C5B6F;
+ --color10: #9B506D;
+ --color11: #C34266;
+ --color12: #4E708D;
+ --color13: #BF6790;
+ --color14: #528899;
+ --color15: #c7bac3;
+ --fg: #0a1e2b;
+ --bg: #ffffff;
+ --altbg: #bf6790;
+ --link: #bf6790;
+ --linkalt: #4e708d;
+}
+
+
+html {
+ background-color: var(--bg);
+ font-family: sans-serif;
+ color: var(--fg);
+ padding-bottom: 100px;
+ -webkit-text-size-adjust: 100%;
+ -ms-text-size-adjust: 100%;
+ -ms-overflow-style: scrollbar;
+ -webkit-tap-highlight-color: transparent;
+}
+.header {
+ text-align: center;
+}
+.header strong{
+ color: var(--color5)
+}
+.header a{
+ text-decoration: none;
+ text-align: center;
+ color: var(--fg);
+ margin-left: 10px;
+ margin-right: 10px;
+}
+.header a:hover{
+ text-decoration: none;
+ text-align: center;
+ color: var(--linkalt);
+ margin-left: 10px;
+ margin-right: 10px;
+}
+.border {
+ padding-top: 1%;
+ border-bottom: solid 2px;
+ color: var(--fg);
+}
+a {
+ text-decoration: none;
+ font-weight: bold;
+ color: var(--link);
+}
+a:hover {
+ text-decoration: underline;
+ font-weight: bold;
+ color: var(--linkalt);
+}
+.post-title {
+ text-align: center;
+}
+ul li::before {
+ color: var(--color4);
+}
+body {
+ width: 80%;
+ max-width: 1050px;
+ margin-left: auto;
+ margin-right: auto;
+ margin-top: 20px;
+ overflow: none;
+ padding-right: 10px;
+ padding-left: 10px;
+ color: var(--fg);
+}
+code {
+ color: var(--fg);
+ content: "> ";
+}
+p,tr,td,table { color: var(--fg); }
+h1 {
+ color: var(--color7);
+ font-weight: bolder;
+}
+h2 {
+ color: var(--color4);
+ font-weight: bold;
+}
+h3 {
+ color: var(--fg);
+ font-weight: bold;
+}
+.footer {
+ text-align: center;
+}
+
+pre { margin-left: 2em; }
+blockquote {
+ border-left: 1px solid var(--color6);
+ font-style: italic;
+}
diff --git a/src/wiki/boot/module-management.md b/src/wiki/boot/module-management.md
deleted file mode 100644
index c9cdffb..0000000
--- a/src/wiki/boot/module-management.md
+++ /dev/null
@@ -1,15 +0,0 @@
-Title: Module Management
-
-Module Management
-=================
-
-With **busybox-init**, a module can be loaded at boot by adding such a line to your `inittab`
-
- ::once:/bin/modprobe module-name
-
-
-With **sinit**, a module can be loaded from your `/etc/rc.local` file. Add this to your file
-
- /bin/modprobe module-name
-
-
diff --git a/src/wiki/index.md b/src/wiki/index.md
deleted file mode 100644
index 3d64de9..0000000
--- a/src/wiki/index.md
+++ /dev/null
@@ -1,17 +0,0 @@
-Wiki
-================================================================================
-
-Welcome to the Carbs Linux wiki! This wiki is open for access, and can be edited
-freely by anyone who wants to contribute.
-
-If you want to make a contribution, go to
-
-Content
---------------------------------------------------------------------------------
-
-* [Module Management](boot/module-management.html)
-* [Switching to Sinit](init/switching-to-sinit.html)
-* [Install](install.html)
-* [X-keymaps](keymaps/X-keymaps.html)
-* [Keymaps in TTY](keymaps/keymaps.html)
-* [Service Management](system/service-management.html)
diff --git a/src/wiki/init/switching-to-sinit.md b/src/wiki/init/switching-to-sinit.md
deleted file mode 100644
index 180b736..0000000
--- a/src/wiki/init/switching-to-sinit.md
+++ /dev/null
@@ -1,52 +0,0 @@
-Title: Switching to Sinit
-
-Switching to Sinit
-==================
-
-Carbs Linux runs `busybox-init` by default. You can switch to
-anything else you desire, but only busybox-init and sinit are
-officially supported. Switching to sinit is extremely easy, you
-can be up and running within minutes. The only "hard" requirement
-is an environment you will be chrooting in. So, let's begin!
-
-
-Preparing your environment
---------------------------
-
-From your other environment, download the kiss-chroot utility
-and make it executable.
-
- $ wget https://dl.getkiss.org/kiss-chroot
- $ chmod +x kiss-chroot
-
- # From your environment start the chroot
- $ kiss-chroot /mnt
-
-Removing busybox-init
----------------------
-
-Now that we are in chroot environment, let's remove busybox-init.
-
- $ kiss r busybox-init
-
-
-Installing and configuring sinit
---------------------------------
-
-Build and install sinit
-
- $ kiss b sinit
- $ kiss i sinit
-
-Open up your `/etc/init/rc.conf` now and uncomment
-the variables regarding SINIT. You are ready now.
-
-If you edited your inittab, make sure you reflect your changes
-on the `/etc/init/sinit-launch-services.boot` file.
-
-
-Finishing up
-------------
-
-If all of the above is done, simply exit the chroot and reboot.
-Sinit should be functioning without any issues.
diff --git a/src/wiki/install.md b/src/wiki/install.md
deleted file mode 100644
index f49da4d..0000000
--- a/src/wiki/install.md
+++ /dev/null
@@ -1,310 +0,0 @@
-Title: Install
-
-Installation Instructions
-=========================
-
-This post will guide you step-by-step in order to install
-Carbs Linux. It is not complete yet.
-
-
-Downloading and Getting Ready to Chroot
----------------------------------------
-
-Installing Carbs Linux is the same as installing most
-rootfs distributions, such as Gentoo, or Void Linux.
-
-
-### Requirements
-
-You simply need a Live Linux ISO. Gentoo would be the best
-as programs you will require will be already there. Get the
-ISO, boot it and set up your network.
-
-**Required Programs:**
-
-* tar
-* wget
-* xz
-
-Rest of the instructions assume that you have set all of these
-up, and will continue on.
-
-
-### Download
-
-
-First, we need to download the rootfs tarball. In your terminal
-type
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz
-
-
-### Check the integrity of the tarball
-
-While optional, it is highly recommended to check the integrity
-of the tarball.
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sha256sum
- $ sha256sum -c carbs-rootfs-20191210.tar.xz.sha256sum
-
-
-### Check the signatures
-
-While optional, it is highly recommended to check the signature
-of the tarball
-
- $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sig
-
- Import the public key of release@carbslinux.org
-
- $ gpg --recv-keys FF484BDFEFCEF8FF
-
- $ gpg --verify carbs-rootfs-20191210.tar.xz.sig
-
-### Download Kiss Linux Chroot Helper
-
- $ wget https://dl.getkiss.org/kiss-chroot
-
- Make the script executable
-
- $ chmod +x kiss-chroot
-
-### Extract the rootfs tarball
-
-You need to extract the tarball to your mounted partition
-
- $ tar xvpf carbs-rootfs-20191210.tar.xz -C /mnt
-
-Chroot
-------
-Chroot into Carbs Linux
-
- $ ./kiss-chroot /mnt
-
-### Enable repository signing (Highly Recommended)
-
-This step is optional, but very highly recommended
-(I cannot stress out the amount I am recommending this).
-This ensures you are receiving updates from Carbs Linux
-and not some other source.
-
-**Install GnuPG**
-
-It is also a great time to learn how to use your new
-package manager, KISS! You simply build and install
-the package
-
- $ kiss build gnupg1
- $ kiss install gnupg1
-
-**Import my key**
-
-
- Import my public key (cem@ckyln.com)
-
- $ gpg --recv-key 4356EE08A364CE09
-
- Create a .gnupg directory if it doesn't exist
-
- $ mkdir -p /root/.gnupg
-
- Trust my public key
-
- $ echo trusted-key 0x4356ee08a364ce09 >> /root/.gnupg/gpg.conf
-
-**Enable signature verification**
-
-
-Git has a built in signature verification feature.
-You can go to the repository directory and enable it
-
- $ cd /var/db/kiss/repo
- $ git config merge.verifySignatures true
-
-### Installing Important Tools
-
-Since Carbs gives you one of the most minimal base,
-you might need to apply some add-ons to your system.
-
-**Update packages**
-
-It might be a good idea to update your packages before
-installing new packages. This ensure compatibility.
-
- $ kiss update
-
-**Filesystems**
-
-
-Currently, e2fsprogs and dosfstools are supported,
-as they are the most-used filesystems.
-
- Support for ext2, ext3, and ex4
-
- $ kiss build e2fsprogs
- $ kiss install e2fsprogs
-
- Support for dosfstools
-
- $ kiss build dosfstools
- $ kiss install dosfstools
-
-**Device management**
-
- $ kiss build eudev
- $ kiss install eudev
-
-**Wireless**
-
-**wpa_supplicant**
-
- $ kiss build wpa_supplicant
- $ kiss install wpa_supplicant
-
-**eiwd (WIP)**
-
- $ kiss build eiwd
- $ kiss install eiwd
-
-**dhcpcd**
-
- $ kiss build dhcpcd
- $ kiss install dhcpcd
-
-**Shells**
-
-Carbs Linux comes preinstalled with busybox ash, but other shells
-can be found on the repository
-
- Install bash
-
- $ kiss build bash
- $ kiss install bash
-
- Install zsh
-
- $ kiss build zsh
- $ kiss install zsh
-
- Install Plan9 rc-shell
-
- $ kiss build 9base
- $ kiss install 9base
-
-
-### Install the Kernel
-
-**IMPORTANT:** If you have GCC 10.x on your system, you need to apply
-this [patch] to your kernel sources. Otherwise your kernel will panic
-during the boot stage.
-
-Next step is installing the kernel, which might sound as a challenge
-you should download and extract the kernel tarball first.
-
- $ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz
-
- Let's move the sources to /usr/src
-
- $ mv linux-5.5.tar.xz /usr/src
- $ tar xf linux-5.5.tar.xz
- $ cd linux-5.5
-
-[patch]: https://dl.carbslinux.org/distfiles/linux-gcc-10-bootfix.patch
-
-**Configure the Kernel**
-
-You can check
-to learn more about kernel configuration. Overall, [Gentoo Wiki](https://wiki.gentoo.org)
-is a good place to learn about kernel configuration related to
-your hardware.
-
-**Build and install the kernel**
-
-The rest of it is simple, build the kernel with
-`make` and install it with `make install`
-
-### Bootloader
-
-The default bootloader is GRUB (GRand Unified Bootloader).
-
-Build and install GRUB
-
- $ kiss b grub
- $ kiss i grub
-
- Install efibootmgr as well if your
- system requires it
-
- $ kiss b efibootmgr
- $ kiss i efibootmgr
-
-
-**Setup GRUB**
-
- For BIOS:
- $ grub-install --target=i386-pc /dev/sdX
-
- For UEFI:
- $ grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=CarbsLinux
-
- $ grub-mkconfig -o /boot/grub/grub.cfg
-
-
-### Install init
-
-Currently, default init for Carbs Linux is `sinit`, but
-busybox-init is also supported. You can also change this yourself.
-
-To install init, you have to
-
- $ kiss b sinit
- $ kiss i sinit
-
-This will also fetch busybox-init as its dependency.
-
-
-### Enabling other repositories
-
-There are other repositories out there that might be of your
-interest. The Official Repositories come with community and testing
-repositories that are not enabled by default. You could also want to
-add the Kiss Linux community repository, or someone's personal kiss
-repository.
-
-**Obtaining repositories**
-
-Obtaining a repository is as simple as a git clone. You can do it
-with Cem's personal repository as an example, but any other repository
-will be the same.
-
- # Clone the repository to your desired location
- # Optionally add "--depth 1" to save precious disk space
-
- $ git clone --depth 1 git://git.ckyln.com/kiss-repository /var/db/kiss/cem-repository
-
-That's it, you have obtained a new repository!
-
-Adding a repository to your KISS_PATH
-
-Now that we have obtained Cem's repository, we can add it to our KISS\_PATH!
-
-We need to edit `/etc/profile.d/kiss_path.sh` for this, but you
-can also change your KISS\_PATH from your shellrc.
-
-Add the full path to the repository, in this case
-`/var/db/kiss/cem-repository/cem` to the variable
-and add a `:` before/after it.
-
-It must be looking like this.
-
- export KISS_PATH=/var/db/kiss/repo/core:/var/db/kiss/repo/extra:/var/db/kiss/repo/xorg:/var/db/kiss/cem-repository/cem
-
-Update your shell variables by doing `. /etc/profile.d/kiss_path.sh` so you can
-immediately access the repository packages
-
-
-More
-----
-
-You should now be able to boot into you Carbs Linux installation.
-To learn more, you can visit the [wiki](//carbslinux.org/wiki)
diff --git a/src/wiki/keymaps/X-keymaps.md b/src/wiki/keymaps/X-keymaps.md
deleted file mode 100644
index e69de29..0000000
diff --git a/src/wiki/keymaps/keymaps.md b/src/wiki/keymaps/keymaps.md
deleted file mode 100644
index 6bcce03..0000000
--- a/src/wiki/keymaps/keymaps.md
+++ /dev/null
@@ -1,53 +0,0 @@
-Title: Keymaps in TTY
-
-Installing and Using Keymaps
-============================
-
-Unlike most other distributions out there
-Carbs Linux does not come preinstalled with console
-keys. You probably won't be using more than
-two either. There are two ways of using keymaps
-
-Installing the "bkeymaps" package
----------------------------------
-
-You can get the `bkeymaps` package from the
-[KISS community repository](https://github.com/kisslinux/community).
-
-Build and install `bkeymaps`.
-
- -> kiss b bkeymaps
- -> kiss i bkeymaps
-
-Now you can find the keymaps in `/usr/share/bkeymaps`.
-
-
-Downloading the keymaps you require
------------------------------------
-
-*This will assume that you are using the us keyboard layout*
-
-You firstly will need to go to
-and download the keymap you need
-
-Loading keymap, doing it on login/boot
---------------------------------------
-
-- Run `loadkmap < file` to load the keymap.
-
-**Load keymap at login**
-
-If you want to load a keymap at login, you can
-add the command above to your `.profile` file.
-
-**Load keymap at boot**
-
-You can also load keymap during boot. You should edit
-`/lib/init/rc.boot` file and add something like
-
- # assuming you are using trq as your keymap
- log "Setting keymap to trq..."; {
- loadkmap < /path/to/trq.bmap
- }
-
-to your main function.
diff --git a/src/wiki/system/service-management.md b/src/wiki/system/service-management.md
deleted file mode 100644
index 8aff8a6..0000000
--- a/src/wiki/system/service-management.md
+++ /dev/null
@@ -1,82 +0,0 @@
-Title: Service Management
-
-Carbs Linux uses `busybox-runit` by default, but the repository additionally has the
-original `runit` and `sysmgr`. You can install either with `kiss b runit; kiss i runit`
-or `kiss b sysmgr; kiss i sysmgr`.
-
-runit
-=====
-
-**Enabling a Service**
-
- ln -sf /etc/sv/acpid /var/service
-
-**Disabling a Service**
-
- unlink /var/service/acpid
-
-**Starting a Service**
-
- sv start acpid
-
-**Stopping a Service**
-
- sv stop acpid
-
-For more information refer to the `sv --help` output. Also check out the `sv(8)`
-manual page if you have installed the `runit` package.
-
-
-sysmgr
-======
-
-[sysmgr] is POSIX-sh service supervisor written by me. Its usage resembles
-`runit`. The biggest difference is that `sysmgr` uses service files instead
-of directories with run scripts inside.
-
-
-svctl
------
-
-`svctl` is the equivalant of `sv` for sysmgr. You can run the above commands for
-`runit` and use `svctl` instead of `sv`. Those would be as follows.
-
-
-**Enabling a Service**
-
- ln -sf /etc/sysmgr/acpid /var/sysmgr
-
-**Disabling a Service**
-
- unlink /var/sysmgr/acpid
-
-**Starting a Service**
-
- svctl start acpid
-
-**Stopping a Service**
-
- svctl stop acpid
-
-
-Switching from runit
---------------------
-
-Switching from `runit` is fairly easy. You can run the following commands to get
-started with `sysmgr`.
-
-
- # Create the directories if you haven't yet
- mkdir -p /var/sysmgr /etc/sysmgr
-
- # Copy all of the run scripts to /etc/sysmgr
- set -- /etc/sv/*
- for service; do cp "$service/run" "/etc/sysmgr/${service##*/}" ; done
-
- # Link all enabled services
- set -- /var/service/*
- for service; do ln -sf /etc/sysmgr/${service##*/} /var/sysmgr ; done
-
-
-
-[sysmgr]: https://github.com/cemkeylan/sysmgr
--
cgit v1.2.3