aboutsummaryrefslogtreecommitdiff
path: root/docs/rss.xml
diff options
context:
space:
mode:
authorCem Keylan <cem@ckyln.com>2020-05-08 03:51:30 +0300
committerCem Keylan <cem@ckyln.com>2020-05-08 03:51:30 +0300
commite527fbafdf0236608eeb2b0b0a92aa354df865fe (patch)
tree03e5aa9fa684f526dfeec5fa8bf52c99e223be38 /docs/rss.xml
parentc99d8f399d839567a6878d05c2ae9119ea1d407d (diff)
downloadwebsite-e527fbafdf0236608eeb2b0b0a92aa354df865fe.tar.gz
update
Diffstat (limited to 'docs/rss.xml')
-rw-r--r--docs/rss.xml125
1 files changed, 124 insertions, 1 deletions
diff --git a/docs/rss.xml b/docs/rss.xml
index cdacc27..7126fe8 100644
--- a/docs/rss.xml
+++ b/docs/rss.xml
@@ -9,7 +9,130 @@
<description>a simple busybox linux distribution</description>
<link>https://carbslinux.org</link>
<atom:link href="https://carbslinux.org/rss.xml" rel="self" type="application/rss+xml" />
-<lastBuildDate>Apr Thu 2020 09:00</lastBuildDate>
+<lastBuildDate>May Fri 2020 00:00</lastBuildDate>
+<item>
+<title>The Relation of Carbs and KISS</title>
+<pubDate>Fri, 08 May 2020</pubDate>
+<dc:creator>Cem Keylan</dc:creator>
+<link>https://carbslinux.org/blog/20200508.html</link>
+<description>&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; May 08 2020&lt;/p&gt;
+
+&lt;p&gt;Since I have forked KISS, I have received many questions
+that can be summarized as &amp;ldquo;Why?&amp;rdquo;. I have realized that I
+never truly answered this question. That&amp;rsquo;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
+&amp;ldquo;FAQ&amp;rdquo; page later on.&lt;/p&gt;
+
+&lt;h2&gt;History&lt;/h2&gt;
+
+&lt;p&gt;I had the idea of creating my own Linux distribution since
+the May of 2019. Back then, I had my own &lt;a href=&quot;https://linuxfromscratch.org&quot;&gt;Linux from Scratch&lt;/a&gt;
+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&amp;rsquo;t satisfied with anything I had built.&lt;/p&gt;
+
+&lt;p&gt;I had written some incomplete package managers (all named &lt;code&gt;fat&lt;/code&gt;)
+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 &amp;ldquo;initial commit&amp;rdquo; until a program I write
+is in a usable state.&lt;/p&gt;
+
+&lt;p&gt;I have obtained the &amp;lsquo;carbslinux.org&amp;rsquo; domain name in September
+2019, but then life got on the way, and I stopped for a long
+time.&lt;/p&gt;
+
+&lt;p&gt;One day on Reddit, I saw Dylan&amp;rsquo;s post on &lt;a href=&quot;https://reddit.com/r/unixporn&quot;&gt;r/unixporn&lt;/a&gt; about
+KISS, and I really thought that it was interesting. Here is
+my &lt;a href=&quot;https://www.reddit.com/r/unixporn/comments/ducd34/sowm_kiss_d/f7lua7x&quot;&gt;comment&lt;/a&gt; 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.&lt;/p&gt;
+
+&lt;h2&gt;Differences between KISS and Carbs&lt;/h2&gt;
+
+&lt;p&gt;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&amp;rsquo;t something like a
+downstream fork of KISS, it is just a distribution that was
+initially based on KISS.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;h2&gt;What I&amp;rsquo;m working on now&lt;/h2&gt;
+
+&lt;p&gt;Currently I have a few projects that I&amp;rsquo;m working on for Carbs.
+These are,&lt;/p&gt;
+
+&lt;p&gt;A BSD port for Carbs. For a while, I have been working on BSD
+compatibility on my fork of the &lt;a href=&quot;https://github.com/carbslinux/kiss&quot;&gt;package manager&lt;/a&gt;. 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&amp;rsquo;t familiar with BSD, BSD has a single source code
+for all of the utilities. Contributions (even chipping in ideas)
+are very welcome.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;h2&gt;What&amp;rsquo;s up with all the init/service daemons?&lt;/h2&gt;
+
+&lt;p&gt;If you have ever checked the &lt;a href=&quot;https://github.com/carbslinux/repository&quot;&gt;repository&lt;/a&gt;, 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 &lt;a href=&quot;https://github.com/cemkeylan/shinit&quot;&gt;init daemon&lt;/a&gt;
+and &lt;a href=&quot;https://github.com/cemkeylan/sysmgr&quot;&gt;service supervisor&lt;/a&gt;. I maintain all those packages on KISS
+Community Repository as well with the exception of busybox. Those
+are, &lt;code&gt;busybox init/runit&lt;/code&gt;, &lt;code&gt;runit&lt;/code&gt;, &lt;code&gt;sinit&lt;/code&gt;, and &lt;code&gt;sysmgr&lt;/code&gt;. I would
+definitely recommend checking out &lt;code&gt;shinit&lt;/code&gt; and &lt;code&gt;sysmgr&lt;/code&gt;.&lt;/p&gt;
+
+&lt;h2&gt;Why I don&amp;rsquo;t publicize Carbs&lt;/h2&gt;
+
+&lt;p&gt;There are a couple of reasons I don&amp;rsquo;t publicize Carbs a lot.&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;
+
+&lt;p&gt;Since I cannot answer questions like &amp;ldquo;What is the difference?&amp;rdquo;, I
+prefer staying as the silent sibling project of KISS Linux. Plus,
+there is no point in dividing the newly-emerging community in half.&lt;/p&gt;
+
+&lt;p&gt;That&amp;rsquo;s not because I don&amp;rsquo;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.&lt;/p&gt;
+
+&lt;p&gt;I think that&amp;rsquo;s about it, if you have questions you can send me a
+mail, ping me on IRC (my handle is &lt;code&gt;merakor&lt;/code&gt;), and I will be happy
+to answer. Maybe your question fits this post, and I can update it
+to thoroughly give an explanation.&lt;/p&gt;
+
+&lt;p&gt;Cheers,
+Cem&lt;/p&gt;</description>
+</item>
<item>
<title>Outsource Repository Concept</title>
<pubDate>Fri, 10 Apr 2020</pubDate>