From 95f85480de7eec5ba26fd54b7d8994f09e550225 Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Tue, 2 Feb 2021 09:40:22 +0300 Subject: site: remove generated files I will be publishing the website through post-receive hooks so that every minor change doesn't generate thousands of lines of git logs. --- .gitignore | 6 + blog/index.org | 11 - blog/rss.org | 463 ----- docs/blog/20200128.html | 60 - docs/blog/20200406.html | 135 -- docs/blog/20200410.html | 69 - docs/blog/20200508.html | 185 -- docs/blog/20200528.html | 92 - docs/blog/20200617.html | 149 -- docs/blog/20200803.html | 134 -- docs/blog/20201210.html | 66 - docs/blog/index.html | 54 - docs/docs.html | 143 -- docs/docs.txt | 98 -- docs/docs/carbslinux.html | 1786 -------------------- docs/docs/carbslinux.txt | 1356 --------------- docs/docs/carbslinux/0010.html | 50 - docs/docs/carbslinux/0011.html | 50 - docs/docs/carbslinux/0012.html | 50 - docs/docs/carbslinux/0013.html | 50 - docs/docs/carbslinux/1010.html | 50 - docs/docs/carbslinux/1020.html | 50 - docs/docs/carbslinux/1030.html | 50 - docs/docs/carbslinux/1040.html | 50 - docs/docs/carbslinux/1041.html | 50 - docs/docs/carbslinux/1042.html | 50 - docs/docs/carbslinux/1043.html | 50 - docs/docs/carbslinux/1050.html | 50 - docs/docs/carbslinux/2010.html | 50 - docs/docs/carbslinux/2020.html | 50 - docs/docs/carbslinux/2030.html | 50 - docs/docs/carbslinux/2040.html | 50 - docs/docs/carbslinux/2050.html | 50 - docs/docs/carbslinux/2210.html | 50 - docs/docs/carbslinux/2211.html | 50 - docs/docs/carbslinux/2212.html | 50 - docs/docs/carbslinux/2220.html | 50 - docs/docs/carbslinux/2230.html | 50 - docs/docs/carbslinux/2240.html | 50 - docs/docs/carbslinux/2241.html | 50 - ...How-to-use-this-License-for-your-documents.html | 50 - docs/docs/carbslinux/Bootloader.html | 92 - docs/docs/carbslinux/Building-the-kernel.html | 73 - docs/docs/carbslinux/Changing-Init-Program.html | 87 - docs/docs/carbslinux/Chroot.html | 81 - docs/docs/carbslinux/Configuring-Init.html | 79 - docs/docs/carbslinux/Configuring-hostname.html | 69 - docs/docs/carbslinux/Contribution-Guidelines.html | 71 - docs/docs/carbslinux/Conventions.html | 97 -- docs/docs/carbslinux/Download.html | 72 - docs/docs/carbslinux/Essential-Software.html | 121 -- docs/docs/carbslinux/Extracting-the-tarball.html | 71 - docs/docs/carbslinux/Fstab.html | 71 - .../carbslinux/GNU-Free-Documentation-License.html | 550 ------ docs/docs/carbslinux/Hosts-file.html | 71 - docs/docs/carbslinux/Init-Hooks.html | 86 - docs/docs/carbslinux/Init-System.html | 74 - docs/docs/carbslinux/Init-scripts.html | 69 - docs/docs/carbslinux/Installation.html | 85 - docs/docs/carbslinux/Installing-packages.html | 72 - docs/docs/carbslinux/KISS-repositories.html | 66 - docs/docs/carbslinux/Kernel-Command-Line.html | 84 - docs/docs/carbslinux/Kernel-dependencies.html | 82 - docs/docs/carbslinux/Kernel.html | 75 - .../carbslinux/Making-your-system-bootable.html | 75 - docs/docs/carbslinux/Obtain-the-chroot-helper.html | 70 - .../carbslinux/Obtaining-the-documentation.html | 78 - .../carbslinux/Obtaining-the-kernel-sources.html | 75 - docs/docs/carbslinux/Post_002dinstallation.html | 71 - docs/docs/carbslinux/Preparing-Environment.html | 89 - .../carbslinux/Rebooting-after-changing-init.html | 74 - docs/docs/carbslinux/Repository-Conventions.html | 220 --- docs/docs/carbslinux/Setting-up-repositories.html | 118 -- docs/docs/carbslinux/Shell-Conventions.html | 105 -- docs/docs/carbslinux/Signature-verification.html | 71 - docs/docs/carbslinux/System-Configuration.html | 72 - docs/docs/carbslinux/Updating-packages.html | 70 - .../_002fetc_002finit_002frcconf-file.html | 67 - docs/docs/carbslinux/index.html | 283 ---- docs/download.html | 65 - docs/download.txt | 46 - docs/index.html | 178 -- docs/index.txt | 133 -- docs/install.html | 663 -------- docs/install.txt | 479 ------ docs/mailing-lists.html | 49 - docs/mailing-lists.txt | 19 - docs/news.xml | 278 --- docs/news/20191210.html | 43 - docs/news/20191210.txt | 13 - docs/news/20191212.html | 44 - docs/news/20191212.txt | 11 - docs/news/20191217.html | 43 - docs/news/20191217.txt | 11 - docs/news/20191218.html | 43 - docs/news/20191218.txt | 10 - docs/news/20200109.html | 56 - docs/news/20200109.txt | 26 - docs/news/20200110.html | 43 - docs/news/20200110.txt | 10 - docs/news/20200113.html | 67 - docs/news/20200113.txt | 30 - docs/news/20200115.html | 43 - docs/news/20200115.txt | 10 - docs/news/20200122.html | 44 - docs/news/20200122.txt | 11 - docs/news/20200128.html | 52 - docs/news/20200128.txt | 16 - docs/news/20200213.html | 45 - docs/news/20200213.txt | 13 - docs/news/20200214.html | 93 - docs/news/20200214.txt | 55 - docs/news/20200218.html | 53 - docs/news/20200218.txt | 17 - docs/news/20200405.html | 56 - docs/news/20200405.txt | 21 - docs/news/20200406.html | 43 - docs/news/20200406.txt | 10 - docs/news/20200410.html | 43 - docs/news/20200410.txt | 10 - docs/news/20200427.html | 48 - docs/news/20200427.txt | 13 - docs/news/20200510.html | 48 - docs/news/20200510.txt | 18 - docs/news/20200519.html | 44 - docs/news/20200519.txt | 11 - docs/news/20200526.html | 44 - docs/news/20200526.txt | 14 - docs/news/20200617.html | 44 - docs/news/20200617.txt | 11 - docs/news/20200727.html | 46 - docs/news/20200727.txt | 13 - docs/news/20200903.html | 45 - docs/news/20200903.txt | 12 - docs/news/20200916.html | 45 - docs/news/20200916.txt | 12 - docs/news/index.html | 238 --- docs/news/index.txt | 209 --- docs/people.html | 47 - docs/people.txt | 7 - docs/rss.xml | 655 ------- docs/style.css | 243 --- news/index.org | 107 -- news/latest-news.org | 19 - news/news.org | 172 -- 145 files changed, 6 insertions(+), 15047 deletions(-) delete mode 100644 blog/index.org delete mode 100644 blog/rss.org delete mode 100644 docs/blog/20200128.html delete mode 100644 docs/blog/20200406.html delete mode 100644 docs/blog/20200410.html delete mode 100644 docs/blog/20200508.html delete mode 100644 docs/blog/20200528.html delete mode 100644 docs/blog/20200617.html delete mode 100644 docs/blog/20200803.html delete mode 100644 docs/blog/20201210.html delete mode 100644 docs/blog/index.html delete mode 100644 docs/docs.html delete mode 100644 docs/docs.txt delete mode 100644 docs/docs/carbslinux.html delete mode 100644 docs/docs/carbslinux.txt delete mode 100644 docs/docs/carbslinux/0010.html delete mode 100644 docs/docs/carbslinux/0011.html delete mode 100644 docs/docs/carbslinux/0012.html delete mode 100644 docs/docs/carbslinux/0013.html delete mode 100644 docs/docs/carbslinux/1010.html delete mode 100644 docs/docs/carbslinux/1020.html delete mode 100644 docs/docs/carbslinux/1030.html delete mode 100644 docs/docs/carbslinux/1040.html delete mode 100644 docs/docs/carbslinux/1041.html delete mode 100644 docs/docs/carbslinux/1042.html delete mode 100644 docs/docs/carbslinux/1043.html delete mode 100644 docs/docs/carbslinux/1050.html delete mode 100644 docs/docs/carbslinux/2010.html delete mode 100644 docs/docs/carbslinux/2020.html delete mode 100644 docs/docs/carbslinux/2030.html delete mode 100644 docs/docs/carbslinux/2040.html delete mode 100644 docs/docs/carbslinux/2050.html delete mode 100644 docs/docs/carbslinux/2210.html delete mode 100644 docs/docs/carbslinux/2211.html delete mode 100644 docs/docs/carbslinux/2212.html delete mode 100644 docs/docs/carbslinux/2220.html delete mode 100644 docs/docs/carbslinux/2230.html delete mode 100644 docs/docs/carbslinux/2240.html delete mode 100644 docs/docs/carbslinux/2241.html delete mode 100644 docs/docs/carbslinux/ADDENDUM-How-to-use-this-License-for-your-documents.html delete mode 100644 docs/docs/carbslinux/Bootloader.html delete mode 100644 docs/docs/carbslinux/Building-the-kernel.html delete mode 100644 docs/docs/carbslinux/Changing-Init-Program.html delete mode 100644 docs/docs/carbslinux/Chroot.html delete mode 100644 docs/docs/carbslinux/Configuring-Init.html delete mode 100644 docs/docs/carbslinux/Configuring-hostname.html delete mode 100644 docs/docs/carbslinux/Contribution-Guidelines.html delete mode 100644 docs/docs/carbslinux/Conventions.html delete mode 100644 docs/docs/carbslinux/Download.html delete mode 100644 docs/docs/carbslinux/Essential-Software.html delete mode 100644 docs/docs/carbslinux/Extracting-the-tarball.html delete mode 100644 docs/docs/carbslinux/Fstab.html delete mode 100644 docs/docs/carbslinux/GNU-Free-Documentation-License.html delete mode 100644 docs/docs/carbslinux/Hosts-file.html delete mode 100644 docs/docs/carbslinux/Init-Hooks.html delete mode 100644 docs/docs/carbslinux/Init-System.html delete mode 100644 docs/docs/carbslinux/Init-scripts.html delete mode 100644 docs/docs/carbslinux/Installation.html delete mode 100644 docs/docs/carbslinux/Installing-packages.html delete mode 100644 docs/docs/carbslinux/KISS-repositories.html delete mode 100644 docs/docs/carbslinux/Kernel-Command-Line.html delete mode 100644 docs/docs/carbslinux/Kernel-dependencies.html delete mode 100644 docs/docs/carbslinux/Kernel.html delete mode 100644 docs/docs/carbslinux/Making-your-system-bootable.html delete mode 100644 docs/docs/carbslinux/Obtain-the-chroot-helper.html delete mode 100644 docs/docs/carbslinux/Obtaining-the-documentation.html delete mode 100644 docs/docs/carbslinux/Obtaining-the-kernel-sources.html delete mode 100644 docs/docs/carbslinux/Post_002dinstallation.html delete mode 100644 docs/docs/carbslinux/Preparing-Environment.html delete mode 100644 docs/docs/carbslinux/Rebooting-after-changing-init.html delete mode 100644 docs/docs/carbslinux/Repository-Conventions.html delete mode 100644 docs/docs/carbslinux/Setting-up-repositories.html delete mode 100644 docs/docs/carbslinux/Shell-Conventions.html delete mode 100644 docs/docs/carbslinux/Signature-verification.html delete mode 100644 docs/docs/carbslinux/System-Configuration.html delete mode 100644 docs/docs/carbslinux/Updating-packages.html delete mode 100644 docs/docs/carbslinux/_002fetc_002finit_002frcconf-file.html delete mode 100644 docs/docs/carbslinux/index.html delete mode 100644 docs/download.html delete mode 100644 docs/download.txt delete mode 100644 docs/index.html delete mode 100644 docs/index.txt delete mode 100644 docs/install.html delete mode 100644 docs/install.txt delete mode 100644 docs/mailing-lists.html delete mode 100644 docs/mailing-lists.txt delete mode 100644 docs/news.xml delete mode 100644 docs/news/20191210.html delete mode 100644 docs/news/20191210.txt delete mode 100644 docs/news/20191212.html delete mode 100644 docs/news/20191212.txt delete mode 100644 docs/news/20191217.html delete mode 100644 docs/news/20191217.txt delete mode 100644 docs/news/20191218.html delete mode 100644 docs/news/20191218.txt delete mode 100644 docs/news/20200109.html delete mode 100644 docs/news/20200109.txt delete mode 100644 docs/news/20200110.html delete mode 100644 docs/news/20200110.txt delete mode 100644 docs/news/20200113.html delete mode 100644 docs/news/20200113.txt delete mode 100644 docs/news/20200115.html delete mode 100644 docs/news/20200115.txt delete mode 100644 docs/news/20200122.html delete mode 100644 docs/news/20200122.txt delete mode 100644 docs/news/20200128.html delete mode 100644 docs/news/20200128.txt delete mode 100644 docs/news/20200213.html delete mode 100644 docs/news/20200213.txt delete mode 100644 docs/news/20200214.html delete mode 100644 docs/news/20200214.txt delete mode 100644 docs/news/20200218.html delete mode 100644 docs/news/20200218.txt delete mode 100644 docs/news/20200405.html delete mode 100644 docs/news/20200405.txt delete mode 100644 docs/news/20200406.html delete mode 100644 docs/news/20200406.txt delete mode 100644 docs/news/20200410.html delete mode 100644 docs/news/20200410.txt delete mode 100644 docs/news/20200427.html delete mode 100644 docs/news/20200427.txt delete mode 100644 docs/news/20200510.html delete mode 100644 docs/news/20200510.txt delete mode 100644 docs/news/20200519.html delete mode 100644 docs/news/20200519.txt delete mode 100644 docs/news/20200526.html delete mode 100644 docs/news/20200526.txt delete mode 100644 docs/news/20200617.html delete mode 100644 docs/news/20200617.txt delete mode 100644 docs/news/20200727.html delete mode 100644 docs/news/20200727.txt delete mode 100644 docs/news/20200903.html delete mode 100644 docs/news/20200903.txt delete mode 100644 docs/news/20200916.html delete mode 100644 docs/news/20200916.txt delete mode 100644 docs/news/index.html delete mode 100644 docs/news/index.txt delete mode 100644 docs/people.html delete mode 100644 docs/people.txt delete mode 100644 docs/rss.xml delete mode 100644 docs/style.css delete mode 100644 news/index.org delete mode 100644 news/latest-news.org delete mode 100644 news/news.org diff --git a/.gitignore b/.gitignore index 4dbe29f..167d057 100644 --- a/.gitignore +++ b/.gitignore @@ -1 +1,7 @@ /.cache/ +/news/index.org +/news/news.org +/news/latest-news.org +/blog/index.org +/blog/rss.org +/docs/ diff --git a/blog/index.org b/blog/index.org deleted file mode 100644 index 875b133..0000000 --- a/blog/index.org +++ /dev/null @@ -1,11 +0,0 @@ -#+TITLE: Blog Index - -This is the Carbs Linux blog index. You can find every post here. [[file:../rss.xml][RSS Feed]] -- [[file:20201210.org][First Year of Carbs Linux]] /posted on 2020-12-10/ -- [[file:20200803.org][August 2020 News Post]] /posted on 2020-08-03/ -- [[file:20200617.org][June Newspost]] /posted on 2020-06-17/ -- [[file:20200528.org][kiss 2.0.0 and Overall Changes]] /posted on 2020-05-28/ -- [[file:20200508.org][The Relation of Carbs and KISS]] /posted on 2020-05-08/ -- [[file:20200410.org][Outsource Repository Concept]] /posted on 2020-04-10/ -- [[file:20200406.org][Roadmap for Carbs]] /posted on 2020-04-06/ -- [[file:20200128.org][Switching to New Website]] /posted on 2020-01-28/ diff --git a/blog/rss.org b/blog/rss.org deleted file mode 100644 index 629b8ca..0000000 --- a/blog/rss.org +++ /dev/null @@ -1,463 +0,0 @@ -#+TITLE: Carbs Linux blog -#+DESCRIPTION: a simple Linux distribution - -* First Year of Carbs Linux -:PROPERTIES: -:RSS_PERMALINK: 20201210.html -:PUBDATE: 2020-12-10 -:ID: 675c108e-10d5-46b1-9fc5-d3d3b41e7726 -:END: -December 10, 2020 marks the first year after the initial release of Carbs Linux. -When I forked the KISS Linux repository on the 9th of December, I was fairly new -to package management. Carbs Linux used to be almost identical to KISS Linux. A -lot has changed since then: - -[2020 Jan 13] Replaced default init system to =sinit= -[2020 Jan 15] Packaged =WebKit2GTK= -[2020 May 17] Added =bearssl= on the testing repository -[2020 May 28] Added =rsync= repository support to kiss -[2020 Jun 03] Replaced =bison= with =byacc= -[2020 Jun 11] Replaced =libressl= with =bearssl= -[2020 Jun 24] Replaced =kiss= with =cpt= - -I have really enjoyed maintaining and developing this distribution, and I want -to thank everyone who was involved in some way or another. While I have slowed -down in development due to college workload, I am still actively maintaining all -the packages on the repository. I do have some ideas that I am thinking of -implementing during the semester break. Hope to see you all in January. -* August 2020 News Post -:PROPERTIES: -:RSS_PERMALINK: 20200803.html -:PUBDATE: 2020-08-03 -:ID: bb30fdcc-88ed-49e7-93ee-f67b870031c6 -:END: -We are having some stalls during this summer, as I am currently working on -university-related stuff. Nonetheless, there are some important changes that I -want to share in this month's post. - -#+toc: headlines 1 local - -** Carbs Packaging Tools - :PROPERTIES: - :ID: 3d410aeb-3a3e-4239-929d-2fb577888b80 - :END: - -This month I have reworked =kiss= into a new package manager, now renamed as -=cpt=. Updating =kiss= will now bootstrap the new package manager, so you don't -have to manually edit your system. If you don't like the idea of this, you can -look up the =post-install= script on =core/kiss= and apply the changes manually. - -You will also need to rename your =KISS_*= variables to =CPT_*=. So, =KISS_PATH= -becomes =CPT_PATH=. - -The rework changes the previous commands on the package manager into standalone -tools, and move the package manager functions to a library. This makes it easier -for a user to import functions and variables from the package manager, and -extend the package manager with their own intended way. Previously this required -ugly hacks and workarounds to use the package manager functions. I will be -making use of these changes to re-implement binary package management functions -as well. - -If you want to use the library on your script you can simply do this: - -#+begin_src sh - #!/bin/sh - . cpt-lib - (...) -#+end_src - -There are obviously some clean-up and simplifications needed in this new -tool-based package management method. - -** Docs - :PROPERTIES: - :ID: fa69f4b3-6b22-4ebe-80cc-0e7a9eb94fb3 - :END: - -I have added documentation for the distribution, and finally updated the guide -for installation. It is now /almost/ complete. These docs can be installed to -your system for online viewing. I will also add a documentation crawler similar -to how werc works (but as an offline viewer). You can find =carbs-docs= from -the repository. Currently, the documentation lacks but I will be adding new -stuff. These will solely be distribution specific documentation and will not be -a wiki-like source. If anyone would like to contribute to a wiki-like -documentation source, I would happily re-open the distribution wiki. You can -find the source on [[https://github.com/CarbsLinux/docs]]. - -** Re-opening the Carbs Linux server - :PROPERTIES: - :ID: 01c7351d-4a89-4039-a5ba-2dde3f8a9dca - :END: - -Back in May, I had shutdown the Carbs Linux server due to financial issues, but -I am slowly reverting to the self-hosted model. Back then, the git repositories -were mirrored to GitHub, and the management was overall much more flexible. The -server used to run Carbs Linux as well (that was fun and horrifying at the same -time). Now, I will be relaunching the git server which will be the upstream -source before August 5. You can switch your remote, but GitHub will stay as a -remote nonetheless. - -*EDIT:* The git-server is up! -* June Newspost -:PROPERTIES: -:RSS_PERMALINK: 20200617.html -:PUBDATE: 2020-06-17 -:ID: 4168855b-e76e-4f8f-803d-b4034152c734 -:END: -This will be an active month for Carbs as major changes to the base and the -package manager will be coming up. - -** Statically linking the base - :PROPERTIES: - :ID: 558e3a55-78ea-45ff-a299-c27e0391744f - :END: - -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. - -I believe that binaries on the core should always be linked statically. This -ensures that an SONAME bump to =libObscure.so= 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. - -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. - -** Major changes on the core repository - :PROPERTIES: - :ID: eb4a6712-9853-4b5f-8978-f85fef463a40 - :END: - -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. - -*** Removed from Core - :PROPERTIES: - :ID: 271cdfd8-5e0c-43c5-8ddb-1a162bcfb7ed - :END: -=git= -=libressl= -=grub= -=bison= -=dhcpcd= -=ubase= - -*** Added to Core - :PROPERTIES: - :ID: a7f46eb4-e41d-438e-9858-68a5c5b20f4a - :END: -=bearssl=, as a =libressl= replacement -=byacc=, as a =bison= replacement - -*** Statically linked - :PROPERTIES: - :ID: f19dd4ac-438b-47c3-bbe7-ba87085027be - :END: -=kiss= -=neatvi= -=mandoc= -=byacc= -=m4= -=e2fsprogs= -=make= -=pkgconf= -=sbase= -=libnl= -=wpa_supplicant= -=bearssl= - -** Making the wiki available offline - :PROPERTIES: - :ID: e8613bd1-b09e-4f12-9c3f-129d70fb7f43 - :END: - -Soon, all documentation regarding Carbs Linux will be avaialable to be installed -from the core repository in a =carbs-docs= 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. - -** ISO image for Carbs - :PROPERTIES: - :ID: 88169788-702b-46a3-b2ec-909e98caae92 - :END: - -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 =arch-install-scripts=. Let's see how that's going to play out. -* kiss 2.0.0 and Overall Changes -:PROPERTIES: -:RSS_PERMALINK: 20200528.html -:PUBDATE: 2020-05-28 -:ID: 9b4e3b5d-7177-405b-9d1e-bc385a232097 -:END: -Carbs Linux kiss version 2.0.0 has been released which introduces rsync -repositories. - -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. - -Git is now on the =extra= repository and is still (optionally) used in the -package manager. - -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. - -This is a precaution with the added bonuses of speed and dropping a mandatory -dependency. - -You can see the rest of the changelog [[https://github.com/CarbsLinux/kiss/blob/master/CHANGELOG.md][here]]. - -** Binary Repositories - :PROPERTIES: - :ID: 04f63c53-9a98-4a50-ab6e-bc07f79f1cd7 - :END: - -A few days ago, I have also published [[https://github.com/CarbsLinux/kiss-bin][kiss-bin]], 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. -* The Relation of Carbs and KISS -:PROPERTIES: -:RSS_PERMALINK: 20200508.html -:PUBDATE: 2020-05-08 -:ID: 30deff4f-04e4-4065-874e-2425833eb92a -:END: -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. - -** History - :PROPERTIES: - :ID: 2381e690-6420-49b4-a594-8963f3f37d34 - :END: - -I had the idea of creating my own Linux distribution since the May of 2019. Back -then, I had my own [[https://linuxfromscratch.org][Linux from Scratch]] 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. - -I had written some incomplete package managers (all named =fat=) 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. - -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. - -One day on Reddit, I saw Dylan's post on [[https://reddit.com/r/unixporn][r/unixporn]] about KISS, and I really -thought that it was interesting. Here is my [[https://www.reddit.com/r/unixporn/comments/ducd34/sowm_kiss_d/f7lua7x][comment]] 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. - -** Differences between KISS and Carbs - :PROPERTIES: - :ID: f2663118-0d66-44de-8465-0b13188147fc - :END: - -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. - -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. - -** What I'm working on now - :PROPERTIES: - :ID: ae507544-f27e-423c-b760-4904e822bd7e - :END: - -Currently I have a few projects that I'm working on for Carbs. These are, - -A BSD port for Carbs. For a while, I have been working on BSD compatibility on -my fork of the [package manager]. 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. - -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. - -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. - -** What's up with all the init/service daemons? - :PROPERTIES: - :ID: f38b625b-abbb-4eaf-8a88-009e6dda9eb0 - :END: - -If you have ever checked the [[https://github.com/carbslinux/repository][repository]], 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 [[https://github.com/cemkeylan/shinit][init daemon]] and [[https://github.com/cemkeylan/sysmgr][service supervisor]]. I maintain all those packages on KISS -Community Repository as well with the exception of busybox. Those are, =busybox - init/runit=, =runit=, =sinit=, and =sysmgr=. I would definitely recommend -checking out =shinit= and =sysmgr=. - -** Why I don't publicize Carbs - :PROPERTIES: - :ID: 85011e8b-9810-482c-9d32-d34649cb0656 - :END: - -There are a couple of reasons I don't publicize Carbs a lot. - -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. - -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. - -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. - -I think that's about it, if you have questions you can send me a mail, ping me -on IRC (my handle is =merakor=), and I will be happy to answer. Maybe your -question fits this post, and I can update it to thoroughly give an explanation. -* Outsource Repository Concept -:PROPERTIES: -:RSS_PERMALINK: 20200410.html -:PUBDATE: 2020-04-10 -:ID: 3f31b269-5607-4cd9-8e52-df3f7bd83d50 -:END: -In April 3rd, I have added submodule support for Carbs Linux's fork of =kiss=. -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). - -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. - -This way, an end-user can also track from their preferred maintainers, and do -that with the tidyness of a single repository in their =KISS_PATH=. - -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. - -[[https://github.com/CarbsLinux/outsource]] -* Roadmap for Carbs -:PROPERTIES: -:RSS_PERMALINK: 20200406.html -:PUBDATE: 2020-04-06 -:ID: 9749c9ce-264b-47bf-a740-4e118eb30a4b -:END: -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. - -** Carbs Linux Server Going Down - :PROPERTIES: - :ID: 95817833-8d4f-4560-b04c-9261d7806841 - :END: - -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 [[https://github.com/CarbsLinux][Github]]. -The repository and the website is served on Github now. I have also moved the -[[https://github.com/CarbsLinux/wiki/wiki][Wiki]] to Github and anyone can edit it there. There are some outdated posts that -I will be fixing around this week. - -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 SourceHut?) - -I feel a little sad for switching, but serving on Github is faster, cheaper, and -hassle-free. - -** Forking KISS - :PROPERTIES: - :ID: 1a806630-59d8-467e-aa3a-93ff42e0e974 - :END: - -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 [[https://github.com/CarbsLinux/kiss][this repository]]. See it for the added -changes. - -This will be a change for the better, as I can develop the package manager as it -fits my views. - -** Small Changes on the Website - :PROPERTIES: - :ID: e836ba6a-b2eb-4ade-b4ad-3b6281797ea5 - :END: - -I have made some small changes on the website. The build is not dependent on -Plan9 utilities anymore. It was fun messing around with =rc= and =mk=, but they -are quite limited compared to POSIX shell. - -RSS feeds are finally working as intended, both for the [[https://carbslinux.org/news.xml][news]] section, and the -[[https://carbslinux.org/rss.xml][blog]] section. - -You can see every page's =.txt= 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'. - -** Outsources Repository - :PROPERTIES: - :ID: 1491c3a9-613a-4833-8812-d73017dfbc20 - :END: - -I have opened an =outsource= 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 [[https://github.com/CarbsLinux/outsource][here]]! - -** New Tarball - :PROPERTIES: - :ID: 4511ac0a-205c-4abd-b10d-08096be6eabe - :END: - -Finally, I have released a new tarball today, which can be obtained from the -[[https://dl.carbslinux.org/releases][downloads page]]. - -I am planning to add more of these update posts as I'm feeling better about the -website structure overall. -* Switching to New Website -:PROPERTIES: -:RSS_PERMALINK: 20200128.html -:PUBDATE: 2020-01-28 -:ID: 7062c433-adc4-44e9-b179-51e97941c09c -:END: -In case you haven't seen it before, this website was powered by [[http://werc.cat-v.org][werc]]. And even -though I liked it really much, it was too powerful for a small website like -this. - -So I have decided to reimplement this website with my own static generation -scripts. The source will probably be on [[https://git.carbslinux.org/website/log.html][its git repository]] when I decide to -publish the website. - -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. diff --git a/docs/blog/20200128.html b/docs/blog/20200128.html deleted file mode 100644 index 771ff8c..0000000 --- a/docs/blog/20200128.html +++ /dev/null @@ -1,60 +0,0 @@ - - - - - - -Switching to New Website - - - - - - -
- -
-
-
-

Switching to New Website

-

posted on 2020-01-28

-

-In case you haven't seen it before, this website was powered by werc. And even -though I liked it really much, it was too powerful for a small website like -this. -

- -

-So I have decided to reimplement this website with my own static generation -scripts. The source will probably be on its git repository when I decide to -publish the website. -

- -

-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. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200406.html b/docs/blog/20200406.html deleted file mode 100644 index 6bc6555..0000000 --- a/docs/blog/20200406.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - - -Roadmap for Carbs - - - - - - -
- -
-
-
-

Roadmap for Carbs

-

posted on 2020-04-06

-

-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. -

- -
-

Carbs Linux Server Going Down

-
-

-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 Github. -The repository and the website is served on Github now. I have also moved the -Wiki to Github and anyone can edit it there. There are some outdated posts that -I will be fixing around this week. -

- -

-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 SourceHut?) -

- -

-I feel a little sad for switching, but serving on Github is faster, cheaper, and -hassle-free. -

-
-
- -
-

Forking KISS

-
-

-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 this repository. See it for the added -changes. -

- -

-This will be a change for the better, as I can develop the package manager as it -fits my views. -

-
-
- -
-

Small Changes on the Website

-
-

-I have made some small changes on the website. The build is not dependent on -Plan9 utilities anymore. It was fun messing around with rc and mk, but they -are quite limited compared to POSIX shell. -

- -

-RSS feeds are finally working as intended, both for the news section, and the -blog section. -

- -

-You can see every page's .txt 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'. -

-
-
- -
-

Outsources Repository

-
-

-I have opened an outsource 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 here! -

-
-
- -
-

New Tarball

-
-

-Finally, I have released a new tarball today, which can be obtained from the -downloads page. -

- -

-I am planning to add more of these update posts as I'm feeling better about the -website structure overall. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200410.html b/docs/blog/20200410.html deleted file mode 100644 index 9779528..0000000 --- a/docs/blog/20200410.html +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - -Outsource Repository Concept - - - - - - -
- -
-
-
-

Outsource Repository Concept

-

posted on 2020-04-10

-

-In April 3rd, I have added submodule support for Carbs Linux's fork of kiss. -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). -

- -

-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. -

- -

-This way, an end-user can also track from their preferred maintainers, and do -that with the tidyness of a single repository in their KISS_PATH. -

- -

-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. -

- -

-https://github.com/CarbsLinux/outsource -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200508.html b/docs/blog/20200508.html deleted file mode 100644 index 4d55993..0000000 --- a/docs/blog/20200508.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - - -The Relation of Carbs and KISS - - - - - - -
- -
-
-
-

The Relation of Carbs and KISS

-

posted on 2020-05-08

-

-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. -

- -
-

History

-
-

-I had the idea of creating my own Linux distribution since the May of 2019. Back -then, I had my own Linux from Scratch 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. -

- -

-I had written some incomplete package managers (all named fat) 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. -

- -

-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. -

- -

-One day on Reddit, I saw Dylan's post on r/unixporn about KISS, and I really -thought that it was interesting. Here is my comment 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. -

-
-
- -
-

Differences between KISS and Carbs

-
-

-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. -

- -

-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. -

-
-
- -
-

What I'm working on now

-
-

-Currently I have a few projects that I'm working on for Carbs. These are, -

- -

-A BSD port for Carbs. For a while, I have been working on BSD compatibility on -my fork of the [package manager]. 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. -

- -

-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. -

- -

-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. -

-
-
- -
-

What's up with all the init/service daemons?

-
-

-If you have ever checked the repository, 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 init daemon and service supervisor. I maintain all those packages on KISS -Community Repository as well with the exception of busybox. Those are, busybox -init/runit, runit, sinit, and sysmgr. I would definitely recommend -checking out shinit and sysmgr. -

-
-
- -
-

Why I don't publicize Carbs

-
-

-There are a couple of reasons I don't publicize Carbs a lot. -

- -

-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. -

- -

-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. -

- -

-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. -

- -

-I think that's about it, if you have questions you can send me a mail, ping me -on IRC (my handle is merakor), and I will be happy to answer. Maybe your -question fits this post, and I can update it to thoroughly give an explanation. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200528.html b/docs/blog/20200528.html deleted file mode 100644 index 3707229..0000000 --- a/docs/blog/20200528.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - -kiss 2.0.0 and Overall Changes - - - - - - -
- -
-
-
-

kiss 2.0.0 and Overall Changes

-

posted on 2020-05-28

-

-Carbs Linux kiss version 2.0.0 has been released which introduces rsync -repositories. -

- -

-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. -

- -

-Git is now on the extra repository and is still (optionally) used in the -package manager. -

- -

-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. -

- -

-This is a precaution with the added bonuses of speed and dropping a mandatory -dependency. -

- -

-You can see the rest of the changelog here. -

- -
-

Binary Repositories

-
-

-A few days ago, I have also published kiss-bin, 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. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200617.html b/docs/blog/20200617.html deleted file mode 100644 index 9576db4..0000000 --- a/docs/blog/20200617.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - - -June Newspost - - - - - - -
- -
-
-
-

June Newspost

-

posted on 2020-06-17

-

-This will be an active month for Carbs as major changes to the base and the -package manager will be coming up. -

- -
-

Statically linking the base

-
-

-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. -

- -

-I believe that binaries on the core should always be linked statically. This -ensures that an SONAME bump to libObscure.so 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. -

- -

-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. -

-
-
- -
-

Major changes on the core repository

-
-

-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. -

-
- -
-

Removed from Core

-
-
    -
  • git
    • -
  • libressl
    • -
  • grub
    • -
  • bison
    • -
  • dhcpcd
    • -
  • ubase
    • -
-
-
- -
-

Added to Core

-
-
    -
  • bearssl, as a libressl replacement
    • -
  • byacc, as a bison replacement
    • -
-
-
- -
-

Statically linked

-
-
    -
  • kiss
    • -
  • neatvi
    • -
  • mandoc
    • -
  • byacc
    • -
  • m4
    • -
  • e2fsprogs
    • -
  • make
    • -
  • pkgconf
    • -
  • sbase
    • -
  • libnl
    • -
  • wpa_supplicant
    • -
  • bearssl
    • -
-
-
-
- -
-

Making the wiki available offline

-
-

-Soon, all documentation regarding Carbs Linux will be avaialable to be installed -from the core repository in a carbs-docs 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. -

-
-
- -
-

ISO image for Carbs

-
-

-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 arch-install-scripts. Let's see how that's going to play out. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20200803.html b/docs/blog/20200803.html deleted file mode 100644 index 67424b2..0000000 --- a/docs/blog/20200803.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - - -August 2020 News Post - - - - - - -
- -
-
-
-

August 2020 News Post

-

posted on 2020-08-03

-

-We are having some stalls during this summer, as I am currently working on -university-related stuff. Nonetheless, there are some important changes that I -want to share in this month's post. -

- -
- -
- -
-

Carbs Packaging Tools

-
-

-This month I have reworked kiss into a new package manager, now renamed as -cpt. Updating kiss will now bootstrap the new package manager, so you don't -have to manually edit your system. If you don't like the idea of this, you can -look up the post-install script on core/kiss and apply the changes manually. -

- -

-You will also need to rename your KISS_* variables to CPT_*. So, KISS_PATH -becomes CPT_PATH. -

- -

-The rework changes the previous commands on the package manager into standalone -tools, and move the package manager functions to a library. This makes it easier -for a user to import functions and variables from the package manager, and -extend the package manager with their own intended way. Previously this required -ugly hacks and workarounds to use the package manager functions. I will be -making use of these changes to re-implement binary package management functions -as well. -

- -

-If you want to use the library on your script you can simply do this: -

- -
-
#!/bin/sh
-. cpt-lib
-(...)
-
-
- -

-There are obviously some clean-up and simplifications needed in this new -tool-based package management method. -

-
-
- -
-

Docs

-
-

-I have added documentation for the distribution, and finally updated the guide -for installation. It is now almost complete. These docs can be installed to -your system for online viewing. I will also add a documentation crawler similar -to how werc works (but as an offline viewer). You can find carbs-docs from -the repository. Currently, the documentation lacks but I will be adding new -stuff. These will solely be distribution specific documentation and will not be -a wiki-like source. If anyone would like to contribute to a wiki-like -documentation source, I would happily re-open the distribution wiki. You can -find the source on https://github.com/CarbsLinux/docs. -

-
-
- -
-

Re-opening the Carbs Linux server

-
-

-Back in May, I had shutdown the Carbs Linux server due to financial issues, but -I am slowly reverting to the self-hosted model. Back then, the git repositories -were mirrored to GitHub, and the management was overall much more flexible. The -server used to run Carbs Linux as well (that was fun and horrifying at the same -time). Now, I will be relaunching the git server which will be the upstream -source before August 5. You can switch your remote, but GitHub will stay as a -remote nonetheless. -

- -

-EDIT: The git-server is up! -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/20201210.html b/docs/blog/20201210.html deleted file mode 100644 index c4b74d1..0000000 --- a/docs/blog/20201210.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - -First Year of Carbs Linux - - - - - - -
- -
-
-
-

First Year of Carbs Linux

-

posted on 2020-12-10

-

-December 10, 2020 marks the first year after the initial release of Carbs Linux. -When I forked the KISS Linux repository on the 9th of December, I was fairly new -to package management. Carbs Linux used to be almost identical to KISS Linux. A -lot has changed since then: -

- - - -

-I have really enjoyed maintaining and developing this distribution, and I want -to thank everyone who was involved in some way or another. While I have slowed -down in development due to college workload, I am still actively maintaining all -the packages on the repository. I do have some ideas that I am thinking of -implementing during the semester break. Hope to see you all in January. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/blog/index.html b/docs/blog/index.html deleted file mode 100644 index 7b6991e..0000000 --- a/docs/blog/index.html +++ /dev/null @@ -1,54 +0,0 @@ - - - - - - -Blog Index - - - - - - -
- -
-
-
-

Blog Index

-

-This is the Carbs Linux blog index. You can find every post here. RSS Feed -

- -
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/docs.html b/docs/docs.html deleted file mode 100644 index 8a71e6c..0000000 --- a/docs/docs.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - - -Documentation - - - - - - -
- -
-
-
-

Documentation

-

-Below are sources of documentation regarding Carbs Linux and tools surrounding -it. -

- -
-

User Manual

-
-

-Carbs Linux User Manual aims to be a general-purpose explanation of the -distribution, from the installation steps to the style guide of the project. It -can be accessed or otherwise obtained with various methods: -

-
- -
-

HTML

-
-

-You can view the Manual from your browser. The Manual can be viewed as -

- - -
-
- -
-

Plain text

-
-

-You can download carbslinux.txt in order to view the Manual from your preferred -pager. -

- -
-
curl -LO https://carbslinux.org/docs/carbslinux.txt
-less carbslinux.txt
-
-
-
-
- -
-

Info

-
-

-You can install the carbs-docs package and either texinfo or info packages -to view the Manual offline. -

- -
-
cpt bi info carbs-docs
-info carbslinux
-
-
-
-
- -
-

Source

-
-

-You can also acquire the source for generating the Manual, which requires -emacs for exporting the Org-mode documentation and texinfo for generating -html/info pages. -

- -
-
git clone git://git.carbslinux.org/docs
-
-
-
-
-
- -
-

Installation Instructions

-
-

-Installation Manual is part of the User Manual, but it can also be obtained -separately: -

- - -
-
- -
-

Carbs Packaging Tools

-
-

-The user manual for CPT is not complete yet, but will be released with the 6.0.0 -release. You can see the repository in order to check its status. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/docs.txt b/docs/docs.txt deleted file mode 100644 index 385ad92..0000000 --- a/docs/docs.txt +++ /dev/null @@ -1,98 +0,0 @@ - _______________ - - DOCUMENTATION - _______________ - - -Below are sources of documentation regarding Carbs Linux and tools -surrounding it. - - -User Manual -=========== - - Carbs Linux User Manual aims to be a general-purpose explanation of - the distribution, from the installation steps to the style guide of - the project. It can be accessed or otherwise obtained with various - methods: - - -HTML -~~~~ - - You can view the Manual from your browser. The Manual can be viewed as - - - [One HTML page per node] - - [Single HTML page] - - -[One HTML page per node] - -[Single HTML page] - - -Plain text -~~~~~~~~~~ - - You can download [carbslinux.txt] in order to view the Manual from - your preferred pager. - - ,---- - | curl -LO https://carbslinux.org/docs/carbslinux.txt - | less carbslinux.txt - `---- - - -[carbslinux.txt] - - -Info -~~~~ - - You can install the `carbs-docs' package and either `texinfo' or - `info' packages to view the Manual offline. - - ,---- - | cpt bi info carbs-docs - | info carbslinux - `---- - - -Source -~~~~~~ - - You can also acquire the source for generating the Manual, which - requires `emacs' for exporting the Org-mode documentation and - `texinfo' for generating html/info pages. - - ,---- - | git clone git://git.carbslinux.org/docs - `---- - - -Installation Instructions -========================= - - Installation Manual is part of the [User Manual], but it can also be - obtained separately: - - - [HTML] - - [Plaintext] - - -[User Manual] See section User Manual - -[HTML] - -[Plaintext] - - -Carbs Packaging Tools -===================== - - The user manual for CPT is not complete yet, but will be released with - the 6.0.0 release. You can see the [repository] in order to check its - status. - - -[repository] diff --git a/docs/docs/carbslinux.html b/docs/docs/carbslinux.html deleted file mode 100644 index e50d6f4..0000000 --- a/docs/docs/carbslinux.html +++ /dev/null @@ -1,1786 +0,0 @@ - - - - - - -Carbs Linux User Manual - - - - - - - - - - - - - - - -

Carbs Linux User Manual

- - - - - -

Table of Contents

- -
- - -
- - -
-

-Next:   [Contents]

-
-

Carbs Linux User Manual

- -

This is the full documentation of Carbs Linux, from the details of the -distribution, installation, to the package manager. It is not yet complete. -

- -

This documentation is also available in the distribution by the -carbs-docs package, which can be read by either running -info carbslinux or reading /usr/share/doc/carbslinux.txt with your -favorite pager. You can install either the info or texinfo -for doing the first. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
• Installation  Installing Carbs Linux -
• Init System  Configure the init system -
• Contribution Guidelines  Contribute to Carbs Linux -
• GNU Free Documentation License  Your rights -
-
-
— The Detailed Node Listing —
-
-Installation
-
-
• Preparing Environment  Getting ready to chroot -
• Chroot  Going inside your new system -
• System Configuration  Customizing your system for personal use -
• Kernel  Compiling your own kernel -
• Making your system bootable  Installing bootloader and boot scripts -
• Post-installation  Post-installation tasks -
-
-Preparing Environment
-
-
• Download  Download the root filesystem tarball -
• Signature verification  Verify the signature of the rootfs tarball -
• Extracting the tarball  Extracting the root filesystem to the desired location -
• Obtain the chroot helper  Download the script to easily chroot into the new filesystem -
-
-Chroot
-
-
• Setting up repositories  Basic setup for obtaining repositories -
• Updating packages  Update your system -
• Installing packages  Install new software on your system -
• Essential Software  Software you might want to include on your system -
• Obtaining the documentation  Install documentation for offline use (optional) -
-
-System Configuration
-
-
• Configuring hostname  Setting up system hostname (recommended) -
• Hosts file  Setting up hosts file for networking (optional) -
-
-Kernel
-
-
• Obtaining the kernel sources  Downloading the Linux source code -
• Kernel dependencies  Requirements for building the kernel -
• Building the kernel  Configure and compile the kernel -
-
-Making your system bootable
-
-
• Bootloader  Install a bootloader for your system -
• Init scripts  Install init scripts for your system -
• Fstab  Generating fstab -
-
-Post-installation
-
-
• KISS repositories  Acquire kiss repositories -
-
-Init System
-
-
• Configuring Init  Ways to configure the init system -
• Changing Init Program  Replace the default busybox init with something new -
-
-Configuring Init
-
-
• Kernel Command Line  Configure init through the boot parameters -
• ‘/etc/init/rc.conf’ file  Configure init through the configuration file -
• Init Hooks  Configure init through hooks -
-
-Changing Init Program
-
-
• Rebooting after changing init  Ways to reboot after replacing the init system -
-
-Contribution Guidelines
-
-
• Conventions  Conventions of the distribution -
-
-Conventions
-
-
• Shell Conventions  Conventions for shell scripts -
• Repository Conventions  Conventions for repository build scripts -
-
-
- -
-
-

-Next: , Previous: , Up: Top   [Contents]

-
-

1 Installation

- -

These are the step-by-step instructions for installing Carbs Linux. It can be -acquired as plain-text to be viewed offline with a pager from -https://carbslinux.org/install.txt. -

-
-
curl -sL https://carbslinux.org/install.txt | less
-
- - - - - - - - -
• Preparing Environment  Getting ready to chroot -
• Chroot  Going inside your new system -
• System Configuration  Customizing your system for personal use -
• Kernel  Compiling your own kernel -
• Making your system bootable  Installing bootloader and boot scripts -
• Post-installation  Post-installation tasks -
- -
-
-

-Next: , Up: Installation   [Contents]

-
-

1.1 Preparing Environment

- -

To install Carbs Linux, you will need a Live Linux ISO. For that purpose, you -can obtain a Gentoo or Void Linux live image. You can follow their instructions -to boot and setup your network. -

-

You will need the following programs in order to install Carbs Linux: -

-
    -
  • tar -
  • wget -
  • xz -
  • some form of base utilities (coreutils, sbase, busybox, etc.) -
- -

Rest of these instructions will assume that you have set all of these up, and -will continue on that point. -

- - - - - -
• Download  Download the root filesystem tarball -
• Signature verification  Verify the signature of the rootfs tarball -
• Extracting the tarball  Extracting the root filesystem to the desired location -
• Obtain the chroot helper  Download the script to easily chroot into the new filesystem -
- -
-
-

-Next: , Up: Preparing Environment   [Contents]

-
-

1.1.1 Download

- -

First, we need to download the rootfs tarball. You can do the following in order -to obtain the rootfs. If you are using an i686 machine, replace the ‘x86_64’ -with ‘i686’. We are setting this in a URL variable so that we don’t have to -write it every time. -

-
-
wget $URL/carbs-rootfs.tar.xz.sha256
-sha256sum -c carbs-rootfs.tar.xz.sha256
-
- -
-
-

-Next: , Previous: , Up: Preparing Environment   [Contents]

-
-

1.1.2 Signature verification

- -

It is highly recommended to verify the signature of the tarball. You will need -GPG for this. -

-
-
wget $URL/carbs-rootfs.tar.xz.sig
-gpg --recv-keys FF484BDFEFCEF8FF
-gpg --verify carbs-rootfs.tar.xz.sig
-
- -
-
-

-Next: , Previous: , Up: Preparing Environment   [Contents]

-
-

1.1.3 Extracting the tarball

- -

You will need to extract the tarball to your desired location. For partitioning, -you can follow this guide. This will assume that you will be mounting your root -partition to ‘/mnt’. -

-
-
mount /dev/sdx1 /mnt
-tar xf carbs-rootfs.tar.xz -C /mnt
-
- -
-
-

-Previous: , Up: Preparing Environment   [Contents]

-
-

1.1.4 Obtain the chroot helper

- -

You can obtain the ‘cpt-chroot’ script in order to do a simple chroot into your -new root filesystem. -

-
-
wget https://dl.carbslinux.org/distfiles/cpt-chroot
-chmod a+x cpt-chroot
-
- -
-
-

-Next: , Previous: , Up: Installation   [Contents]

-
-

1.2 Chroot

- -

Chroot into Carbs Linux! -

-
-
./cpt-chroot /mnt
-
- - - - - - - -
• Setting up repositories  Basic setup for obtaining repositories -
• Updating packages  Update your system -
• Installing packages  Install new software on your system -
• Essential Software  Software you might want to include on your system -
• Obtaining the documentation  Install documentation for offline use (optional) -
- -
-
-

-Next: , Up: Chroot   [Contents]

-
-

1.2.1 Setting up repositories

- -

Newest tarballs do not come with repositories, so you will need to manually -obtain them, and set your ‘CPT_PATH’ environment variable. Carbs Linux -repositories can either be obtained by ‘git’ or ‘rsync’. While rsync -repositories are overall faster and smaller, git offers the whole history of the -repository and a means to manipulate your repository as you like it. If you want -to obtain the git repository, you will need to install ‘git’ itself. -

-

The following guide will assume that you put the repositories into ‘~/repos/’ -directory, but you can put the repositories into any directory you want. So go -ahead and create that directory: -

-
-
mkdir -p $HOME/repos
-
- -
    -
  1. Obtaining from git - - -

    Carbs Linux git repositories can be found both from the main server and GitHub -(mirror). Here are both their repository links. You can clone any of them. -

    - - -
    -
    git clone git://git.carbslinux.org/repository $HOME/repos/carbs
-
    - -
  2. Obtaining from rsync - - -

    Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In -order to obtain it, run the following: -

    -
    -
    rsync -avc rsync://carbslinux.org/repo $HOME/repos/carbs
-
    - -
  3. Making the package manager use the repositories - - -

    In your shell’s configuration file, or in your ‘~/.profile’ file, add the -following lines: -

    -
    -
    CPT_PATH=$HOME/repos/carbs/core
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/extra
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/xorg
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/community
-export CPT_PATH
-
    -
- -
-
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-

1.2.2 Updating packages

- -

It is good practice to make sure your system is up to date, especially before -building new packages. If there is an update for the package manager you will -need to update twice. -

-
-
cpt-update && cpt-update
-
- -
-
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-

1.2.3 Installing packages

- -

Since you are operating on a really small base, you might need to build and -install new programs to extend the functionality of your system. In order to -build and install packages new packages in Carbs, you need to execute the -following. "Package" is not actually a package and is given as an example. -

-
-
cpt-build   package
-cpt-install package
-
- -
-
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-

1.2.4 Essential Software

- -

Here is a list of software that you might want to have on your system. -

-

BOOTLOADERS -

-
    -
  • efibootmgr -
  • grub -
- -

FILESYSTEMS -

-
    -
  • e2fsprogs -
  • dosfstools -
  • ntfs-3g -
- -

NETWORKING -

-
    -
  • dhcpcd -
  • wpa_supplicant -
- -

TEXT EDITORS -

-
    -
  • nano -
  • vim -
  • neatvi -
  • emacs -
  • emacs-nox (terminal-only version of emacs) -
- -

USER SHELLS -

-
    -
  • bash -
  • zsh -
  • oksh -
  • rc -
- -

POSIX BASE UTILITIES -

-
    -
  • busybox -
  • sbase -
  • coreutils -
- -

DOCUMENTATION -

-
    -
  • carbs-docs -
  • man-pages -
  • man-pages-posix -
- -
-
-

-Previous: , Up: Chroot   [Contents]

-
-

1.2.5 Obtaining the documentation

- -

All the documentation for Carbs Linux can be found on a single info manual to be -viewed offline. You can obtain texinfo or the info (standalone) package in order -to view the documentation. -

-
-
# Install the documentation.
-cpt b carbs-docs && cpt i carbs-docs
-
-# Install either texinfo or the info package. We will be installing standalone info
-# as it doesn't need perl.
-cpt b info && cpt i info
-
-# You can then run info and navigate through the documentation.
-info carbslinux
-
- -
-
-

-Next: , Previous: , Up: Installation   [Contents]

-
-

1.3 System Configuration

- -

After you have finished installing some extra packages, you can configure your -system to your liking. -

- - - -
• Configuring hostname  Setting up system hostname (recommended) -
• Hosts file  Setting up hosts file for networking (optional) -
- -
-
-

-Next: , Up: System Configuration   [Contents]

-
-

1.3.1 Configuring hostname

- -

You might want to add a hostname, especially in a networked environment. Your -hostname will default to ’carbslinux’ unless you set this. -

-
-
echo your-hostname > /etc/hostname
-
- -
-
-

-Previous: , Up: System Configuration   [Contents]

-
-

1.3.2 Hosts file

- -

You can edit your /etc/hosts file, which is the static lookup table for host -names. By default, there are two entries for localhost which are OKAY. You can -replace the ’localhost’ part of these entries to your hostname. -

-
-
127.0.0.1  localhost.localdomain localhost
-::1        localhost.localdomain localhost ip6-localhost
-
- -
-
-

-Next: , Previous: , Up: Installation   [Contents]

-
-

1.4 Kernel

- -

Kernel isn’t managed under the main repositories, even though you could package -one for your personal use. Here is an example kernel package, which you will -need to reconfigure for your specific setup if you want to make use of it. -

- - - - -
• Obtaining the kernel sources  Downloading the Linux source code -
• Kernel dependencies  Requirements for building the kernel -
• Building the kernel  Configure and compile the kernel -
- -
-
-

-Next: , Up: Kernel   [Contents]

-
-

1.4.1 Obtaining the kernel sources

- -

You can visit the https://kernel.org website to choose a kernel that you want -to install. Though only the latest stable and longterm (LTS) versions are -supported. -

-
-
# Download the kernel and extract it
-wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz
-tar xf linux-5.9.1.tar.xz
-
-# Change directory into the kernel sources
-cd linux-5.9.1
-
- -
-
-

-Next: , Previous: , Up: Kernel   [Contents]

-
-

1.4.2 Kernel dependencies

- -

In order to compile the kernel you will need to install some dependencies. You -will need ‘libelf’, and ‘bison’ to compile the kernel. If you want to configure -using the menu interface you will also need ‘ncurses’. -

-
-
# The package manager asks to install if you are building more than one package,
-# so no need to run 'cpt i ...'
-cpt b libelf ncurses
-
- -

In the vanilla kernel sources, you need perl to compile the kernel, but it can -be easily patched out. You will need to apply the following patch. Patch was -written by E5ten. You will need to obtain and apply the patch in the kernel -source directory. -

-
-
wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch
-patch -p1 < kernel-no-perl.patch
-
- -
-
-

-Previous: , Up: Kernel   [Contents]

-
-

1.4.3 Building the kernel

- -

Next step is configuring and building the kernel. You can check Gentoo’s -kernel configuration guide to learn more about the matter. Overall, Gentoo Wiki -is a good place to learn about configuration according to your hardware. The -following will assume a monolithic kernel. -

-
-
make menuconfig
-make
-install -Dm755 $(make -s image_name) /boot/vmlinuz-linux
-
- -
-
-

-Next: , Previous: , Up: Installation   [Contents]

-
-

1.5 Making your system bootable

- -

In order to be able to boot your fresh system, wou will need an init-daemon, -init-scripts and a bootloader. The init daemon is already provided by busybox, -but you can optionally change it. -

- - - - -
• Bootloader  Install a bootloader for your system -
• Init scripts  Install init scripts for your system -
• Fstab  Generating fstab -
- -
-
-

-Next: , Up: Making your system bootable   [Contents]

-
-

1.5.1 Bootloader

- -

In the main repository, there is efibootmgr and grub to serve as bootloaders. -efibootmgr can be used as a standalone bootloader, or can be used to install -grub in a UEFI environment. efibootmgr is needed unless you are using a device -without UEFI support (or you really want to use BIOS for a reason). -

-
    -
  1. GRUB BIOS installation - - -
    -
    cpt b grub && cpt i grub
-grub-install --target=i386-pc /dev/sdX
-grub-mkconfig -o /boot/grub/grub.cfg
-
    - -
  2. GRUB UEFI installation - - -
    -
    cpt b efibootmgr && cpt i efibootmgr
-cpt b grub && cpt i grub
-
-grub-install --target=x86_64-efi \
-             --efi-directory=esp \
-             --bootloader-id=CarbsLinux
-
-grub-mkconfig -o /boot/grub/grub.cfg
-
    -
- -
-
-

-Next: , Previous: , Up: Making your system bootable   [Contents]

-
-

1.5.2 Init scripts

- -

Only thing left to do is installing the init-scripts, and now you are almost -ready to boot your system! -

-
-
cpt b carbs-init && cpt i carbs-init
-
- -
-
-

-Previous: , Up: Making your system bootable   [Contents]

-
-

1.5.3 Fstab

- -

You can now manually edit your fstab entry, or you can use the genfstab tool. -If you want to use the tool, exit the chroot and run the following: -

-
-
wget https://github.com/cemkeylan/genfstab/raw/master/genfstab
-chmod +x genfstab
-./genfstab -U /mnt >> /mnt/etc/fstab
-
- -
-
-

-Previous: , Up: Installation   [Contents]

-
-

1.6 Post-installation

- -

The base installation is now complete, you can now fine tune your system -according to your needs. Rest of these instructions are completely optional. -You can check the rest of the documentation to learn more about the system. -

- - -
• KISS repositories  Acquire kiss repositories -
- -
-
-

-Up: Post-installation   [Contents]

-
-

1.6.1 KISS repositories

- -

While not 100% compatible with cpt, you can use kiss repositories in your -system the same way you are using the distribution repositories. Here is an -example for the KISS Linux Community repository. -

-
-
-

-Next: , Previous: , Up: Top   [Contents]

-
-

2 Init System

- -

Carbs Linux init scripts are run by the init daemon (‘busybox’ by default) on -boot and shutdown processes. It also provides its own halting program named -shalt. This provides a portable method that doesn’t rely on non-POSIX external -programs. -

- - - -
• Configuring Init  Ways to configure the init system -
• Changing Init Program  Replace the default busybox init with something new -
- -
-
-

-Next: , Up: Init System   [Contents]

-
-

2.1 Configuring Init

- -

There are three ways you can change the behaviour of the init system. Those are: -

-
    -
  • Kernel Command Line -
  • ‘/etc/init/rc.conf’ file -
  • Init Hooks -
- - - - - -
• Kernel Command Line  Configure init through the boot parameters -
• ‘/etc/init/rc.conf’ file  Configure init through the configuration file -
• Init Hooks  Configure init through hooks -
- -
-
-

-Next: , Up: Configuring Init   [Contents]

-
-

2.1.1 Kernel Command Line

- -

On GRUB, you can edit the kernel command line parameters, which will be parsed -as variables on the init system. Not all of the parameters will be acted upon, -but all of them will be set as variables on the init script. For example an -example command line, and how it is interpreted. -

-
-
BOOT_IMAGE=/boot/vmlinuz root=/dev/sda2 rw loglevel=3 quiet
-
- -

This command line will be parsed to set the following variables: -

-
-
BOOT_IMAGE=/boot/vmlinuz
-root=/dev/sda2
-rw=1
-loglevel=3
-quiet=1
-
- -

Some of these variables, such as ‘rw=/=ro’, ‘loglevel’, and ‘quiet’, will be -used by the init system to change the behaviour of the startup. -

-
-
-

-Next: , Previous: , Up: Configuring Init   [Contents]

-
-

2.1.2 ‘/etc/init/rc.conf’ file

- -

However, the kernel command line isn’t the only place to set your boot -parameters. You can specify variables here as well, although note that the -kernel command line always gets the priority for these variables since they can -be set just before boot. -

-
-
-

-Previous: , Up: Configuring Init   [Contents]

-
-

2.1.3 Init Hooks

- -

Init hooks are for custom personal commands that the user may want to add to -alter their boot. These can be used to load kernel modules, modify interfaces, -and lot more. Those hooks are added to the ‘/etc/init’ directory with the -hook name as the suffix. For example, a boot script will be placed as -‘/etc/init/my-hook.boot’. Currently, there are 4 hooks that the user can use. -

-
-
early-boot
-

Run after pseudo-filesystems are mounted. -

-
boot
-

Run before the boot stage is completed. -

-
pre.shutdown
-

Run first when shutting down. -

-
umount
-

Run just before filesystems are unmounted. -

-
post.shutdown
-

Run just before the system is halted. -

-
- -
-
-

-Previous: , Up: Init System   [Contents]

-
-

2.2 Changing Init Program

- -

By default, Carbs Linux comes preinstalled with ‘busybox-init’, but this can -easily be replaced without any issues. Currently, available init systems are: -

-
    -
  • ‘sinit’ -
  • ‘busybox’ -
  • ‘runit’ -
  • ‘shinit’ -
- -

This example is for runit, but it will work with all init systems packaged in the -distribution repositories. See the ‘cpt-alternatives(1)’ manual page for more -details. -

-
-
cpt a runit /usr/bin/init
-cpt a runit /usr/bin/poweroff
-cpt a runit /usr/bin/reboot
-
- - - -
• Rebooting after changing init  Ways to reboot after replacing the init system -
- -
-
-

-Up: Changing Init Program   [Contents]

-
-

2.2.1 Rebooting after changing init

- -

After switching init systems, your running init system may not accept the -new poweroff commands. You will need to reboot/poweroff using the running init’s -utilities for the new utilities to work. These commands are for the init system -currently running on your system and not the one you are switching to. -

- - - - - -
ProgramCommand
busybox‘busybox reboot’
runit‘runit-init 6’
shinit/sinit‘kill -s INT 1’
- -
-
-

-Next: , Previous: , Up: Top   [Contents]

-
-

3 Contribution Guidelines

- -

Thanks for taking your time to contribute! To maintain stylistic behaviour -throughout the repositories, one must adhere to these conventions. Exceptions -and changes may occur with good reasoning. -

- - -
• Conventions  Conventions of the distribution -
- -
-
-

-Up: Contribution Guidelines   [Contents]

-
-

3.1 Conventions

- - - -
-
[0010]
-

Try to keep the file readable. -

-
[0011]
-

Characters on a line shouldn’t exceed 100 characters. -

-
[0012]
-

Make sure you don’t have code commented out during -commit. Uncomment them or remove them completely. -

-
[0013]
-

Do not add comments following the code, add them to the -top of the code. It makes it harder to read, and lines longer. Here is an example: -

-
- -
-
# Good way of commenting.
-your code goes here
-
-your code goes here  # Avoid this way of commenting.
-
-
-
- - - - -
• Shell Conventions  Conventions for shell scripts -
• Repository Conventions  Conventions for repository build scripts -
- -
-
-

-Next: , Up: Conventions   [Contents]

-
-

3.1.1 Shell Conventions

- -

Shell is central to Carbs Linux projects. Most of the tools and packages are -written in POSIX sh. -

-
-
[1010]
-

Use 4 spaces for indentation, don’t use tabs. -

-
[1020]
-

Make sure you don’t use bash-specific code. -

-
[1030]
-

Make sure you lint your code with ‘shellcheck’ and if -you are new to POSIX sh, use ‘checkbashisms’. -

-
[1040]
-

Don’t spawn new processes if you don’t absolutely need -to, especially during string manipulation. -

-
[1041]
-

Never use a program for text manupilation that isn’t -defined in the POSIX standard. This includes ‘gawk’ and ‘perl’. -

-
[1042]
-

Instead of $(basename $file), use ${file##*}. -

-
[1043]
-

Instead of $(dirname $file), use ${file%/*}. -

-
- -
-
# This is the same thing as basename /path/to/test.asc .asc
-
-$ file=/path/to/test.asc file=${file##*/} file=${file%.asc}
-$ echo $file
-test
-
-
-
[1050]
-

Instead of backticks, use $(..). -

-
- -
-
-

-Previous: , Up: Conventions   [Contents]

-
-

3.1.2 Repository Conventions

- -

Repository conventions are important in order to ensure every package resemble -themselves. Here are the things to keep in mind: -

-
-
[2010]
-

Prefer tarballs over git packages unless there is a -sensible reason. Here are some: -

    -
  • Every patch is a new release. (See vim) -
  • There are no releases. (See sbase) -
  • Following a development branch. -
  • There has been a long time since the latest release, but upstream is far -ahead. -
-
-
[2020]
-

Prefer sources without a dependency to ‘automake’. There -are usually distribution tarballs that are ‘autoconf’’ed. Don’t submit tarballs -with an automake dependency unless you are ‘sure’ there is no alternative. -

-
[2030]
-

Avoid these packages: -

-
dbus
-

Usually can be disabled by --disable-dbus. -

-
gettext
-

Usually can be disabled by --disable-nls. -

-
-
-
[2040]
-
    -
  • Always install a package to the ‘/usr’ prefix. -
  • All binaries should go to ‘/usr/bin’, not ‘/usr/sbin’ or any other directory. -
  • All libraries should go to ‘/usr/lib’. -
-
-
[2050]
-

All build files on the repository should be a POSIX -shell script, and must start with #!/bin/sh -e. -

-
- -

The next section is about package templates that should be used in order to -ensure stylistic consistency. Note that the option configurations shouldn’t be -taken literally, they are meant as examples. -

-
    -
  1. Make [2210] - - -
    -
    #!/bin/sh -e
-
-make
-make DESTDIR="$1" PREFIX=/usr install
-
    - -
  2. Configure/Make [2211] - - -
    -
    #!/bin/sh -e
-
-./configure \
-    --prefix=/usr \
-    --disable-option \
-    --enable-option
-
-make
-make DESTDIR="$1" install
-
    - -
  3. Autoconf/Automake [2212] - - -

    See 2020 -

    -
    -
    #!/bin/sh -e
-
-autoreconf -fi
-
-./configure \
-    --prefix=/usr \
-    --disable-option \
-    --enable-option
-
-make
-make DESTDIR="$1" install
-
    - -
  4. Meson [2220] - - -
    -
    #!/bin/sh -e
-
-export DESTDIR=$1
-
-meson \
-    --prefix=/usr \
-    -Doption=false \
-    -Doption2=true \
-    . output
-
-ninja -C output
-ninja -C output install
-
    - -
  5. Cmake [2230] - - -
    -
    #!/bin/sh -e
-
-export DESTDIR=$1
-
-cmake -B build \
-    -DCMAKE_INSTALL_PREFIX=/usr \
-    -DCMAKE_BUILD_TYPE=Release \
-    -DOPTION=ON
-
-cmake --build   build
-cmake --install build
-
    - -
  6. Go [2240] - - -
    -
    #!/bin/sh -e
-
-export GOPATH=$PWD/gopath
-trap "go clean -modcache" EXIT INT
-go mod vendor
-
-go build
-install -Dm755 program "$1/usr/bin/program"
-
    - -
  7. Python [2241] - - -
    -
    #!/bin/sh -e
-
-python setup.py build
-python setup.py install --prefix=/usr --root="$1"
-
    -
- -
-
-

-Previous: , Up: Top   [Contents]

-
-

Appendix A GNU Free Documentation License

- -
Version 1.3, 3 November 2008 -
-
-
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-http://fsf.org/
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
- -
    -
  1. PREAMBLE - -

    The purpose of this License is to make a manual, textbook, or other -functional and useful document free -in the sense of freedom: to assure everyone the effective freedom -to copy and redistribute it, with or without modifying it, either -commercially or noncommercially. Secondarily, this License -preserves for the author and publisher a way to get credit for -their work, while not being considered responsible for -modifications made by others. -

    -

    This License is a kind of "copyleft", which means that derivative -works of the document must themselves be free in the same sense. -It complements the GNU General Public License, which is a copyleft -license designed for free software. -

    -

    We have designed this License in order to use it for manuals for -free software, because free software needs free documentation: -a free program should come with manuals providing the same freedoms -that the software does. But this License is not limited to -software manuals; it can be used for any textual work, regardless -of subject matter or whether it is published as a printed book. We -recommend this License principally for works whose purpose is -instruction or reference. -

    -
  2. APPLICABILITY AND DEFINITIONS - -

    This License applies to any manual or other work, in any medium, -that contains a notice placed by the copyright holder saying it can -be distributed under the terms of this License. Such a notice -grants a world-wide, royalty-free license, unlimited in duration, -to use that work under the conditions stated herein. The -"Document", below, refers to any such manual or work. Any member -of the public is a licensee, and is addressed as "you". You accept -the license if you copy, modify or distribute the work in a way -requiring permission under copyright law. -

    -

    A "Modified Version" of the Document means any work containing the -Document or a portion of it, either copied verbatim, or with -modifications and/or translated into another language. -

    -

    A "Secondary Section" is a named appendix or a front-matter section -of the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document’s overall -subject (or to related matters) and contains nothing that could -fall directly within that overall subject. (Thus, if the Document -is in part a textbook of mathematics, a Secondary Section may not -explain any mathematics.) The relationship could be a matter of -historical connection with the subject or with related matters, or -of legal, commercial, philosophical, ethical or political position -regarding them. -

    -

    The "Invariant Sections" are certain Secondary Sections whose -titles are designated, as being those of Invariant Sections, in the -notice that says that the Document is released under this License. -If a section does not fit the above definition of Secondary then it -is not allowed to be designated as Invariant. The Document may -contain zero Invariant Sections. If the Document does not identify -any Invariant Sections then there are none. -

    -

    The "Cover Texts" are certain short passages of text that are -listed, as Front-Cover Texts or Back-Cover Texts, in the notice -that says that the Document is released under this License. -A Front-Cover Text may be at most 5 words, and a Back-Cover Text -may be at most 25 words. -

    -

    A "Transparent" copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, that is suitable for revising the document -straightforwardly with generic text editors or (for images composed -of pixels) generic paint programs or (for drawings) some widely -available drawing editor, and that is suitable for input to text -formatters or for automatic translation to a variety of formats -suitable for input to text formatters. A copy made in an otherwise -Transparent file format whose markup, or absence of markup, has -been arranged to thwart or discourage subsequent modification by -readers is not Transparent. An image format is not Transparent if -used for any substantial amount of text. A copy that is not -"Transparent" is called "Opaque". -

    -

    Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, LaTeX input format, -SGML or XML using a publicly available DTD, and standard-conforming -simple HTML, PostScript or PDF designed for human modification. -Examples of transparent image formats include PNG, XCF and JPG. -Opaque formats include proprietary formats that can be read and -edited only by proprietary word processors, SGML or XML for which -the DTD and/or processing tools are not generally available, and -the machine-generated HTML, PostScript or PDF produced by some word -processors for output purposes only. -

    -

    The "Title Page" means, for a printed book, the title page itself, -plus such following pages as are needed to hold, legibly, the -material this License requires to appear in the title page. For -works in formats which do not have any title page as such, "Title -Page" means the text near the most prominent appearance of the -work’s title, preceding the beginning of the body of the text. -

    -

    The "publisher" means any person or entity that distributes copies -of the Document to the public. -

    -

    A section "Entitled XYZ" means a named subunit of the Document -whose title either is precisely XYZ or contains XYZ in parentheses -following text that translates XYZ in another language. (Here XYZ -stands for a specific section name mentioned below, such as -"Acknowledgements", "Dedications", "Endorsements", or "History".) -To "Preserve the Title" of such a section when you modify the -Document means that it remains a section "Entitled XYZ" according -to this definition. -

    -

    The Document may include Warranty Disclaimers next to the notice -which states that this License applies to the Document. These -Warranty Disclaimers are considered to be included by reference in -this License, but only as regards disclaiming warranties: any other -implication that these Warranty Disclaimers may have is void and -has no effect on the meaning of this License. -

    -
  3. VERBATIM COPYING - -

    You may copy and distribute the Document in any medium, either -commercially or noncommercially, provided that this License, the -copyright notices, and the license notice saying this License -applies to the Document are reproduced in all copies, and that you -add no other conditions whatsoever to those of this License. You -may not use technical measures to obstruct or control the reading -or further copying of the copies you make or distribute. However, -you may accept compensation in exchange for copies. If you -distribute a large enough number of copies you must also follow the -conditions in section 3. -

    -

    You may also lend copies, under the same conditions stated above, -and you may publicly display copies. -

    -
  4. COPYING IN QUANTITY - -

    If you publish printed copies (or copies in media that commonly -have printed covers) of the Document, numbering more than 100, and -the Document’s license notice requires Cover Texts, you must -enclose the copies in covers that carry, clearly and legibly, all -these Cover Texts: Front-Cover Texts on the front cover, and -Back-Cover Texts on the back cover. Both covers must also clearly -and legibly identify you as the publisher of these copies. The -front cover must present the full title with all words of the title -equally prominent and visible. You may add other material on the -covers in addition. Copying with changes limited to the covers, as -long as they preserve the title of the Document and satisfy these -conditions, can be treated as verbatim copying in other respects. -

    -

    If the required texts for either cover are too voluminous to fit -legibly, you should put the first ones listed (as many as fit -reasonably) on the actual cover, and continue the rest onto -adjacent pages. -

    -

    If you publish or distribute Opaque copies of the Document -numbering more than 100, you must either include a machine-readable -Transparent copy along with each Opaque copy, or state in or with -each Opaque copy a computer-network location from which the general -network-using public has access to download using public-standard -network protocols a complete Transparent copy of the Document, free -of added material. If you use the latter option, you must take -reasonably prudent steps, when you begin distribution of Opaque -copies in quantity, to ensure that this Transparent copy will -remain thus accessible at the stated location until at least one -year after the last time you distribute an Opaque copy (directly or -through your agents or retailers) of that edition to the public. -

    -

    It is requested, but not required, that you contact the authors of -the Document well before redistributing any large number of copies, -to give them a chance to provide you with an updated version of the -Document. -

    -
  5. MODIFICATIONS - -

    You may copy and distribute a Modified Version of the Document -under the conditions of sections 2 and 3 above, provided that you -release the Modified Version under precisely this License, with the -Modified Version filling the role of the Document, thus licensing -distribution and modification of the Modified Version to whoever -possesses a copy of it. In addition, you must do these things in -the Modified Version: -

    -
      -
    1. Use in the Title Page (and on the covers, if any) a title -distinct from that of the Document, and from those of previous -versions (which should, if there were any, be listed in the -History section of the Document). You may use the same title as -a previous version if the original publisher of that version -gives permission. - -
    2. List on the Title Page, as authors, one or more persons or -entities responsible for authorship of the modifications in the -Modified Version, together with at least five of the principal -authors of the Document (all of its principal authors, if it has -fewer than five), unless they release you from this requirement. - -
    3. State on the Title page the name of the publisher of the -Modified Version, as the publisher. - -
    4. Preserve all the copyright notices of the Document. - -
    5. Add an appropriate copyright notice for your modifications -adjacent to the other copyright notices. - -
    6. Include, immediately after the copyright notices, a license -notice giving the public permission to use the Modified Version -under the terms of this License, in the form shown in the -Addendum below. - -
    7. Preserve in that license notice the full lists of Invariant -Sections and required Cover Texts given in the Document’s -license notice. - -
    8. Include an unaltered copy of this License. - -
    9. Preserve the section Entitled "History", Preserve its Title, and -add to it an item stating at least the title, year, new authors, -and publisher of the Modified Version as given on the Title -Page. If there is no section Entitled "History" in the Document, -create one stating the title, year, authors, and publisher of -the Document as given on its Title Page, then add an item -describing the Modified Version as stated in the previous -sentence. - -
    10. Preserve the network location, if any, given in the Document -for public access to a Transparent copy of the Document, and -likewise the network locations given in the Document for -previous versions it was based on. These may be placed in the -"History" section. You may omit a network location for a work -that was published at least four years before the Document -itself, or if the original publisher of the version it refers -to gives permission. - -
    11. For any section Entitled "Acknowledgements" or "Dedications", -Preserve the Title of the section, and preserve in the section -all the substance and tone of each of the contributor -acknowledgements and/or dedications given therein. - -
    12. Preserve all the Invariant Sections of the Document, unaltered -in their text and in their titles. Section numbers or the -equivalent are not considered part of the section titles. - -
    13. Delete any section Entitled "Endorsements". Such a section may -not be included in the Modified Version. - -
    14. Do not retitle any existing section to be Entitled -"Endorsements" or to conflict in title with any Invariant -Section. - -
    15. Preserve any Warranty Disclaimers. -
    - -

    If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections and contain no material -copied from the Document, you may at your option designate some or all -of these sections as invariant. To do this, add their titles to the -list of Invariant Sections in the Modified Version’s license notice. -These titles must be distinct from any other section titles. -

    -

    You may add a section Entitled "Endorsements", provided it contains -nothing but endorsements of your Modified Version by various -parties—for example, statements of peer review or that the text has -been approved by an organization as the authoritative definition of a -standard. -

    -

    You may add a passage of up to five words as a Front-Cover Text, and a -passage of up to 25 words as a Back-Cover Text, to the end of the list -of Cover Texts in the Modified Version. Only one passage of -Front-Cover Text and one of Back-Cover Text may be added by (or -through arrangements made by) any one entity. If the Document already -includes a cover text for the same cover, previously added by you or -by arrangement made by the same entity you are acting on behalf of, -you may not add another; but you may replace the old one, on explicit -permission from the previous publisher that added the old one. -

    -

    The author(s) and publisher(s) of the Document do not by this License -give permission to use their names for publicity for or to assert or -imply endorsement of any Modified Version. -

    -
  6. COMBINING DOCUMENTS - -

    You may combine the Document with other documents released under -this License, under the terms defined in section 4 above for -modified versions, provided that you include in the combination all -of the Invariant Sections of all of the original documents, -unmodified, and list them all as Invariant Sections of your -combined work in its license notice, and that you preserve all -their Warranty Disclaimers. -

    -

    The combined work need only contain one copy of this License, and -multiple identical Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections with the same name -but different contents, make the title of each such section unique -by adding at the end of it, in parentheses, the name of the -original author or publisher of that section if known, or else -a unique number. Make the same adjustment to the section titles in -the list of Invariant Sections in the license notice of the -combined work. -

    -

    In the combination, you must combine any sections Entitled -"History" in the various original documents, forming one section -Entitled "History"; likewise combine any sections Entitled -"Acknowledgements", and any sections Entitled "Dedications". You -must delete all sections Entitled "Endorsements." -

    -
  7. COLLECTIONS OF DOCUMENTS - -

    You may make a collection consisting of the Document and other -documents released under this License, and replace the individual -copies of this License in the various documents with a single copy -that is included in the collection, provided that you follow the -rules of this License for verbatim copying of each of the documents -in all other respects. -

    -

    You may extract a single document from such a collection, and -distribute it individually under this License, provided you insert -a copy of this License into the extracted document, and follow this -License in all other respects regarding verbatim copying of that -document. -

    -
  8. AGGREGATION WITH INDEPENDENT WORKS - -

    A compilation of the Document or its derivatives with other -separate and independent documents or works, in or on a volume of -a storage or distribution medium, is called an "aggregate" if the -copyright resulting from the compilation is not used to limit the -legal rights of the compilation’s users beyond what the individual -works permit. When the Document is included in an aggregate, this -License does not apply to the other works in the aggregate which -are not themselves derivative works of the Document. -

    -

    If the Cover Text requirement of section 3 is applicable to these -copies of the Document, then if the Document is less than one half -of the entire aggregate, the Document’s Cover Texts may be placed -on covers that bracket the Document within the aggregate, or the -electronic equivalent of covers if the Document is in electronic -form. Otherwise they must appear on printed covers that bracket -the whole aggregate. -

    -
  9. TRANSLATION - -

    Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of -section 4. Replacing Invariant Sections with translations requires -special permission from their copyright holders, but you may -include translations of some or all Invariant Sections in addition -to the original versions of these Invariant Sections. You may -include a translation of this License, and all the license notices -in the Document, and any Warranty Disclaimers, provided that you -also include the original English version of this License and the -original versions of those notices and disclaimers. In case of -a disagreement between the translation and the original version of -this License or a notice or disclaimer, the original version will -prevail. -

    -

    If a section in the Document is Entitled "Acknowledgements", -"Dedications", or "History", the requirement (section 4) to -Preserve its Title (section 1) will typically require changing the -actual title. -

    -
  10. TERMINATION - -

    You may not copy, modify, sublicense, or distribute the Document -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense, or distribute it is void, -and will automatically terminate your rights under this License. -

    -

    However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the -copyright holder fails to notify you of the violation by some -reasonable means prior to 60 days after the cessation. -

    -

    Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from -that copyright holder, and you cure the violation prior to 30 days -after your receipt of the notice. -

    -

    Termination of your rights under this section does not terminate -the licenses of parties who have received copies or rights from you -under this License. If your rights have been terminated and not -permanently reinstated, receipt of a copy of some or all of the -same material does not give you any rights to use it. -

    -
  11. FUTURE REVISIONS OF THIS LICENSE - -

    The Free Software Foundation may publish new, revised versions of -the GNU Free Documentation License from time to time. Such new -versions will be similar in spirit to the present version, but may -differ in detail to address new problems or concerns. See -http://www.gnu.org/copyleft/. -

    -

    Each version of the License is given a distinguishing version -number. If the Document specifies that a particular numbered -version of this License "or any later version" applies to it, you -have the option of following the terms and conditions either of -that specified version or of any later version that has been -published (not as a draft) by the Free Software Foundation. If -the Document does not specify a version number of this License, -you may choose any version ever published (not as a draft) by the -Free Software Foundation. If the Document specifies that a proxy -can decide which future versions of this License can be used, that -proxy’s public statement of acceptance of a version permanently -authorizes you to choose that version for the Document. -

    -
  12. RELICENSING - -

    "Massive Multiauthor Collaboration Site" (or "MMC Site") means any -World Wide Web server that publishes copyrightable works and also -provides prominent facilities for anybody to edit those works. -A public wiki that anybody can edit is an example of such -a server. A "Massive Multiauthor Collaboration" (or "MMC") -contained in the site means any set of copyrightable works thus -published on the MMC site. -

    -

    "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 -license published by Creative Commons Corporation, -a not-for-profit corporation with a principal place of business in -San Francisco, California, as well as future copyleft versions of -that license published by that same organization. -

    -

    "Incorporate" means to publish or republish a Document, in whole -or in part, as part of another Document. -

    -

    An MMC is "eligible for relicensing" if it is licensed under this -License, and if all works that were first published under this -License somewhere other than this MMC, and subsequently -incorporated in whole or in part into the MMC, (1) had no cover -texts or invariant sections, and (2) were thus incorporated prior -to November 1, 2008. -

    -

    The operator of an MMC Site may republish an MMC contained in the -site under CC-BY-SA on the same site at any time before August 1, -2009, provided the MMC is eligible for relicensing. -

- - -

A.1 ADDENDUM: How to use this License for your documents

- -

To use this License in a document you have written, include a copy of -the License in the document and put the following copyright and -license notices just after the title page: -

-
-
Copyright (C)  YEAR  YOUR NAME.
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3
-or any later version published by the Free Software Foundation;
-with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
-Texts.  A copy of the license is included in the section entitled ``GNU
-Free Documentation License''.
-
- -

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, -replace the "with…Texts." line with this: -

-
-
with the Invariant Sections being LIST THEIR TITLES, with
-the Front-Cover Texts being LIST, and with the Back-Cover Texts
-being LIST.
-
- -

If you have Invariant Sections without Cover Texts, or some other -combination of the three, merge those two alternatives to suit the -situation. -

-

If your document contains nontrivial examples of program code, we -recommend releasing these examples in parallel under your choice of -free software license, such as the GNU General Public License, to -permit their use in free software. -

-
- - - - - diff --git a/docs/docs/carbslinux.txt b/docs/docs/carbslinux.txt deleted file mode 100644 index a969c74..0000000 --- a/docs/docs/carbslinux.txt +++ /dev/null @@ -1,1356 +0,0 @@ - _________________________ - - CARBS LINUX USER MANUAL - - Cem Keylan - _________________________ - - -Table of Contents -_________________ - -1. Copying -2. Installation -.. 1. Preparing Environment -..... 1. Download -..... 2. Signature verification -..... 3. Extracting the tarball -..... 4. Obtain the chroot helper -.. 2. Chroot -..... 1. Setting up repositories -..... 2. Updating packages -..... 3. Installing packages -..... 4. Essential Software -..... 5. Obtaining the documentation -.. 3. System Configuration -..... 1. Configuring hostname -..... 2. Hosts file -.. 4. Kernel -..... 1. Obtaining the kernel sources -..... 2. Kernel dependencies -..... 3. Building the kernel -.. 5. Making your system bootable -..... 1. Bootloader -..... 2. Init scripts -..... 3. Fstab -.. 6. Post-installation -..... 1. KISS repositories -3. Init System -.. 1. Configuring Init -..... 1. Kernel Command Line -..... 2. `/etc/init/rc.conf' file -..... 3. Init Hooks -.. 2. Changing Init Program -..... 1. Rebooting after changing init -4. Contribution Guidelines -.. 1. Conventions -..... 1. Shell Conventions -..... 2. Repository Conventions -5. GNU Free Documentation License - - -This is the full documentation of [Carbs Linux], from the details of the -distribution, installation, to the package manager. It is not yet -complete. - -You can build and install the 'info' package in order to view this documentation -with the info reader. It is divided into sections and easier to read. - - -[Carbs Linux] - - -1 Copying -========= - - Copyright (c) 2020 Cem Keylan - - Permission is granted to copy, distribute and/or modify - this document under the terms of the GNU Free - Documentation License, Version 1.3 or any later version - published by the Free Software Foundation; with no - Invariant Sections, with no Front-Cover Texts and no - Back-Cover Texts. A copy of the license is included in - the section entitled "GNU Free Documentation License." - - -2 Installation -============== - - These are the step-by-step instructions for installing Carbs Linux. It - can be acquired as plain-text to be viewed offline with a pager from - . - - ,---- - | curl -sL https://carbslinux.org/install.txt | less - `---- - - .. 1. Preparing Environment - ..... 1. Download - ..... 2. Signature verification - ..... 3. Extracting the tarball - ..... 4. Obtain the chroot helper - .. 2. Chroot - ..... 1. Setting up repositories - ..... 2. Updating packages - ..... 3. Installing packages - ..... 4. Essential Software - ..... 5. Obtaining the documentation - .. 3. System Configuration - ..... 1. Configuring hostname - ..... 2. Hosts file - .. 4. Kernel - ..... 1. Obtaining the kernel sources - ..... 2. Kernel dependencies - ..... 3. Building the kernel - .. 5. Making your system bootable - ..... 1. Bootloader - ..... 2. Init scripts - ..... 3. Fstab - .. 6. Post-installation - ..... 1. KISS repositories - - -2.1 Preparing Environment -~~~~~~~~~~~~~~~~~~~~~~~~~ - - To install Carbs Linux, you will need a Live Linux ISO. For that - purpose, you can obtain a Gentoo or Void Linux live image. You can - follow their instructions to boot and setup your network. - - You will need the following programs in order to install Carbs Linux: - - - tar - - wget - - xz - - some form of base utilities (coreutils, sbase, busybox, etc.) - - Rest of these instructions will assume that you have set all of these - up, and will continue on that point. - - -2.1.1 Download --------------- - - First, we need to download the rootfs tarball. You can do the - following in order to obtain the rootfs. If you are using an i686 - machine, replace the `x86_64' with `i686'. We are setting this in a - URL variable so that we don't have to write it every time. - - ,---- - | wget $URL/carbs-rootfs.tar.xz.sha256 - | sha256sum -c carbs-rootfs.tar.xz.sha256 - `---- - - -2.1.2 Signature verification ----------------------------- - - It is highly recommended to verify the signature of the tarball. You - will need GPG for this. - - ,---- - | wget $URL/carbs-rootfs.tar.xz.sig - | gpg --recv-keys FF484BDFEFCEF8FF - | gpg --verify carbs-rootfs.tar.xz.sig - `---- - - -2.1.3 Extracting the tarball ----------------------------- - - You will need to extract the tarball to your desired location. For - partitioning, you can follow [this guide]. This will assume that you - will be mounting your root partition to `/mnt'. - - ,---- - | mount /dev/sdx1 /mnt - | tar xf carbs-rootfs.tar.xz -C /mnt - `---- - - -[this guide] - - -2.1.4 Obtain the chroot helper ------------------------------- - - You can obtain the `cpt-chroot' script in order to do a simple chroot - into your new root filesystem. - - ,---- - | wget https://dl.carbslinux.org/distfiles/cpt-chroot - | chmod a+x cpt-chroot - `---- - - -2.2 Chroot -~~~~~~~~~~ - - Chroot into Carbs Linux! - - ,---- - | ./cpt-chroot /mnt - `---- - - -2.2.1 Setting up repositories ------------------------------ - - Newest tarballs do not come with repositories, so you will need to - manually obtain them, and set your `CPT_PATH' environment - variable. Carbs Linux repositories can either be obtained by `git' or - `rsync'. While rsync repositories are overall faster and smaller, git - offers the whole history of the repository and a means to manipulate - your repository as you like it. If you want to obtain the git - repository, you will need to install `git' itself. - - The following guide will assume that you put the repositories into - `~/repos/' directory, but you can put the repositories into any - directory you want. So go ahead and create that directory: - - ,---- - | mkdir -p $HOME/repos - `---- - - -* 2.2.1.1 Obtaining from git - - Carbs Linux git repositories can be found both from the main server - and GitHub (mirror). Here are both their repository links. You can - clone any of them. - - - git://git.carbslinux.org/repository - - - - ,---- - | git clone git://git.carbslinux.org/repository $HOME/repos/carbs - `---- - - -* 2.2.1.2 Obtaining from rsync - - Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In - order to obtain it, run the following: - - ,---- - | rsync -avc rsync://carbslinux.org/repo $HOME/repos/carbs - `---- - - -* 2.2.1.3 Making the package manager use the repositories - - In your shell's configuration file, or in your `~/.profile' file, add - the following lines: - - ,---- - | CPT_PATH=$HOME/repos/carbs/core - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/extra - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/xorg - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/community - | export CPT_PATH - `---- - - -2.2.2 Updating packages ------------------------ - - It is good practice to make sure your system is up to date, especially - before building new packages. If there is an update for the package - manager you will need to update twice. - - ,---- - | cpt-update && cpt-update - `---- - - -2.2.3 Installing packages -------------------------- - - Since you are operating on a really small base, you might need to - build and install new programs to extend the functionality of your - system. In order to build and install packages new packages in Carbs, - you need to execute the following. "Package" is not actually a package - and is given as an example. - - ,---- - | cpt-build package - | cpt-install package - `---- - - -2.2.4 Essential Software ------------------------- - - Here is a list of software that you might want to have on your system. - - *BOOTLOADERS* - - - efibootmgr - - grub - - *FILESYSTEMS* - - - e2fsprogs - - dosfstools - - ntfs-3g - - *NETWORKING* - - - dhcpcd - - wpa_supplicant - - *TEXT EDITORS* - - - nano - - vim - - neatvi - - emacs - - emacs-nox (terminal-only version of emacs) - - *USER SHELLS* - - - bash - - zsh - - oksh - - rc - - *POSIX BASE UTILITIES* - - - busybox - - sbase - - coreutils - - *DOCUMENTATION* - - - carbs-docs - - man-pages - - man-pages-posix - - -2.2.5 Obtaining the documentation ---------------------------------- - - All the documentation for Carbs Linux can be found on a single info - manual to be viewed offline. You can obtain texinfo or the info - (standalone) package in order to view the documentation. - - ,---- - | # Install the documentation. - | cpt b carbs-docs && cpt i carbs-docs - | - | # Install either texinfo or the info package. We will be installing standalone info - | # as it doesn't need perl. - | cpt b info && cpt i info - | - | # You can then run info and navigate through the documentation. - | info carbslinux - `---- - - -2.3 System Configuration -~~~~~~~~~~~~~~~~~~~~~~~~ - - After you have finished installing some extra packages, you can - configure your system to your liking. - - -2.3.1 Configuring hostname --------------------------- - - You might want to add a hostname, especially in a networked - environment. Your hostname will default to 'carbslinux' unless you set - this. - - ,---- - | echo your-hostname > /etc/hostname - `---- - - -2.3.2 Hosts file ----------------- - - You can edit your /etc/hosts file, which is the static lookup table - for host names. By default, there are two entries for localhost which - are OKAY. You can replace the 'localhost' part of these entries to - your hostname. - - ,---- - | 127.0.0.1 localhost.localdomain localhost - | ::1 localhost.localdomain localhost ip6-localhost - `---- - - -2.4 Kernel -~~~~~~~~~~ - - Kernel isn't managed under the main repositories, even though you - could package one for your personal use. Here is an [example kernel - package], which you will need to reconfigure for your specific setup - if you want to make use of it. - - -[example kernel package] - - -2.4.1 Obtaining the kernel sources ----------------------------------- - - You can visit the website to choose a kernel that - you want to install. Though only the latest stable and longterm (LTS) - versions are supported. - - ,---- - | # Download the kernel and extract it - | wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz - | tar xf linux-5.9.1.tar.xz - | - | # Change directory into the kernel sources - | cd linux-5.9.1 - `---- - - -2.4.2 Kernel dependencies -------------------------- - - In order to compile the kernel you will need to install some - dependencies. You will need `libelf', and `bison' to compile the - kernel. If you want to configure using the menu interface you will - also need `ncurses'. - - ,---- - | # The package manager asks to install if you are building more than one package, - | # so no need to run 'cpt i ...' - | cpt b libelf ncurses - `---- - - In the vanilla kernel sources, you need perl to compile the kernel, - but it can be easily patched out. You will need to apply the following - patch. Patch was written by [E5ten]. You will need to obtain and apply - the patch in the kernel source directory. - - ,---- - | wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch - | patch -p1 < kernel-no-perl.patch - `---- - - -[E5ten] - - -2.4.3 Building the kernel -------------------------- - - Next step is configuring and building the kernel. You can check - Gentoo's [kernel configuration guide] to learn more about the - matter. Overall, Gentoo Wiki is a good place to learn about - configuration according to your hardware. The following will assume a - monolithic kernel. - - ,---- - | make menuconfig - | make - | install -Dm755 $(make -s image_name) /boot/vmlinuz-linux - `---- - - -[kernel configuration guide] - - - -2.5 Making your system bootable -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - In order to be able to boot your fresh system, wou will need an - init-daemon, init-scripts and a bootloader. The init daemon is already - provided by busybox, but you can optionally change it. - - -2.5.1 Bootloader ----------------- - - In the main repository, there is efibootmgr and grub to serve as - bootloaders. efibootmgr can be used as a standalone bootloader, or - can be used to install grub in a UEFI environment. efibootmgr is - needed unless you are using a device without UEFI support (or you - really want to use BIOS for a reason). - - -* 2.5.1.1 GRUB BIOS installation - - ,---- - | cpt b grub && cpt i grub - | grub-install --target=i386-pc /dev/sdX - | grub-mkconfig -o /boot/grub/grub.cfg - `---- - - -* 2.5.1.2 GRUB UEFI installation - - ,---- - | cpt b efibootmgr && cpt i efibootmgr - | cpt b grub && cpt i grub - | - | grub-install --target=x86_64-efi \ - | --efi-directory=esp \ - | --bootloader-id=CarbsLinux - | - | grub-mkconfig -o /boot/grub/grub.cfg - `---- - - -2.5.2 Init scripts ------------------- - - Only thing left to do is installing the init-scripts, and now you are - almost ready to boot your system! - - ,---- - | cpt b carbs-init && cpt i carbs-init - `---- - - -2.5.3 Fstab ------------ - - You can now manually edit your fstab entry, or you can use the - genfstab tool. If you want to use the tool, exit the chroot and run - the following: - - ,---- - | wget https://github.com/cemkeylan/genfstab/raw/master/genfstab - | chmod +x genfstab - | ./genfstab -U /mnt >> /mnt/etc/fstab - `---- - - -2.6 Post-installation -~~~~~~~~~~~~~~~~~~~~~ - - The base installation is now complete, you can now fine tune your - system according to your needs. Rest of these instructions are - completely optional. You can check the rest of the documentation to - learn more about the system. - - -2.6.1 KISS repositories ------------------------ - - While not 100% compatible with cpt, you can use kiss repositories in - your system the same way you are using the distribution - repositories. Here is an example for the KISS Linux Community - repository. - - -3 Init System -============= - - Carbs Linux init scripts are run by the init daemon (`busybox' by - default) on boot and shutdown processes. It also provides its own - halting program named shalt. This provides a portable method that - doesn't rely on non-POSIX external programs. - - -3.1 Configuring Init -~~~~~~~~~~~~~~~~~~~~ - - There are three ways you can change the behaviour of the init - system. Those are: - - - Kernel Command Line - - `/etc/init/rc.conf' file - - Init Hooks - - -3.1.1 Kernel Command Line -------------------------- - - On GRUB, you can edit the kernel command line parameters, which will - be parsed as variables on the init system. Not all of the parameters - will be acted upon, but all of them will be set as variables on the - init script. For example an example command line, and how it is - interpreted. - - ,---- - | BOOT_IMAGE=/boot/vmlinuz root=/dev/sda2 rw loglevel=3 quiet - `---- - - This command line will be parsed to set the following variables: - - ,---- - | BOOT_IMAGE=/boot/vmlinuz - | root=/dev/sda2 - | rw=1 - | loglevel=3 - | quiet=1 - `---- - - Some of these variables, such as `rw=/=ro', `loglevel', and `quiet', - will be used by the init system to change the behaviour of the - startup. - - -3.1.2 `/etc/init/rc.conf' file ------------------------------- - - However, the kernel command line isn't the only place to set your boot - parameters. You can specify variables here as well, although note that - the kernel command line always gets the priority for these variables - since they can be set just before boot. - - -3.1.3 Init Hooks ----------------- - - Init hooks are for custom personal commands that the user may want to - add to alter their boot. These can be used to load kernel modules, - modify interfaces, and lot more. Those hooks are added to the - `/etc/init' directory with the hook name as the suffix. For example, a - boot script will be placed as `/etc/init/my-hook.boot'. Currently, - there are 4 hooks that the user can use. - - early-boot - Run after pseudo-filesystems are mounted. - boot - Run before the boot stage is completed. - pre.shutdown - Run first when shutting down. - umount - Run just before filesystems are unmounted. - post.shutdown - Run just before the system is halted. - - -3.2 Changing Init Program -~~~~~~~~~~~~~~~~~~~~~~~~~ - - By default, Carbs Linux comes preinstalled with `busybox-init', but - this can easily be replaced without any issues. Currently, available - init systems are: - - - `sinit' - - `busybox' - - `runit' - - `shinit' - - This example is for runit, but it will work with all init systems - packaged in the distribution repositories. See the - `cpt-alternatives(1)' manual page for more details. - - ,---- - | cpt a runit /usr/bin/init - | cpt a runit /usr/bin/poweroff - | cpt a runit /usr/bin/reboot - `---- - - -3.2.1 Rebooting after changing init ------------------------------------ - - After switching init systems, your running init system may not accept - the new poweroff commands. You will need to reboot/poweroff using the - running init's utilities for the new utilities to work. These commands - are for the init system currently running on your system and not the - one you are switching to. - - Program Command - -------------------------------- - busybox `busybox reboot' - runit `runit-init 6' - shinit/sinit `kill -s INT 1' - - -4 Contribution Guidelines -========================= - - Thanks for taking your time to contribute! To maintain stylistic - behaviour throughout the repositories, one must adhere to these - conventions. Exceptions and changes may occur with good reasoning. - - -4.1 Conventions -~~~~~~~~~~~~~~~ - - [0010] - Try to keep the file readable. - [0011] - Characters on a line shouldn't exceed 100 characters. - [0012] - Make sure you don't have code commented out during - commit. Uncomment them or remove them completely. - [0013] - Do not add comments following the code, add them to the - top of the code. It makes it harder to read, and lines - longer. Here is an example: - - ,---- - | # Good way of commenting. - | your code goes here - | - | your code goes here # Avoid this way of commenting. - `---- - - -4.1.1 Shell Conventions ------------------------ - - Shell is central to Carbs Linux projects. Most of the tools and - packages are written in POSIX sh. - - [1010] - Use 4 spaces for indentation, don't use tabs. - [1020] - Make sure you don't use bash-specific code. - [1030] - Make sure you lint your code with `shellcheck' and if you are - new to POSIX sh, use `checkbashisms'. - [1040] - Don't spawn new processes if you don't absolutely need to, - especially during string manipulation. - [1041] - Never use a program for text manupilation that isn't - defined in the POSIX standard. This includes `gawk' and - `perl'. - [1042] - Instead of `$(basename $file)', use `${file##*}'. - [1043] - Instead of `$(dirname $file)', use `${file%/*}'. - - ,---- - | # This is the same thing as basename /path/to/test.asc .asc - | - | $ file=/path/to/test.asc file=${file##*/} file=${file%.asc} - | $ echo $file - | test - `---- - [1050] - Instead of backticks, use `$(..)'. - - -4.1.2 Repository Conventions ----------------------------- - - Repository conventions are important in order to ensure every package - resemble themselves. Here are the things to keep in mind: - - [2010] - Prefer tarballs over git packages unless there is a sensible - reason. Here are some: - - Every patch is a new release. (See [vim]) - - There are no releases. (See [sbase]) - - Following a development branch. - - There has been a long time since the latest release, but - upstream is far ahead. - [2020] - Prefer sources without a dependency to `automake'. There are - usually distribution tarballs that are `autoconf''ed. Don't - submit tarballs with an automake dependency unless you are - `sure' there is no alternative. - [2030] - Avoid these packages: - dbus - Usually can be disabled by `--disable-dbus'. - gettext - Usually can be disabled by `--disable-nls'. - [2040] - - Always install a package to the `/usr' prefix. - - All binaries should go to `/usr/bin', not `/usr/sbin' or any - other directory. - - All libraries should go to `/usr/lib'. - [2050] - All build files on the repository should be a POSIX shell - script, and must start with `#!/bin/sh -e'. - - The next section is about package templates that should be used in - order to ensure stylistic consistency. Note that the option - configurations shouldn't be taken literally, they are meant as - examples. - - -[vim] - -[sbase] - -* 4.1.2.1 Make [2210] - - ,---- - | #!/bin/sh -e - | - | make - | make DESTDIR="$1" PREFIX=/usr install - `---- - - -* 4.1.2.2 Configure/Make [2211] - - ,---- - | #!/bin/sh -e - | - | ./configure \ - | --prefix=/usr \ - | --disable-option \ - | --enable-option - | - | make - | make DESTDIR="$1" install - `---- - - -* 4.1.2.3 Autoconf/Automake [2212] - - ,---- - | #!/bin/sh -e - | - | autoreconf -fi - | - | ./configure \ - | --prefix=/usr \ - | --disable-option \ - | --enable-option - | - | make - | make DESTDIR="$1" install - `---- - - -* 4.1.2.4 Meson [2220] - - ,---- - | #!/bin/sh -e - | - | export DESTDIR=$1 - | - | meson \ - | --prefix=/usr \ - | -Doption=false \ - | -Doption2=true \ - | . output - | - | ninja -C output - | ninja -C output install - `---- - - -* 4.1.2.5 Cmake [2230] - - ,---- - | #!/bin/sh -e - | - | export DESTDIR=$1 - | - | cmake -B build \ - | -DCMAKE_INSTALL_PREFIX=/usr \ - | -DCMAKE_BUILD_TYPE=Release \ - | -DOPTION=ON - | - | cmake --build build - | cmake --install build - `---- - - -* 4.1.2.6 Go [2240] - - ,---- - | #!/bin/sh -e - | - | export GOPATH=$PWD/gopath - | trap "go clean -modcache" EXIT INT - | go mod vendor - | - | go build - | install -Dm755 program "$1/usr/bin/program" - `---- - - -* 4.1.2.7 Python [2241] - - ,---- - | #!/bin/sh -e - | - | python setup.py build - | python setup.py install --prefix=/usr --root="$1" - `---- - - -5 GNU Free Documentation License -================================ - - Version 1.3, 3 November 2008 - - Copyright (c) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. - - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - 0. PREAMBLE - - The purpose of this License is to make a manual, textbook, or other - functional and useful document free in the sense of freedom: to - assure everyone the effective freedom to copy and redistribute it, - with or without modifying it, either commercially or - noncommercially. Secondarily, this License preserves for the author - and publisher a way to get credit for their work, while not being - considered responsible for modifications made by others. - - This License is a kind of "copyleft", which means that derivative - works of the document must themselves be free in the same sense. - It complements the GNU General Public License, which is a copyleft - license designed for free software. - - We have designed this License in order to use it for manuals for - free software, because free software needs free documentation: a - free program should come with manuals providing the same freedoms - that the software does. But this License is not limited to - software manuals; it can be used for any textual work, regardless - of subject matter or whether it is published as a printed book. We - recommend this License principally for works whose purpose is - instruction or reference. - - 1. APPLICABILITY AND DEFINITIONS - - This License applies to any manual or other work, in any medium, - that contains a notice placed by the copyright holder saying it can - be distributed under the terms of this License. Such a notice - grants a world-wide, royalty-free license, unlimited in duration, - to use that work under the conditions stated herein. The - "Document", below, refers to any such manual or work. Any member - of the public is a licensee, and is addressed as "you". You accept - the license if you copy, modify or distribute the work in a way - requiring permission under copyright law. - - A "Modified Version" of the Document means any work containing the - Document or a portion of it, either copied verbatim, or with - modifications and/or translated into another language. - - A "Secondary Section" is a named appendix or a front-matter section - of the Document that deals exclusively with the relationship of the - publishers or authors of the Document to the Document's overall - subject (or to related matters) and contains nothing that could - fall directly within that overall subject. (Thus, if the Document - is in part a textbook of mathematics, a Secondary Section may not - explain any mathematics.) The relationship could be a matter of - historical connection with the subject or with related matters, or - of legal, commercial, philosophical, ethical or political position - regarding them. - - The "Invariant Sections" are certain Secondary Sections whose - titles are designated, as being those of Invariant Sections, in the - notice that says that the Document is released under this License. - If a section does not fit the above definition of Secondary then it - is not allowed to be designated as Invariant. The Document may - contain zero Invariant Sections. If the Document does not identify - any Invariant Sections then there are none. - - The "Cover Texts" are certain short passages of text that are - listed, as Front-Cover Texts or Back-Cover Texts, in the notice - that says that the Document is released under this License. A - Front-Cover Text may be at most 5 words, and a Back-Cover Text may - be at most 25 words. - - A "Transparent" copy of the Document means a machine-readable copy, - represented in a format whose specification is available to the - general public, that is suitable for revising the document - straightforwardly with generic text editors or (for images composed - of pixels) generic paint programs or (for drawings) some widely - available drawing editor, and that is suitable for input to text - formatters or for automatic translation to a variety of formats - suitable for input to text formatters. A copy made in an otherwise - Transparent file format whose markup, or absence of markup, has - been arranged to thwart or discourage subsequent modification by - readers is not Transparent. An image format is not Transparent if - used for any substantial amount of text. A copy that is not - "Transparent" is called "Opaque". - - Examples of suitable formats for Transparent copies include plain - ASCII without markup, Texinfo input format, LaTeX input format, - SGML or XML using a publicly available DTD, and standard-conforming - simple HTML, PostScript or PDF designed for human modification. - Examples of transparent image formats include PNG, XCF and JPG. - Opaque formats include proprietary formats that can be read and - edited only by proprietary word processors, SGML or XML for which - the DTD and/or processing tools are not generally available, and - the machine-generated HTML, PostScript or PDF produced by some word - processors for output purposes only. - - The "Title Page" means, for a printed book, the title page itself, - plus such following pages as are needed to hold, legibly, the - material this License requires to appear in the title page. For - works in formats which do not have any title page as such, "Title - Page" means the text near the most prominent appearance of the - work's title, preceding the beginning of the body of the text. - - The "publisher" means any person or entity that distributes copies - of the Document to the public. - - A section "Entitled XYZ" means a named subunit of the Document - whose title either is precisely XYZ or contains XYZ in parentheses - following text that translates XYZ in another language. (Here XYZ - stands for a specific section name mentioned below, such as - "Acknowledgements", "Dedications", "Endorsements", or "History".) - To "Preserve the Title" of such a section when you modify the - Document means that it remains a section "Entitled XYZ" according - to this definition. - - The Document may include Warranty Disclaimers next to the notice - which states that this License applies to the Document. These - Warranty Disclaimers are considered to be included by reference in - this License, but only as regards disclaiming warranties: any other - implication that these Warranty Disclaimers may have is void and - has no effect on the meaning of this License. - - 2. VERBATIM COPYING - - You may copy and distribute the Document in any medium, either - commercially or noncommercially, provided that this License, the - copyright notices, and the license notice saying this License - applies to the Document are reproduced in all copies, and that you - add no other conditions whatsoever to those of this License. You - may not use technical measures to obstruct or control the reading - or further copying of the copies you make or distribute. However, - you may accept compensation in exchange for copies. If you - distribute a large enough number of copies you must also follow the - conditions in section 3. - - You may also lend copies, under the same conditions stated above, - and you may publicly display copies. - - 3. COPYING IN QUANTITY - - If you publish printed copies (or copies in media that commonly - have printed covers) of the Document, numbering more than 100, and - the Document's license notice requires Cover Texts, you must - enclose the copies in covers that carry, clearly and legibly, all - these Cover Texts: Front-Cover Texts on the front cover, and - Back-Cover Texts on the back cover. Both covers must also clearly - and legibly identify you as the publisher of these copies. The - front cover must present the full title with all words of the title - equally prominent and visible. You may add other material on the - covers in addition. Copying with changes limited to the covers, as - long as they preserve the title of the Document and satisfy these - conditions, can be treated as verbatim copying in other respects. - - If the required texts for either cover are too voluminous to fit - legibly, you should put the first ones listed (as many as fit - reasonably) on the actual cover, and continue the rest onto - adjacent pages. - - If you publish or distribute Opaque copies of the Document - numbering more than 100, you must either include a machine-readable - Transparent copy along with each Opaque copy, or state in or with - each Opaque copy a computer-network location from which the general - network-using public has access to download using public-standard - network protocols a complete Transparent copy of the Document, free - of added material. If you use the latter option, you must take - reasonably prudent steps, when you begin distribution of Opaque - copies in quantity, to ensure that this Transparent copy will - remain thus accessible at the stated location until at least one - year after the last time you distribute an Opaque copy (directly or - through your agents or retailers) of that edition to the public. - - It is requested, but not required, that you contact the authors of - the Document well before redistributing any large number of copies, - to give them a chance to provide you with an updated version of the - Document. - - 4. MODIFICATIONS - - You may copy and distribute a Modified Version of the Document - under the conditions of sections 2 and 3 above, provided that you - release the Modified Version under precisely this License, with the - Modified Version filling the role of the Document, thus licensing - distribution and modification of the Modified Version to whoever - possesses a copy of it. In addition, you must do these things in - the Modified Version: - - 1. Use in the Title Page (and on the covers, if any) a title - distinct from that of the Document, and from those of previous - versions (which should, if there were any, be listed in the - History section of the Document). You may use the same title as - a previous version if the original publisher of that version - gives permission. - - 2. List on the Title Page, as authors, one or more persons or - entities responsible for authorship of the modifications in the - Modified Version, together with at least five of the principal - authors of the Document (all of its principal authors, if it has - fewer than five), unless they release you from this requirement. - - 3. State on the Title page the name of the publisher of the - Modified Version, as the publisher. - - 4. Preserve all the copyright notices of the Document. - - 5. Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. - - 6. Include, immediately after the copyright notices, a license - notice giving the public permission to use the Modified Version - under the terms of this License, in the form shown in the - Addendum below. - - 7. Preserve in that license notice the full lists of Invariant - Sections and required Cover Texts given in the Document's - license notice. - - 8. Include an unaltered copy of this License. - - 9. Preserve the section Entitled "History", Preserve its Title, and - add to it an item stating at least the title, year, new authors, - and publisher of the Modified Version as given on the Title - Page. If there is no section Entitled "History" in the Document, - create one stating the title, year, authors, and publisher of - the Document as given on its Title Page, then add an item - describing the Modified Version as stated in the previous - sentence. - - 10. Preserve the network location, if any, given in the Document - for public access to a Transparent copy of the Document, and - likewise the network locations given in the Document for - previous versions it was based on. These may be placed in the - "History" section. You may omit a network location for a work - that was published at least four years before the Document - itself, or if the original publisher of the version it refers - to gives permission. - - 11. For any section Entitled "Acknowledgements" or "Dedications", - Preserve the Title of the section, and preserve in the section - all the substance and tone of each of the contributor - acknowledgements and/or dedications given therein. - - 12. Preserve all the Invariant Sections of the Document, unaltered - in their text and in their titles. Section numbers or the - equivalent are not considered part of the section titles. - - 13. Delete any section Entitled "Endorsements". Such a section may - not be included in the Modified Version. - - 14. Do not retitle any existing section to be Entitled - "Endorsements" or to conflict in title with any Invariant - Section. - - 15. Preserve any Warranty Disclaimers. - - If the Modified Version includes new front-matter sections or - appendices that qualify as Secondary Sections and contain no - material copied from the Document, you may at your option designate - some or all of these sections as invariant. To do this, add their - titles to the list of Invariant Sections in the Modified Version's - license notice. These titles must be distinct from any other - section titles. - - You may add a section Entitled "Endorsements", provided it contains - nothing but endorsements of your Modified Version by various - parties---for example, statements of peer review or that the text - has been approved by an organization as the authoritative - definition of a standard. - - You may add a passage of up to five words as a Front-Cover Text, - and a passage of up to 25 words as a Back-Cover Text, to the end of - the list of Cover Texts in the Modified Version. Only one passage - of Front-Cover Text and one of Back-Cover Text may be added by (or - through arrangements made by) any one entity. If the Document - already includes a cover text for the same cover, previously added - by you or by arrangement made by the same entity you are acting on - behalf of, you may not add another; but you may replace the old - one, on explicit permission from the previous publisher that added - the old one. - - The author(s) and publisher(s) of the Document do not by this - License give permission to use their names for publicity for or to - assert or imply endorsement of any Modified Version. - - 5. COMBINING DOCUMENTS - - You may combine the Document with other documents released under - this License, under the terms defined in section 4 above for - modified versions, provided that you include in the combination all - of the Invariant Sections of all of the original documents, - unmodified, and list them all as Invariant Sections of your - combined work in its license notice, and that you preserve all - their Warranty Disclaimers. - - The combined work need only contain one copy of this License, and - multiple identical Invariant Sections may be replaced with a single - copy. If there are multiple Invariant Sections with the same name - but different contents, make the title of each such section unique - by adding at the end of it, in parentheses, the name of the - original author or publisher of that section if known, or else a - unique number. Make the same adjustment to the section titles in - the list of Invariant Sections in the license notice of the - combined work. - - In the combination, you must combine any sections Entitled - "History" in the various original documents, forming one section - Entitled "History"; likewise combine any sections Entitled - "Acknowledgements", and any sections Entitled "Dedications". You - must delete all sections Entitled "Endorsements." - - 6. COLLECTIONS OF DOCUMENTS - - You may make a collection consisting of the Document and other - documents released under this License, and replace the individual - copies of this License in the various documents with a single copy - that is included in the collection, provided that you follow the - rules of this License for verbatim copying of each of the documents - in all other respects. - - You may extract a single document from such a collection, and - distribute it individually under this License, provided you insert - a copy of this License into the extracted document, and follow this - License in all other respects regarding verbatim copying of that - document. - - 7. AGGREGATION WITH INDEPENDENT WORKS - - A compilation of the Document or its derivatives with other - separate and independent documents or works, in or on a volume of a - storage or distribution medium, is called an "aggregate" if the - copyright resulting from the compilation is not used to limit the - legal rights of the compilation's users beyond what the individual - works permit. When the Document is included in an aggregate, this - License does not apply to the other works in the aggregate which - are not themselves derivative works of the Document. - - If the Cover Text requirement of section 3 is applicable to these - copies of the Document, then if the Document is less than one half - of the entire aggregate, the Document's Cover Texts may be placed - on covers that bracket the Document within the aggregate, or the - electronic equivalent of covers if the Document is in electronic - form. Otherwise they must appear on printed covers that bracket - the whole aggregate. - - 8. TRANSLATION - - Translation is considered a kind of modification, so you may - distribute translations of the Document under the terms of section - 4. Replacing Invariant Sections with translations requires special - permission from their copyright holders, but you may include - translations of some or all Invariant Sections in addition to the - original versions of these Invariant Sections. You may include a - translation of this License, and all the license notices in the - Document, and any Warranty Disclaimers, provided that you also - include the original English version of this License and the - original versions of those notices and disclaimers. In case of a - disagreement between the translation and the original version of - this License or a notice or disclaimer, the original version will - prevail. - - If a section in the Document is Entitled "Acknowledgements", - "Dedications", or "History", the requirement (section 4) to - Preserve its Title (section 1) will typically require changing the - actual title. - - 9. TERMINATION - - You may not copy, modify, sublicense, or distribute the Document - except as expressly provided under this License. Any attempt - otherwise to copy, modify, sublicense, or distribute it is void, - and will automatically terminate your rights under this License. - - However, if you cease all violation of this License, then your - license from a particular copyright holder is reinstated (a) - provisionally, unless and until the copyright holder explicitly and - finally terminates your license, and (b) permanently, if the - copyright holder fails to notify you of the violation by some - reasonable means prior to 60 days after the cessation. - - Moreover, your license from a particular copyright holder is - reinstated permanently if the copyright holder notifies you of the - violation by some reasonable means, this is the first time you have - received notice of violation of this License (for any work) from - that copyright holder, and you cure the violation prior to 30 days - after your receipt of the notice. - - Termination of your rights under this section does not terminate - the licenses of parties who have received copies or rights from you - under this License. If your rights have been terminated and not - permanently reinstated, receipt of a copy of some or all of the - same material does not give you any rights to use it. - - 10. FUTURE REVISIONS OF THIS LICENSE - - The Free Software Foundation may publish new, revised versions of - the GNU Free Documentation License from time to time. Such new - versions will be similar in spirit to the present version, but may - differ in detail to address new problems or concerns. See - . - - Each version of the License is given a distinguishing version - number. If the Document specifies that a particular numbered - version of this License "or any later version" applies to it, you - have the option of following the terms and conditions either of - that specified version or of any later version that has been - published (not as a draft) by the Free Software Foundation. If - the Document does not specify a version number of this License, - you may choose any version ever published (not as a draft) by the - Free Software Foundation. If the Document specifies that a proxy - can decide which future versions of this License can be used, that - proxy's public statement of acceptance of a version permanently - authorizes you to choose that version for the Document. - - 11. RELICENSING - - "Massive Multiauthor Collaboration Site" (or "MMC Site") means any - World Wide Web server that publishes copyrightable works and also - provides prominent facilities for anybody to edit those works. A - public wiki that anybody can edit is an example of such a server. - A "Massive Multiauthor Collaboration" (or "MMC") contained in the - site means any set of copyrightable works thus published on the - MMC site. - - "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 - license published by Creative Commons Corporation, a - not-for-profit corporation with a principal place of business in - San Francisco, California, as well as future copyleft versions of - that license published by that same organization. - - "Incorporate" means to publish or republish a Document, in whole - or in part, as part of another Document. - - An MMC is "eligible for relicensing" if it is licensed under this - License, and if all works that were first published under this - License somewhere other than this MMC, and subsequently - incorporated in whole or in part into the MMC, (1) had no cover - texts or invariant sections, and (2) were thus incorporated prior - to November 1, 2008. - - The operator of an MMC Site may republish an MMC contained in the - site under CC-BY-SA on the same site at any time before August 1, - 2009, provided the MMC is eligible for relicensing. - - -ADDENDUM: How to use this License for your documents -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - To use this License in a document you have written, include a copy of - the License in the document and put the following copyright and - license notices just after the title page: - - ,---- - | Copyright (C) YEAR YOUR NAME. - | Permission is granted to copy, distribute and/or modify this document - | under the terms of the GNU Free Documentation License, Version 1.3 - | or any later version published by the Free Software Foundation; - | with no Invariant Sections, no Front-Cover Texts, and no Back-Cover - | Texts. A copy of the license is included in the section entitled ``GNU - | Free Documentation License''. - `---- - - If you have Invariant Sections, Front-Cover Texts and Back-Cover - Texts, replace the "with...Texts." line with this: - - ,---- - | with the Invariant Sections being LIST THEIR TITLES, with - | the Front-Cover Texts being LIST, and with the Back-Cover Texts - | being LIST. - `---- - - If you have Invariant Sections without Cover Texts, or some other - combination of the three, merge those two alternatives to suit the - situation. - - If your document contains nontrivial examples of program code, we - recommend releasing these examples in parallel under your choice of - free software license, such as the GNU General Public License, to - permit their use in free software. diff --git a/docs/docs/carbslinux/0010.html b/docs/docs/carbslinux/0010.html deleted file mode 100644 index fa3dd1b..0000000 --- a/docs/docs/carbslinux/0010.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -0010 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 0010.

- diff --git a/docs/docs/carbslinux/0011.html b/docs/docs/carbslinux/0011.html deleted file mode 100644 index 69daf27..0000000 --- a/docs/docs/carbslinux/0011.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -0011 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 0011.

- diff --git a/docs/docs/carbslinux/0012.html b/docs/docs/carbslinux/0012.html deleted file mode 100644 index e2bed83..0000000 --- a/docs/docs/carbslinux/0012.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -0012 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 0012.

- diff --git a/docs/docs/carbslinux/0013.html b/docs/docs/carbslinux/0013.html deleted file mode 100644 index 5551717..0000000 --- a/docs/docs/carbslinux/0013.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -0013 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 0013.

- diff --git a/docs/docs/carbslinux/1010.html b/docs/docs/carbslinux/1010.html deleted file mode 100644 index fd3abcf..0000000 --- a/docs/docs/carbslinux/1010.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1010 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1010.

- diff --git a/docs/docs/carbslinux/1020.html b/docs/docs/carbslinux/1020.html deleted file mode 100644 index 6c23536..0000000 --- a/docs/docs/carbslinux/1020.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1020 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1020.

- diff --git a/docs/docs/carbslinux/1030.html b/docs/docs/carbslinux/1030.html deleted file mode 100644 index ca4c4f1..0000000 --- a/docs/docs/carbslinux/1030.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1030 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1030.

- diff --git a/docs/docs/carbslinux/1040.html b/docs/docs/carbslinux/1040.html deleted file mode 100644 index 783086a..0000000 --- a/docs/docs/carbslinux/1040.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1040 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1040.

- diff --git a/docs/docs/carbslinux/1041.html b/docs/docs/carbslinux/1041.html deleted file mode 100644 index 0105a70..0000000 --- a/docs/docs/carbslinux/1041.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1041 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1041.

- diff --git a/docs/docs/carbslinux/1042.html b/docs/docs/carbslinux/1042.html deleted file mode 100644 index 433eef2..0000000 --- a/docs/docs/carbslinux/1042.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1042 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1042.

- diff --git a/docs/docs/carbslinux/1043.html b/docs/docs/carbslinux/1043.html deleted file mode 100644 index d15d15c..0000000 --- a/docs/docs/carbslinux/1043.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1043 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1043.

- diff --git a/docs/docs/carbslinux/1050.html b/docs/docs/carbslinux/1050.html deleted file mode 100644 index 8908db4..0000000 --- a/docs/docs/carbslinux/1050.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -1050 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 1050.

- diff --git a/docs/docs/carbslinux/2010.html b/docs/docs/carbslinux/2010.html deleted file mode 100644 index a6b7f67..0000000 --- a/docs/docs/carbslinux/2010.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2010 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2010.

- diff --git a/docs/docs/carbslinux/2020.html b/docs/docs/carbslinux/2020.html deleted file mode 100644 index 28febe7..0000000 --- a/docs/docs/carbslinux/2020.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2020 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2020.

- diff --git a/docs/docs/carbslinux/2030.html b/docs/docs/carbslinux/2030.html deleted file mode 100644 index 451a74c..0000000 --- a/docs/docs/carbslinux/2030.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2030 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2030.

- diff --git a/docs/docs/carbslinux/2040.html b/docs/docs/carbslinux/2040.html deleted file mode 100644 index 8263dbc..0000000 --- a/docs/docs/carbslinux/2040.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2040 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2040.

- diff --git a/docs/docs/carbslinux/2050.html b/docs/docs/carbslinux/2050.html deleted file mode 100644 index 38e5164..0000000 --- a/docs/docs/carbslinux/2050.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2050 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2050.

- diff --git a/docs/docs/carbslinux/2210.html b/docs/docs/carbslinux/2210.html deleted file mode 100644 index a48998d..0000000 --- a/docs/docs/carbslinux/2210.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2210 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2210.

- diff --git a/docs/docs/carbslinux/2211.html b/docs/docs/carbslinux/2211.html deleted file mode 100644 index 018f16b..0000000 --- a/docs/docs/carbslinux/2211.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2211 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2211.

- diff --git a/docs/docs/carbslinux/2212.html b/docs/docs/carbslinux/2212.html deleted file mode 100644 index 8937bda..0000000 --- a/docs/docs/carbslinux/2212.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2212 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2212.

- diff --git a/docs/docs/carbslinux/2220.html b/docs/docs/carbslinux/2220.html deleted file mode 100644 index 505b409..0000000 --- a/docs/docs/carbslinux/2220.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2220 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2220.

- diff --git a/docs/docs/carbslinux/2230.html b/docs/docs/carbslinux/2230.html deleted file mode 100644 index 36319c1..0000000 --- a/docs/docs/carbslinux/2230.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2230 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2230.

- diff --git a/docs/docs/carbslinux/2240.html b/docs/docs/carbslinux/2240.html deleted file mode 100644 index 44b3647..0000000 --- a/docs/docs/carbslinux/2240.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2240 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2240.

- diff --git a/docs/docs/carbslinux/2241.html b/docs/docs/carbslinux/2241.html deleted file mode 100644 index 73d123e..0000000 --- a/docs/docs/carbslinux/2241.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -2241 (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at 2241.

- diff --git a/docs/docs/carbslinux/ADDENDUM-How-to-use-this-License-for-your-documents.html b/docs/docs/carbslinux/ADDENDUM-How-to-use-this-License-for-your-documents.html deleted file mode 100644 index 0664ccd..0000000 --- a/docs/docs/carbslinux/ADDENDUM-How-to-use-this-License-for-your-documents.html +++ /dev/null @@ -1,50 +0,0 @@ - - - - - - - -ADDENDUM How to use this License for your documents (Carbs Linux User Manual) - - - - - - - - - - - - - - - -

The node you are looking for is at ADDENDUM How to use this License for your documents.

- diff --git a/docs/docs/carbslinux/Bootloader.html b/docs/docs/carbslinux/Bootloader.html deleted file mode 100644 index 8b52d9d..0000000 --- a/docs/docs/carbslinux/Bootloader.html +++ /dev/null @@ -1,92 +0,0 @@ - - - - - - -Bootloader (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Making your system bootable   [Contents]

-
-
-

1.5.1 Bootloader

- -

In the main repository, there is efibootmgr and grub to serve as bootloaders. -efibootmgr can be used as a standalone bootloader, or can be used to install -grub in a UEFI environment. efibootmgr is needed unless you are using a device -without UEFI support (or you really want to use BIOS for a reason). -

-
    -
  1. GRUB BIOS installation - - -
    -
    cpt b grub && cpt i grub
-grub-install --target=i386-pc /dev/sdX
-grub-mkconfig -o /boot/grub/grub.cfg
-
    - -
  2. GRUB UEFI installation - - -
    -
    cpt b efibootmgr && cpt i efibootmgr
-cpt b grub && cpt i grub
-
-grub-install --target=x86_64-efi \
-             --efi-directory=esp \
-             --bootloader-id=CarbsLinux
-
-grub-mkconfig -o /boot/grub/grub.cfg
-
    -
- - - - - - diff --git a/docs/docs/carbslinux/Building-the-kernel.html b/docs/docs/carbslinux/Building-the-kernel.html deleted file mode 100644 index 250925d..0000000 --- a/docs/docs/carbslinux/Building-the-kernel.html +++ /dev/null @@ -1,73 +0,0 @@ - - - - - - -Building the kernel (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Kernel   [Contents]

-
-
-

1.4.3 Building the kernel

- -

Next step is configuring and building the kernel. You can check Gentoo’s -kernel configuration guide to learn more about the matter. Overall, Gentoo Wiki -is a good place to learn about configuration according to your hardware. The -following will assume a monolithic kernel. -

-
-
make menuconfig
-make
-install -Dm755 $(make -s image_name) /boot/vmlinuz-linux
-
- - - - - - diff --git a/docs/docs/carbslinux/Changing-Init-Program.html b/docs/docs/carbslinux/Changing-Init-Program.html deleted file mode 100644 index 41568f9..0000000 --- a/docs/docs/carbslinux/Changing-Init-Program.html +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - -Changing Init Program (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Init System   [Contents]

-
-
-

2.2 Changing Init Program

- -

By default, Carbs Linux comes preinstalled with ‘busybox-init’, but this can -easily be replaced without any issues. Currently, available init systems are: -

-
    -
  • ‘sinit’ -
  • ‘busybox’ -
  • ‘runit’ -
  • ‘shinit’ -
- -

This example is for runit, but it will work with all init systems packaged in the -distribution repositories. See the ‘cpt-alternatives(1)’ manual page for more -details. -

-
-
cpt a runit /usr/bin/init
-cpt a runit /usr/bin/poweroff
-cpt a runit /usr/bin/reboot
-
- - - -
• Rebooting after changing init  Ways to reboot after replacing the init system -
- - - - - - diff --git a/docs/docs/carbslinux/Chroot.html b/docs/docs/carbslinux/Chroot.html deleted file mode 100644 index 02749c4..0000000 --- a/docs/docs/carbslinux/Chroot.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - - -Chroot (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Installation   [Contents]

-
-
-

1.2 Chroot

- -

Chroot into Carbs Linux! -

-
-
./cpt-chroot /mnt
-
- - - - - - - -
• Setting up repositories  Basic setup for obtaining repositories -
• Updating packages  Update your system -
• Installing packages  Install new software on your system -
• Essential Software  Software you might want to include on your system -
• Obtaining the documentation  Install documentation for offline use (optional) -
- - - - - - diff --git a/docs/docs/carbslinux/Configuring-Init.html b/docs/docs/carbslinux/Configuring-Init.html deleted file mode 100644 index d8fe8fd..0000000 --- a/docs/docs/carbslinux/Configuring-Init.html +++ /dev/null @@ -1,79 +0,0 @@ - - - - - - -Configuring Init (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Init System   [Contents]

-
-
-

2.1 Configuring Init

- -

There are three ways you can change the behaviour of the init system. Those are: -

-
    -
  • Kernel Command Line -
  • ‘/etc/init/rc.conf’ file -
  • Init Hooks -
- - - - - -
• Kernel Command Line  Configure init through the boot parameters -
• ‘/etc/init/rc.conf’ file  Configure init through the configuration file -
• Init Hooks  Configure init through hooks -
- - - - - - diff --git a/docs/docs/carbslinux/Configuring-hostname.html b/docs/docs/carbslinux/Configuring-hostname.html deleted file mode 100644 index b3c2a29..0000000 --- a/docs/docs/carbslinux/Configuring-hostname.html +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - -Configuring hostname (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: System Configuration   [Contents]

-
-
-

1.3.1 Configuring hostname

- -

You might want to add a hostname, especially in a networked environment. Your -hostname will default to ’carbslinux’ unless you set this. -

-
-
echo your-hostname > /etc/hostname
-
- - - - - - diff --git a/docs/docs/carbslinux/Contribution-Guidelines.html b/docs/docs/carbslinux/Contribution-Guidelines.html deleted file mode 100644 index df6c4b1..0000000 --- a/docs/docs/carbslinux/Contribution-Guidelines.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Contribution Guidelines (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Top   [Contents]

-
-
-

3 Contribution Guidelines

- -

Thanks for taking your time to contribute! To maintain stylistic behaviour -throughout the repositories, one must adhere to these conventions. Exceptions -and changes may occur with good reasoning. -

- - -
• Conventions  Conventions of the distribution -
- - - - - - diff --git a/docs/docs/carbslinux/Conventions.html b/docs/docs/carbslinux/Conventions.html deleted file mode 100644 index b91b9a7..0000000 --- a/docs/docs/carbslinux/Conventions.html +++ /dev/null @@ -1,97 +0,0 @@ - - - - - - -Conventions (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Up: Contribution Guidelines   [Contents]

-
-
-

3.1 Conventions

- - - -
-
[0010]
-

Try to keep the file readable. -

-
[0011]
-

Characters on a line shouldn’t exceed 100 characters. -

-
[0012]
-

Make sure you don’t have code commented out during -commit. Uncomment them or remove them completely. -

-
[0013]
-

Do not add comments following the code, add them to the -top of the code. It makes it harder to read, and lines longer. Here is an example: -

-
- -
-
# Good way of commenting.
-your code goes here
-
-your code goes here  # Avoid this way of commenting.
-
-
-
- - - - -
• Shell Conventions  Conventions for shell scripts -
• Repository Conventions  Conventions for repository build scripts -
- - - - - - diff --git a/docs/docs/carbslinux/Download.html b/docs/docs/carbslinux/Download.html deleted file mode 100644 index ef12617..0000000 --- a/docs/docs/carbslinux/Download.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - - -Download (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Preparing Environment   [Contents]

-
-
-

1.1.1 Download

- -

First, we need to download the rootfs tarball. You can do the following in order -to obtain the rootfs. If you are using an i686 machine, replace the ‘x86_64’ -with ‘i686’. We are setting this in a URL variable so that we don’t have to -write it every time. -

-
-
wget $URL/carbs-rootfs.tar.xz.sha256
-sha256sum -c carbs-rootfs.tar.xz.sha256
-
- - - - - - diff --git a/docs/docs/carbslinux/Essential-Software.html b/docs/docs/carbslinux/Essential-Software.html deleted file mode 100644 index 2c24ed7..0000000 --- a/docs/docs/carbslinux/Essential-Software.html +++ /dev/null @@ -1,121 +0,0 @@ - - - - - - -Essential Software (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-
-

1.2.4 Essential Software

- -

Here is a list of software that you might want to have on your system. -

-

BOOTLOADERS -

-
    -
  • efibootmgr -
  • grub -
- -

FILESYSTEMS -

-
    -
  • e2fsprogs -
  • dosfstools -
  • ntfs-3g -
- -

NETWORKING -

-
    -
  • dhcpcd -
  • wpa_supplicant -
- -

TEXT EDITORS -

-
    -
  • nano -
  • vim -
  • neatvi -
  • emacs -
  • emacs-nox (terminal-only version of emacs) -
- -

USER SHELLS -

-
    -
  • bash -
  • zsh -
  • oksh -
  • rc -
- -

POSIX BASE UTILITIES -

-
    -
  • busybox -
  • sbase -
  • coreutils -
- -

DOCUMENTATION -

-
    -
  • carbs-docs -
  • man-pages -
  • man-pages-posix -
- - - - - - diff --git a/docs/docs/carbslinux/Extracting-the-tarball.html b/docs/docs/carbslinux/Extracting-the-tarball.html deleted file mode 100644 index a562feb..0000000 --- a/docs/docs/carbslinux/Extracting-the-tarball.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Extracting the tarball (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Preparing Environment   [Contents]

-
-
-

1.1.3 Extracting the tarball

- -

You will need to extract the tarball to your desired location. For partitioning, -you can follow this guide. This will assume that you will be mounting your root -partition to ‘/mnt’. -

-
-
mount /dev/sdx1 /mnt
-tar xf carbs-rootfs.tar.xz -C /mnt
-
- - - - - - diff --git a/docs/docs/carbslinux/Fstab.html b/docs/docs/carbslinux/Fstab.html deleted file mode 100644 index 43ab331..0000000 --- a/docs/docs/carbslinux/Fstab.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Fstab (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Making your system bootable   [Contents]

-
-
-

1.5.3 Fstab

- -

You can now manually edit your fstab entry, or you can use the genfstab tool. -If you want to use the tool, exit the chroot and run the following: -

-
-
wget https://github.com/cemkeylan/genfstab/raw/master/genfstab
-chmod +x genfstab
-./genfstab -U /mnt >> /mnt/etc/fstab
-
- - - - - - diff --git a/docs/docs/carbslinux/GNU-Free-Documentation-License.html b/docs/docs/carbslinux/GNU-Free-Documentation-License.html deleted file mode 100644 index bda1afd..0000000 --- a/docs/docs/carbslinux/GNU-Free-Documentation-License.html +++ /dev/null @@ -1,550 +0,0 @@ - - - - - - -GNU Free Documentation License (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Top   [Contents]

-
-
-

Appendix A GNU Free Documentation License

- -
Version 1.3, 3 November 2008 -
-
-
Copyright © 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
-http://fsf.org/
-
-Everyone is permitted to copy and distribute verbatim copies
-of this license document, but changing it is not allowed.
-
- -
    -
  1. PREAMBLE - -

    The purpose of this License is to make a manual, textbook, or other -functional and useful document free -in the sense of freedom: to assure everyone the effective freedom -to copy and redistribute it, with or without modifying it, either -commercially or noncommercially. Secondarily, this License -preserves for the author and publisher a way to get credit for -their work, while not being considered responsible for -modifications made by others. -

    -

    This License is a kind of "copyleft", which means that derivative -works of the document must themselves be free in the same sense. -It complements the GNU General Public License, which is a copyleft -license designed for free software. -

    -

    We have designed this License in order to use it for manuals for -free software, because free software needs free documentation: -a free program should come with manuals providing the same freedoms -that the software does. But this License is not limited to -software manuals; it can be used for any textual work, regardless -of subject matter or whether it is published as a printed book. We -recommend this License principally for works whose purpose is -instruction or reference. -

    -
  2. APPLICABILITY AND DEFINITIONS - -

    This License applies to any manual or other work, in any medium, -that contains a notice placed by the copyright holder saying it can -be distributed under the terms of this License. Such a notice -grants a world-wide, royalty-free license, unlimited in duration, -to use that work under the conditions stated herein. The -"Document", below, refers to any such manual or work. Any member -of the public is a licensee, and is addressed as "you". You accept -the license if you copy, modify or distribute the work in a way -requiring permission under copyright law. -

    -

    A "Modified Version" of the Document means any work containing the -Document or a portion of it, either copied verbatim, or with -modifications and/or translated into another language. -

    -

    A "Secondary Section" is a named appendix or a front-matter section -of the Document that deals exclusively with the relationship of the -publishers or authors of the Document to the Document’s overall -subject (or to related matters) and contains nothing that could -fall directly within that overall subject. (Thus, if the Document -is in part a textbook of mathematics, a Secondary Section may not -explain any mathematics.) The relationship could be a matter of -historical connection with the subject or with related matters, or -of legal, commercial, philosophical, ethical or political position -regarding them. -

    -

    The "Invariant Sections" are certain Secondary Sections whose -titles are designated, as being those of Invariant Sections, in the -notice that says that the Document is released under this License. -If a section does not fit the above definition of Secondary then it -is not allowed to be designated as Invariant. The Document may -contain zero Invariant Sections. If the Document does not identify -any Invariant Sections then there are none. -

    -

    The "Cover Texts" are certain short passages of text that are -listed, as Front-Cover Texts or Back-Cover Texts, in the notice -that says that the Document is released under this License. -A Front-Cover Text may be at most 5 words, and a Back-Cover Text -may be at most 25 words. -

    -

    A "Transparent" copy of the Document means a machine-readable copy, -represented in a format whose specification is available to the -general public, that is suitable for revising the document -straightforwardly with generic text editors or (for images composed -of pixels) generic paint programs or (for drawings) some widely -available drawing editor, and that is suitable for input to text -formatters or for automatic translation to a variety of formats -suitable for input to text formatters. A copy made in an otherwise -Transparent file format whose markup, or absence of markup, has -been arranged to thwart or discourage subsequent modification by -readers is not Transparent. An image format is not Transparent if -used for any substantial amount of text. A copy that is not -"Transparent" is called "Opaque". -

    -

    Examples of suitable formats for Transparent copies include plain -ASCII without markup, Texinfo input format, LaTeX input format, -SGML or XML using a publicly available DTD, and standard-conforming -simple HTML, PostScript or PDF designed for human modification. -Examples of transparent image formats include PNG, XCF and JPG. -Opaque formats include proprietary formats that can be read and -edited only by proprietary word processors, SGML or XML for which -the DTD and/or processing tools are not generally available, and -the machine-generated HTML, PostScript or PDF produced by some word -processors for output purposes only. -

    -

    The "Title Page" means, for a printed book, the title page itself, -plus such following pages as are needed to hold, legibly, the -material this License requires to appear in the title page. For -works in formats which do not have any title page as such, "Title -Page" means the text near the most prominent appearance of the -work’s title, preceding the beginning of the body of the text. -

    -

    The "publisher" means any person or entity that distributes copies -of the Document to the public. -

    -

    A section "Entitled XYZ" means a named subunit of the Document -whose title either is precisely XYZ or contains XYZ in parentheses -following text that translates XYZ in another language. (Here XYZ -stands for a specific section name mentioned below, such as -"Acknowledgements", "Dedications", "Endorsements", or "History".) -To "Preserve the Title" of such a section when you modify the -Document means that it remains a section "Entitled XYZ" according -to this definition. -

    -

    The Document may include Warranty Disclaimers next to the notice -which states that this License applies to the Document. These -Warranty Disclaimers are considered to be included by reference in -this License, but only as regards disclaiming warranties: any other -implication that these Warranty Disclaimers may have is void and -has no effect on the meaning of this License. -

    -
  3. VERBATIM COPYING - -

    You may copy and distribute the Document in any medium, either -commercially or noncommercially, provided that this License, the -copyright notices, and the license notice saying this License -applies to the Document are reproduced in all copies, and that you -add no other conditions whatsoever to those of this License. You -may not use technical measures to obstruct or control the reading -or further copying of the copies you make or distribute. However, -you may accept compensation in exchange for copies. If you -distribute a large enough number of copies you must also follow the -conditions in section 3. -

    -

    You may also lend copies, under the same conditions stated above, -and you may publicly display copies. -

    -
  4. COPYING IN QUANTITY - -

    If you publish printed copies (or copies in media that commonly -have printed covers) of the Document, numbering more than 100, and -the Document’s license notice requires Cover Texts, you must -enclose the copies in covers that carry, clearly and legibly, all -these Cover Texts: Front-Cover Texts on the front cover, and -Back-Cover Texts on the back cover. Both covers must also clearly -and legibly identify you as the publisher of these copies. The -front cover must present the full title with all words of the title -equally prominent and visible. You may add other material on the -covers in addition. Copying with changes limited to the covers, as -long as they preserve the title of the Document and satisfy these -conditions, can be treated as verbatim copying in other respects. -

    -

    If the required texts for either cover are too voluminous to fit -legibly, you should put the first ones listed (as many as fit -reasonably) on the actual cover, and continue the rest onto -adjacent pages. -

    -

    If you publish or distribute Opaque copies of the Document -numbering more than 100, you must either include a machine-readable -Transparent copy along with each Opaque copy, or state in or with -each Opaque copy a computer-network location from which the general -network-using public has access to download using public-standard -network protocols a complete Transparent copy of the Document, free -of added material. If you use the latter option, you must take -reasonably prudent steps, when you begin distribution of Opaque -copies in quantity, to ensure that this Transparent copy will -remain thus accessible at the stated location until at least one -year after the last time you distribute an Opaque copy (directly or -through your agents or retailers) of that edition to the public. -

    -

    It is requested, but not required, that you contact the authors of -the Document well before redistributing any large number of copies, -to give them a chance to provide you with an updated version of the -Document. -

    -
  5. MODIFICATIONS - -

    You may copy and distribute a Modified Version of the Document -under the conditions of sections 2 and 3 above, provided that you -release the Modified Version under precisely this License, with the -Modified Version filling the role of the Document, thus licensing -distribution and modification of the Modified Version to whoever -possesses a copy of it. In addition, you must do these things in -the Modified Version: -

    -
      -
    1. Use in the Title Page (and on the covers, if any) a title -distinct from that of the Document, and from those of previous -versions (which should, if there were any, be listed in the -History section of the Document). You may use the same title as -a previous version if the original publisher of that version -gives permission. - -
    2. List on the Title Page, as authors, one or more persons or -entities responsible for authorship of the modifications in the -Modified Version, together with at least five of the principal -authors of the Document (all of its principal authors, if it has -fewer than five), unless they release you from this requirement. - -
    3. State on the Title page the name of the publisher of the -Modified Version, as the publisher. - -
    4. Preserve all the copyright notices of the Document. - -
    5. Add an appropriate copyright notice for your modifications -adjacent to the other copyright notices. - -
    6. Include, immediately after the copyright notices, a license -notice giving the public permission to use the Modified Version -under the terms of this License, in the form shown in the -Addendum below. - -
    7. Preserve in that license notice the full lists of Invariant -Sections and required Cover Texts given in the Document’s -license notice. - -
    8. Include an unaltered copy of this License. - -
    9. Preserve the section Entitled "History", Preserve its Title, and -add to it an item stating at least the title, year, new authors, -and publisher of the Modified Version as given on the Title -Page. If there is no section Entitled "History" in the Document, -create one stating the title, year, authors, and publisher of -the Document as given on its Title Page, then add an item -describing the Modified Version as stated in the previous -sentence. - -
    10. Preserve the network location, if any, given in the Document -for public access to a Transparent copy of the Document, and -likewise the network locations given in the Document for -previous versions it was based on. These may be placed in the -"History" section. You may omit a network location for a work -that was published at least four years before the Document -itself, or if the original publisher of the version it refers -to gives permission. - -
    11. For any section Entitled "Acknowledgements" or "Dedications", -Preserve the Title of the section, and preserve in the section -all the substance and tone of each of the contributor -acknowledgements and/or dedications given therein. - -
    12. Preserve all the Invariant Sections of the Document, unaltered -in their text and in their titles. Section numbers or the -equivalent are not considered part of the section titles. - -
    13. Delete any section Entitled "Endorsements". Such a section may -not be included in the Modified Version. - -
    14. Do not retitle any existing section to be Entitled -"Endorsements" or to conflict in title with any Invariant -Section. - -
    15. Preserve any Warranty Disclaimers. -
    - -

    If the Modified Version includes new front-matter sections or -appendices that qualify as Secondary Sections and contain no material -copied from the Document, you may at your option designate some or all -of these sections as invariant. To do this, add their titles to the -list of Invariant Sections in the Modified Version’s license notice. -These titles must be distinct from any other section titles. -

    -

    You may add a section Entitled "Endorsements", provided it contains -nothing but endorsements of your Modified Version by various -parties—for example, statements of peer review or that the text has -been approved by an organization as the authoritative definition of a -standard. -

    -

    You may add a passage of up to five words as a Front-Cover Text, and a -passage of up to 25 words as a Back-Cover Text, to the end of the list -of Cover Texts in the Modified Version. Only one passage of -Front-Cover Text and one of Back-Cover Text may be added by (or -through arrangements made by) any one entity. If the Document already -includes a cover text for the same cover, previously added by you or -by arrangement made by the same entity you are acting on behalf of, -you may not add another; but you may replace the old one, on explicit -permission from the previous publisher that added the old one. -

    -

    The author(s) and publisher(s) of the Document do not by this License -give permission to use their names for publicity for or to assert or -imply endorsement of any Modified Version. -

    -
  6. COMBINING DOCUMENTS - -

    You may combine the Document with other documents released under -this License, under the terms defined in section 4 above for -modified versions, provided that you include in the combination all -of the Invariant Sections of all of the original documents, -unmodified, and list them all as Invariant Sections of your -combined work in its license notice, and that you preserve all -their Warranty Disclaimers. -

    -

    The combined work need only contain one copy of this License, and -multiple identical Invariant Sections may be replaced with a single -copy. If there are multiple Invariant Sections with the same name -but different contents, make the title of each such section unique -by adding at the end of it, in parentheses, the name of the -original author or publisher of that section if known, or else -a unique number. Make the same adjustment to the section titles in -the list of Invariant Sections in the license notice of the -combined work. -

    -

    In the combination, you must combine any sections Entitled -"History" in the various original documents, forming one section -Entitled "History"; likewise combine any sections Entitled -"Acknowledgements", and any sections Entitled "Dedications". You -must delete all sections Entitled "Endorsements." -

    -
  7. COLLECTIONS OF DOCUMENTS - -

    You may make a collection consisting of the Document and other -documents released under this License, and replace the individual -copies of this License in the various documents with a single copy -that is included in the collection, provided that you follow the -rules of this License for verbatim copying of each of the documents -in all other respects. -

    -

    You may extract a single document from such a collection, and -distribute it individually under this License, provided you insert -a copy of this License into the extracted document, and follow this -License in all other respects regarding verbatim copying of that -document. -

    -
  8. AGGREGATION WITH INDEPENDENT WORKS - -

    A compilation of the Document or its derivatives with other -separate and independent documents or works, in or on a volume of -a storage or distribution medium, is called an "aggregate" if the -copyright resulting from the compilation is not used to limit the -legal rights of the compilation’s users beyond what the individual -works permit. When the Document is included in an aggregate, this -License does not apply to the other works in the aggregate which -are not themselves derivative works of the Document. -

    -

    If the Cover Text requirement of section 3 is applicable to these -copies of the Document, then if the Document is less than one half -of the entire aggregate, the Document’s Cover Texts may be placed -on covers that bracket the Document within the aggregate, or the -electronic equivalent of covers if the Document is in electronic -form. Otherwise they must appear on printed covers that bracket -the whole aggregate. -

    -
  9. TRANSLATION - -

    Translation is considered a kind of modification, so you may -distribute translations of the Document under the terms of -section 4. Replacing Invariant Sections with translations requires -special permission from their copyright holders, but you may -include translations of some or all Invariant Sections in addition -to the original versions of these Invariant Sections. You may -include a translation of this License, and all the license notices -in the Document, and any Warranty Disclaimers, provided that you -also include the original English version of this License and the -original versions of those notices and disclaimers. In case of -a disagreement between the translation and the original version of -this License or a notice or disclaimer, the original version will -prevail. -

    -

    If a section in the Document is Entitled "Acknowledgements", -"Dedications", or "History", the requirement (section 4) to -Preserve its Title (section 1) will typically require changing the -actual title. -

    -
  10. TERMINATION - -

    You may not copy, modify, sublicense, or distribute the Document -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense, or distribute it is void, -and will automatically terminate your rights under this License. -

    -

    However, if you cease all violation of this License, then your -license from a particular copyright holder is reinstated (a) -provisionally, unless and until the copyright holder explicitly and -finally terminates your license, and (b) permanently, if the -copyright holder fails to notify you of the violation by some -reasonable means prior to 60 days after the cessation. -

    -

    Moreover, your license from a particular copyright holder is -reinstated permanently if the copyright holder notifies you of the -violation by some reasonable means, this is the first time you have -received notice of violation of this License (for any work) from -that copyright holder, and you cure the violation prior to 30 days -after your receipt of the notice. -

    -

    Termination of your rights under this section does not terminate -the licenses of parties who have received copies or rights from you -under this License. If your rights have been terminated and not -permanently reinstated, receipt of a copy of some or all of the -same material does not give you any rights to use it. -

    -
  11. FUTURE REVISIONS OF THIS LICENSE - -

    The Free Software Foundation may publish new, revised versions of -the GNU Free Documentation License from time to time. Such new -versions will be similar in spirit to the present version, but may -differ in detail to address new problems or concerns. See -http://www.gnu.org/copyleft/. -

    -

    Each version of the License is given a distinguishing version -number. If the Document specifies that a particular numbered -version of this License "or any later version" applies to it, you -have the option of following the terms and conditions either of -that specified version or of any later version that has been -published (not as a draft) by the Free Software Foundation. If -the Document does not specify a version number of this License, -you may choose any version ever published (not as a draft) by the -Free Software Foundation. If the Document specifies that a proxy -can decide which future versions of this License can be used, that -proxy’s public statement of acceptance of a version permanently -authorizes you to choose that version for the Document. -

    -
  12. RELICENSING - -

    "Massive Multiauthor Collaboration Site" (or "MMC Site") means any -World Wide Web server that publishes copyrightable works and also -provides prominent facilities for anybody to edit those works. -A public wiki that anybody can edit is an example of such -a server. A "Massive Multiauthor Collaboration" (or "MMC") -contained in the site means any set of copyrightable works thus -published on the MMC site. -

    -

    "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 -license published by Creative Commons Corporation, -a not-for-profit corporation with a principal place of business in -San Francisco, California, as well as future copyleft versions of -that license published by that same organization. -

    -

    "Incorporate" means to publish or republish a Document, in whole -or in part, as part of another Document. -

    -

    An MMC is "eligible for relicensing" if it is licensed under this -License, and if all works that were first published under this -License somewhere other than this MMC, and subsequently -incorporated in whole or in part into the MMC, (1) had no cover -texts or invariant sections, and (2) were thus incorporated prior -to November 1, 2008. -

    -

    The operator of an MMC Site may republish an MMC contained in the -site under CC-BY-SA on the same site at any time before August 1, -2009, provided the MMC is eligible for relicensing. -

- - -

A.1 ADDENDUM: How to use this License for your documents

- -

To use this License in a document you have written, include a copy of -the License in the document and put the following copyright and -license notices just after the title page: -

-
-
Copyright (C)  YEAR  YOUR NAME.
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3
-or any later version published by the Free Software Foundation;
-with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
-Texts.  A copy of the license is included in the section entitled ``GNU
-Free Documentation License''.
-
- -

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, -replace the "with…Texts." line with this: -

-
-
with the Invariant Sections being LIST THEIR TITLES, with
-the Front-Cover Texts being LIST, and with the Back-Cover Texts
-being LIST.
-
- -

If you have Invariant Sections without Cover Texts, or some other -combination of the three, merge those two alternatives to suit the -situation. -

-

If your document contains nontrivial examples of program code, we -recommend releasing these examples in parallel under your choice of -free software license, such as the GNU General Public License, to -permit their use in free software. -

-
-
-

-Previous: , Up: Top   [Contents]

-
- - - - - diff --git a/docs/docs/carbslinux/Hosts-file.html b/docs/docs/carbslinux/Hosts-file.html deleted file mode 100644 index 8ca871d..0000000 --- a/docs/docs/carbslinux/Hosts-file.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Hosts file (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: System Configuration   [Contents]

-
-
-

1.3.2 Hosts file

- -

You can edit your /etc/hosts file, which is the static lookup table for host -names. By default, there are two entries for localhost which are OKAY. You can -replace the ’localhost’ part of these entries to your hostname. -

-
-
127.0.0.1  localhost.localdomain localhost
-::1        localhost.localdomain localhost ip6-localhost
-
- - - - - - diff --git a/docs/docs/carbslinux/Init-Hooks.html b/docs/docs/carbslinux/Init-Hooks.html deleted file mode 100644 index 03ea867..0000000 --- a/docs/docs/carbslinux/Init-Hooks.html +++ /dev/null @@ -1,86 +0,0 @@ - - - - - - -Init Hooks (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Configuring Init   [Contents]

-
-
-

2.1.3 Init Hooks

- -

Init hooks are for custom personal commands that the user may want to add to -alter their boot. These can be used to load kernel modules, modify interfaces, -and lot more. Those hooks are added to the ‘/etc/init’ directory with the -hook name as the suffix. For example, a boot script will be placed as -‘/etc/init/my-hook.boot’. Currently, there are 4 hooks that the user can use. -

-
-
early-boot
-

Run after pseudo-filesystems are mounted. -

-
boot
-

Run before the boot stage is completed. -

-
pre.shutdown
-

Run first when shutting down. -

-
umount
-

Run just before filesystems are unmounted. -

-
post.shutdown
-

Run just before the system is halted. -

-
- - - - - - diff --git a/docs/docs/carbslinux/Init-System.html b/docs/docs/carbslinux/Init-System.html deleted file mode 100644 index bbba51f..0000000 --- a/docs/docs/carbslinux/Init-System.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - -Init System (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Top   [Contents]

-
-
-

2 Init System

- -

Carbs Linux init scripts are run by the init daemon (‘busybox’ by default) on -boot and shutdown processes. It also provides its own halting program named -shalt. This provides a portable method that doesn’t rely on non-POSIX external -programs. -

- - - -
• Configuring Init  Ways to configure the init system -
• Changing Init Program  Replace the default busybox init with something new -
- - - - - - diff --git a/docs/docs/carbslinux/Init-scripts.html b/docs/docs/carbslinux/Init-scripts.html deleted file mode 100644 index 6b81ed0..0000000 --- a/docs/docs/carbslinux/Init-scripts.html +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - -Init scripts (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Making your system bootable   [Contents]

-
-
-

1.5.2 Init scripts

- -

Only thing left to do is installing the init-scripts, and now you are almost -ready to boot your system! -

-
-
cpt b carbs-init && cpt i carbs-init
-
- - - - - - diff --git a/docs/docs/carbslinux/Installation.html b/docs/docs/carbslinux/Installation.html deleted file mode 100644 index 64dd231..0000000 --- a/docs/docs/carbslinux/Installation.html +++ /dev/null @@ -1,85 +0,0 @@ - - - - - - -Installation (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Top   [Contents]

-
-
-

1 Installation

- -

These are the step-by-step instructions for installing Carbs Linux. It can be -acquired as plain-text to be viewed offline with a pager from -https://carbslinux.org/install.txt. -

-
-
curl -sL https://carbslinux.org/install.txt | less
-
- - - - - - - - -
• Preparing Environment  Getting ready to chroot -
• Chroot  Going inside your new system -
• System Configuration  Customizing your system for personal use -
• Kernel  Compiling your own kernel -
• Making your system bootable  Installing bootloader and boot scripts -
• Post-installation  Post-installation tasks -
- - - - - - diff --git a/docs/docs/carbslinux/Installing-packages.html b/docs/docs/carbslinux/Installing-packages.html deleted file mode 100644 index 3838155..0000000 --- a/docs/docs/carbslinux/Installing-packages.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - - -Installing packages (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-
-

1.2.3 Installing packages

- -

Since you are operating on a really small base, you might need to build and -install new programs to extend the functionality of your system. In order to -build and install packages new packages in Carbs, you need to execute the -following. "Package" is not actually a package and is given as an example. -

-
-
cpt-build   package
-cpt-install package
-
- - - - - - diff --git a/docs/docs/carbslinux/KISS-repositories.html b/docs/docs/carbslinux/KISS-repositories.html deleted file mode 100644 index 755007d..0000000 --- a/docs/docs/carbslinux/KISS-repositories.html +++ /dev/null @@ -1,66 +0,0 @@ - - - - - - -KISS repositories (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Up: Post-installation   [Contents]

-
-
-

1.6.1 KISS repositories

- -

While not 100% compatible with cpt, you can use kiss repositories in your -system the same way you are using the distribution repositories. Here is an -example for the KISS Linux Community repository. -

- - - - - diff --git a/docs/docs/carbslinux/Kernel-Command-Line.html b/docs/docs/carbslinux/Kernel-Command-Line.html deleted file mode 100644 index 2f73ec9..0000000 --- a/docs/docs/carbslinux/Kernel-Command-Line.html +++ /dev/null @@ -1,84 +0,0 @@ - - - - - - -Kernel Command Line (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Configuring Init   [Contents]

-
-
-

2.1.1 Kernel Command Line

- -

On GRUB, you can edit the kernel command line parameters, which will be parsed -as variables on the init system. Not all of the parameters will be acted upon, -but all of them will be set as variables on the init script. For example an -example command line, and how it is interpreted. -

-
-
BOOT_IMAGE=/boot/vmlinuz root=/dev/sda2 rw loglevel=3 quiet
-
- -

This command line will be parsed to set the following variables: -

-
-
BOOT_IMAGE=/boot/vmlinuz
-root=/dev/sda2
-rw=1
-loglevel=3
-quiet=1
-
- -

Some of these variables, such as ‘rw=/=ro’, ‘loglevel’, and ‘quiet’, will be -used by the init system to change the behaviour of the startup. -

- - - - - diff --git a/docs/docs/carbslinux/Kernel-dependencies.html b/docs/docs/carbslinux/Kernel-dependencies.html deleted file mode 100644 index f5ee8b0..0000000 --- a/docs/docs/carbslinux/Kernel-dependencies.html +++ /dev/null @@ -1,82 +0,0 @@ - - - - - - -Kernel dependencies (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Kernel   [Contents]

-
-
-

1.4.2 Kernel dependencies

- -

In order to compile the kernel you will need to install some dependencies. You -will need ‘libelf’, and ‘bison’ to compile the kernel. If you want to configure -using the menu interface you will also need ‘ncurses’. -

-
-
# The package manager asks to install if you are building more than one package,
-# so no need to run 'cpt i ...'
-cpt b libelf ncurses
-
- -

In the vanilla kernel sources, you need perl to compile the kernel, but it can -be easily patched out. You will need to apply the following patch. Patch was -written by E5ten. You will need to obtain and apply the patch in the kernel -source directory. -

-
-
wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch
-patch -p1 < kernel-no-perl.patch
-
- - - - - - diff --git a/docs/docs/carbslinux/Kernel.html b/docs/docs/carbslinux/Kernel.html deleted file mode 100644 index fe31cd7..0000000 --- a/docs/docs/carbslinux/Kernel.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - -Kernel (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Installation   [Contents]

-
-
-

1.4 Kernel

- -

Kernel isn’t managed under the main repositories, even though you could package -one for your personal use. Here is an example kernel package, which you will -need to reconfigure for your specific setup if you want to make use of it. -

- - - - -
• Obtaining the kernel sources  Downloading the Linux source code -
• Kernel dependencies  Requirements for building the kernel -
• Building the kernel  Configure and compile the kernel -
- - - - - - diff --git a/docs/docs/carbslinux/Making-your-system-bootable.html b/docs/docs/carbslinux/Making-your-system-bootable.html deleted file mode 100644 index 43c369d..0000000 --- a/docs/docs/carbslinux/Making-your-system-bootable.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - -Making your system bootable (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Installation   [Contents]

-
-
-

1.5 Making your system bootable

- -

In order to be able to boot your fresh system, wou will need an init-daemon, -init-scripts and a bootloader. The init daemon is already provided by busybox, -but you can optionally change it. -

- - - - -
• Bootloader  Install a bootloader for your system -
• Init scripts  Install init scripts for your system -
• Fstab  Generating fstab -
- - - - - - diff --git a/docs/docs/carbslinux/Obtain-the-chroot-helper.html b/docs/docs/carbslinux/Obtain-the-chroot-helper.html deleted file mode 100644 index 3a29294..0000000 --- a/docs/docs/carbslinux/Obtain-the-chroot-helper.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Obtain the chroot helper (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Preparing Environment   [Contents]

-
-
-

1.1.4 Obtain the chroot helper

- -

You can obtain the ‘cpt-chroot’ script in order to do a simple chroot into your -new root filesystem. -

-
-
wget https://dl.carbslinux.org/distfiles/cpt-chroot
-chmod a+x cpt-chroot
-
- - - - - - diff --git a/docs/docs/carbslinux/Obtaining-the-documentation.html b/docs/docs/carbslinux/Obtaining-the-documentation.html deleted file mode 100644 index c9ff1c8..0000000 --- a/docs/docs/carbslinux/Obtaining-the-documentation.html +++ /dev/null @@ -1,78 +0,0 @@ - - - - - - -Obtaining the documentation (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Chroot   [Contents]

-
-
-

1.2.5 Obtaining the documentation

- -

All the documentation for Carbs Linux can be found on a single info manual to be -viewed offline. You can obtain texinfo or the info (standalone) package in order -to view the documentation. -

-
-
# Install the documentation.
-cpt b carbs-docs && cpt i carbs-docs
-
-# Install either texinfo or the info package. We will be installing standalone info
-# as it doesn't need perl.
-cpt b info && cpt i info
-
-# You can then run info and navigate through the documentation.
-info carbslinux
-
- - - - - - diff --git a/docs/docs/carbslinux/Obtaining-the-kernel-sources.html b/docs/docs/carbslinux/Obtaining-the-kernel-sources.html deleted file mode 100644 index 34c92ed..0000000 --- a/docs/docs/carbslinux/Obtaining-the-kernel-sources.html +++ /dev/null @@ -1,75 +0,0 @@ - - - - - - -Obtaining the kernel sources (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Kernel   [Contents]

-
-
-

1.4.1 Obtaining the kernel sources

- -

You can visit the https://kernel.org website to choose a kernel that you want -to install. Though only the latest stable and longterm (LTS) versions are -supported. -

-
-
# Download the kernel and extract it
-wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz
-tar xf linux-5.9.1.tar.xz
-
-# Change directory into the kernel sources
-cd linux-5.9.1
-
- - - - - - diff --git a/docs/docs/carbslinux/Post_002dinstallation.html b/docs/docs/carbslinux/Post_002dinstallation.html deleted file mode 100644 index 9dcfed8..0000000 --- a/docs/docs/carbslinux/Post_002dinstallation.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Post-installation (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Installation   [Contents]

-
-
-

1.6 Post-installation

- -

The base installation is now complete, you can now fine tune your system -according to your needs. Rest of these instructions are completely optional. -You can check the rest of the documentation to learn more about the system. -

- - -
• KISS repositories  Acquire kiss repositories -
- - - - - - diff --git a/docs/docs/carbslinux/Preparing-Environment.html b/docs/docs/carbslinux/Preparing-Environment.html deleted file mode 100644 index a6c2ce8..0000000 --- a/docs/docs/carbslinux/Preparing-Environment.html +++ /dev/null @@ -1,89 +0,0 @@ - - - - - - -Preparing Environment (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Installation   [Contents]

-
-
-

1.1 Preparing Environment

- -

To install Carbs Linux, you will need a Live Linux ISO. For that purpose, you -can obtain a Gentoo or Void Linux live image. You can follow their instructions -to boot and setup your network. -

-

You will need the following programs in order to install Carbs Linux: -

-
    -
  • tar -
  • wget -
  • xz -
  • some form of base utilities (coreutils, sbase, busybox, etc.) -
- -

Rest of these instructions will assume that you have set all of these up, and -will continue on that point. -

- - - - - -
• Download  Download the root filesystem tarball -
• Signature verification  Verify the signature of the rootfs tarball -
• Extracting the tarball  Extracting the root filesystem to the desired location -
• Obtain the chroot helper  Download the script to easily chroot into the new filesystem -
- - - - - - diff --git a/docs/docs/carbslinux/Rebooting-after-changing-init.html b/docs/docs/carbslinux/Rebooting-after-changing-init.html deleted file mode 100644 index d586bbd..0000000 --- a/docs/docs/carbslinux/Rebooting-after-changing-init.html +++ /dev/null @@ -1,74 +0,0 @@ - - - - - - -Rebooting after changing init (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Up: Changing Init Program   [Contents]

-
-
-

2.2.1 Rebooting after changing init

- -

After switching init systems, your running init system may not accept the -new poweroff commands. You will need to reboot/poweroff using the running init’s -utilities for the new utilities to work. These commands are for the init system -currently running on your system and not the one you are switching to. -

- - - - - -
ProgramCommand
busybox‘busybox reboot’
runit‘runit-init 6’
shinit/sinit‘kill -s INT 1’
- - - - - - diff --git a/docs/docs/carbslinux/Repository-Conventions.html b/docs/docs/carbslinux/Repository-Conventions.html deleted file mode 100644 index 79b7eec..0000000 --- a/docs/docs/carbslinux/Repository-Conventions.html +++ /dev/null @@ -1,220 +0,0 @@ - - - - - - -Repository Conventions (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Previous: , Up: Conventions   [Contents]

-
-
-

3.1.2 Repository Conventions

- -

Repository conventions are important in order to ensure every package resemble -themselves. Here are the things to keep in mind: -

-
-
[2010]
-

Prefer tarballs over git packages unless there is a -sensible reason. Here are some: -

    -
  • Every patch is a new release. (See vim) -
  • There are no releases. (See sbase) -
  • Following a development branch. -
  • There has been a long time since the latest release, but upstream is far -ahead. -
-
-
[2020]
-

Prefer sources without a dependency to ‘automake’. There -are usually distribution tarballs that are ‘autoconf’’ed. Don’t submit tarballs -with an automake dependency unless you are ‘sure’ there is no alternative. -

-
[2030]
-

Avoid these packages: -

-
dbus
-

Usually can be disabled by --disable-dbus. -

-
gettext
-

Usually can be disabled by --disable-nls. -

-
-
-
[2040]
-
    -
  • Always install a package to the ‘/usr’ prefix. -
  • All binaries should go to ‘/usr/bin’, not ‘/usr/sbin’ or any other directory. -
  • All libraries should go to ‘/usr/lib’. -
-
-
[2050]
-

All build files on the repository should be a POSIX -shell script, and must start with #!/bin/sh -e. -

-
- -

The next section is about package templates that should be used in order to -ensure stylistic consistency. Note that the option configurations shouldn’t be -taken literally, they are meant as examples. -

-
    -
  1. Make [2210] - - -
    -
    #!/bin/sh -e
-
-make
-make DESTDIR="$1" PREFIX=/usr install
-
    - -
  2. Configure/Make [2211] - - -
    -
    #!/bin/sh -e
-
-./configure \
-    --prefix=/usr \
-    --disable-option \
-    --enable-option
-
-make
-make DESTDIR="$1" install
-
    - -
  3. Autoconf/Automake [2212] - - -

    See 2020 -

    -
    -
    #!/bin/sh -e
-
-autoreconf -fi
-
-./configure \
-    --prefix=/usr \
-    --disable-option \
-    --enable-option
-
-make
-make DESTDIR="$1" install
-
    - -
  4. Meson [2220] - - -
    -
    #!/bin/sh -e
-
-export DESTDIR=$1
-
-meson \
-    --prefix=/usr \
-    -Doption=false \
-    -Doption2=true \
-    . output
-
-ninja -C output
-ninja -C output install
-
    - -
  5. Cmake [2230] - - -
    -
    #!/bin/sh -e
-
-export DESTDIR=$1
-
-cmake -B build \
-    -DCMAKE_INSTALL_PREFIX=/usr \
-    -DCMAKE_BUILD_TYPE=Release \
-    -DOPTION=ON
-
-cmake --build   build
-cmake --install build
-
    - -
  6. Go [2240] - - -
    -
    #!/bin/sh -e
-
-export GOPATH=$PWD/gopath
-trap "go clean -modcache" EXIT INT
-go mod vendor
-
-go build
-install -Dm755 program "$1/usr/bin/program"
-
    - -
  7. Python [2241] - - -
    -
    #!/bin/sh -e
-
-python setup.py build
-python setup.py install --prefix=/usr --root="$1"
-
    -
- -
-
-

-Previous: , Up: Conventions   [Contents]

-
- - - - - diff --git a/docs/docs/carbslinux/Setting-up-repositories.html b/docs/docs/carbslinux/Setting-up-repositories.html deleted file mode 100644 index 1c7310e..0000000 --- a/docs/docs/carbslinux/Setting-up-repositories.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - -Setting up repositories (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Chroot   [Contents]

-
-
-

1.2.1 Setting up repositories

- -

Newest tarballs do not come with repositories, so you will need to manually -obtain them, and set your ‘CPT_PATH’ environment variable. Carbs Linux -repositories can either be obtained by ‘git’ or ‘rsync’. While rsync -repositories are overall faster and smaller, git offers the whole history of the -repository and a means to manipulate your repository as you like it. If you want -to obtain the git repository, you will need to install ‘git’ itself. -

-

The following guide will assume that you put the repositories into ‘~/repos/’ -directory, but you can put the repositories into any directory you want. So go -ahead and create that directory: -

-
-
mkdir -p $HOME/repos
-
- -
    -
  1. Obtaining from git - - -

    Carbs Linux git repositories can be found both from the main server and GitHub -(mirror). Here are both their repository links. You can clone any of them. -

    - - -
    -
    git clone git://git.carbslinux.org/repository $HOME/repos/carbs
-
    - -
  2. Obtaining from rsync - - -

    Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In -order to obtain it, run the following: -

    -
    -
    rsync -avc rsync://carbslinux.org/repo $HOME/repos/carbs
-
    - -
  3. Making the package manager use the repositories - - -

    In your shell’s configuration file, or in your ‘~/.profile’ file, add the -following lines: -

    -
    -
    CPT_PATH=$HOME/repos/carbs/core
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/extra
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/xorg
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/community
-export CPT_PATH
-
    -
- - - - - - diff --git a/docs/docs/carbslinux/Shell-Conventions.html b/docs/docs/carbslinux/Shell-Conventions.html deleted file mode 100644 index 5902238..0000000 --- a/docs/docs/carbslinux/Shell-Conventions.html +++ /dev/null @@ -1,105 +0,0 @@ - - - - - - -Shell Conventions (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Up: Conventions   [Contents]

-
-
-

3.1.1 Shell Conventions

- -

Shell is central to Carbs Linux projects. Most of the tools and packages are -written in POSIX sh. -

-
-
[1010]
-

Use 4 spaces for indentation, don’t use tabs. -

-
[1020]
-

Make sure you don’t use bash-specific code. -

-
[1030]
-

Make sure you lint your code with ‘shellcheck’ and if -you are new to POSIX sh, use ‘checkbashisms’. -

-
[1040]
-

Don’t spawn new processes if you don’t absolutely need -to, especially during string manipulation. -

-
[1041]
-

Never use a program for text manupilation that isn’t -defined in the POSIX standard. This includes ‘gawk’ and ‘perl’. -

-
[1042]
-

Instead of $(basename $file), use ${file##*}. -

-
[1043]
-

Instead of $(dirname $file), use ${file%/*}. -

-
- -
-
# This is the same thing as basename /path/to/test.asc .asc
-
-$ file=/path/to/test.asc file=${file##*/} file=${file%.asc}
-$ echo $file
-test
-
-
-
[1050]
-

Instead of backticks, use $(..). -

-
- - - - - - diff --git a/docs/docs/carbslinux/Signature-verification.html b/docs/docs/carbslinux/Signature-verification.html deleted file mode 100644 index 9eb486d..0000000 --- a/docs/docs/carbslinux/Signature-verification.html +++ /dev/null @@ -1,71 +0,0 @@ - - - - - - -Signature verification (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Preparing Environment   [Contents]

-
-
-

1.1.2 Signature verification

- -

It is highly recommended to verify the signature of the tarball. You will need -GPG for this. -

-
-
wget $URL/carbs-rootfs.tar.xz.sig
-gpg --recv-keys FF484BDFEFCEF8FF
-gpg --verify carbs-rootfs.tar.xz.sig
-
- - - - - - diff --git a/docs/docs/carbslinux/System-Configuration.html b/docs/docs/carbslinux/System-Configuration.html deleted file mode 100644 index aed313d..0000000 --- a/docs/docs/carbslinux/System-Configuration.html +++ /dev/null @@ -1,72 +0,0 @@ - - - - - - -System Configuration (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Installation   [Contents]

-
-
-

1.3 System Configuration

- -

After you have finished installing some extra packages, you can configure your -system to your liking. -

- - - -
• Configuring hostname  Setting up system hostname (recommended) -
• Hosts file  Setting up hosts file for networking (optional) -
- - - - - - diff --git a/docs/docs/carbslinux/Updating-packages.html b/docs/docs/carbslinux/Updating-packages.html deleted file mode 100644 index 47e186c..0000000 --- a/docs/docs/carbslinux/Updating-packages.html +++ /dev/null @@ -1,70 +0,0 @@ - - - - - - -Updating packages (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Chroot   [Contents]

-
-
-

1.2.2 Updating packages

- -

It is good practice to make sure your system is up to date, especially before -building new packages. If there is an update for the package manager you will -need to update twice. -

-
-
cpt-update && cpt-update
-
- - - - - - diff --git a/docs/docs/carbslinux/_002fetc_002finit_002frcconf-file.html b/docs/docs/carbslinux/_002fetc_002finit_002frcconf-file.html deleted file mode 100644 index 1a34d8f..0000000 --- a/docs/docs/carbslinux/_002fetc_002finit_002frcconf-file.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - -/etc/init/rcconf file (Carbs Linux User Manual) - - - - - - - - - - - - - - - - - - -
-

-Next: , Previous: , Up: Configuring Init   [Contents]

-
-
-

2.1.2 ‘/etc/init/rc.conf’ file

- -

However, the kernel command line isn’t the only place to set your boot -parameters. You can specify variables here as well, although note that the -kernel command line always gets the priority for these variables since they can -be set just before boot. -

- - - - - diff --git a/docs/docs/carbslinux/index.html b/docs/docs/carbslinux/index.html deleted file mode 100644 index 2a4bbbe..0000000 --- a/docs/docs/carbslinux/index.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - - -Top (Carbs Linux User Manual) - - - - - - - - - - - - - - - - -

Carbs Linux User Manual

- - - - - -

Table of Contents

- -
- - -
- - -
-

-Next:   [Contents]

-
-
-

Carbs Linux User Manual

- -

This is the full documentation of Carbs Linux, from the details of the -distribution, installation, to the package manager. It is not yet complete. -

- -

This documentation is also available in the distribution by the -carbs-docs package, which can be read by either running -info carbslinux or reading /usr/share/doc/carbslinux.txt with your -favorite pager. You can install either the info or texinfo -for doing the first. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
• Installation  Installing Carbs Linux -
• Init System  Configure the init system -
• Contribution Guidelines  Contribute to Carbs Linux -
• GNU Free Documentation License  Your rights -
-
-
— The Detailed Node Listing —
-
-Installation
-
-
• Preparing Environment  Getting ready to chroot -
• Chroot  Going inside your new system -
• System Configuration  Customizing your system for personal use -
• Kernel  Compiling your own kernel -
• Making your system bootable  Installing bootloader and boot scripts -
• Post-installation  Post-installation tasks -
-
-Preparing Environment
-
-
• Download  Download the root filesystem tarball -
• Signature verification  Verify the signature of the rootfs tarball -
• Extracting the tarball  Extracting the root filesystem to the desired location -
• Obtain the chroot helper  Download the script to easily chroot into the new filesystem -
-
-Chroot
-
-
• Setting up repositories  Basic setup for obtaining repositories -
• Updating packages  Update your system -
• Installing packages  Install new software on your system -
• Essential Software  Software you might want to include on your system -
• Obtaining the documentation  Install documentation for offline use (optional) -
-
-System Configuration
-
-
• Configuring hostname  Setting up system hostname (recommended) -
• Hosts file  Setting up hosts file for networking (optional) -
-
-Kernel
-
-
• Obtaining the kernel sources  Downloading the Linux source code -
• Kernel dependencies  Requirements for building the kernel -
• Building the kernel  Configure and compile the kernel -
-
-Making your system bootable
-
-
• Bootloader  Install a bootloader for your system -
• Init scripts  Install init scripts for your system -
• Fstab  Generating fstab -
-
-Post-installation
-
-
• KISS repositories  Acquire kiss repositories -
-
-Init System
-
-
• Configuring Init  Ways to configure the init system -
• Changing Init Program  Replace the default busybox init with something new -
-
-Configuring Init
-
-
• Kernel Command Line  Configure init through the boot parameters -
• ‘/etc/init/rc.conf’ file  Configure init through the configuration file -
• Init Hooks  Configure init through hooks -
-
-Changing Init Program
-
-
• Rebooting after changing init  Ways to reboot after replacing the init system -
-
-Contribution Guidelines
-
-
• Conventions  Conventions of the distribution -
-
-Conventions
-
-
• Shell Conventions  Conventions for shell scripts -
• Repository Conventions  Conventions for repository build scripts -
-
-
- -
-
-

-Next:   [Contents]

-
- - - - - diff --git a/docs/download.html b/docs/download.html deleted file mode 100644 index cc0896e..0000000 --- a/docs/download.html +++ /dev/null @@ -1,65 +0,0 @@ - - - - - - -Download Carbs Linux - - - - - - -
- -
-
-
-

Download Carbs Linux

-

-Below are the latest tarballs for the x86_64 and i686 architectures. You can -visit https://dl.carbslinux.org/releases for all downloads. Follow the -Installation guide to learn more about verifying the releases, and the required -steps for installing the system. -

- -
-

x86-64

-
-

-carbs-rootfs.tar.xz | SHA256SUM | Signature -

-
-
- - -
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/download.txt b/docs/download.txt deleted file mode 100644 index 8364fdd..0000000 --- a/docs/download.txt +++ /dev/null @@ -1,46 +0,0 @@ - ______________________ - - DOWNLOAD CARBS LINUX - ______________________ - - -Below are the latest tarballs for the `x86_64' and `i686' -architectures. You can visit for -all downloads. Follow the [Installation guide] to learn more about -verifying the releases, and the required steps for installing the -system. - - -[Installation guide] - - -x86-64 -====== - - [carbs-rootfs.tar.xz] | [SHA256SUM] | [Signature] - - -[carbs-rootfs.tar.xz] - - -[SHA256SUM] - - -[Signature] - - - -i686 -==== - - [carbs-rootfs.tar.xz] | [SHA256SUM] | [Signature] - - -[carbs-rootfs.tar.xz] - - -[SHA256SUM] - - -[Signature] - diff --git a/docs/index.html b/docs/index.html deleted file mode 100644 index 74d704d..0000000 --- a/docs/index.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - - -Carbs Linux - - - - - - - -
- -
-
-

-Carbs Linux is a source-based Linux® distribution that aims to be simple, -flexible and extensible while staying as pragmatic and practical as possible. -The system can consist of as much or as little as its user can intend to. -

- -
-

Package Manager

-
-

-Carbs Linux uses its own package manager Carbs Packaging Tools, a POSIX shell -package manager forked from KISS with the tool-based approach of xbps. -

-
-
- - -
-

Small base

-
-

-By default, Carbs Linux comes with busybox for coreutils, bearssl for its -crypto library, musl libc, and other basic utilities that are required for -building new software. The majority of the base packages are statically linked. -

-
-
- - -
-

Multiple Init Support

-
-

-Carbs Linux has support for multiple init systems and service supervisors. In -the main repository are -

- -
    -
  • sinit
    • -
  • busybox-init (SysVinit clone)
    • -
  • runit-init
    • -
- -

-for init systems, and -

- -
    -
  • sysmgr
    • -
  • busybox-runit
    • -
  • runit
    • -
- -

-for service supervisors. The carbs-init package is the collection of init -scripts that ensure the interoperability of these init and service systems, and -make it easier for the user to switch to their preferred combinations of system -supervision. -

- -

-Nothing holds you back, however, from ditching any of these and packaging some -other system supervision technique along with your own init scripts. -

-
-
- - -
-

Links

-
- -
-
- -
-

News

-
-

-RSS Feed | See all news -

-
- -
-

Sep 16, 2020

-
-

-The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -

-
-
-
-

Sep 03, 2020

-
-

-The default TLS provider has been reverted to libressl. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -

-
-
-
-

Jul 27, 2020

-
-

-Carbs Linux's fork of the kiss package manager has been renamed to Carbs - Packaging Tools due to huge amount of changes. Your latest kiss update will -handle the bootstrapping. You will need to rename your KISS-* variables to -CPT-*. -

-
-
-
-

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. -

-
-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/index.txt b/docs/index.txt deleted file mode 100644 index 50c04b2..0000000 --- a/docs/index.txt +++ /dev/null @@ -1,133 +0,0 @@ -Carbs Linux is a source-based Linux(r) distribution that aims to be -simple, flexible and extensible while staying as pragmatic and practical -as possible. The system can consist of as much or as little as its user -can intend to. - - -Package Manager -=============== - - Carbs Linux uses its own package manager [Carbs Packaging Tools], a - POSIX shell package manager forked from KISS with the tool-based - approach of xbps. - - -[Carbs Packaging Tools] - - -Small base -========== - - By default, Carbs Linux comes with busybox for coreutils, bearssl for - its crypto library, musl libc, and other basic utilities that are - required for building new software. The majority of the base packages - are statically linked. - - -Multiple Init Support -===================== - - Carbs Linux has support for multiple init systems and service - supervisors. In the main repository are - - - `sinit' - - `busybox-init' (SysVinit clone) - - `runit-init' - - for init systems, and - - - `sysmgr' - - `busybox-runit' - - `runit' - - for service supervisors. The [carbs-init] package is the collection of - init scripts that ensure the interoperability of these init and - service systems, and make it easier for the user to switch to their - preferred combinations of system supervision. - - Nothing holds you back, however, from ditching any of these and - packaging some other system supervision technique along with your own - init scripts. - - -[carbs-init] - - - -Links -===== - - - IRC - `#carbslinux' on freenode - - Reddit - [r/carbslinux] - - [Mailing Lists] - - -[r/carbslinux] - -[Mailing Lists] - - -News -==== - - [RSS Feed] | [See all news] - - -[RSS Feed] - -[See all news] - -[Sep 16, 2020] -~~~~~~~~~~~~~~ - - The libressl "revert" was reverted. System update will replace - libressl dependencies with bearssl. You may choose to keep or remove - bearssl after the update. - - -[Sep 16, 2020] - - -[Sep 03, 2020] -~~~~~~~~~~~~~~ - - The default TLS provider has been reverted to `libressl'. System - update will replace bearssl dependencies with libressl. You may choose - to keep or remove bearssl after the update. - - -[Sep 03, 2020] - - -[Jul 27, 2020] -~~~~~~~~~~~~~~ - - Carbs Linux's fork of the `kiss' package manager has been renamed to - `Carbs Packaging Tools' due to huge amount of changes. Your latest - `kiss' update will handle the bootstrapping. You will need to rename - your `KISS-*' variables to `CPT-*'. - - -[Jul 27, 2020] - - -[Jun 17, 2020] -~~~~~~~~~~~~~~ - - A new rootfs tarball including the changes to the core is released and - can be found on the downloads page. - - -[Jun 17, 2020] - - -[May 26, 2020] -~~~~~~~~~~~~~~ - - An initial version for binary package management is released. It can - be found on the [GitHub page]. - - -[May 26, 2020] - -[GitHub page] diff --git a/docs/install.html b/docs/install.html deleted file mode 100644 index 9f9f2fc..0000000 --- a/docs/install.html +++ /dev/null @@ -1,663 +0,0 @@ - - - - - - -Installation Guide - - - - - - -
- -
-
-
-

Installation Guide

-

-These are the step-by-step instructions for installing Carbs Linux. It can be -acquired as plain-text to be viewed offline with a pager from -https://carbslinux.org/install.txt. -

- -
-
curl -sL https://carbslinux.org/install.txt | less
-
-
- -
- -
-
-

1 Preparing Environment

-
-

-To install Carbs Linux, you will need a Live Linux ISO. For that purpose, you -can obtain a Gentoo or Void Linux live image. You can follow their instructions -to boot and setup your network. -

- -

-You will need the following programs in order to install Carbs Linux: -

- -
    -
  • tar
    • -
  • wget
    • -
  • xz
    • -
  • some form of base utilities (coreutils, sbase, busybox, etc.)
    • -
- -

-Rest of these instructions will assume that you have set all of these up, and -will continue on that point. -

-
- -
-

1.1 Download

-
-

-First, we need to download the rootfs tarball. You can do the following in order -to obtain the rootfs. If you are using an i686 machine, replace the x86_64 -with i686. We are setting this in a URL variable so that we don't have to -write it every time. -

- -
-
wget $URL/carbs-rootfs.tar.xz.sha256
-sha256sum -c carbs-rootfs.tar.xz.sha256
-
-
-
-
- -
-

1.2 Signature verification

-
-

-It is highly recommended to verify the signature of the tarball. You will need -GPG for this. -

- -
-
wget $URL/carbs-rootfs.tar.xz.sig
-gpg --recv-keys FF484BDFEFCEF8FF
-gpg --verify carbs-rootfs.tar.xz.sig
-
-
-
-
- -
-

1.3 Extracting the tarball

-
-

-You will need to extract the tarball to your desired location. For partitioning, -you can follow this guide. This will assume that you will be mounting your root -partition to /mnt. -

- -
-
mount /dev/sdx1 /mnt
-tar xf carbs-rootfs.tar.xz -C /mnt
-
-
-
-
- -
-

1.4 Obtain the chroot helper

-
-

-You can obtain the cpt-chroot script in order to do a simple chroot into your -new root filesystem. -

- -
-
wget https://dl.carbslinux.org/distfiles/cpt-chroot
-chmod a+x cpt-chroot
-
-
-
-
-
- -
-

2 Chroot

-
-

-Chroot into Carbs Linux! -

- -
-
./cpt-chroot /mnt
-
-
-
- -
-

2.1 Setting up repositories

-
-

-Newest tarballs do not come with repositories, so you will need to manually -obtain them, and set your CPT_PATH environment variable. Carbs Linux -repositories can either be obtained by git or rsync. While rsync -repositories are overall faster and smaller, git offers the whole history of the -repository and a means to manipulate your repository as you like it. If you want -to obtain the git repository, you will need to install git itself. -

- -

-The following guide will assume that you put the repositories into ~/repos/ -directory, but you can put the repositories into any directory you want. So go -ahead and create that directory: -

- -
-
mkdir -p $HOME/repos
-
-
-
- -
-

2.1.1 Obtaining from git

-
-

-Carbs Linux git repositories can be found both from the main server and GitHub -(mirror). Here are both their repository links. You can clone any of them. -

- - - -
-
git clone git://git.carbslinux.org/repository $HOME/repos/carbs
-
-
-
-
- -
-

2.1.2 Obtaining from rsync

-
-

-Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In -order to obtain it, run the following: -

- -
-
rsync -avc rsync://carbslinux.org/repo $HOME/repos/carbs
-
-
-
-
- -
-

2.1.3 Making the package manager use the repositories

-
-

-In your shell's configuration file, or in your ~/.profile file, add the -following lines: -

- -
-
CPT_PATH=$HOME/repos/carbs/core
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/extra
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/xorg
-CPT_PATH=$CPT_PATH:$HOME/repos/carbs/community
-export CPT_PATH
-
-
-
-
-
- -
-

2.2 Updating packages

-
-

-It is good practice to make sure your system is up to date, especially before -building new packages. If there is an update for the package manager you will -need to update twice. -

- -
-
cpt-update && cpt-update
-
-
-
-
- -
-

2.3 Installing packages

-
-

-Since you are operating on a really small base, you might need to build and -install new programs to extend the functionality of your system. In order to -build and install packages new packages in Carbs, you need to execute the -following. "Package" is not actually a package and is given as an example. -

- -
-
cpt-build   package
-cpt-install package
-
-
-
-
- -
-

2.4 Essential Software

-
-

-Here is a list of software that you might want to have on your system. -

- -

-BOOTLOADERS -

- -
    -
  • efibootmgr
    • -
  • grub
    • -
- -

-FILESYSTEMS -

- -
    -
  • e2fsprogs
    • -
  • dosfstools
    • -
  • ntfs-3g
    • -
- -

-NETWORKING -

- -
    -
  • dhcpcd
    • -
  • wpasupplicant
    • -
- -

-TEXT EDITORS -

- -
    -
  • nano
    • -
  • vim
    • -
  • neatvi
    • -
  • emacs
    • -
  • emacs-nox (terminal-only version of emacs)
    • -
- -

-USER SHELLS -

- -
    -
  • bash
    • -
  • zsh
    • -
  • oksh
    • -
  • rc
    • -
- -

-POSIX BASE UTILITIES -

- -
    -
  • busybox
    • -
  • sbase
    • -
  • coreutils
    • -
- -

-DOCUMENTATION -

- -
    -
  • carbs-docs
    • -
  • man-pages
    • -
  • man-pages-posix
    • -
-
-
- -
-

2.5 Obtaining the documentation

-
-

-All the documentation for Carbs Linux can be found on a single info manual to be -viewed offline. You can obtain texinfo or the info (standalone) package in order -to view the documentation. -

- -
-
# Install the documentation.
-cpt b carbs-docs && cpt i carbs-docs
-
-# Install either texinfo or the info package. We will be installing standalone info
-# as it doesn't need perl.
-cpt b info && cpt i info
-
-# You can then run info and navigate through the documentation.
-info carbslinux
-
-
-
-
-
- -
-

3 System Configuration

-
-

-After you have finished installing some extra packages, you can configure your -system to your liking. -

-
- -
-

3.1 Configuring hostname

-
-

-You might want to add a hostname, especially in a networked environment. Your -hostname will default to 'carbslinux' unless you set this. -

- -
-
echo your-hostname > /etc/hostname
-
-
-
-
- -
-

3.2 Hosts file

-
-

-You can edit your /etc/hosts file, which is the static lookup table for host -names. By default, there are two entries for localhost which are OKAY. You can -replace the 'localhost' part of these entries to your hostname. -

- -
-127.0.0.1  localhost.localdomain localhost
-::1        localhost.localdomain localhost ip6-localhost
-
-
-
-
- -
-

4 Kernel

-
-

-Kernel isn't managed under the main repositories, even though you could package -one for your personal use. Here is an example kernel package, which you will -need to reconfigure for your specific setup if you want to make use of it. -

-
- -
-

4.1 Obtaining the kernel sources

-
-

-You can visit the https://kernel.org website to choose a kernel that you want -to install. Though only the latest stable and longterm (LTS) versions are -supported. -

- -
-
# Download the kernel and extract it
-wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz
-tar xf linux-5.9.1.tar.xz
-
-# Change directory into the kernel sources
-cd linux-5.9.1
-
-
-
-
- -
-

4.2 Kernel dependencies

-
-

-In order to compile the kernel you will need to install some dependencies. You -will need libelf, and bison to compile the kernel. If you want to configure -using the menu interface you will also need ncurses. -

- -
-
# The package manager asks to install if you are building more than one package,
-# so no need to run 'cpt i ...'
-cpt b libelf ncurses
-
-
- -

-In the vanilla kernel sources, you need perl to compile the kernel, but it can -be easily patched out. You will need to apply the following patch. Patch was -written by E5ten. You will need to obtain and apply the patch in the kernel -source directory. -

- -
-
wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch
-patch -p1 < kernel-no-perl.patch
-
-
-
-
- -
-

4.3 Building the kernel

-
-

-Next step is configuring and building the kernel. You can check Gentoo's -kernel configuration guide to learn more about the matter. Overall, Gentoo Wiki -is a good place to learn about configuration according to your hardware. The -following will assume a monolithic kernel. -

- -
-
make menuconfig
-make
-install -Dm755 $(make -s image_name) /boot/vmlinuz-linux
-
-
-
-
-
- -
-

5 Making your system bootable

-
-

-In order to be able to boot your fresh system, wou will need an init-daemon, -init-scripts and a bootloader. The init daemon is already provided by busybox, -but you can optionally change it. -

-
- -
-

5.1 Bootloader

-
-

-In the main repository, there is efibootmgr and grub to serve as bootloaders. -efibootmgr can be used as a standalone bootloader, or can be used to install -grub in a UEFI environment. efibootmgr is needed unless you are using a device -without UEFI support (or you really want to use BIOS for a reason). -

-
- -
-

5.1.1 GRUB BIOS installation

-
-
-
cpt b grub && cpt i grub
-grub-install --target=i386-pc /dev/sdX
-grub-mkconfig -o /boot/grub/grub.cfg
-
-
-
-
- -
-

5.1.2 GRUB UEFI installation

-
-
-
cpt b efibootmgr && cpt i efibootmgr
-cpt b grub && cpt i grub
-
-grub-install --target=x86_64-efi \
-             --efi-directory=esp \
-             --bootloader-id=CarbsLinux
-
-grub-mkconfig -o /boot/grub/grub.cfg
-
-
-
-
-
- -
-

5.2 Init scripts

-
-

-Only thing left to do is installing the init-scripts, and now you are almost -ready to boot your system! -

- -
-
cpt b carbs-init && cpt i carbs-init
-
-
-
-
- -
-

5.3 Fstab

-
-

-You can now manually edit your fstab entry, or you can use the genfstab tool. -If you want to use the tool, exit the chroot and run the following: -

- -
-
wget https://github.com/cemkeylan/genfstab/raw/master/genfstab
-chmod +x genfstab
-./genfstab -U /mnt >> /mnt/etc/fstab
-
-
-
-
-
- -
-

6 Post-installation

-
-

-The base installation is now complete, you can now fine tune your system -according to your needs. Rest of these instructions are completely optional. -You can check the rest of the documentation to learn more about the system. -

-
- -
-

6.1 KISS repositories

-
-

-While not 100% compatible with cpt, you can use kiss repositories in your -system the same way you are using the distribution repositories. Here is an -example for the KISS Linux Community repository. -

-
-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/install.txt b/docs/install.txt deleted file mode 100644 index ba1899c..0000000 --- a/docs/install.txt +++ /dev/null @@ -1,479 +0,0 @@ - ____________________ - - INSTALLATION GUIDE - ____________________ - - -These are the step-by-step instructions for installing Carbs Linux. It -can be acquired as plain-text to be viewed offline with a pager from -. - -,---- -| curl -sL https://carbslinux.org/install.txt | less -`---- - -1. Preparing Environment -.. 1. Download -.. 2. Signature verification -.. 3. Extracting the tarball -.. 4. Obtain the chroot helper -2. Chroot -.. 1. Setting up repositories -..... 1. Obtaining from git -..... 2. Obtaining from rsync -..... 3. Making the package manager use the repositories -.. 2. Updating packages -.. 3. Installing packages -.. 4. Essential Software -.. 5. Obtaining the documentation -3. System Configuration -.. 1. Configuring hostname -.. 2. Hosts file -4. Kernel -.. 1. Obtaining the kernel sources -.. 2. Kernel dependencies -.. 3. Building the kernel -5. Making your system bootable -.. 1. Bootloader -..... 1. GRUB BIOS installation -..... 2. GRUB UEFI installation -.. 2. Init scripts -.. 3. Fstab -6. Post-installation -.. 1. KISS repositories - - -1 Preparing Environment -======================= - - To install Carbs Linux, you will need a Live Linux ISO. For that - purpose, you can obtain a Gentoo or Void Linux live image. You can - follow their instructions to boot and setup your network. - - You will need the following programs in order to install Carbs Linux: - - - tar - - wget - - xz - - some form of base utilities (coreutils, sbase, busybox, etc.) - - Rest of these instructions will assume that you have set all of these - up, and will continue on that point. - - -1.1 Download -~~~~~~~~~~~~ - - First, we need to download the rootfs tarball. You can do the - following in order to obtain the rootfs. If you are using an i686 - machine, replace the `x86_64' with `i686'. We are setting this in a - URL variable so that we don't have to write it every time. - - ,---- - | wget $URL/carbs-rootfs.tar.xz.sha256 - | sha256sum -c carbs-rootfs.tar.xz.sha256 - `---- - - -1.2 Signature verification -~~~~~~~~~~~~~~~~~~~~~~~~~~ - - It is highly recommended to verify the signature of the tarball. You - will need GPG for this. - - ,---- - | wget $URL/carbs-rootfs.tar.xz.sig - | gpg --recv-keys FF484BDFEFCEF8FF - | gpg --verify carbs-rootfs.tar.xz.sig - `---- - - -1.3 Extracting the tarball -~~~~~~~~~~~~~~~~~~~~~~~~~~ - - You will need to extract the tarball to your desired location. For - partitioning, you can follow [this guide]. This will assume that you - will be mounting your root partition to `/mnt'. - - ,---- - | mount /dev/sdx1 /mnt - | tar xf carbs-rootfs.tar.xz -C /mnt - `---- - - -[this guide] - - -1.4 Obtain the chroot helper -~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - You can obtain the `cpt-chroot' script in order to do a simple chroot - into your new root filesystem. - - ,---- - | wget https://dl.carbslinux.org/distfiles/cpt-chroot - | chmod a+x cpt-chroot - `---- - - -2 Chroot -======== - - Chroot into Carbs Linux! - - ,---- - | ./cpt-chroot /mnt - `---- - - -2.1 Setting up repositories -~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - Newest tarballs do not come with repositories, so you will need to - manually obtain them, and set your `CPT_PATH' environment - variable. Carbs Linux repositories can either be obtained by `git' or - `rsync'. While rsync repositories are overall faster and smaller, git - offers the whole history of the repository and a means to manipulate - your repository as you like it. If you want to obtain the git - repository, you will need to install `git' itself. - - The following guide will assume that you put the repositories into - `~/repos/' directory, but you can put the repositories into any - directory you want. So go ahead and create that directory: - - ,---- - | mkdir -p $HOME/repos - `---- - - -2.1.1 Obtaining from git ------------------------- - - Carbs Linux git repositories can be found both from the main server - and GitHub (mirror). Here are both their repository links. You can - clone any of them. - - - git://git.carbslinux.org/repository - - - - ,---- - | git clone git://git.carbslinux.org/repository $HOME/repos/carbs - `---- - - -2.1.2 Obtaining from rsync --------------------------- - - Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In - order to obtain it, run the following: - - ,---- - | rsync -avc rsync://carbslinux.org/repo $HOME/repos/carbs - `---- - - -2.1.3 Making the package manager use the repositories ------------------------------------------------------ - - In your shell's configuration file, or in your `~/.profile' file, add - the following lines: - - ,---- - | CPT_PATH=$HOME/repos/carbs/core - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/extra - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/xorg - | CPT_PATH=$CPT_PATH:$HOME/repos/carbs/community - | export CPT_PATH - `---- - - -2.2 Updating packages -~~~~~~~~~~~~~~~~~~~~~ - - It is good practice to make sure your system is up to date, especially - before building new packages. If there is an update for the package - manager you will need to update twice. - - ,---- - | cpt-update && cpt-update - `---- - - -2.3 Installing packages -~~~~~~~~~~~~~~~~~~~~~~~ - - Since you are operating on a really small base, you might need to - build and install new programs to extend the functionality of your - system. In order to build and install packages new packages in Carbs, - you need to execute the following. "Package" is not actually a package - and is given as an example. - - ,---- - | cpt-build package - | cpt-install package - `---- - - -2.4 Essential Software -~~~~~~~~~~~~~~~~~~~~~~ - - Here is a list of software that you might want to have on your system. - - *BOOTLOADERS* - - - efibootmgr - - grub - - *FILESYSTEMS* - - - e2fsprogs - - dosfstools - - ntfs-3g - - *NETWORKING* - - - dhcpcd - - wpa_supplicant - - *TEXT EDITORS* - - - nano - - vim - - neatvi - - emacs - - emacs-nox (terminal-only version of emacs) - - *USER SHELLS* - - - bash - - zsh - - oksh - - rc - - *POSIX BASE UTILITIES* - - - busybox - - sbase - - coreutils - - *DOCUMENTATION* - - - carbs-docs - - man-pages - - man-pages-posix - - -2.5 Obtaining the documentation -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - All the documentation for Carbs Linux can be found on a single info - manual to be viewed offline. You can obtain texinfo or the info - (standalone) package in order to view the documentation. - - ,---- - | # Install the documentation. - | cpt b carbs-docs && cpt i carbs-docs - | - | # Install either texinfo or the info package. We will be installing standalone info - | # as it doesn't need perl. - | cpt b info && cpt i info - | - | # You can then run info and navigate through the documentation. - | info carbslinux - `---- - - -3 System Configuration -====================== - - After you have finished installing some extra packages, you can - configure your system to your liking. - - -3.1 Configuring hostname -~~~~~~~~~~~~~~~~~~~~~~~~ - - You might want to add a hostname, especially in a networked - environment. Your hostname will default to 'carbslinux' unless you set - this. - - ,---- - | echo your-hostname > /etc/hostname - `---- - - -3.2 Hosts file -~~~~~~~~~~~~~~ - - You can edit your /etc/hosts file, which is the static lookup table - for host names. By default, there are two entries for localhost which - are OKAY. You can replace the 'localhost' part of these entries to - your hostname. - - ,---- - | 127.0.0.1 localhost.localdomain localhost - | ::1 localhost.localdomain localhost ip6-localhost - `---- - - -4 Kernel -======== - - Kernel isn't managed under the main repositories, even though you - could package one for your personal use. Here is an [example kernel - package], which you will need to reconfigure for your specific setup - if you want to make use of it. - - -[example kernel package] - - -4.1 Obtaining the kernel sources -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - - You can visit the website to choose a kernel that - you want to install. Though only the latest stable and longterm (LTS) - versions are supported. - - ,---- - | # Download the kernel and extract it - | wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz - | tar xf linux-5.9.1.tar.xz - | - | # Change directory into the kernel sources - | cd linux-5.9.1 - `---- - - -4.2 Kernel dependencies -~~~~~~~~~~~~~~~~~~~~~~~ - - In order to compile the kernel you will need to install some - dependencies. You will need `libelf', and `bison' to compile the - kernel. If you want to configure using the menu interface you will - also need `ncurses'. - - ,---- - | # The package manager asks to install if you are building more than one package, - | # so no need to run 'cpt i ...' - | cpt b libelf ncurses - `---- - - In the vanilla kernel sources, you need perl to compile the kernel, - but it can be easily patched out. You will need to apply the following - patch. Patch was written by [E5ten]. You will need to obtain and apply - the patch in the kernel source directory. - - ,---- - | wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch - | patch -p1 < kernel-no-perl.patch - `---- - - -[E5ten] - - -4.3 Building the kernel -~~~~~~~~~~~~~~~~~~~~~~~ - - Next step is configuring and building the kernel. You can check - Gentoo's [kernel configuration guide] to learn more about the - matter. Overall, Gentoo Wiki is a good place to learn about - configuration according to your hardware. The following will assume a - monolithic kernel. - - ,---- - | make menuconfig - | make - | install -Dm755 $(make -s image_name) /boot/vmlinuz-linux - `---- - - -[kernel configuration guide] - - - -5 Making your system bootable -============================= - - In order to be able to boot your fresh system, wou will need an - init-daemon, init-scripts and a bootloader. The init daemon is already - provided by busybox, but you can optionally change it. - - -5.1 Bootloader -~~~~~~~~~~~~~~ - - In the main repository, there is efibootmgr and grub to serve as - bootloaders. efibootmgr can be used as a standalone bootloader, or - can be used to install grub in a UEFI environment. efibootmgr is - needed unless you are using a device without UEFI support (or you - really want to use BIOS for a reason). - - -5.1.1 GRUB BIOS installation ----------------------------- - - ,---- - | cpt b grub && cpt i grub - | grub-install --target=i386-pc /dev/sdX - | grub-mkconfig -o /boot/grub/grub.cfg - `---- - - -5.1.2 GRUB UEFI installation ----------------------------- - - ,---- - | cpt b efibootmgr && cpt i efibootmgr - | cpt b grub && cpt i grub - | - | grub-install --target=x86_64-efi \ - | --efi-directory=esp \ - | --bootloader-id=CarbsLinux - | - | grub-mkconfig -o /boot/grub/grub.cfg - `---- - - -5.2 Init scripts -~~~~~~~~~~~~~~~~ - - Only thing left to do is installing the init-scripts, and now you are - almost ready to boot your system! - - ,---- - | cpt b carbs-init && cpt i carbs-init - `---- - - -5.3 Fstab -~~~~~~~~~ - - You can now manually edit your fstab entry, or you can use the - genfstab tool. If you want to use the tool, exit the chroot and run - the following: - - ,---- - | wget https://github.com/cemkeylan/genfstab/raw/master/genfstab - | chmod +x genfstab - | ./genfstab -U /mnt >> /mnt/etc/fstab - `---- - - -6 Post-installation -=================== - - The base installation is now complete, you can now fine tune your - system according to your needs. Rest of these instructions are - completely optional. You can check the rest of the documentation to - learn more about the system. - - -6.1 KISS repositories -~~~~~~~~~~~~~~~~~~~~~ - - While not 100% compatible with cpt, you can use kiss repositories in - your system the same way you are using the distribution - repositories. Here is an example for the KISS Linux Community - repository. diff --git a/docs/mailing-lists.html b/docs/mailing-lists.html deleted file mode 100644 index 2b11d8b..0000000 --- a/docs/mailing-lists.html +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - -Mailing Lists - - - - - - -
- -
-
-
-

Mailing Lists

-

-We have mailing lists set up at SourceHut. You can subscribe to the mailing -list by sending an empty mail to ~carbslinux/dev+subscribe@lists.sr.ht. -

- -

-You can also see the archives. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/mailing-lists.txt b/docs/mailing-lists.txt deleted file mode 100644 index 35773e9..0000000 --- a/docs/mailing-lists.txt +++ /dev/null @@ -1,19 +0,0 @@ - _______________ - - MAILING LISTS - _______________ - - -We have mailing lists set up at [SourceHut]. You can subscribe to the -mailing list by sending an empty mail to -[~carbslinux/dev+subscribe@lists.sr.ht]. - -You can also see the [archives]. - - -[SourceHut] - -[~carbslinux/dev+subscribe@lists.sr.ht] - - -[archives] diff --git a/docs/news.xml b/docs/news.xml deleted file mode 100644 index 2837b30..0000000 --- a/docs/news.xml +++ /dev/null @@ -1,278 +0,0 @@ - - - Carbs Linux news - - https://carbslinux.org/news - - en - Tue, 02 Feb 2021 03:52:20 +0300 - Tue, 02 Feb 2021 03:52:20 +0300 - Emacs 27.1 Org-mode 9.4.4 - root@carbslinux.org (Cem Keylan) - - https://orgmode.org/img/org-mode-unicorn-logo.png - Carbs Linux news - https://carbslinux.org/news - - - - - - https://carbslinux.org/news/20200916.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200916.html - Wed, 16 Sep 2020 00:00:00 +0300 - - - The libressl "revert" was reverted. System update will replace libressl - dependencies with bearssl. You may choose to keep or remove bearssl after the - update. -

- ]]> - - - - https://carbslinux.org/news/20200903.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200903.html - Thu, 03 Sep 2020 00:00:00 +0300 - - - The default TLS provider has been reverted to libressl. System update will - replace bearssl dependencies with libressl. You may choose to keep or remove - bearssl after the update. -

- ]]> - - - - https://carbslinux.org/news/20200727.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200727.html - Mon, 27 Jul 2020 00:00:00 +0300 - - - Carbs Linux's fork of the kiss package manager has been renamed to Carbs - Packaging Tools due to huge amount of changes. Your latest kiss update will - handle the bootstrapping. You will need to rename your KISS-* variables to - CPT-*. -

- ]]> - - - - https://carbslinux.org/news/20200617.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200617.html - Wed, 17 Jun 2020 00:00:00 +0300 - - - A new rootfs tarball including the changes to the core is released and can be - found on the downloads page. -

- ]]> - - - - https://carbslinux.org/news/20200526.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200526.html - Tue, 26 May 2020 00:00:00 +0300 - - - An initial version for binary package management is released. It can be found on - the GitHub page. -

- ]]> - - - - https://carbslinux.org/news/20200519.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200519.html - Tue, 19 May 2020 00:00:00 +0300 - - - A rootfs tarball targeting the i686 architecture has been released. It can be - found on the downloads page. -

- ]]> - - - - https://carbslinux.org/news/20200510.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200510.html - Sun, 10 May 2020 00:00:00 +0300 - - - 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 patch to your kernel sources. -

- -

- EDIT: The patch is no longer necessary. -

- ]]> - - - - https://carbslinux.org/news/20200427.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200427.html - Mon, 27 Apr 2020 00:00:00 +0300 - - - A new rootfs tarball has been released! You can see it on - https://dl.carbslinux.org/releases! -

- -

- EDIT: A new bug fix release has been made. -

- ]]> - - - - https://carbslinux.org/news/20200410.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200410.html - Fri, 10 Apr 2020 00:00:00 +0300 - - - IRC channel can now be accessed from #carbslinux at freenode! -

- ]]> - - - - https://carbslinux.org/news/20200406.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200406.html - Mon, 06 Apr 2020 00:00:00 +0300 - - - A new rootfs tarball has been released. See the downloads page. -

- ]]> - - - - https://carbslinux.org/news/20200405.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200405.html - Sun, 05 Apr 2020 00:00:00 +0300 - - - 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 https://github.com/CarbsLinux/repository. The git repository will - continue to be served until then (without additional commits). -

- -

- You can switch your remote by executing the following command on your repository - directory. -

- -
- 
git remote set-url origin https://github.com/CarbsLinux/repository
-
-
- ]]> - - - - https://carbslinux.org/news/20200218.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200218.html - Tue, 18 Feb 2020 00:00:00 +0300 - - - A new tarball is released. It can be found on https://dl.carbslinux.org. -

- -

- edit: I have removed the tarball because of a bootstrapping issue. I will be - re-adding it later today. -

- -

- edit 2: I have added a tarball (20200219) to reflect my recent changes on - Busybox. -

- ]]> - - - - https://carbslinux.org/news/20200214.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/news/20200214.html - Fri, 14 Feb 2020 00:00:00 +0300 - - - IMPORTANT! 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. -

- -
- 
# 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.
-
-
- -

- 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. -

- -

- To give an example, before this update busybox-init was managing getty - through inittab, runit was managing through /etc/runit/2, and - minit/sinit were launching from /etc/init/launch-services.boot. 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. -

- ]]> - - - diff --git a/docs/news/20191210.html b/docs/news/20191210.html deleted file mode 100644 index 37cd85b..0000000 --- a/docs/news/20191210.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Dec 10, 2019 - - - - - -
- -
-
-
-

Dec 10, 2019

-

-First alpha release was made. See the downloads page. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20191210.txt b/docs/news/20191210.txt deleted file mode 100644 index 379c42b..0000000 --- a/docs/news/20191210.txt +++ /dev/null @@ -1,13 +0,0 @@ - ______________ - - DEC 10, 2019 - ______________ - - - <2019-12-10 Tue> - - -First alpha release was made. See the [downloads page]. - - -[downloads page] diff --git a/docs/news/20191212.html b/docs/news/20191212.html deleted file mode 100644 index 273b0b1..0000000 --- a/docs/news/20191212.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - -Dec 12, 2019 - - - - - -
- -
-
-
-

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. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20191212.txt b/docs/news/20191212.txt deleted file mode 100644 index c07ad48..0000000 --- a/docs/news/20191212.txt +++ /dev/null @@ -1,11 +0,0 @@ - ______________ - - DEC 12, 2019 - ______________ - - - <2019-12-12 Thu> - - -Busybox and Busybox-init has been seperated into two different packages. -This is for adding standalone runit/runit-init to the repositories. diff --git a/docs/news/20191217.html b/docs/news/20191217.html deleted file mode 100644 index ae232f9..0000000 --- a/docs/news/20191217.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Dec 17, 2019 - - - - - -
- -
-
-
-

Dec 17, 2019

-

-Installation instruction are now complete. A review would be greatly appreciated! -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20191217.txt b/docs/news/20191217.txt deleted file mode 100644 index f12e258..0000000 --- a/docs/news/20191217.txt +++ /dev/null @@ -1,11 +0,0 @@ - ______________ - - DEC 17, 2019 - ______________ - - - <2019-12-17 Tue> - - -Installation instruction are now complete. A review would be greatly -appreciated! diff --git a/docs/news/20191218.html b/docs/news/20191218.html deleted file mode 100644 index 5caa9e6..0000000 --- a/docs/news/20191218.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Dec 18, 2019 - - - - - -
- -
-
-
-

Dec 18, 2019

-

-carbs-rootfs-20191218.tar.xz was released. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20191218.txt b/docs/news/20191218.txt deleted file mode 100644 index b82fbc8..0000000 --- a/docs/news/20191218.txt +++ /dev/null @@ -1,10 +0,0 @@ - ______________ - - DEC 18, 2019 - ______________ - - - <2019-12-18 Wed> - - -carbs-rootfs-20191218.tar.xz was released. diff --git a/docs/news/20200109.html b/docs/news/20200109.html deleted file mode 100644 index ce9d1d7..0000000 --- a/docs/news/20200109.html +++ /dev/null @@ -1,56 +0,0 @@ - - - - - - -Jan 09, 2020 - - - - - -
- -
-
-
-

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. -This week I will be changing/adding some things. -

- -

-Important things are, -

- -
    -
  • Carbs-init was updated to 0.3.
    • -
  • I will be adding an implementation of suckless.org's sinit as carbs-sinit
    • -
  • Carbs Repository was added to repology.org
    • -
  • A new rootfs tarball will be coming up tomorrow.
    • -
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200109.txt b/docs/news/20200109.txt deleted file mode 100644 index cdd37b4..0000000 --- a/docs/news/20200109.txt +++ /dev/null @@ -1,26 +0,0 @@ - ______________ - - JAN 09, 2020 - ______________ - - - <2020-01-09 Thu> - - -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. - -Important things are, - -- Carbs-init was updated to 0.3. -- I will be adding an implementation of suckless.org's [sinit] as - `carbs-sinit' -- Carbs Repository was added to [repology.org] -- A new rootfs tarball will be coming up tomorrow. - - -[sinit] - -[repology.org] diff --git a/docs/news/20200110.html b/docs/news/20200110.html deleted file mode 100644 index b501568..0000000 --- a/docs/news/20200110.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Jan 10, 2020 - - - - - -
- -
-
-
-

Jan 10, 2020

-

-carbs-rootfs-20200110.tar.xz was released. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200110.txt b/docs/news/20200110.txt deleted file mode 100644 index 4963520..0000000 --- a/docs/news/20200110.txt +++ /dev/null @@ -1,10 +0,0 @@ - ______________ - - JAN 10, 2020 - ______________ - - - <2020-01-10 Fri> - - -carbs-rootfs-20200110.tar.xz was released. diff --git a/docs/news/20200113.html b/docs/news/20200113.html deleted file mode 100644 index c498e68..0000000 --- a/docs/news/20200113.html +++ /dev/null @@ -1,67 +0,0 @@ - - - - - - -Jan 13, 2020 - - - - - -
- -
-
-
-

Jan 13, 2020

-

-Busybox update reqires manual intervention -

- -

-The new busybox package conflicts with the pre-update busybox-init. That's why -you should rebuild and install `busybox-init` before doing the update. -

- -
-
# 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
-
-
-
- -

-I have moved runit and logging utilities from the busybox-init package to the busybox -package, which is the cause of these conflicts. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200113.txt b/docs/news/20200113.txt deleted file mode 100644 index a5a44a8..0000000 --- a/docs/news/20200113.txt +++ /dev/null @@ -1,30 +0,0 @@ - ______________ - - JAN 13, 2020 - ______________ - - - <2020-01-13 Mon> - - -**Busybox update reqires manual intervention** - -The new busybox package conflicts with the pre-update -busybox-init. That's why you should rebuild and install `busybox-init` -before doing the update. - -,---- -| # 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 -| -`---- - -I have moved runit and logging utilities from the busybox-init package -to the busybox package, which is the cause of these conflicts. diff --git a/docs/news/20200115.html b/docs/news/20200115.html deleted file mode 100644 index 3285765..0000000 --- a/docs/news/20200115.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Jan 15, 2020 - - - - - -
- -
-
-
-

Jan 15, 2020

-

-sinit has been taken to core, and is now officially supported -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200115.txt b/docs/news/20200115.txt deleted file mode 100644 index 9c2ec17..0000000 --- a/docs/news/20200115.txt +++ /dev/null @@ -1,10 +0,0 @@ - ______________ - - JAN 15, 2020 - ______________ - - - <2020-01-15 Wed> - - -sinit has been taken to `core', and is now officially supported diff --git a/docs/news/20200122.html b/docs/news/20200122.html deleted file mode 100644 index f4c3dfe..0000000 --- a/docs/news/20200122.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - -Jan 22, 2020 - - - - - -
- -
-
-
-

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! -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200122.txt b/docs/news/20200122.txt deleted file mode 100644 index f7930d0..0000000 --- a/docs/news/20200122.txt +++ /dev/null @@ -1,11 +0,0 @@ - ______________ - - JAN 22, 2020 - ______________ - - - <2020-01-22 Wed> - - -Expect downtime on Jan 24 2020 22:00 UTC as I will be migrating this web -server to my Carbs Linux server! diff --git a/docs/news/20200128.html b/docs/news/20200128.html deleted file mode 100644 index f656998..0000000 --- a/docs/news/20200128.html +++ /dev/null @@ -1,52 +0,0 @@ - - - - - - -Jan 28, 2020 - - - - - -
- -
-
-
-

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. Downtimes can be expected. -

- -

-UPDATE: ssl is now working. -

- -

-UPDATE2: downloads are back again. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200128.txt b/docs/news/20200128.txt deleted file mode 100644 index f504343..0000000 --- a/docs/news/20200128.txt +++ /dev/null @@ -1,16 +0,0 @@ - ______________ - - JAN 28, 2020 - ______________ - - - <2020-01-28 Tue> - - -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. - -UPDATE: ssl is now working. - -UPDATE2: downloads are back again. diff --git a/docs/news/20200213.html b/docs/news/20200213.html deleted file mode 100644 index 3c19840..0000000 --- a/docs/news/20200213.html +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Feb 13, 2020 - - - - - -
- -
-
-
-

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 utilities with the -actual runit. This will reduce the dependency on busybox greatly. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200213.txt b/docs/news/20200213.txt deleted file mode 100644 index 6422bc7..0000000 --- a/docs/news/20200213.txt +++ /dev/null @@ -1,13 +0,0 @@ - ______________ - - FEB 13, 2020 - ______________ - - - <2020-02-13 Thu> - - -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. diff --git a/docs/news/20200214.html b/docs/news/20200214.html deleted file mode 100644 index df44014..0000000 --- a/docs/news/20200214.html +++ /dev/null @@ -1,93 +0,0 @@ - - - - - - -Feb 14, 2020 - - - - - -
- -
-
-
-

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 -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. -

- -
-
# 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.
-
-
- -

-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. -

- -

-To give an example, before this update busybox-init was managing getty -through inittab, runit was managing through /etc/runit/2, and -minit/sinit were launching from /etc/init/launch-services.boot. 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. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200214.txt b/docs/news/20200214.txt deleted file mode 100644 index e585cff..0000000 --- a/docs/news/20200214.txt +++ /dev/null @@ -1,55 +0,0 @@ - ______________ - - FEB 14, 2020 - ______________ - - - <2020-02-14 Fri> - - -**IMPORTANT!** 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. - -,---- -| # 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. -`---- - -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. - -To give an example, before this update busybox-init was managing getty -through `inittab', runit was managing through `/etc/runit/2', and -minit/sinit were launching from `/etc/init/launch-services.boot'. 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. diff --git a/docs/news/20200218.html b/docs/news/20200218.html deleted file mode 100644 index 3e2d309..0000000 --- a/docs/news/20200218.html +++ /dev/null @@ -1,53 +0,0 @@ - - - - - - -Feb 18, 2020 - - - - - -
- -
-
-
-

Feb 18, 2020

-

-A new tarball is released. It can be found on https://dl.carbslinux.org. -

- -

-edit: I have removed the tarball because of a bootstrapping issue. I will be -re-adding it later today. -

- -

-edit 2: I have added a tarball (20200219) to reflect my recent changes on -Busybox. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200218.txt b/docs/news/20200218.txt deleted file mode 100644 index d954d7d..0000000 --- a/docs/news/20200218.txt +++ /dev/null @@ -1,17 +0,0 @@ - ______________ - - FEB 18, 2020 - ______________ - - - <2020-02-18 Tue> - - -A new tarball is released. It can be found on -. - -**edit:** I have removed the tarball because of a bootstrapping issue. I -will be re-adding it later today. - -**edit 2:** I have added a tarball (20200219) to reflect my recent -changes on Busybox. diff --git a/docs/news/20200405.html b/docs/news/20200405.html deleted file mode 100644 index 1f50f64..0000000 --- a/docs/news/20200405.html +++ /dev/null @@ -1,56 +0,0 @@ - - - - - - -Apr 05, 2020 - - - - - -
- -
-
-
-

Apr 05, 2020

-

-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 https://github.com/CarbsLinux/repository. The git repository will -continue to be served until then (without additional commits). -

- -

-You can switch your remote by executing the following command on your repository -directory. -

- -
-
git remote set-url origin https://github.com/CarbsLinux/repository
-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200405.txt b/docs/news/20200405.txt deleted file mode 100644 index e46d328..0000000 --- a/docs/news/20200405.txt +++ /dev/null @@ -1,21 +0,0 @@ - ______________ - - APR 05, 2020 - ______________ - - - <2020-04-05 Sun> - - -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 -. The git repository will -continue to be served until then (without additional commits). - -You can switch your remote by executing the following command on your -repository directory. - -,---- -| git remote set-url origin https://github.com/CarbsLinux/repository -`---- diff --git a/docs/news/20200406.html b/docs/news/20200406.html deleted file mode 100644 index 4f7ff62..0000000 --- a/docs/news/20200406.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Apr 06, 2020 - - - - - -
- -
-
-
-

Apr 06, 2020

-

-A new rootfs tarball has been released. See the downloads page. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200406.txt b/docs/news/20200406.txt deleted file mode 100644 index 7cca6f7..0000000 --- a/docs/news/20200406.txt +++ /dev/null @@ -1,10 +0,0 @@ - ______________ - - APR 06, 2020 - ______________ - - - <2020-04-06 Mon> - - -A new rootfs tarball has been released. See the downloads page. diff --git a/docs/news/20200410.html b/docs/news/20200410.html deleted file mode 100644 index 32d22a2..0000000 --- a/docs/news/20200410.html +++ /dev/null @@ -1,43 +0,0 @@ - - - - - - -Apr 10, 2020 - - - - - -
- -
-
-
-

Apr 10, 2020

-

-IRC channel can now be accessed from #carbslinux at freenode! -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200410.txt b/docs/news/20200410.txt deleted file mode 100644 index 0c1befc..0000000 --- a/docs/news/20200410.txt +++ /dev/null @@ -1,10 +0,0 @@ - ______________ - - APR 10, 2020 - ______________ - - - <2020-04-10 Fri> - - -IRC channel can now be accessed from `#carbslinux' at freenode! diff --git a/docs/news/20200427.html b/docs/news/20200427.html deleted file mode 100644 index ad20d4e..0000000 --- a/docs/news/20200427.html +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - -Apr 27, 2020 - - - - - -
- -
-
-
-

Apr 27, 2020

-

-A new rootfs tarball has been released! You can see it on -https://dl.carbslinux.org/releases! -

- -

-EDIT: A new bug fix release has been made. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200427.txt b/docs/news/20200427.txt deleted file mode 100644 index 6f7815f..0000000 --- a/docs/news/20200427.txt +++ /dev/null @@ -1,13 +0,0 @@ - ______________ - - APR 27, 2020 - ______________ - - - <2020-04-27 Mon> - - -A new rootfs tarball has been released! You can see it on -! - -**EDIT:** A new bug fix release has been made. diff --git a/docs/news/20200510.html b/docs/news/20200510.html deleted file mode 100644 index 88883af..0000000 --- a/docs/news/20200510.html +++ /dev/null @@ -1,48 +0,0 @@ - - - - - - -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 patch to your kernel sources. -

- -

-EDIT: The patch is no longer necessary. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200510.txt b/docs/news/20200510.txt deleted file mode 100644 index 394585e..0000000 --- a/docs/news/20200510.txt +++ /dev/null @@ -1,18 +0,0 @@ - ______________ - - MAY 10, 2020 - ______________ - - - <2020-05-10 Sun> - - -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 [patch] to your kernel -sources. - -**EDIT:** The patch is no longer necessary. - - -[patch] - diff --git a/docs/news/20200519.html b/docs/news/20200519.html deleted file mode 100644 index 6892585..0000000 --- a/docs/news/20200519.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - -May 19, 2020 - - - - - -
- -
-
-
-

May 19, 2020

-

-A rootfs tarball targeting the i686 architecture has been released. It can be -found on the downloads page. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200519.txt b/docs/news/20200519.txt deleted file mode 100644 index 2f3ef90..0000000 --- a/docs/news/20200519.txt +++ /dev/null @@ -1,11 +0,0 @@ - ______________ - - MAY 19, 2020 - ______________ - - - <2020-05-19 Tue> - - -A rootfs tarball targeting the i686 architecture has been released. It -can be found on the downloads page. diff --git a/docs/news/20200526.html b/docs/news/20200526.html deleted file mode 100644 index 5758a12..0000000 --- a/docs/news/20200526.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - -May 26, 2020 - - - - - -
- -
-
-
-

May 26, 2020

-

-An initial version for binary package management is released. It can be found on -the GitHub page. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200526.txt b/docs/news/20200526.txt deleted file mode 100644 index 7ad092b..0000000 --- a/docs/news/20200526.txt +++ /dev/null @@ -1,14 +0,0 @@ - ______________ - - MAY 26, 2020 - ______________ - - - <2020-05-26 Tue> - - -An initial version for binary package management is released. It can be -found on the [GitHub page]. - - -[GitHub page] diff --git a/docs/news/20200617.html b/docs/news/20200617.html deleted file mode 100644 index 8e70d1c..0000000 --- a/docs/news/20200617.html +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - -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. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200617.txt b/docs/news/20200617.txt deleted file mode 100644 index 2515111..0000000 --- a/docs/news/20200617.txt +++ /dev/null @@ -1,11 +0,0 @@ - ______________ - - JUN 17, 2020 - ______________ - - - <2020-06-17 Wed> - - -A new rootfs tarball including the changes to the core is released and -can be found on the downloads page. diff --git a/docs/news/20200727.html b/docs/news/20200727.html deleted file mode 100644 index 613ff2d..0000000 --- a/docs/news/20200727.html +++ /dev/null @@ -1,46 +0,0 @@ - - - - - - -Jul 27, 2020 - - - - - -
- -
-
-
-

Jul 27, 2020

-

-Carbs Linux's fork of the kiss package manager has been renamed to Carbs -Packaging Tools due to huge amount of changes. Your latest kiss update will -handle the bootstrapping. You will need to rename your KISS-* variables to -CPT-*. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200727.txt b/docs/news/20200727.txt deleted file mode 100644 index eaf0544..0000000 --- a/docs/news/20200727.txt +++ /dev/null @@ -1,13 +0,0 @@ - ______________ - - JUL 27, 2020 - ______________ - - - <2020-07-27 Mon> - - -Carbs Linux's fork of the `kiss' package manager has been renamed to -`Carbs Packaging Tools' due to huge amount of changes. Your latest -`kiss' update will handle the bootstrapping. You will need to rename -your `KISS-*' variables to `CPT-*'. diff --git a/docs/news/20200903.html b/docs/news/20200903.html deleted file mode 100644 index c1ebfe7..0000000 --- a/docs/news/20200903.html +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Sep 03, 2020 - - - - - -
- -
-
-
-

Sep 03, 2020

-

-The default TLS provider has been reverted to libressl. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200903.txt b/docs/news/20200903.txt deleted file mode 100644 index 816c61c..0000000 --- a/docs/news/20200903.txt +++ /dev/null @@ -1,12 +0,0 @@ - ______________ - - SEP 03, 2020 - ______________ - - - <2020-09-03 Thu> - - -The default TLS provider has been reverted to `libressl'. System update -will replace bearssl dependencies with libressl. You may choose to keep -or remove bearssl after the update. diff --git a/docs/news/20200916.html b/docs/news/20200916.html deleted file mode 100644 index 6497f92..0000000 --- a/docs/news/20200916.html +++ /dev/null @@ -1,45 +0,0 @@ - - - - - - -Sep 16, 2020 - - - - - -
- -
-
-
-

Sep 16, 2020

-

-The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -

-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/20200916.txt b/docs/news/20200916.txt deleted file mode 100644 index b0a7925..0000000 --- a/docs/news/20200916.txt +++ /dev/null @@ -1,12 +0,0 @@ - ______________ - - SEP 16, 2020 - ______________ - - - <2020-09-16 Wed> - - -The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl -after the update. diff --git a/docs/news/index.html b/docs/news/index.html deleted file mode 100644 index bb09ed4..0000000 --- a/docs/news/index.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - - -News Index - - - - - -
- -
-
-
-

News Index

-
-
-

Sep 16, 2020

-
-

-The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -

-
-
-
-

Sep 03, 2020

-
-

-The default TLS provider has been reverted to libressl. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -

-
-
-
-

Jul 27, 2020

-
-

-Carbs Linux's fork of the kiss package manager has been renamed to Carbs - Packaging Tools due to huge amount of changes. Your latest kiss update will -handle the bootstrapping. You will need to rename your KISS-* variables to -CPT-*. -

-
-
-
-

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. -

-
-
-
-

May 19, 2020

-
-

-A rootfs tarball targeting the i686 architecture has been released. It can be -found on the downloads page. -

-
-
-
-

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 patch to your kernel sources. -

- -

-EDIT: The patch is no longer necessary. -

-
-
-
-

Apr 27, 2020

-
-

-A new rootfs tarball has been released! You can see it on -https://dl.carbslinux.org/releases! -

- -

-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 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 May 4, 2020 Monday to switch your -remotes to https://github.com/CarbsLinux/repository. The git repository will -continue to be served until then (without additional commits). -

- -

-You can switch your remote by executing the following command on your repository -directory. -

- -
-
git remote set-url origin https://github.com/CarbsLinux/repository
-
-
-
-
-
-

Feb 18, 2020

-
-

-A new tarball is released. It can be found on https://dl.carbslinux.org. -

- -

-edit: I have removed the tarball because of a bootstrapping issue. I will be -re-adding it later today. -

- -

-edit 2: I have added a tarball (20200219) to reflect my recent 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 -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. -

- -
-
# 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.
-
-
- -

-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. -

- -

-To give an example, before this update busybox-init was managing getty -through inittab, runit was managing through /etc/runit/2, and -minit/sinit were launching from /etc/init/launch-services.boot. 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. -

-
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/news/index.txt b/docs/news/index.txt deleted file mode 100644 index 3f1a3b9..0000000 --- a/docs/news/index.txt +++ /dev/null @@ -1,209 +0,0 @@ - ____________ - - NEWS INDEX - ____________ - - - - - -[Sep 16, 2020] -============== - - The libressl "revert" was reverted. System update will replace - libressl dependencies with bearssl. You may choose to keep or remove - bearssl after the update. - - -[Sep 16, 2020] - - -[Sep 03, 2020] -============== - - The default TLS provider has been reverted to `libressl'. System - update will replace bearssl dependencies with libressl. You may choose - to keep or remove bearssl after the update. - - -[Sep 03, 2020] - - -[Jul 27, 2020] -============== - - Carbs Linux's fork of the `kiss' package manager has been renamed to - `Carbs Packaging Tools' due to huge amount of changes. Your latest - `kiss' update will handle the bootstrapping. You will need to rename - your `KISS-*' variables to `CPT-*'. - - -[Jul 27, 2020] - - -[Jun 17, 2020] -============== - - A new rootfs tarball including the changes to the core is released and - can be found on the downloads page. - - -[Jun 17, 2020] - - -[May 26, 2020] -============== - - An initial version for binary package management is released. It can - be found on the [GitHub page]. - - -[May 26, 2020] - -[GitHub page] - - -[May 19, 2020] -============== - - A rootfs tarball targeting the i686 architecture has been released. It - can be found on the downloads page. - - -[May 19, 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 [patch] to your - kernel sources. - - **EDIT:** The patch is no longer necessary. - - -[May 10, 2020] - -[patch] - - - -[Apr 27, 2020] -============== - - A new rootfs tarball has been released! You can see it on - ! - - **EDIT:** A new bug fix release has been made. - - -[Apr 27, 2020] - - -[Apr 10, 2020] -============== - - IRC channel can now be accessed from `#carbslinux' at freenode! - - -[Apr 10, 2020] - - -[Apr 06, 2020] -============== - - A new rootfs tarball has been released. See the downloads page. - - -[Apr 06, 2020] - - -[Apr 05, 2020] -============== - - 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 - . The git repository will - continue to be served until then (without additional commits). - - You can switch your remote by executing the following command on your - repository directory. - - ,---- - | git remote set-url origin https://github.com/CarbsLinux/repository - `---- - - -[Apr 05, 2020] - - -[Feb 18, 2020] -============== - - A new tarball is released. It can be found on - . - - **edit:** I have removed the tarball because of a bootstrapping - issue. I will be re-adding it later today. - - **edit 2:** I have added a tarball (20200219) to reflect my recent - changes on Busybox. - - -[Feb 18, 2020] - - -[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 - 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. - - ,---- - | # 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. - `---- - - 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. - - To give an example, before this update busybox-init was managing getty - through `inittab', runit was managing through `/etc/runit/2', and - minit/sinit were launching from `/etc/init/launch-services.boot'. 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. - - -[Feb 14, 2020] diff --git a/docs/people.html b/docs/people.html deleted file mode 100644 index 40ac761..0000000 --- a/docs/people.html +++ /dev/null @@ -1,47 +0,0 @@ - - - - - - -‎ - - - - - - -
- -
-
-
-

People

-
- -
-
-
-
-
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2021 Cem Keylan

-
-
- - diff --git a/docs/people.txt b/docs/people.txt deleted file mode 100644 index 9d17718..0000000 --- a/docs/people.txt +++ /dev/null @@ -1,7 +0,0 @@ -People -====== - - - Cem Keylan - Founder [cem@carbslinux.org] - - -[cem@carbslinux.org] diff --git a/docs/rss.xml b/docs/rss.xml deleted file mode 100644 index 71ab49a..0000000 --- a/docs/rss.xml +++ /dev/null @@ -1,655 +0,0 @@ - - - Carbs Linux blog - - https://carbslinux.org/blog - - en - Tue, 02 Feb 2021 03:52:24 +0300 - Tue, 02 Feb 2021 03:52:24 +0300 - Emacs 27.1 Org-mode 9.4.4 - root@carbslinux.org (Cem Keylan) - - https://orgmode.org/img/org-mode-unicorn-logo.png - Carbs Linux blog - https://carbslinux.org/blog - - - - - First Year of Carbs Linux - https://carbslinux.org/blog/20201210.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20201210.html - Thu, 10 Dec 2020 00:00:00 +0300 - - - December 10, 2020 marks the first year after the initial release of Carbs Linux. - When I forked the KISS Linux repository on the 9th of December, I was fairly new - to package management. Carbs Linux used to be almost identical to KISS Linux. A - lot has changed since then: -

- -

- [2020 Jan 13] Replaced default init system to sinit - [2020 Jan 15] Packaged WebKit2GTK - [2020 May 17] Added bearssl on the testing repository - [2020 May 28] Added rsync repository support to kiss - [2020 Jun 03] Replaced bison with byacc - [2020 Jun 11] Replaced libressl with bearssl - [2020 Jun 24] Replaced kiss with cpt -

- -

- I have really enjoyed maintaining and developing this distribution, and I want - to thank everyone who was involved in some way or another. While I have slowed - down in development due to college workload, I am still actively maintaining all - the packages on the repository. I do have some ideas that I am thinking of - implementing during the semester break. Hope to see you all in January. -

- ]]> - - - August 2020 News Post - https://carbslinux.org/blog/20200803.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200803.html - Mon, 03 Aug 2020 00:00:00 +0300 - - - We are having some stalls during this summer, as I am currently working on - university-related stuff. Nonetheless, there are some important changes that I - want to share in this month's post. -

- -
- -
- -
-

Carbs Packaging Tools

-
-

- This month I have reworked kiss into a new package manager, now renamed as - cpt. Updating kiss will now bootstrap the new package manager, so you don't - have to manually edit your system. If you don't like the idea of this, you can - look up the post-install script on core/kiss and apply the changes manually. -

- -

- You will also need to rename your KISS_* variables to CPT_*. So, KISS_PATH - becomes CPT_PATH. -

- -

- The rework changes the previous commands on the package manager into standalone - tools, and move the package manager functions to a library. This makes it easier - for a user to import functions and variables from the package manager, and - extend the package manager with their own intended way. Previously this required - ugly hacks and workarounds to use the package manager functions. I will be - making use of these changes to re-implement binary package management functions - as well. -

- -

- If you want to use the library on your script you can simply do this: -

- -
- 
#!/bin/sh
-    . cpt-lib
-    (...)
-
-
- -

- There are obviously some clean-up and simplifications needed in this new - tool-based package management method. -

-
-
- -
-

Docs

-
-

- I have added documentation for the distribution, and finally updated the guide - for installation. It is now almost complete. These docs can be installed to - your system for online viewing. I will also add a documentation crawler similar - to how werc works (but as an offline viewer). You can find carbs-docs from - the repository. Currently, the documentation lacks but I will be adding new - stuff. These will solely be distribution specific documentation and will not be - a wiki-like source. If anyone would like to contribute to a wiki-like - documentation source, I would happily re-open the distribution wiki. You can - find the source on https://github.com/CarbsLinux/docs. -

-
-
- -
-

Re-opening the Carbs Linux server

-
-

- Back in May, I had shutdown the Carbs Linux server due to financial issues, but - I am slowly reverting to the self-hosted model. Back then, the git repositories - were mirrored to GitHub, and the management was overall much more flexible. The - server used to run Carbs Linux as well (that was fun and horrifying at the same - time). Now, I will be relaunching the git server which will be the upstream - source before August 5. You can switch your remote, but GitHub will stay as a - remote nonetheless. -

- -

- EDIT: The git-server is up! -

-
-
- ]]> - - - June Newspost - https://carbslinux.org/blog/20200617.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200617.html - Wed, 17 Jun 2020 00:00:00 +0300 - - - This will be an active month for Carbs as major changes to the base and the - package manager will be coming up. -

- -
-

Statically linking the base

-
-

- 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. -

- -

- I believe that binaries on the core should always be linked statically. This - ensures that an SONAME bump to libObscure.so 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. -

- -

- 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. -

-
-
- -
-

Major changes on the core repository

-
-

- 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. -

-
- -
-

Removed from Core

-
-

- git - libressl - grub - bison - dhcpcd - ubase -

-
-
- -
-

Added to Core

-
-

- bearssl, as a libressl replacement - byacc, as a bison replacement -

-
-
- -
-

Statically linked

-
-

- kiss - neatvi - mandoc - byacc - m4 - e2fsprogs - make - pkgconf - sbase - libnl - wpa_supplicant - bearssl -

-
-
-
- -
-

Making the wiki available offline

-
-

- Soon, all documentation regarding Carbs Linux will be avaialable to be installed - from the core repository in a carbs-docs 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. -

-
-
- -
-

ISO image for Carbs

-
-

- 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 arch-install-scripts. Let's see how that's going to play out. -

-
-
- ]]> - - - kiss 2.0.0 and Overall Changes - https://carbslinux.org/blog/20200528.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200528.html - Thu, 28 May 2020 00:00:00 +0300 - - - Carbs Linux kiss version 2.0.0 has been released which introduces rsync - repositories. -

- -

- 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. -

- -

- Git is now on the extra repository and is still (optionally) used in the - package manager. -

- -

- 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. -

- -

- This is a precaution with the added bonuses of speed and dropping a mandatory - dependency. -

- -

- You can see the rest of the changelog here. -

- -
-

Binary Repositories

-
-

- A few days ago, I have also published kiss-bin, 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. -

-
-
- ]]> - - - The Relation of Carbs and KISS - https://carbslinux.org/blog/20200508.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200508.html - Fri, 08 May 2020 00:00:00 +0300 - - - 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. -

- -
-

History

-
-

- I had the idea of creating my own Linux distribution since the May of 2019. Back - then, I had my own Linux from Scratch 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. -

- -

- I had written some incomplete package managers (all named fat) 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. -

- -

- 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. -

- -

- One day on Reddit, I saw Dylan's post on r/unixporn about KISS, and I really - thought that it was interesting. Here is my comment 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. -

-
-
- -
-

Differences between KISS and Carbs

-
-

- 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. -

- -

- 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. -

-
-
- -
-

What I'm working on now

-
-

- Currently I have a few projects that I'm working on for Carbs. These are, -

- -

- A BSD port for Carbs. For a while, I have been working on BSD compatibility on - my fork of the [package manager]. 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. -

- -

- 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. -

- -

- 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. -

-
-
- -
-

What's up with all the init/service daemons?

-
-

- If you have ever checked the repository, 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 init daemon and service supervisor. I maintain all those packages on KISS - Community Repository as well with the exception of busybox. Those are, busybox - init/runit, runit, sinit, and sysmgr. I would definitely recommend - checking out shinit and sysmgr. -

-
-
- -
-

Why I don't publicize Carbs

-
-

- There are a couple of reasons I don't publicize Carbs a lot. -

- -

- 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. -

- -

- 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. -

- -

- 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. -

- -

- I think that's about it, if you have questions you can send me a mail, ping me - on IRC (my handle is merakor), and I will be happy to answer. Maybe your - question fits this post, and I can update it to thoroughly give an explanation. -

-
-
- ]]> - - - Outsource Repository Concept - https://carbslinux.org/blog/20200410.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200410.html - Fri, 10 Apr 2020 00:00:00 +0300 - - - In April 3rd, I have added submodule support for Carbs Linux's fork of kiss. - 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). -

- -

- 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. -

- -

- This way, an end-user can also track from their preferred maintainers, and do - that with the tidyness of a single repository in their KISS_PATH. -

- -

- 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. -

- -

- https://github.com/CarbsLinux/outsource -

- ]]> - - - Roadmap for Carbs - https://carbslinux.org/blog/20200406.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200406.html - Mon, 06 Apr 2020 00:00:00 +0300 - - - 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. -

- -
-

Carbs Linux Server Going Down

-
-

- 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 Github. - The repository and the website is served on Github now. I have also moved the - Wiki to Github and anyone can edit it there. There are some outdated posts that - I will be fixing around this week. -

- -

- 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 SourceHut?) -

- -

- I feel a little sad for switching, but serving on Github is faster, cheaper, and - hassle-free. -

-
-
- -
-

Forking KISS

-
-

- 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 this repository. See it for the added - changes. -

- -

- This will be a change for the better, as I can develop the package manager as it - fits my views. -

-
-
- -
-

Small Changes on the Website

-
-

- I have made some small changes on the website. The build is not dependent on - Plan9 utilities anymore. It was fun messing around with rc and mk, but they - are quite limited compared to POSIX shell. -

- -

- RSS feeds are finally working as intended, both for the news section, and the - blog section. -

- -

- You can see every page's .txt 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'. -

-
-
- -
-

Outsources Repository

-
-

- I have opened an outsource 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 here! -

-
-
- -
-

New Tarball

-
-

- Finally, I have released a new tarball today, which can be obtained from the - downloads page. -

- -

- I am planning to add more of these update posts as I'm feeling better about the - website structure overall. -

-
-
- ]]> - - - Switching to New Website - https://carbslinux.org/blog/20200128.html - root@carbslinux.org (Cem Keylan) - https://carbslinux.org/blog/20200128.html - Tue, 28 Jan 2020 00:00:00 +0300 - - - In case you haven't seen it before, this website was powered by werc. And even - though I liked it really much, it was too powerful for a small website like - this. -

- -

- So I have decided to reimplement this website with my own static generation - scripts. The source will probably be on its git repository when I decide to - publish the website. -

- -

- 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. -

- ]]> - - - diff --git a/docs/style.css b/docs/style.css deleted file mode 100644 index d35af15..0000000 --- a/docs/style.css +++ /dev/null @@ -1,243 +0,0 @@ -/* - * Stylesheet for Carbs Linux website - * Copyright (c) 2019-2021 Cem Keylan - */ -:root { - --color-carbs-color-bg: #F3F6F8; - --color-carbs-color-fg: #0A1E2B; - --color-carbs-highlight: #E9ECEE; - --color-carbs-pink: #BF6790; - --color-carbs-purple: #8C45D4; - --color-carbs-blue: #3F74A6; - --color-carbs-blue-alt: #3F41A6; - --color-carbs-red: #D32C2C; - --color-carbs-grey: #738B8B; - --color-carbs-green: #027A59; - --color-carbs-orange: #B45123; } - @media (prefers-color-scheme: dark) { - :root { - --color-carbs-color-bg: #0A1E2B; - --color-carbs-color-fg: #F3F6F8; - --color-carbs-highlight: #0A2830; - --color-carbs-pink: #BF6790; - --color-carbs-purple: #A6A6D2; - --color-carbs-blue: #6790BF; - --color-carbs-blue-alt: #67BCBF; - --color-carbs-red: #C34266; - --color-carbs-grey: #686868; - --color-carbs-green: #67BF96; - --color-carbs-orange: #F47A00; } } -body { - margin: 0; - background-color: var(--color-carbs-color-bg); - font-family: "Noto Sans", "Open Sans", sans-serif; - font-size: 16px; - color: var(--color-carbs-color-fg); - -webkit-text-size-adjust: 100%; - -ms-text-size-adjust: 100%; - -ms-overflow-style: scrollbar; - -webkit-tap-highlight-color: transparent; } - -/* Reasonable line-height for better readability. */ -p, pre, li, dt, dd, table, code, address { - line-height: 1.5em; } - -p { - margin-top: 1em; - margin-bottom: 1em; } - -#content { - width: 95%; - margin: 0 auto; - margin-left: auto; - margin-right: auto; - text-align: left; - max-width: 50em; } - -.subtitle { - color: var(--color-carbs-color-fg); - font-weight: normal; - font-size: 16px; - font-style: italic; } - -code, pre.src { - padding: .2em .4em; - margin: 0; - font-size: 85%; } - -code { - background-color: var(--color-carbs-highlight); - border-radius: 3px; } - -h1 a, h2 a, h3 a, h4 a, h5 a, h6 a { - color: inherit; } - h1 a:hover, h2 a:hover, h3 a:hover, h4 a:hover, h5 a:hover, h6 a:hover { - text-decoration: none; } - -h1 { - color: var(--color-carbs-pink); - font-weight: 800; } - h1 a:hover { - color: #bf6a67; } - @media (prefers-color-scheme: dark) { - h1 a:hover { - color: #bf6a67; } } -h2 { - color: var(--color-carbs-blue); - font-weight: 700; } - h2 a:hover { - color: var(--color-carbs-purple); } - -h3 { - color: var(--color-carbs-color-fg); - font-weight: 600; } - h3 a:hover { - color: var(--color-carbs-blue); } - -pre { - font: monospace; - border-radius: 3px; - border: 1px solid var(--color-carbs-highlight); - background-color: var(--color-carbs-highlight); - padding: 0.5em; - margin: 1em; } - pre code, pre.src { - display: block; - overflow: auto; } - pre code { - background: transparent; } - -a { - text-decoration: none; - font-weight: bold; - color: var(--color-carbs-pink); } - -a:hover { - text-decoration: underline; - color: var(--color-carbs-blue-alt); } - -blockquote { - border-left: 1px solid var(--color-carbs-highlight); - font-style: italic; } - -#preamble { - margin-bottom: 2em; } - -#navbar { - background: #0A1E2B none repeat scroll 0 0 !important; - border-bottom: 5px solid #BF6790 !important; - min-height: 40px; - padding: 10px 15px !important; } - #navbar label, #navbar #hamburger { - display: none; } - #navbar a.navbartitle { - margin: 0 !important; - padding: 0 !important; - color: #BF6790 !important; - float: left !important; - font-weight: bolder !important; - font-size: 200% !important; } - #navbar a.navbartitle:hover { - text-decoration: none; - color: #BF6790; } - #navbar #navbarlist li a { - color: #F3F6F8; - font-weight: bold; - text-decoration: none; } - #navbar ul { - display: block; - list-style: none; - margin: 0; - padding: 0; - text-align: right; - font-size: 0; - letter-spacing: 0; } - #navbar ul li { - display: inline-block; - font-size: 14px; - font-family: "Noto Sans", "Open Sans", sans-serif !important; - line-height: 1.4; - letter-spacing: 0; - padding-top: 14px; - padding-right: 15px; - padding-left: 15px; - margin: 0; } - #navbar ul li a:hover { - color: #A6A6D2 !important; - text-decoration: none !important; } - -@media screen and (max-width: 768px) { - #navbar label { - display: inline-block; - box-sizing: border-box; - color: #F3F6F8; - background: #BF6790; - border-radius: 0.2em; - font-style: normal; - text-align: center; - margin-right: auto; - margin-left: auto; - font-size: 1em; - padding: 0.5em 0; - font-size: 1em; - width: 2.2em; - height: 100%; - float: right; } - #navbar ul { - margin-left: 0; - margin-right: 0; - text-align: left; } - #navbar #navbarlist { - margin-top: 50px; - display: none; } - #navbar #navbarlist li { - box-sizing: border-box; - border-top: 1px solid var(--color-carbs-purple); - display: block; - width: 100%; - padding: 0.5em; } - #navbar input:checked ~ #navbarlist { - display: block; } } - -footer { - clear: both; - margin-top: 2em; - background: #0A1E2B none repeat scroll 0 0 !important; - border-top: 5px solid #BF6790 !important; - padding: 10px 15px !important; - bottom: 0; } - footer p { - text-align: center; - color: #F3F6F8; } - -/* Syntax highlighting for org-mode source block exports */ -.org-comment, .org-comment-delimiter { - color: var(--color-carbs-grey); - font-style: italic; } - -.org-builtin { - color: var(--color-carbs-blue); } - -.org-constant { - color: var(--color-carbs-pink); } - -.org-doc { - color: var(--color-carbs-grey); } - -.org-function-name { - color: var(--color-carbs-blue); } - -.org-variable-name { - color: var(--color-carbs-purple); } - -.org-keyword { - color: var(--color-carbs-blue-alt); } - -.org-string { - color: var(--color-carbs-green); } - -.org-type { - color: var(--color-carbs-orange); } - -.org-warning { - color: var(--color-carbs-red); } diff --git a/news/index.org b/news/index.org deleted file mode 100644 index 3a09a0f..0000000 --- a/news/index.org +++ /dev/null @@ -1,107 +0,0 @@ -#+TITLE: News Index - -* [[file:20200916.html][Sep 16, 2020]] -The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -* [[file:20200903.html][Sep 03, 2020]] -The default TLS provider has been reverted to =libressl=. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -* [[file:20200727.html][Jul 27, 2020]] -Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs - Packaging Tools= due to huge amount of changes. Your latest =kiss= update will -handle the bootstrapping. You will need to rename your =KISS-*= variables to -=CPT-*=. -* [[file:20200617.html][Jun 17, 2020]] -A new rootfs tarball including the changes to the core is released and can be -found on the downloads page. -* [[file:20200526.html][May 26, 2020]] -An initial version for binary package management is released. It can be found on -the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. -* [[file:20200519.html][May 19, 2020]] -A rootfs tarball targeting the i686 architecture has been released. It can be -found on the downloads page. -* [[file:20200510.html][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 [[https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22][patch]] to your kernel sources. - -**EDIT:** The patch is no longer necessary. -* [[file:20200427.html][Apr 27, 2020]] -A new rootfs tarball has been released! You can see it on -[[https://dl.carbslinux.org/releases]]! - -**EDIT:** A new bug fix release has been made. -* [[file:20200410.html][Apr 10, 2020]] -IRC channel can now be accessed from =#carbslinux= at freenode! -* [[file:20200406.html][Apr 06, 2020]] -A new rootfs tarball has been released. See the downloads page. -* [[file:20200405.html][Apr 05, 2020]] -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 [[https://github.com/CarbsLinux/repository]]. The git repository will -continue to be served until then (without additional commits). - -You can switch your remote by executing the following command on your repository -directory. - -#+begin_src sh - git remote set-url origin https://github.com/CarbsLinux/repository -#+end_src -* [[file:20200218.html][Feb 18, 2020]] -A new tarball is released. It can be found on [[https://dl.carbslinux.org]]. - -**edit:** I have removed the tarball because of a bootstrapping issue. I will be -re-adding it later today. - -**edit 2:** I have added a tarball (20200219) to reflect my recent changes on -Busybox. -* [[file:20200214.html][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 -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. - -#+begin_src sh - # 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. -#+end_src - -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. - -To give an example, before this update busybox-init was managing getty -through =inittab=, runit was managing through =/etc/runit/2=, and -minit/sinit were launching from =/etc/init/launch-services.boot=. 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. - - diff --git a/news/latest-news.org b/news/latest-news.org deleted file mode 100644 index 6922cf2..0000000 --- a/news/latest-news.org +++ /dev/null @@ -1,19 +0,0 @@ -* [[file:20200916.html][Sep 16, 2020]] -The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -* [[file:20200903.html][Sep 03, 2020]] -The default TLS provider has been reverted to =libressl=. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -* [[file:20200727.html][Jul 27, 2020]] -Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs - Packaging Tools= due to huge amount of changes. Your latest =kiss= update will -handle the bootstrapping. You will need to rename your =KISS-*= variables to -=CPT-*=. -* [[file:20200617.html][Jun 17, 2020]] -A new rootfs tarball including the changes to the core is released and can be -found on the downloads page. -* [[file:20200526.html][May 26, 2020]] -An initial version for binary package management is released. It can be found on -the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. diff --git a/news/news.org b/news/news.org deleted file mode 100644 index 4361e70..0000000 --- a/news/news.org +++ /dev/null @@ -1,172 +0,0 @@ -#+TITLE: Carbs Linux news -#+DESCRIPTION: a simple Linux distribution - -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200916.html -:PUBDATE: 2020-09-16 -:ID: 1b068ea7-ef38-4eb7-a3cc-36a3585823d1 -:END: -The libressl "revert" was reverted. System update will replace libressl -dependencies with bearssl. You may choose to keep or remove bearssl after the -update. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200903.html -:PUBDATE: 2020-09-03 -:ID: 2000a109-f125-4e8f-9458-a6ac995cb70f -:END: -The default TLS provider has been reverted to =libressl=. System update will -replace bearssl dependencies with libressl. You may choose to keep or remove -bearssl after the update. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200727.html -:PUBDATE: 2020-07-27 -:ID: b3f1fc2a-09b7-4895-9c81-5c912aba63ea -:END: -Carbs Linux's fork of the =kiss= package manager has been renamed to =Carbs - Packaging Tools= due to huge amount of changes. Your latest =kiss= update will -handle the bootstrapping. You will need to rename your =KISS-*= variables to -=CPT-*=. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200617.html -:PUBDATE: 2020-06-17 -:ID: 347ee0df-a4b7-42bc-8a6d-a26a39336954 -:END: -A new rootfs tarball including the changes to the core is released and can be -found on the downloads page. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200526.html -:PUBDATE: 2020-05-26 -:ID: 557f67e8-9d80-483b-859e-89f82d19fdd8 -:END: -An initial version for binary package management is released. It can be found on -the [[https://github.com/CarbsLinux/kiss-bin][GitHub page]]. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200519.html -:PUBDATE: 2020-05-19 -:ID: 6a8f3d80-6d73-4e97-b7c0-d1b6fccbf27d -:END: -A rootfs tarball targeting the i686 architecture has been released. It can be -found on the downloads page. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200510.html -:PUBDATE: 2020-05-10 -:ID: c574a132-47b7-4e14-a740-10fd9ec5a279 -:END: -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 [[https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/patch/?id=f670269a42bfdd2c83a1118cc3d1b475547eac22][patch]] to your kernel sources. - -**EDIT:** The patch is no longer necessary. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200427.html -:PUBDATE: 2020-04-27 -:ID: 8d85adcc-3c03-406f-8901-4da9b3b8596c -:END: -A new rootfs tarball has been released! You can see it on -[[https://dl.carbslinux.org/releases]]! - -**EDIT:** A new bug fix release has been made. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200410.html -:PUBDATE: 2020-04-10 -:ID: f90898fb-362d-42cb-82d7-f40f9e73e7b3 -:END: -IRC channel can now be accessed from =#carbslinux= at freenode! -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200406.html -:PUBDATE: 2020-04-06 -:ID: b50fa538-5896-4483-a12b-ca8c4c6c2a53 -:END: -A new rootfs tarball has been released. See the downloads page. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200405.html -:PUBDATE: 2020-04-05 -:ID: 3ce41a15-5ca6-4ea1-b7b9-01e1b2a5c60f -:END: -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 [[https://github.com/CarbsLinux/repository]]. The git repository will -continue to be served until then (without additional commits). - -You can switch your remote by executing the following command on your repository -directory. - -#+begin_src sh - git remote set-url origin https://github.com/CarbsLinux/repository -#+end_src -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200218.html -:PUBDATE: 2020-02-18 -:ID: c05366a9-7175-48a6-b37c-366e61b62e1a -:END: -A new tarball is released. It can be found on [[https://dl.carbslinux.org]]. - -**edit:** I have removed the tarball because of a bootstrapping issue. I will be -re-adding it later today. - -**edit 2:** I have added a tarball (20200219) to reflect my recent changes on -Busybox. -* {{{date(%b %d\, %Y)}}} -:PROPERTIES: -:RSS_PERMALINK: 20200214.html -:PUBDATE: 2020-02-14 -:ID: f9a58bcf-b300-4502-9981-c030710cb5e8 -:END: -**IMPORTANT!** 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. - -#+begin_src sh - # 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. -#+end_src - -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. - -To give an example, before this update busybox-init was managing getty -through =inittab=, runit was managing through =/etc/runit/2=, and -minit/sinit were launching from =/etc/init/launch-services.boot=. 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. - -- cgit v1.2.3