diff options
Diffstat (limited to 'docs/docs/install.html')
| -rw-r--r-- | docs/docs/install.html | 1205 |
1 files changed, 817 insertions, 388 deletions
diff --git a/docs/docs/install.html b/docs/docs/install.html index 6ed93a7..176aacd 100644 --- a/docs/docs/install.html +++ b/docs/docs/install.html @@ -1,393 +1,822 @@ -<!DOCTYPE HTML> -<html lan=en> - <head> - <title>install | Carbs Linux</title> - <link rel="stylesheet" href="/style.css"> - <meta charset="utf-8"> - <meta name="Description" content="Carbs Linux - a simple linux distribution"> - <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> - </head> - <body> - <p class=header><strong>Carbs Linux - a simple linux distribution</strong></p> - <div class="header"> - <nav> - <a href='/'>index</a> - <a href="//git.carbslinux.org">git</a> - <a href='//dl.carbslinux.org'>downloads</a> - <a href='/blog'>blog</a> - <a href='/docs/Installation.html'>installation</a> - <a href='/docs'>user manual</a> - </nav> - </div><div class="border"></div> -<pre> -1 Installation -************** - -These are the step-by-step instructions for installing Carbs Linux. - -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. - -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. - - $ URL=<a href=https://dl.carbslinux.org/releases/x86_64>https://dl.carbslinux.org/releases/x86_64</a> - $ wget $URL/carbs-rootfs.tar.xz - - We can then check the integrity of the tarball and do a signature -verification. Even thought these are optional, they are highly -recommended. - -1.1.2 Check the integrity of the tarball (Recommended) ------------------------------------------------------- - -All of the releases are saved in a single file named 'sha256sums.txt', -but the latest release is saved on 'carbs-rootfs.tar.xz.sha256'. You -can acquire and verify the tarball. - - $ wget $URL/carbs-rootfs.tar.xz.sha256 - $ sha256sum -c carbs-rootfs.tar.xz.sha256 - -1.1.3 Verify the signature --------------------------- - -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.1.4 Extracting the tarball ----------------------------- - -You will need to extract the tarball to your desired location. For -partitioning, you can follow this guide -(<a href=https://wiki.archlinux.org/index.php/Partitioning>https://wiki.archlinux.org/index.php/Partitioning</a>). 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.1.5 Obtain the chroot helper ------------------------------- - -You can obtain the 'cpt-chroot' script in order to do a simple chroot -into your new root filesystem. - - $ wget <a href=https://dl.carbslinux.org/distfiles/cpt-chroot>https://dl.carbslinux.org/distfiles/cpt-chroot</a> - $ chmod a+x cpt-chroot - -1.2 Chroot -========== - +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" +"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> +<head> +<!-- 2020-12-26 Sat 03:17 --> +<meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> +<meta name="viewport" content="width=device-width, initial-scale=1" /> +<title>Carbs Linux Installation Guide</title> +<meta name="generator" content="Org mode" /> +<meta name="author" content="Cem Keylan" /> +<style type="text/css"> + <!--/*--><![CDATA[/*><!--*/ + .title { text-align: center; + margin-bottom: .2em; } + .subtitle { text-align: center; + font-size: medium; + font-weight: bold; + margin-top:0; } + .todo { font-family: monospace; color: red; } + .done { font-family: monospace; color: green; } + .priority { font-family: monospace; color: orange; } + .tag { background-color: #eee; font-family: monospace; + padding: 2px; font-size: 80%; font-weight: normal; } + .timestamp { color: #bebebe; } + .timestamp-kwd { color: #5f9ea0; } + .org-right { margin-left: auto; margin-right: 0px; text-align: right; } + .org-left { margin-left: 0px; margin-right: auto; text-align: left; } + .org-center { margin-left: auto; margin-right: auto; text-align: center; } + .underline { text-decoration: underline; } + #postamble p, #preamble p { font-size: 90%; margin: .2em; } + p.verse { margin-left: 3%; } + pre { + border: 1px solid #ccc; + box-shadow: 3px 3px 3px #eee; + padding: 8pt; + font-family: monospace; + overflow: auto; + margin: 1.2em; + } + pre.src { + position: relative; + overflow: visible; + padding-top: 1.2em; + } + pre.src:before { + display: none; + position: absolute; + background-color: white; + top: -10px; + right: 10px; + padding: 3px; + border: 1px solid black; + } + pre.src:hover:before { display: inline;} + /* Languages per Org manual */ + pre.src-asymptote:before { content: 'Asymptote'; } + pre.src-awk:before { content: 'Awk'; } + pre.src-C:before { content: 'C'; } + /* pre.src-C++ doesn't work in CSS */ + pre.src-clojure:before { content: 'Clojure'; } + pre.src-css:before { content: 'CSS'; } + pre.src-D:before { content: 'D'; } + pre.src-ditaa:before { content: 'ditaa'; } + pre.src-dot:before { content: 'Graphviz'; } + pre.src-calc:before { content: 'Emacs Calc'; } + pre.src-emacs-lisp:before { content: 'Emacs Lisp'; } + pre.src-fortran:before { content: 'Fortran'; } + pre.src-gnuplot:before { content: 'gnuplot'; } + pre.src-haskell:before { content: 'Haskell'; } + pre.src-hledger:before { content: 'hledger'; } + pre.src-java:before { content: 'Java'; } + pre.src-js:before { content: 'Javascript'; } + pre.src-latex:before { content: 'LaTeX'; } + pre.src-ledger:before { content: 'Ledger'; } + pre.src-lisp:before { content: 'Lisp'; } + pre.src-lilypond:before { content: 'Lilypond'; } + pre.src-lua:before { content: 'Lua'; } + pre.src-matlab:before { content: 'MATLAB'; } + pre.src-mscgen:before { content: 'Mscgen'; } + pre.src-ocaml:before { content: 'Objective Caml'; } + pre.src-octave:before { content: 'Octave'; } + pre.src-org:before { content: 'Org mode'; } + pre.src-oz:before { content: 'OZ'; } + pre.src-plantuml:before { content: 'Plantuml'; } + pre.src-processing:before { content: 'Processing.js'; } + pre.src-python:before { content: 'Python'; } + pre.src-R:before { content: 'R'; } + pre.src-ruby:before { content: 'Ruby'; } + pre.src-sass:before { content: 'Sass'; } + pre.src-scheme:before { content: 'Scheme'; } + pre.src-screen:before { content: 'Gnu Screen'; } + pre.src-sed:before { content: 'Sed'; } + pre.src-sh:before { content: 'shell'; } + pre.src-sql:before { content: 'SQL'; } + pre.src-sqlite:before { content: 'SQLite'; } + /* additional languages in org.el's org-babel-load-languages alist */ + pre.src-forth:before { content: 'Forth'; } + pre.src-io:before { content: 'IO'; } + pre.src-J:before { content: 'J'; } + pre.src-makefile:before { content: 'Makefile'; } + pre.src-maxima:before { content: 'Maxima'; } + pre.src-perl:before { content: 'Perl'; } + pre.src-picolisp:before { content: 'Pico Lisp'; } + pre.src-scala:before { content: 'Scala'; } + pre.src-shell:before { content: 'Shell Script'; } + pre.src-ebnf2ps:before { content: 'ebfn2ps'; } + /* additional language identifiers per "defun org-babel-execute" + in ob-*.el */ + pre.src-cpp:before { content: 'C++'; } + pre.src-abc:before { content: 'ABC'; } + pre.src-coq:before { content: 'Coq'; } + pre.src-groovy:before { content: 'Groovy'; } + /* additional language identifiers from org-babel-shell-names in + ob-shell.el: ob-shell is the only babel language using a lambda to put + the execution function name together. */ + pre.src-bash:before { content: 'bash'; } + pre.src-csh:before { content: 'csh'; } + pre.src-ash:before { content: 'ash'; } + pre.src-dash:before { content: 'dash'; } + pre.src-ksh:before { content: 'ksh'; } + pre.src-mksh:before { content: 'mksh'; } + pre.src-posh:before { content: 'posh'; } + /* Additional Emacs modes also supported by the LaTeX listings package */ + pre.src-ada:before { content: 'Ada'; } + pre.src-asm:before { content: 'Assembler'; } + pre.src-caml:before { content: 'Caml'; } + pre.src-delphi:before { content: 'Delphi'; } + pre.src-html:before { content: 'HTML'; } + pre.src-idl:before { content: 'IDL'; } + pre.src-mercury:before { content: 'Mercury'; } + pre.src-metapost:before { content: 'MetaPost'; } + pre.src-modula-2:before { content: 'Modula-2'; } + pre.src-pascal:before { content: 'Pascal'; } + pre.src-ps:before { content: 'PostScript'; } + pre.src-prolog:before { content: 'Prolog'; } + pre.src-simula:before { content: 'Simula'; } + pre.src-tcl:before { content: 'tcl'; } + pre.src-tex:before { content: 'TeX'; } + pre.src-plain-tex:before { content: 'Plain TeX'; } + pre.src-verilog:before { content: 'Verilog'; } + pre.src-vhdl:before { content: 'VHDL'; } + pre.src-xml:before { content: 'XML'; } + pre.src-nxml:before { content: 'XML'; } + /* add a generic configuration mode; LaTeX export needs an additional + (add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */ + pre.src-conf:before { content: 'Configuration File'; } + + table { border-collapse:collapse; } + caption.t-above { caption-side: top; } + caption.t-bottom { caption-side: bottom; } + td, th { vertical-align:top; } + th.org-right { text-align: center; } + th.org-left { text-align: center; } + th.org-center { text-align: center; } + td.org-right { text-align: right; } + td.org-left { text-align: left; } + td.org-center { text-align: center; } + dt { font-weight: bold; } + .footpara { display: inline; } + .footdef { margin-bottom: 1em; } + .figure { padding: 1em; } + .figure p { text-align: center; } + .equation-container { + display: table; + text-align: center; + width: 100%; + } + .equation { + vertical-align: middle; + } + .equation-label { + display: table-cell; + text-align: right; + vertical-align: middle; + } + .inlinetask { + padding: 10px; + border: 2px solid gray; + margin: 10px; + background: #ffffcc; + } + #org-div-home-and-up + { text-align: right; font-size: 70%; white-space: nowrap; } + textarea { overflow-x: auto; } + .linenr { font-size: smaller } + .code-highlighted { background-color: #ffff00; } + .org-info-js_info-navigation { border-style: none; } + #org-info-js_console-label + { font-size: 10px; font-weight: bold; white-space: nowrap; } + .org-info-js_search-highlight + { background-color: #ffff00; color: #000000; font-weight: bold; } + .org-svg { width: 90%; } + /*]]>*/--> +</style> +</head> +<body> +<div id="content"> +<h1 class="title">Carbs Linux Installation Guide</h1> +<div id="table-of-contents"> +<h2>Table of Contents</h2> +<div id="text-table-of-contents"> +<ul> +<li><a href="#orgf69e554">1. Preparing Environment</a> +<ul> +<li><a href="#org95a0e69">1.1. Download</a></li> +<li><a href="#org8e36ac6">1.2. Signature verification</a></li> +<li><a href="#orgea2754a">1.3. Extracting the tarball</a></li> +<li><a href="#org04cd78e">1.4. Obtain the chroot helper</a></li> +</ul> +</li> +<li><a href="#org75ac2b4">2. Chroot</a> +<ul> +<li><a href="#org8778be8">2.1. Setting up repositories</a> +<ul> +<li><a href="#orga965761">2.1.1. Obtaining from git</a></li> +<li><a href="#orgb7bea54">2.1.2. Obtaining from rsync</a></li> +<li><a href="#orgb72886d">2.1.3. Making the package manager use the repositories</a></li> +</ul> +</li> +<li><a href="#org2a9ee98">2.2. Updating packages</a></li> +<li><a href="#orgf04d2d5">2.3. Installing packages</a></li> +<li><a href="#orgb80a3a8">2.4. Essential Software</a></li> +<li><a href="#org1e0d5e0">2.5. Obtaining the documentation</a></li> +</ul> +</li> +<li><a href="#orgd61a283">3. System Configuration</a> +<ul> +<li><a href="#orgc097724">3.1. Configuring hostname</a></li> +<li><a href="#org88a7ef3">3.2. Hosts file</a></li> +</ul> +</li> +<li><a href="#org92806b4">4. Kernel</a> +<ul> +<li><a href="#orgb246a4d">4.1. Obtaining the kernel sources</a></li> +<li><a href="#orgf9a076f">4.2. Kernel dependencies</a></li> +<li><a href="#orga3c74bc">4.3. Building the kernel</a></li> +</ul> +</li> +<li><a href="#orgb176eb1">5. Making your system bootable</a> +<ul> +<li><a href="#org31a5fde">5.1. Bootloader</a> +<ul> +<li><a href="#org43ed898">5.1.1. GRUB BIOS installation</a></li> +<li><a href="#orgf826efe">5.1.2. GRUB UEFI installation</a></li> +</ul> +</li> +<li><a href="#org2d43b5f">5.2. Init scripts</a></li> +<li><a href="#orgfe8161b">5.3. Fstab</a></li> +</ul> +</li> +<li><a href="#org917e2c8">6. Post-installation</a> +<ul> +<li><a href="#org96641ac">6.1. KISS repositories</a></li> +</ul> +</li> +</ul> +</div> +</div> +<p> +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 +<a href="https://carbslinux.org/docs/install.txt">https://carbslinux.org/docs/install.txt</a>. +</p> + +<div id="outline-container-orgf69e554" class="outline-2"> +<h2 id="orgf69e554"><span class="section-number-2">1</span> Preparing Environment</h2> +<div class="outline-text-2" id="text-1"> +<p> +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. +</p> + +<p> +You will need the following programs in order to install Carbs Linux: +</p> + +<ul class="org-ul"> +<li>tar</li> +<li>wget</li> +<li>xz</li> +<li>some form of base utilities (coreutils, sbase, busybox, etc.)</li> +</ul> + +<p> +Rest of these instructions will assume that you have set all of these up, and +will continue on that point. +</p> +</div> + +<div id="outline-container-org95a0e69" class="outline-3"> +<h3 id="org95a0e69"><span class="section-number-3">1.1</span> Download</h3> +<div class="outline-text-3" id="text-1-1"> +<p> +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 <code>x86_64</code> +with <code>i686</code>. We are setting this in a URL variable so that we don't have to +write it every time. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">wget $<span style="color: #8e44ad;">URL</span>/carbs-rootfs.tar.xz.sha256 +sha256sum -c carbs-rootfs.tar.xz.sha256 +</pre> +</div> +</div> +</div> + +<div id="outline-container-org8e36ac6" class="outline-3"> +<h3 id="org8e36ac6"><span class="section-number-3">1.2</span> Signature verification</h3> +<div class="outline-text-3" id="text-1-2"> +<p> +It is highly recommended to verify the signature of the tarball. You will need +GPG for this. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">wget $<span style="color: #8e44ad;">URL</span>/carbs-rootfs.tar.xz.sig +gpg --recv-keys FF484BDFEFCEF8FF +gpg --verify carbs-rootfs.tar.xz.sig +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgea2754a" class="outline-3"> +<h3 id="orgea2754a"><span class="section-number-3">1.3</span> Extracting the tarball</h3> +<div class="outline-text-3" id="text-1-3"> +<p> +You will need to extract the tarball to your desired location. For partitioning, +you can follow <a href="https://wiki.archlinux.org/index.php/Partitioning">this guide</a>. This will assume that you will be mounting your root +partition to <code>/mnt</code>. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">mount /dev/sdx1 /mnt +tar xf carbs-rootfs.tar.xz -C /mnt +</pre> +</div> +</div> +</div> + +<div id="outline-container-org04cd78e" class="outline-3"> +<h3 id="org04cd78e"><span class="section-number-3">1.4</span> Obtain the chroot helper</h3> +<div class="outline-text-3" id="text-1-4"> +<p> +You can obtain the <code>cpt-chroot</code> script in order to do a simple chroot into your +new root filesystem. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">wget https://dl.carbslinux.org/distfiles/cpt-chroot +chmod a+x cpt-chroot +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-org75ac2b4" class="outline-2"> +<h2 id="org75ac2b4"><span class="section-number-2">2</span> Chroot</h2> +<div class="outline-text-2" id="text-2"> +<p> Chroot into Carbs Linux! +</p> - $ ./cpt-chroot /mnt - -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.2.1.1 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 - -1.2.1.2 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> - * <<a href=https://github.com/carbslinux/repository>>https://github.com/carbslinux/repository></a> - - $ git clone git://git.carbslinux.org/repository $HOME/repos/carbs - -1.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: - - export CPT_PATH='' - CPT_PATH=$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 - -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 - -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 - -1.2.4 Essential Software ------------------------- - +<div class="org-src-container"> +<pre class="src src-sh">./cpt-chroot /mnt +</pre> +</div> +</div> + +<div id="outline-container-org8778be8" class="outline-3"> +<h3 id="org8778be8"><span class="section-number-3">2.1</span> Setting up repositories</h3> +<div class="outline-text-3" id="text-2-1"> +<p> +Newest tarballs do not come with repositories, so you will need to manually +obtain them, and set your <code>CPT_PATH</code> environment variable. Carbs Linux +repositories can either be obtained by <code>git</code> or <code>rsync</code>. 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 <code>git</code> itself. +</p> + +<p> +The following guide will assume that you put the repositories into <code>~/repos/</code> +directory, but you can put the repositories into any directory you want. So go +ahead and create that directory: +</p> + +<div class="org-src-container"> +<pre class="src src-sh">mkdir -p $<span style="color: #8e44ad;">HOME</span>/repos +</pre> +</div> +</div> + +<div id="outline-container-orga965761" class="outline-4"> +<h4 id="orga965761"><span class="section-number-4">2.1.1</span> Obtaining from git</h4> +<div class="outline-text-4" id="text-2-1-1"> +<p> +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. +</p> + +<ul class="org-ul"> +<li>git://git.carbslinux.org/repository</li> +<li><a href="https://github.com/carbslinux/repository">https://github.com/carbslinux/repository</a></li> +</ul> + +<div class="org-src-container"> +<pre class="src src-sh">git clone git://git.carbslinux.org/repository $<span style="color: #8e44ad;">HOME</span>/repos/carbs +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgb7bea54" class="outline-4"> +<h4 id="orgb7bea54"><span class="section-number-4">2.1.2</span> Obtaining from rsync</h4> +<div class="outline-text-4" id="text-2-1-2"> +<p> +Carbs Linux rsync repositories live in rsync://carbslinux.org/repo. In +order to obtain it, run the following: +</p> + +<div class="org-src-container"> +<pre class="src src-sh">rsync -avc rsync://carbslinux.org/repo $<span style="color: #8e44ad;">HOME</span>/repos/carbs +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgb72886d" class="outline-4"> +<h4 id="orgb72886d"><span class="section-number-4">2.1.3</span> Making the package manager use the repositories</h4> +<div class="outline-text-4" id="text-2-1-3"> +<p> +In your shell's configuration file, or in your <code>~/.profile</code> file, add the +following lines: +</p> + +<div class="org-src-container"> +<pre class="src src-sh"><span style="color: #8e44ad;">CPT_PATH</span>=$<span style="color: #8e44ad;">HOME</span>/repos/carbs/core +<span style="color: #8e44ad;">CPT_PATH</span>=$<span style="color: #8e44ad;">CPT_PATH</span>:$<span style="color: #8e44ad;">HOME</span>/repos/carbs/extra +<span style="color: #8e44ad;">CPT_PATH</span>=$<span style="color: #8e44ad;">CPT_PATH</span>:$<span style="color: #8e44ad;">HOME</span>/repos/carbs/xorg +<span style="color: #8e44ad;">CPT_PATH</span>=$<span style="color: #8e44ad;">CPT_PATH</span>:$<span style="color: #8e44ad;">HOME</span>/repos/carbs/community +<span style="color: #16a085;">export</span> CPT_PATH +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-org2a9ee98" class="outline-3"> +<h3 id="org2a9ee98"><span class="section-number-3">2.2</span> Updating packages</h3> +<div class="outline-text-3" id="text-2-2"> +<p> +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. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">cpt-update && cpt-update +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgf04d2d5" class="outline-3"> +<h3 id="orgf04d2d5"><span class="section-number-3">2.3</span> Installing packages</h3> +<div class="outline-text-3" id="text-2-3"> +<p> +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. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">cpt-build package +cpt-install package +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgb80a3a8" class="outline-3"> +<h3 id="orgb80a3a8"><span class="section-number-3">2.4</span> Essential Software</h3> +<div class="outline-text-3" id="text-2-4"> +<p> 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 - * nvi - * emacs - * emacs-nox (terminal-only version of emacs) - USER SHELLS - * bash - * zsh - * dash - * oksh - * rc - POSIX BASE UTILITIES - * busybox - * sbase - * coreutils - DOCUMENTATION - * carbs-docs - * man-pages - * man-pages-posix - -1.2.5 Obtaining the documentation (optional) --------------------------------------------- - -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 - -1.3 System Configuration -======================== - -After you have finished installing some extra packages, you can -configure your system to your liking. - -1.3.1 Configuring hostname (recommended) ----------------------------------------- - -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 - -1.3.2 Setting up hosts file (optional) --------------------------------------- - -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 - -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 -(<a href=https://github.com/cemkeylan/kiss-repository/tree/master/personal/linux>https://github.com/cemkeylan/kiss-repository/tree/master/personal/linux</a>), -which you will need to reconfigure for your specific setup if you want -to make use of it. - -1.4.1 Obtaining the kernel sources ----------------------------------- - -You can visit the <a href=https://kernel.org>https://kernel.org</a> 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 <a href=https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.7.6.tar.xz>https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.7.6.tar.xz</a> - $ tar xf linux-5.7.6.tar.xz - - Change directory into the kernel sources - $ cd linux-5.7.6 - -1.4.2 Installing dependencies ------------------------------ - -In order to compile the kernel you will need to install some -dependencies. You will need 'libelf' 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 (<a href=https://github.com/E5ten>https://github.com/E5ten</a>). You will -need to obtain and apply the patch in the kernel source directory. - - $ wget <a href=https://dl.carbslinux.org/distfiles/kernel-no-perl.patch>https://dl.carbslinux.org/distfiles/kernel-no-perl.patch</a> - $ patch -p1 < kernel-no-perl.patch - -1.4.3 Compiling the kernel --------------------------- - -Next step is configuring and building the kernel. You can check -Gentoo's kernel configuration guide -(<a href=https://wiki.gentoo.org/wiki/Kernel/Configuration>https://wiki.gentoo.org/wiki/Kernel/Configuration</a>) 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 - -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. - -1.5.1 Installing a 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). - - GRUB BIOS installation - - $ cpt b grub && cpt i grub - $ grub-install --target=i386-pc /dev/sdX - $ grub-mkconfig -o /boot/grub/grub.cfg - - 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 - -1.5.2 Installing 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 - -1.5.3 Generating 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 <a href=https://github.com/cemkeylan/genfstab/raw/master/genfstab>https://github.com/cemkeylan/genfstab/raw/master/genfstab</a> - $ chmod +x genfstab - $ ./genfstab -U /mnt >> /mnt/etc/fstab - -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. - -1.6.1 Acquiring 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. - - $ git clone <a href=https://github.com/kisslinux/community>https://github.com/kisslinux/community</a> $HOME/repos/kiss-community - $ export CPT_PATH=$CPT_PATH:$HOME/repos/kiss-community/community - - NOTE: There are lots of packages on the KISS community repository -that are also on Carbs Linux main repository. I would advise giving -lower priority to the KISS community repository as it may affect other -packages that you might install. - +</p> + +<p> +<b>BOOTLOADERS</b> +</p> + +<ul class="org-ul"> +<li>efibootmgr</li> +<li>grub</li> +</ul> + +<p> +<b>FILESYSTEMS</b> +</p> + +<ul class="org-ul"> +<li>e2fsprogs</li> +<li>dosfstools</li> +<li>ntfs-3g</li> +</ul> + +<p> +<b>NETWORKING</b> +</p> + +<ul class="org-ul"> +<li>dhcpcd</li> +<li>wpa<sub>supplicant</sub></li> +</ul> + +<p> +<b>TEXT EDITORS</b> +</p> + +<ul class="org-ul"> +<li>nano</li> +<li>vim</li> +<li>neatvi</li> +<li>emacs</li> +<li>emacs-nox (terminal-only version of emacs)</li> +</ul> + +<p> +<b>USER SHELLS</b> +</p> + +<ul class="org-ul"> +<li>bash</li> +<li>zsh</li> +<li>oksh</li> +<li>rc</li> +</ul> + +<p> +<b>POSIX BASE UTILITIES</b> +</p> + +<ul class="org-ul"> +<li>busybox</li> +<li>sbase</li> +<li>coreutils</li> +</ul> + +<p> +<b>DOCUMENTATION</b> +</p> + +<ul class="org-ul"> +<li>carbs-docs</li> +<li>man-pages</li> +<li>man-pages-posix</li> +</ul> +</div> +</div> + +<div id="outline-container-org1e0d5e0" class="outline-3"> +<h3 id="org1e0d5e0"><span class="section-number-3">2.5</span> Obtaining the documentation</h3> +<div class="outline-text-3" id="text-2-5"> +<p> +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. +</p> + +<div class="org-src-container"> +<pre class="src src-sh"><span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">Install the documentation.</span> +cpt b carbs-docs && cpt i carbs-docs + +<span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">Install either texinfo or the info package. We will be installing standalone info</span> +<span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">as it doesn't need perl.</span> +cpt b info && cpt i info + +<span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">You can then run info and navigate through the documentation.</span> +info carbslinux +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-orgd61a283" class="outline-2"> +<h2 id="orgd61a283"><span class="section-number-2">3</span> System Configuration</h2> +<div class="outline-text-2" id="text-3"> +<p> +After you have finished installing some extra packages, you can configure your +system to your liking. +</p> +</div> + +<div id="outline-container-orgc097724" class="outline-3"> +<h3 id="orgc097724"><span class="section-number-3">3.1</span> Configuring hostname</h3> +<div class="outline-text-3" id="text-3-1"> +<p> +You might want to add a hostname, especially in a networked environment. Your +hostname will default to 'carbslinux' unless you set this. +</p> + +<div class="org-src-container"> +<pre class="src src-sh"><span style="color: #16a085;">echo</span> your-hostname > /etc/hostname </pre> - <a href="/docs/install.txt">View Page Source</a> - <div class="border"></div> - <p class=footer>Linux® is a registered trademark of Linus Torvalds</p> - <p class=footer>Copyright © 2019-2020 Cem Keylan</p> - </body> +</div> +</div> +</div> + +<div id="outline-container-org88a7ef3" class="outline-3"> +<h3 id="org88a7ef3"><span class="section-number-3">3.2</span> Hosts file</h3> +<div class="outline-text-3" id="text-3-2"> +<p> +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. +</p> + +<pre class="example"> +127.0.0.1 localhost.localdomain localhost +::1 localhost.localdomain localhost ip6-localhost +</pre> +</div> +</div> +</div> + +<div id="outline-container-org92806b4" class="outline-2"> +<h2 id="org92806b4"><span class="section-number-2">4</span> Kernel</h2> +<div class="outline-text-2" id="text-4"> +<p> +Kernel isn't managed under the main repositories, even though you could package +one for your personal use. Here is an <a href="https://github.com/cemkeylan/kiss-repository/tree/master/personal/linux">example kernel package</a>, which you will +need to reconfigure for your specific setup if you want to make use of it. +</p> +</div> + +<div id="outline-container-orgb246a4d" class="outline-3"> +<h3 id="orgb246a4d"><span class="section-number-3">4.1</span> Obtaining the kernel sources</h3> +<div class="outline-text-3" id="text-4-1"> +<p> +You can visit the <a href="https://kernel.org">https://kernel.org</a> website to choose a kernel that you want +to install. Though only the latest stable and longterm (LTS) versions are +supported. +</p> + +<div class="org-src-container"> +<pre class="src src-sh"><span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">Download the kernel and extract it</span> +wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.9.1.tar.xz +tar xf linux-5.9.1.tar.xz + +<span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">Change directory into the kernel sources</span> +<span style="color: #16a085;">cd</span> linux-5.9.1 +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgf9a076f" class="outline-3"> +<h3 id="orgf9a076f"><span class="section-number-3">4.2</span> Kernel dependencies</h3> +<div class="outline-text-3" id="text-4-2"> +<p> +In order to compile the kernel you will need to install some dependencies. You +will need <code>libelf</code> to compile the kernel. If you want to configure using the +menu interface you will also need <code>ncurses</code>. +</p> + +<div class="org-src-container"> +<pre class="src src-sh"><span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">The package manager asks to install if you are building more than one package,</span> +<span style="color: #95a5a6;"># </span><span style="color: #7f8c8d;">so no need to run 'cpt i ...'</span> +cpt b libelf ncurses +</pre> +</div> + +<p> +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 <a href="https://github.com/E5ten">E5ten</a>. You will need to obtain and apply the patch in the kernel +source directory. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">wget https://dl.carbslinux.org/distfiles/kernel-no-perl.patch +patch -p1 < kernel-no-perl.patch +</pre> +</div> +</div> +</div> + +<div id="outline-container-orga3c74bc" class="outline-3"> +<h3 id="orga3c74bc"><span class="section-number-3">4.3</span> Building the kernel</h3> +<div class="outline-text-3" id="text-4-3"> +<p> +Next step is configuring and building the kernel. You can check Gentoo's +<a href="https://wiki.gentoo.org/wiki/Kernel/Configuration">kernel configuration guide</a> 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. +</p> + +<div class="org-src-container"> +<pre class="src src-sh">make menuconfig +make +install -Dm755 $(make -s image_name) /boot/vmlinuz-linux +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-orgb176eb1" class="outline-2"> +<h2 id="orgb176eb1"><span class="section-number-2">5</span> Making your system bootable</h2> +<div class="outline-text-2" id="text-5"> +<p> +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. +</p> +</div> + +<div id="outline-container-org31a5fde" class="outline-3"> +<h3 id="org31a5fde"><span class="section-number-3">5.1</span> Bootloader</h3> +<div class="outline-text-3" id="text-5-1"> +<p> +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). +</p> +</div> + +<div id="outline-container-org43ed898" class="outline-4"> +<h4 id="org43ed898"><span class="section-number-4">5.1.1</span> GRUB BIOS installation</h4> +<div class="outline-text-4" id="text-5-1-1"> +<div class="org-src-container"> +<pre class="src src-sh">cpt b grub && cpt i grub +grub-install --target=i386-pc /dev/sdX +grub-mkconfig -o /boot/grub/grub.cfg +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgf826efe" class="outline-4"> +<h4 id="orgf826efe"><span class="section-number-4">5.1.2</span> GRUB UEFI installation</h4> +<div class="outline-text-4" id="text-5-1-2"> +<div class="org-src-container"> +<pre class="src src-sh">cpt b efibootmgr && cpt i efibootmgr +cpt b grub && cpt i grub + +grub-install --target=x86_64-efi <span style="color: #0a74b9;">\</span> + --efi-directory=esp <span style="color: #0a74b9;">\</span> + --bootloader-id=CarbsLinux + +grub-mkconfig -o /boot/grub/grub.cfg +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-org2d43b5f" class="outline-3"> +<h3 id="org2d43b5f"><span class="section-number-3">5.2</span> Init scripts</h3> +<div class="outline-text-3" id="text-5-2"> +<p> +Only thing left to do is installing the init-scripts, and now you are almost +ready to boot your system! +</p> + +<div class="org-src-container"> +<pre class="src src-sh">cpt b carbs-init && cpt i carbs-init +</pre> +</div> +</div> +</div> + +<div id="outline-container-orgfe8161b" class="outline-3"> +<h3 id="orgfe8161b"><span class="section-number-3">5.3</span> Fstab</h3> +<div class="outline-text-3" id="text-5-3"> +<p> +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: +</p> + +<div class="org-src-container"> +<pre class="src src-sh">wget https://github.com/cemkeylan/genfstab/raw/master/genfstab +chmod +x genfstab +./genfstab -U /mnt >> /mnt/etc/fstab +</pre> +</div> +</div> +</div> +</div> + +<div id="outline-container-org917e2c8" class="outline-2"> +<h2 id="org917e2c8"><span class="section-number-2">6</span> Post-installation</h2> +<div class="outline-text-2" id="text-6"> +<p> +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. +</p> +</div> + +<div id="outline-container-org96641ac" class="outline-3"> +<h3 id="org96641ac"><span class="section-number-3">6.1</span> KISS repositories</h3> +<div class="outline-text-3" id="text-6-1"> +<p> +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. +</p> +</div> +</div> +</div> +</div> +</body> </html> |