From 22940b398010e3b653052dd27d0ac6fddbdae83c Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Sat, 27 Jun 2020 23:22:15 +0300 Subject: update --- docs/wiki/boot/module-management.html | 34 ---- docs/wiki/boot/module-management.txt | 14 -- docs/wiki/index.html | 41 ---- docs/wiki/index.txt | 17 -- docs/wiki/init/switching-to-sinit.html | 68 ------- docs/wiki/init/switching-to-sinit.txt | 51 ----- docs/wiki/install.html | 337 ------------------------------- docs/wiki/install.txt | 309 ---------------------------- docs/wiki/keymaps/X-keymaps.html | 23 --- docs/wiki/keymaps/X-keymaps.txt | 0 docs/wiki/keymaps/keymaps.html | 74 ------- docs/wiki/keymaps/keymaps.txt | 52 ----- docs/wiki/system/service-management.html | 99 --------- docs/wiki/system/service-management.txt | 81 -------- 14 files changed, 1200 deletions(-) delete mode 100644 docs/wiki/boot/module-management.html delete mode 100644 docs/wiki/boot/module-management.txt delete mode 100644 docs/wiki/index.html delete mode 100644 docs/wiki/index.txt delete mode 100644 docs/wiki/init/switching-to-sinit.html delete mode 100644 docs/wiki/init/switching-to-sinit.txt delete mode 100644 docs/wiki/install.html delete mode 100644 docs/wiki/install.txt delete mode 100644 docs/wiki/keymaps/X-keymaps.html delete mode 100644 docs/wiki/keymaps/X-keymaps.txt delete mode 100644 docs/wiki/keymaps/keymaps.html delete mode 100644 docs/wiki/keymaps/keymaps.txt delete mode 100644 docs/wiki/system/service-management.html delete mode 100644 docs/wiki/system/service-management.txt (limited to 'docs/wiki') diff --git a/docs/wiki/boot/module-management.html b/docs/wiki/boot/module-management.html deleted file mode 100644 index a77685d..0000000 --- a/docs/wiki/boot/module-management.html +++ /dev/null @@ -1,34 +0,0 @@ - - - -Module Management | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Module Management

- -

With busybox-init, a module can be loaded at boot by adding such a line to your inittab

- -
::once:/bin/modprobe module-name
-
- -

With sinit, a module can be loaded from your /etc/rc.local file. Add this to your file

- -
/bin/modprobe module-name
-
-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/boot/module-management.txt b/docs/wiki/boot/module-management.txt deleted file mode 100644 index 96256c1..0000000 --- a/docs/wiki/boot/module-management.txt +++ /dev/null @@ -1,14 +0,0 @@ - -Module Management -================= - -With **busybox-init**, a module can be loaded at boot by adding such a line to your `inittab` - - ::once:/bin/modprobe module-name - - -With **sinit**, a module can be loaded from your `/etc/rc.local` file. Add this to your file - - /bin/modprobe module-name - - diff --git a/docs/wiki/index.html b/docs/wiki/index.html deleted file mode 100644 index 10843fb..0000000 --- a/docs/wiki/index.html +++ /dev/null @@ -1,41 +0,0 @@ - - - -Wiki | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Wiki

- -

Welcome to the Carbs Linux wiki! This wiki is open for access, and can be edited -freely by anyone who wants to contribute.

- -

If you want to make a contribution, go to https://github.com/CarbsLinux/wiki

- -

Content

- - - -View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/index.txt b/docs/wiki/index.txt deleted file mode 100644 index 3d64de9..0000000 --- a/docs/wiki/index.txt +++ /dev/null @@ -1,17 +0,0 @@ -Wiki -================================================================================ - -Welcome to the Carbs Linux wiki! This wiki is open for access, and can be edited -freely by anyone who wants to contribute. - -If you want to make a contribution, go to - -Content --------------------------------------------------------------------------------- - -* [Module Management](boot/module-management.html) -* [Switching to Sinit](init/switching-to-sinit.html) -* [Install](install.html) -* [X-keymaps](keymaps/X-keymaps.html) -* [Keymaps in TTY](keymaps/keymaps.html) -* [Service Management](system/service-management.html) diff --git a/docs/wiki/init/switching-to-sinit.html b/docs/wiki/init/switching-to-sinit.html deleted file mode 100644 index 775e01c..0000000 --- a/docs/wiki/init/switching-to-sinit.html +++ /dev/null @@ -1,68 +0,0 @@ - - - -Switching to Sinit | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Switching to Sinit

- -

Carbs Linux runs busybox-init by default. You can switch to -anything else you desire, but only busybox-init and sinit are -officially supported. Switching to sinit is extremely easy, you -can be up and running within minutes. The only “hard” requirement -is an environment you will be chrooting in. So, let’s begin!

- -

Preparing your environment

- -

From your other environment, download the kiss-chroot utility -and make it executable.

- -
$ wget https://dl.getkiss.org/kiss-chroot
-$ chmod +x kiss-chroot
-
-# From your environment start the chroot
-$ kiss-chroot /mnt
-
- -

Removing busybox-init

- -

Now that we are in chroot environment, let’s remove busybox-init.

- -
$ kiss r busybox-init
-
- -

Installing and configuring sinit

- -

Build and install sinit

- -
$ kiss b sinit
-$ kiss i sinit
-
- -

Open up your /etc/init/rc.conf now and uncomment -the variables regarding SINIT. You are ready now.

- -

If you edited your inittab, make sure you reflect your changes -on the /etc/init/sinit-launch-services.boot file.

- -

Finishing up

- -

If all of the above is done, simply exit the chroot and reboot. -Sinit should be functioning without any issues.

-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/init/switching-to-sinit.txt b/docs/wiki/init/switching-to-sinit.txt deleted file mode 100644 index 3bee312..0000000 --- a/docs/wiki/init/switching-to-sinit.txt +++ /dev/null @@ -1,51 +0,0 @@ - -Switching to Sinit -================== - -Carbs Linux runs `busybox-init` by default. You can switch to -anything else you desire, but only busybox-init and sinit are -officially supported. Switching to sinit is extremely easy, you -can be up and running within minutes. The only "hard" requirement -is an environment you will be chrooting in. So, let's begin! - - -Preparing your environment --------------------------- - -From your other environment, download the kiss-chroot utility -and make it executable. - - $ wget https://dl.getkiss.org/kiss-chroot - $ chmod +x kiss-chroot - - # From your environment start the chroot - $ kiss-chroot /mnt - -Removing busybox-init ---------------------- - -Now that we are in chroot environment, let's remove busybox-init. - - $ kiss r busybox-init - - -Installing and configuring sinit --------------------------------- - -Build and install sinit - - $ kiss b sinit - $ kiss i sinit - -Open up your `/etc/init/rc.conf` now and uncomment -the variables regarding SINIT. You are ready now. - -If you edited your inittab, make sure you reflect your changes -on the `/etc/init/sinit-launch-services.boot` file. - - -Finishing up ------------- - -If all of the above is done, simply exit the chroot and reboot. -Sinit should be functioning without any issues. diff --git a/docs/wiki/install.html b/docs/wiki/install.html deleted file mode 100644 index e9c882b..0000000 --- a/docs/wiki/install.html +++ /dev/null @@ -1,337 +0,0 @@ - - - -Install | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Installation Instructions

- -

This post will guide you step-by-step in order to install -Carbs Linux. It is not complete yet.

- -

Downloading and Getting Ready to Chroot

- -

Installing Carbs Linux is the same as installing most -rootfs distributions, such as Gentoo, or Void Linux.

- -

Requirements

- -

You simply need a Live Linux ISO. Gentoo would be the best -as programs you will require will be already there. Get the -ISO, boot it and set up your network.

- -

Required Programs:

- - - - -

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

- -

Download

- -

First, we need to download the rootfs tarball. In your terminal -type

- -
$ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz
-
- -

Check the integrity of the tarball

- -

While optional, it is highly recommended to check the integrity -of the tarball.

- -
$ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sha256sum
-$ sha256sum -c carbs-rootfs-20191210.tar.xz.sha256sum
-
- -

Check the signatures

- -

While optional, it is highly recommended to check the signature -of the tarball

- -
$ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sig
-
-Import the public key of release@carbslinux.org
-
-$ gpg --recv-keys FF484BDFEFCEF8FF
-
-$ gpg --verify carbs-rootfs-20191210.tar.xz.sig
-
- -

Download Kiss Linux Chroot Helper

- -
$ wget https://dl.getkiss.org/kiss-chroot
-
-Make the script executable
-
-$ chmod +x kiss-chroot
-
- -

Extract the rootfs tarball

- -

You need to extract the tarball to your mounted partition

- -
$ tar xvpf carbs-rootfs-20191210.tar.xz -C /mnt
-
- -

Chroot

- -

Chroot into Carbs Linux

- -
$ ./kiss-chroot /mnt
-
- -

Enable repository signing (Highly Recommended)

- -

This step is optional, but very highly recommended -(I cannot stress out the amount I am recommending this). -This ensures you are receiving updates from Carbs Linux -and not some other source.

- -

Install GnuPG

- -

It is also a great time to learn how to use your new -package manager, KISS! You simply build and install -the package

- -
$ kiss build gnupg1
-$ kiss install gnupg1
-
- -

Import my key

- -
Import my public key (cem@ckyln.com)
-
-$ gpg --recv-key 4356EE08A364CE09
-
-Create a .gnupg directory if it doesn't exist
-
-$ mkdir -p /root/.gnupg
-
-Trust my public key
-
-$ echo trusted-key 0x4356ee08a364ce09 >> /root/.gnupg/gpg.conf
-
- -

Enable signature verification

- -

Git has a built in signature verification feature. -You can go to the repository directory and enable it

- -
$ cd /var/db/kiss/repo
-$ git config merge.verifySignatures true
-
- -

Installing Important Tools

- -

Since Carbs gives you one of the most minimal base, -you might need to apply some add-ons to your system.

- -

Update packages

- -

It might be a good idea to update your packages before -installing new packages. This ensure compatibility.

- -
$ kiss update
-
- -

Filesystems

- -

Currently, e2fsprogs and dosfstools are supported, -as they are the most-used filesystems.

- -
Support for ext2, ext3, and ex4
-
-$ kiss build e2fsprogs
-$ kiss install e2fsprogs
-
-Support for dosfstools
-
-$ kiss build dosfstools
-$ kiss install dosfstools
-
- -

Device management

- -
$ kiss build eudev
-$ kiss install eudev
-
- -

Wireless

- -

wpa_supplicant

- -
$ kiss build wpa_supplicant
-$ kiss install wpa_supplicant
-
- -

eiwd (WIP)

- -
$ kiss build eiwd
-$ kiss install eiwd
-
- -

dhcpcd

- -
$ kiss build dhcpcd
-$ kiss install dhcpcd
-
- -

Shells

- -

Carbs Linux comes preinstalled with busybox ash, but other shells -can be found on the repository

- -
Install bash
-
-$ kiss build bash
-$ kiss install bash
-
-Install zsh
-
-$ kiss build zsh
-$ kiss install zsh
-
-Install Plan9 rc-shell
-
-$ kiss build 9base
-$ kiss install 9base
-
- -

Install the Kernel

- -

IMPORTANT: If you have GCC 10.x on your system, you need to apply -this patch to your kernel sources. Otherwise your kernel will panic -during the boot stage.

- -

Next step is installing the kernel, which might sound as a challenge -you should download and extract the kernel tarball first.

- -
$ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz
-
-Let's move the sources to /usr/src
-
-$ mv linux-5.5.tar.xz /usr/src
-$ tar xf linux-5.5.tar.xz
-$ cd linux-5.5
-
- -

Configure the Kernel

- -

You can check https://wiki.gentoo.org/wiki/Kernel/Configuration -to learn more about kernel configuration. Overall, Gentoo Wiki -is a good place to learn about kernel configuration related to -your hardware.

- -

Build and install the kernel

- -

The rest of it is simple, build the kernel with -make and install it with make install

- -

Bootloader

- -

The default bootloader is GRUB (GRand Unified Bootloader).

- -

Build and install GRUB

- -
$ kiss b grub
-$ kiss i grub
-
-Install efibootmgr as well if your
-system requires it
-
-$ kiss b efibootmgr
-$ kiss i efibootmgr
-
- -

Setup GRUB

- -
For BIOS:
-$ grub-install --target=i386-pc /dev/sdX
-
-For UEFI:
-$ grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=CarbsLinux
-
-$ grub-mkconfig -o /boot/grub/grub.cfg
-
- -

Install init

- -

Currently, default init for Carbs Linux is sinit, but -busybox-init is also supported. You can also change this yourself.

- -

To install init, you have to

- -
$ kiss b sinit
-$ kiss i sinit
-
- -

This will also fetch busybox-init as its dependency.

- -

Enabling other repositories

- -

There are other repositories out there that might be of your -interest. The Official Repositories come with community and testing -repositories that are not enabled by default. You could also want to -add the Kiss Linux community repository, or someone’s personal kiss -repository.

- -

Obtaining repositories

- -

Obtaining a repository is as simple as a git clone. You can do it -with Cem’s personal repository as an example, but any other repository -will be the same.

- -
# Clone the repository to your desired location
-# Optionally add "--depth 1" to save precious disk space
-
-$ git clone --depth 1 git://git.ckyln.com/kiss-repository /var/db/kiss/cem-repository
-
- -

That’s it, you have obtained a new repository!

- -

Adding a repository to your KISS_PATH

- -

Now that we have obtained Cem’s repository, we can add it to our KISS_PATH!

- -

We need to edit /etc/profile.d/kiss_path.sh for this, but you -can also change your KISS_PATH from your shellrc.

- -

Add the full path to the repository, in this case -/var/db/kiss/cem-repository/cem to the variable -and add a : before/after it.

- -

It must be looking like this.

- -
export KISS_PATH=/var/db/kiss/repo/core:/var/db/kiss/repo/extra:/var/db/kiss/repo/xorg:/var/db/kiss/cem-repository/cem
-
- -

Update your shell variables by doing . /etc/profile.d/kiss_path.sh so you can -immediately access the repository packages

- -

More

- -

You should now be able to boot into you Carbs Linux installation. -To learn more, you can visit the wiki

-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/install.txt b/docs/wiki/install.txt deleted file mode 100644 index 81f87d1..0000000 --- a/docs/wiki/install.txt +++ /dev/null @@ -1,309 +0,0 @@ - -Installation Instructions -========================= - -This post will guide you step-by-step in order to install -Carbs Linux. It is not complete yet. - - -Downloading and Getting Ready to Chroot ---------------------------------------- - -Installing Carbs Linux is the same as installing most -rootfs distributions, such as Gentoo, or Void Linux. - - -### Requirements - -You simply need a Live Linux ISO. Gentoo would be the best -as programs you will require will be already there. Get the -ISO, boot it and set up your network. - -**Required Programs:** - -* tar -* wget -* xz - -Rest of the instructions assume that you have set all of these -up, and will continue on. - - -### Download - - -First, we need to download the rootfs tarball. In your terminal -type - - $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz - - -### Check the integrity of the tarball - -While optional, it is highly recommended to check the integrity -of the tarball. - - $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sha256sum - $ sha256sum -c carbs-rootfs-20191210.tar.xz.sha256sum - - -### Check the signatures - -While optional, it is highly recommended to check the signature -of the tarball - - $ wget https://carbslinux.org/releases/carbs-rootfs-20191210.tar.xz.sig - - Import the public key of release@carbslinux.org - - $ gpg --recv-keys FF484BDFEFCEF8FF - - $ gpg --verify carbs-rootfs-20191210.tar.xz.sig - -### Download Kiss Linux Chroot Helper - - $ wget https://dl.getkiss.org/kiss-chroot - - Make the script executable - - $ chmod +x kiss-chroot - -### Extract the rootfs tarball - -You need to extract the tarball to your mounted partition - - $ tar xvpf carbs-rootfs-20191210.tar.xz -C /mnt - -Chroot ------- -Chroot into Carbs Linux - - $ ./kiss-chroot /mnt - -### Enable repository signing (Highly Recommended) - -This step is optional, but very highly recommended -(I cannot stress out the amount I am recommending this). -This ensures you are receiving updates from Carbs Linux -and not some other source. - -**Install GnuPG** - -It is also a great time to learn how to use your new -package manager, KISS! You simply build and install -the package - - $ kiss build gnupg1 - $ kiss install gnupg1 - -**Import my key** - - - Import my public key (cem@ckyln.com) - - $ gpg --recv-key 4356EE08A364CE09 - - Create a .gnupg directory if it doesn't exist - - $ mkdir -p /root/.gnupg - - Trust my public key - - $ echo trusted-key 0x4356ee08a364ce09 >> /root/.gnupg/gpg.conf - -**Enable signature verification** - - -Git has a built in signature verification feature. -You can go to the repository directory and enable it - - $ cd /var/db/kiss/repo - $ git config merge.verifySignatures true - -### Installing Important Tools - -Since Carbs gives you one of the most minimal base, -you might need to apply some add-ons to your system. - -**Update packages** - -It might be a good idea to update your packages before -installing new packages. This ensure compatibility. - - $ kiss update - -**Filesystems** - - -Currently, e2fsprogs and dosfstools are supported, -as they are the most-used filesystems. - - Support for ext2, ext3, and ex4 - - $ kiss build e2fsprogs - $ kiss install e2fsprogs - - Support for dosfstools - - $ kiss build dosfstools - $ kiss install dosfstools - -**Device management** - - $ kiss build eudev - $ kiss install eudev - -**Wireless** - -**wpa_supplicant** - - $ kiss build wpa_supplicant - $ kiss install wpa_supplicant - -**eiwd (WIP)** - - $ kiss build eiwd - $ kiss install eiwd - -**dhcpcd** - - $ kiss build dhcpcd - $ kiss install dhcpcd - -**Shells** - -Carbs Linux comes preinstalled with busybox ash, but other shells -can be found on the repository - - Install bash - - $ kiss build bash - $ kiss install bash - - Install zsh - - $ kiss build zsh - $ kiss install zsh - - Install Plan9 rc-shell - - $ kiss build 9base - $ kiss install 9base - - -### Install the Kernel - -**IMPORTANT:** If you have GCC 10.x on your system, you need to apply -this [patch] to your kernel sources. Otherwise your kernel will panic -during the boot stage. - -Next step is installing the kernel, which might sound as a challenge -you should download and extract the kernel tarball first. - - $ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz - - Let's move the sources to /usr/src - - $ mv linux-5.5.tar.xz /usr/src - $ tar xf linux-5.5.tar.xz - $ cd linux-5.5 - -[patch]: https://dl.carbslinux.org/distfiles/linux-gcc-10-bootfix.patch - -**Configure the Kernel** - -You can check -to learn more about kernel configuration. Overall, [Gentoo Wiki](https://wiki.gentoo.org) -is a good place to learn about kernel configuration related to -your hardware. - -**Build and install the kernel** - -The rest of it is simple, build the kernel with -`make` and install it with `make install` - -### Bootloader - -The default bootloader is GRUB (GRand Unified Bootloader). - -Build and install GRUB - - $ kiss b grub - $ kiss i grub - - Install efibootmgr as well if your - system requires it - - $ kiss b efibootmgr - $ kiss i efibootmgr - - -**Setup GRUB** - - For BIOS: - $ grub-install --target=i386-pc /dev/sdX - - For UEFI: - $ grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=CarbsLinux - - $ grub-mkconfig -o /boot/grub/grub.cfg - - -### Install init - -Currently, default init for Carbs Linux is `sinit`, but -busybox-init is also supported. You can also change this yourself. - -To install init, you have to - - $ kiss b sinit - $ kiss i sinit - -This will also fetch busybox-init as its dependency. - - -### Enabling other repositories - -There are other repositories out there that might be of your -interest. The Official Repositories come with community and testing -repositories that are not enabled by default. You could also want to -add the Kiss Linux community repository, or someone's personal kiss -repository. - -**Obtaining repositories** - -Obtaining a repository is as simple as a git clone. You can do it -with Cem's personal repository as an example, but any other repository -will be the same. - - # Clone the repository to your desired location - # Optionally add "--depth 1" to save precious disk space - - $ git clone --depth 1 git://git.ckyln.com/kiss-repository /var/db/kiss/cem-repository - -That's it, you have obtained a new repository! - -Adding a repository to your KISS_PATH - -Now that we have obtained Cem's repository, we can add it to our KISS\_PATH! - -We need to edit `/etc/profile.d/kiss_path.sh` for this, but you -can also change your KISS\_PATH from your shellrc. - -Add the full path to the repository, in this case -`/var/db/kiss/cem-repository/cem` to the variable -and add a `:` before/after it. - -It must be looking like this. - - export KISS_PATH=/var/db/kiss/repo/core:/var/db/kiss/repo/extra:/var/db/kiss/repo/xorg:/var/db/kiss/cem-repository/cem - -Update your shell variables by doing `. /etc/profile.d/kiss_path.sh` so you can -immediately access the repository packages - - -More ----- - -You should now be able to boot into you Carbs Linux installation. -To learn more, you can visit the [wiki](//carbslinux.org/wiki) diff --git a/docs/wiki/keymaps/X-keymaps.html b/docs/wiki/keymaps/X-keymaps.html deleted file mode 100644 index 960ba5c..0000000 --- a/docs/wiki/keymaps/X-keymaps.html +++ /dev/null @@ -1,23 +0,0 @@ - - - -X-keymaps | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/keymaps/X-keymaps.txt b/docs/wiki/keymaps/X-keymaps.txt deleted file mode 100644 index e69de29..0000000 diff --git a/docs/wiki/keymaps/keymaps.html b/docs/wiki/keymaps/keymaps.html deleted file mode 100644 index 15a24e5..0000000 --- a/docs/wiki/keymaps/keymaps.html +++ /dev/null @@ -1,74 +0,0 @@ - - - -Keymaps in TTY | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Installing and Using Keymaps

- -

Unlike most other distributions out there -Carbs Linux does not come preinstalled with console -keys. You probably won’t be using more than -two either. There are two ways of using keymaps

- -

Installing the “bkeymaps” package

- -

You can get the bkeymaps package from the -KISS community repository.

- -

Build and install bkeymaps.

- -
-> kiss b bkeymaps
--> kiss i bkeymaps
-
- -

Now you can find the keymaps in /usr/share/bkeymaps.

- -

Downloading the keymaps you require

- -

This will assume that you are using the us keyboard layout

- -

You firstly will need to go to https://dev.alpinelinux.org/bkeymaps/ -and download the keymap you need

- -

Loading keymap, doing it on login/boot

- -
    -
  • Run loadkmap < file to load the keymap.
    • -
- - -

Load keymap at login

- -

If you want to load a keymap at login, you can -add the command above to your .profile file.

- -

Load keymap at boot

- -

You can also load keymap during boot. You should edit -/lib/init/rc.boot file and add something like

- -
# assuming you are using trq as your keymap
-log "Setting keymap to trq..."; {
-    loadkmap < /path/to/trq.bmap
-}
-
- -

to your main function.

-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/keymaps/keymaps.txt b/docs/wiki/keymaps/keymaps.txt deleted file mode 100644 index 89a7e8c..0000000 --- a/docs/wiki/keymaps/keymaps.txt +++ /dev/null @@ -1,52 +0,0 @@ - -Installing and Using Keymaps -============================ - -Unlike most other distributions out there -Carbs Linux does not come preinstalled with console -keys. You probably won't be using more than -two either. There are two ways of using keymaps - -Installing the "bkeymaps" package ---------------------------------- - -You can get the `bkeymaps` package from the -[KISS community repository](https://github.com/kisslinux/community). - -Build and install `bkeymaps`. - - -> kiss b bkeymaps - -> kiss i bkeymaps - -Now you can find the keymaps in `/usr/share/bkeymaps`. - - -Downloading the keymaps you require ------------------------------------ - -*This will assume that you are using the us keyboard layout* - -You firstly will need to go to -and download the keymap you need - -Loading keymap, doing it on login/boot --------------------------------------- - -- Run `loadkmap < file` to load the keymap. - -**Load keymap at login** - -If you want to load a keymap at login, you can -add the command above to your `.profile` file. - -**Load keymap at boot** - -You can also load keymap during boot. You should edit -`/lib/init/rc.boot` file and add something like - - # assuming you are using trq as your keymap - log "Setting keymap to trq..."; { - loadkmap < /path/to/trq.bmap - } - -to your main function. diff --git a/docs/wiki/system/service-management.html b/docs/wiki/system/service-management.html deleted file mode 100644 index da639fb..0000000 --- a/docs/wiki/system/service-management.html +++ /dev/null @@ -1,99 +0,0 @@ - - - -Service Management | Carbs Linux - - - - - -

Carbs Linux - a simple busybox linux distribution

-
-

Carbs Linux uses busybox-runit by default, but the repository additionally has the -original runit and sysmgr. You can install either with kiss b runit; kiss i runit -or kiss b sysmgr; kiss i sysmgr.

- -

runit

- -

Enabling a Service

- -
ln -sf /etc/sv/acpid /var/service
-
- -

Disabling a Service

- -
unlink /var/service/acpid
-
- -

Starting a Service

- -
sv start acpid
-
- -

Stopping a Service

- -
sv stop acpid
-
- -

For more information refer to the sv --help output. Also check out the sv(8) -manual page if you have installed the runit package.

- -

sysmgr

- -

sysmgr is POSIX-sh service supervisor written by me. Its usage resembles -runit. The biggest difference is that sysmgr uses service files instead -of directories with run scripts inside.

- -

svctl

- -

svctl is the equivalant of sv for sysmgr. You can run the above commands for -runit and use svctl instead of sv. Those would be as follows.

- -

Enabling a Service

- -
ln -sf /etc/sysmgr/acpid /var/sysmgr
-
- -

Disabling a Service

- -
unlink /var/sysmgr/acpid
-
- -

Starting a Service

- -
svctl start acpid
-
- -

Stopping a Service

- -
svctl stop acpid
-
- -

Switching from runit

- -

Switching from runit is fairly easy. You can run the following commands to get -started with sysmgr.

- -
# Create the directories if you haven't yet
-mkdir -p /var/sysmgr /etc/sysmgr
-
-# Copy all of the run scripts to /etc/sysmgr
-set -- /etc/sv/*
-for service; do cp "$service/run" "/etc/sysmgr/${service##*/}" ; done
-
-# Link all enabled services
-set -- /var/service/*
-for service; do ln -sf /etc/sysmgr/${service##*/} /var/sysmgr ; done
-
-View Page Source
-

Linux® is a registered trademark of Linus Torvalds

-

Copyright © 2019-2020 Cem Keylan

- - diff --git a/docs/wiki/system/service-management.txt b/docs/wiki/system/service-management.txt deleted file mode 100644 index 2133ea5..0000000 --- a/docs/wiki/system/service-management.txt +++ /dev/null @@ -1,81 +0,0 @@ - -Carbs Linux uses `busybox-runit` by default, but the repository additionally has the -original `runit` and `sysmgr`. You can install either with `kiss b runit; kiss i runit` -or `kiss b sysmgr; kiss i sysmgr`. - -runit -===== - -**Enabling a Service** - - ln -sf /etc/sv/acpid /var/service - -**Disabling a Service** - - unlink /var/service/acpid - -**Starting a Service** - - sv start acpid - -**Stopping a Service** - - sv stop acpid - -For more information refer to the `sv --help` output. Also check out the `sv(8)` -manual page if you have installed the `runit` package. - - -sysmgr -====== - -[sysmgr] is POSIX-sh service supervisor written by me. Its usage resembles -`runit`. The biggest difference is that `sysmgr` uses service files instead -of directories with run scripts inside. - - -svctl ------ - -`svctl` is the equivalant of `sv` for sysmgr. You can run the above commands for -`runit` and use `svctl` instead of `sv`. Those would be as follows. - - -**Enabling a Service** - - ln -sf /etc/sysmgr/acpid /var/sysmgr - -**Disabling a Service** - - unlink /var/sysmgr/acpid - -**Starting a Service** - - svctl start acpid - -**Stopping a Service** - - svctl stop acpid - - -Switching from runit --------------------- - -Switching from `runit` is fairly easy. You can run the following commands to get -started with `sysmgr`. - - - # Create the directories if you haven't yet - mkdir -p /var/sysmgr /etc/sysmgr - - # Copy all of the run scripts to /etc/sysmgr - set -- /etc/sv/* - for service; do cp "$service/run" "/etc/sysmgr/${service##*/}" ; done - - # Link all enabled services - set -- /var/service/* - for service; do ln -sf /etc/sysmgr/${service##*/} /var/sysmgr ; done - - - -[sysmgr]: https://github.com/cemkeylan/sysmgr -- cgit v1.2.3