• Open file search
• Turn on regular expressions
• Enter ( {2})(?: {2})(\b|(?!=[,'";\.:\*\\\/\{\}\[\]\(\)])) in the search fields
• Enter: $1 in the replace field

How to turn 2 spaces indents in all files in VSCode to 4 spaces

• Open file search
• Turn on regular expressions
• Enter ( {2})(\b|(?!=[,'";\.:\\*\\\/{\}\[\]\(\)])) in the search fields
• Enter: $1$1 in the replace field

Hope someone see this :)

find / -type f -size +20000k -exec ls -lh {} \; | awk '{ print $9 ": " $5 }'

You’re welcome :)

$ pacman -Syu

Sample output

:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update multilib (unable to lock database)
error: failed to synchronize any databases
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
 if you're sure a package manager is not already
 running, you can remove /var/lib/pacman/db.lck

The beauty of Linux distros is sometimes they will the explicitly display the solution along with the error message. As you can see in the above output, it says: “..you can remove /var/lib/pacman/db.lck”.

So, I simply deleted aforementioned file with command:

$ sudo rm /var/lib/pacman/db.lck

Voila! It worked. I can then able to update, install and remove without any problems.

$ sudo pacman -Syu

Sample output

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 endeavouros is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (64) alsa-lib-1.2.3.2-1  cdrtools-3.02a09-3  code-1.47.0-1  electron7-7.1.14-6  endeavouros-theming-5-2.2  firefox-78.0.2-1  fribidi-1.0.10-1  gjs-2:1.64.4-1
              gnome-boxes-3.36.5-1  gnome-clocks-3.36.2-2  gnome-control-center-3.36.4-1  gnome-desktop-1:3.36.4-1  gnome-multi-writer-3.32.1-2  gnome-music-1:3.36.4.1-1
              gnome-packagekit-3.32.0-2  gnome-shell-1:3.36.4-1  gnome-usage-3.33.2-2  grub-tools-1.3-1  hardinfo-0.5.1.816.g877ea2b-2  hidapi-0.9.0-2  i3lock-2.12-2
              i3status-2.13-3  jq-1.6-3  js68-68.10.0-1  jshon-20131105-4  keyutils-1.6.3-1  lib32-libpng-1.6.37-3  libconfig-1.7.2-3  libfdk-aac-2.0.1-2  libgcrypt-1.8.6-1
              libiptcdata-1.0.4-5  liblrdf-0.6.1-4  libmfx-20.2.0-1  libnfs-4.0.0-4  libopenraw-0.1.3-2  libosinfo-1.8.0-1  libpng-1.6.37-3  libsodium-1.0.18-2
              libutempter-1.2.1-1  lsb-release-1.4-16  lxappearance-0.6.3-3  lxinput-gtk3-0.3.5-3  mesa-20.1.3-1  mutter-3.36.4-1  ndisc6-1.0.4-2  os-prober-1.77-2
              osinfo-db-20200529-1  php-7.4.8-2  php-gd-7.4.8-2  plank-0.11.89-2  python-sphinx-3.1.2-1  re2-1:20200706-1  sdl2-2.0.12-2  simple-scan-3.36.4-1
              sqlitebrowser-3.11.2-2  thunderbird-extension-enigmail-2.1.7-3  ttf-ubuntu-font-family-0.83-6  usbredir-0.8.0-2  webkit2gtk-2.28.3-1  wmctrl-1.07-6
              wvdial-1.61-8  xl2tpd-1.3.15-2  xterm-357-1  zeromq-4.3.2-2

Total Download Size:     5.59 MiB
Total Installed Size:  820.45 MiB
Net Upgrade Size:       -0.78 MiB

Saya butuh waktu yang sangat lama untuk benar-benar memahami tentang mengapa harus mengendalikan amarah dan bagaimana caranya. Juga untuk mengerti tentang apa sebenarnya yang disebut “Ikhlas” itu, dan bagaimana rasanya.

Saya tidak akan bercerita tentang pengalaman detilnya, namun ciri utamanya saja. Yakni: jika orang sudah ikhlas tentang suatu hal, dia tidak akan membicarakan itu lagi. Tidak membahas, tidak mengingat-ingat, tidak bercerita di laman medsos, tidak curhat, tidak nggrundhel, juga tidak lagi berusaha ikhlas dengan berulang-ulang mengatakan berusaha ikhlas. Semua lepas, seperti layang-layang yang dibiarkan terbang mengikuti angin. Tak lagi dipegang, dikendalikan, atau dicari.

Ini berlaku untuk semua pengalaman, baik kecil maupun besar. Tidak ada batas usia maupun bobot pengalaman. Begitu ybs sudah ikhlas beneran, semua keinginan untuk bercerita atau mengulang-ulang kenangan lama, akan sirna begitu saja. Paling-paling kalau menemui hal serupa, ia hanya merespon pendek dan tidak punya minat lagi untuk membahasnya.

Satu hal yang membuat ikhlas jadi sukar dilakukan adalah: Ego. Misalnya: ada orang pernah disakiti. Ia merasa diperlakukan tidak adil, merasa berhak untuk membalas, merasa tak layak disakiti, merasa ingin melihat mereka yang menyakitinya mendapat balasan setimpal, merasa ingin membicarakannya terus-menerus, dan masih memberi ruang khusus di hatinya untuk menyimpan file buruk tersebut. Masih ada rasa sakit di hati ketika mengenang pengalaman itu, dan masih ada rasa penasaran tentang kapan balasan akan menimpa orang yang pernah menyakitinya.

Sebaliknya, kalau sudah ikhlas, semua rasa marah dan sakit itu lenyap seketika. Berganti dengan rasa “Nrimo”. No problem, no hard feeling, menerima semua pengalaman itu dengan lapang dada dan gembira. Menerima semuanya sebagai keniscayaan semata, sebagai bagian dari proses bertumbuh sebagai manusia. Bukan lagi sebagai pengalaman yang dilabeli dengan buruk-baik.

–

Susah juga ternyata, ya?

First of all we need a server that will be used to host our public node. You can use your own server or purchase a cheap VPS at DigitalOcean, Google Cloud, Vultr or any others VPS provider. Many cloud providers have a free trial so you can set up a server at no cost.

We’ll use an Ubuntu 18.04 server for this purpose. The steps will be almost the same for any flavor of Linux. You can use ssh or putty for connecting to your server.

Now we need to add a user as most VPS comes with a root login and it is really not a good idea to run anythis as root (consider it as a admin with superpowers). We’ll create a user named turtlenode but you’re free to choose any username.

# adduser turtlenode

Set and confirm the new user’s password at the prompt. A strong password is highly recommended! Follow the prompts to set the new user’s information. It is fine to accept the defaults to leave all of this information blank.

Next, run this command to provide admin rights to our server and switch to our new user

# usermod -aG sudo turtlenode
# su - turtlenode

After running this command, you’llbe able to see the prompt has changed. If you’ve completed these steps and see a terminal with username as turtlenode, congrats! You’re already halfway through!

Getting TurtleCoin

Now we’ll build TurtleCoin on our server. First of all, we need to install all the dependencies.

sudo apt-get install -y build-essential python-dev gcc g++ git cmake
sudo add-apt-repository universe
sudo apt-get update
sudo apt-get install libboost-all-dev

After all the dependencies have been installed, we need to get the TurtleCoin source code and build using the following commands

git clone -b master --single-branch https://github.com/turtlecoin/turtlecoin && cd turtlecoin
mkdir build && cd build
cmake .. && make

This will take some time to complete so you can grab a coffee till then. After this step is complete, you’ll be able to see new files in the ~/turtlecoin/build/src/ directory. If you don’t, then probably the build did not complete successfully and you may want to execute these steps again.

Setting up TurtleCoind High-Availability Daemon Wrapper

Now that we have everything ready with us, we need to make sure that our daemon always stays up and on the right chain. For this, we’ll be using the turtlecoind-ha-wrapper.

First of all we need to get back to our home directory (~) using

cd ~

Next, we need to install nodejs, a dependency for the wrapper using the following command

sudo apt-get install nodejs npm

Verify if it is installed successfully by running

nodejs -v

This will output the current version of nodejs. If your version is v8.x or higher, you’re good to go. Else, you’ll need to update.

Next, we need to clone the wrapper and place the daemon to work with the wrapper

git clone https://github.com/turtlecoin/turtlecoind-ha.git && cd turtlecoind-ha
cp ~/turtlecoin/build/src/TurtleCoind .

Now we need to install all the dependencies for the wrapper. Don’t worry, we don’t need to run every command now as installing dependencies with nodejs is pretty easy. All you need to do is run this single command

npm install

Note : Running npm install will automatically fetch and starting syncing from checkpoints for a faster sync.

We now need to set a few parameters to tell the network about our daemon and the fee it charges, for example say 250.00 TRTL per transaction. We need to add these parameters to the file service.js. Open up a text editor, in this tutorial i will use nano.

nano service.js

Add the following lines in bold here (after line number 10) without missing the commas

var daemon = new TurtleCoind({
    loadCheckpoints: './checkpoints.csv',
    feeAddress: "YOUR TURTLECOIN ADDRES",
    feeAmount: 25000
})

Substitute your wallet address and the feeAmount. Please not that the amount here is in shells.

1 TRTL = 100 shells, so 25000 shells = 250 TRTL

Save this file with CTRL + O, then CTRL + X

As we want our daemon to continue running non-stop 24x7x365, we need something that will help us accomplish that.

There’s a process manager called pm2 wich can be installed with npm, the package manager for nodejs. The setup is very simple

sudo npm install -g pm2

Simple, isn’t it?

Now start the daemon with the following command

pm2 start service.js --name turtlecoind

Now if you want to monitor your daemon or want to check the logs, you can do so by

pm2 monit
pm2 log

Yay! You’ve successfully set up your own public TurtleCoin node.

Congratulations! You are now a TurtleCoin service operator.

–

If you liked this tutorial, or made some TRTLs running your public node, please consider donating. Thanks!

TRTLv2Vdfgp3chLbD5NUKMEgkwQjLthtuf3YHLUv6tSATLxDv6VP69N9GH8H6uQF4J1rBr5P1wPfM58sG5NRFXdfPGXoag7fvpz

Bruteforcing. The act of systematically checking every possible password until the correct one is found - see Wikipedia for more.

The Math Behind It

I know, now you’ll start to hate me. It seems that the definition of bruteforcing requires you not to worry about math. If anything, bruteforcers want to get away from math. But once you get started with it, it’s not possible to evade it.

So i told myself i needed to learn it, at least to be able to know how long cracking this file would work.

Bruteforcing is pure math and i didn’t understand that in the beginning. Which is why i ended up frustrated after trying to crack on password 24/7 for 30 consecutive days with no results :(.

The math it is simple. Let’s define its two component and then their relationship:

1. Character set
2. Password length

Character Set

The character set is a list of characters the password, you are trying to bruteforce, contains. Typically it’s made up of a combination of the following types:

• lowercase alphabet [a-z]
• uppercase alphabet [A-Z]
• numbers [0-9]
• extra characters [.-!]

Let’s use a practical example. In the case of the file i wanted to crack, i used the following command to bruteforce it.

$ fcrackzip -b -c aA1! -u -l 4-10 file.zip > result.txt

In fcrackzip the c aA1! parameter defines the character set. In this case it means that we are going to use lowercase and uppercase alphabet numbers and extra characters.

Character set = a-z + A-Z + 0-9 + .-!

# of characters = 26 + 26 + 10 + 33 = 95

If you add all these characters, you will end up with a total of 95. Let’s go look at password length.

Password Length

It defines how many characters the password, we are trying to crack, has.

When bruteforcing, the password length tends to be an educated guess. It’s rare to exactly know how long the password is. More often we know a minimal and maximum password length.

If we took at the command from above again, we can see that i, too, made an educated guess concercing the password length.

$ fcrackzip -b -c aA1! -u -l 4-10 file.zip > result.txt

I estimated it to be between 4 and 10 characters.

The Relationship

Now that we have the basic information straightened out, let’s see how this helps us. Let us calculate the total number of possible combinations.

So far, we have established the following:

Minimum password length : 4
Maximum password length : 10
Size of character set : 95

The relationship between the two is described by this equation:

For each character in the password you have 95 possibilities.

95 x 95 x 95 x 95 = 81,450,625 possible combinations

That means for a 4 characters password, you have 81 million possible combinations. For a password with 5 characters the total number of combinations is:

95 x 95 x 95 x 95 x 95 = 7,737,809,375 possible combinations

We can obviously also calculate the number of combinations for a 6, 7, 8, 9 or 10 character password - if it interests you, do go ahead and calculate it.

Step 1: Install software

We use the Homebrew package manager for this step.

brew install gpg2 gnupg pinentry-mac       

Step 2: Update ~/.gnupg/gpg-agent.conf

If this file does not exist, create it.

# Insert the following text
pinentry-program /usr/local/bin/pinentry-mac

Step 3: Update or Create ~/.gnupg/gpg.conf

If this file does not exist, create it.

# Uncomment within config (or add this line)
# This tells gpg to use the gpg-agent
use-agent

Step 4: Modify your Shell

Append the following to your ~/.bash_profile or ~/.bashrc or ~/.zshrc

...
export GPG_TTY=`tty`

Step 5: Restart your Terminal or source your ~/.*rc file

# on the built-in bash on macos use
source ~/.bash_profile
# if using bash through homebrew over ssh use
source ~/.bashrc
# and if using zsh
source ~/.zshrc

Step 6: Create your GPG Key

Run the following command to generate your key, note we have to use the --expert flag so as to generate a 4096-bit key.

gpg --full-gen-key

Step 7: Update the Permissions on your ~/.gnupg Directory

You will need to modify the permissions to 700 to secure this directory.

chmod 700 ~/.gnupg

Step 8: Answer the Questions

Once you have entered your options, pinentry will prompt you for a password for the new PGP key.

Please select what kind of key you want:
   (1) RSA and RSA (default)
   (2) DSA and Elgamal
   (3) DSA (sign only)
   (4) RSA (sign only)
Your selection? 4
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 4096
Requested keysize is 4096 bits
Please specify how long the key should be valid.
         0 = key does not expire
      <n>  = key expires in n days
      <n>w = key expires in n weeks
      <n>m = key expires in n months
      <n>y = key expires in n years
Key is valid for? (0) 3y
Key does not expire at all
Is this correct? (y/N) y

You need a user ID to identify your key; the software constructs the user ID
from the Real Name, Comment and Email Address in this form:
    "RandallTux (rndtx) <me@rndtx.id>"

Real name: RandallTux
Email address: me@rndtx.id
Comment:
You selected this USER-ID:
    "RandallTux <me@rndtx.id>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
You need a Passphrase to protect your secret key.

Step 9: Get your key info for Git, etc.

# List your keys
gpg -k

Step 10: Get your key id

Use the next command to generate a short form of the key fingerprint.

Copy the text after the rsa4096/ and before the date generated and use the copied id in step 13:

gpg -K --keyid-format SHORT
sec rsa4096/######## YYYY-MM-DD [SC] [expires: YYYY-MM-DD]

You need to copy the output similar to the example above where the ######## is.

Step 11: Export the fingerprint

In the output from step 10, the line below the row that says ‘pub’ shows a fingerprint-this is what you use in the placeholder. The output from below is what you copy to Github:

# The export command below gives you the key you add to GitHub
gpg --armor --export <your key id>

Step 12: Configure Git to use gpg

git config --global gpg.program $(which gpg)

Step 13: Configure Git to use your signing key

The below command needs the fingerprint from step 10 above:

git config --global user.signingkey 1111111

Step 14: Configure Git to sign all commits (Optional-you can configure this per repository too)

This tells Git to sign all commits using the key you specified in step 13.

git config --global commit.gpgsign true

Step 15: Perform a Commit

git commit -S -s -m "My Signed Commit"

Step 16: Pinentry Prompt

You will now be prompted by Pinentry for the password for your signing key. You can enter it into the Dialog box-with the option of saving the password to the macOS X Keychain.

Step 17: Submit your PGP key to Github to verify your Commits

Login into Github.com and go to your settings, SSH and GPG Keys, and add your GPG key from the page.

Step 18: Submitting Your Key to a Public Keyserver (very optional)

Before you jump on submitting your key to a service such as the MIT PGP Key Server, you should consider the following:

• You cannot delete your key once submitted
• Spammers have been known to harvest email addresses from these servers
• If you’re only signing your Git commits to Github this isn’t necessary

Troubleshooting

If you have any errors when generating a key regarding gpg-agent, try the following command to see what error it generates:

gpg-agent --daemon

The installation is very similiar to Gentoo’s stage 3 tarballs.

An archive is used which contains a full KISS system minus the boot-loader and kernel. The provided archive contains all of the tooling needed to rebuild itself as well as the remaining packages needed for an installation.

You will need an existing Linux distribution to use as a base for the installation. It does not matter what kind of distribution it is nor does it matter what lib it uses.

For the purpose of this guide I will be using another Linux distribution’s Live-CD to bootstrap KISS. The Live-CD must include tar (with xz support), mountpoint and other basic utilities.

From this point on, the guide assumes you have booted a Live-CD and have an internet connection.

Index

• Setting up disks
• Install KISS
• Enable repository signing
• Rebuild KISS
• Build userspace tools
• Configure and build the kernel
  • Download the kernel sources
  • Extract the kernel sources
  • Configure the kernel
  • Build the kernel
  • Install the kernel
• Install grub
• Install init scripts
• Enable the community repository

Setting up disks

Get the disks ready for the installation. This involves creating a partition table, partitions and the desired file-systems. This step will differ depending on whether or not you are doing a BIOS or UEFI installation.

The guide will not cover this step. If you require assistance with this step; read one of the links below. This step is not unique to KISS and there are tried and tested resources for all kinds of disk layout online.

• Gentoo wiki
• Archlinux wiki

Install KISS

At this stage your disks should be setup and mounted to /mnt.

Download the latest release.

$ wget https://dl.getkiss.org/kiss-chroot.tar.xz

# recommend: verify the download.
$ wget https://dl.getkiss.org/kiss-chroot.tar.xz.sha256
$ sha256sum kiss-chroot.tar.xz | diff kiss-chroot.tar.xz.sha256 - && echo good

# recommend: verify the download's signature.
$ wget https://dl.getkiss.org/kiss-chroot.tar.xz.asc
$ gpg --verify kiss-chroot.tar.xz.asc kiss-chroot.tar.xz

Download the chroot helper

$ wget https://dl.getkiss.org/kiss-chroot

# inspect the script before you execute it below
$ vi kiss-chroot

# ensure the script is executable
$ chmod +x kiss-chroot

Unpack the tarbal (Install KISS)

# make sure disks are first mounted to /mnt
$ mount -t ext4 /dev/sdaX /mnt
$ tar xvf kiss-chroot.tar.xz -C /mnt --strip-components 1

Enter the chroot

./kiss-chroot /mnt

Enable repository signing

This step is entirely optional and can also be done after the installation. See #60 for more information.

Build and install gnupg1

$ kiss build gnupg1
$ kiss install gnupg1

Import Dylanarap’s key

$ gpg --keyserver keys.gnupg.net --recv-key 46D62DD9F1DE636E

Trust Dylanarap’s key

$ echo trusted-key 0x46d62dd9f1de636e >> /root/.gnupg/gpg.conf

Go to the system-wide repository

$ cd /var/db/kiss/repo

Enable signature verification

$ git config merge.verifySignature true

Rebuild KISS

This step is entirely optional and you can just use the supplied binaries from the downloaded chroot. This step can also be done after the installation.

Modify compiler options (Optional)

$ export CHOST="x86_64-pc-linux-gnu"
$ export CFLAGS="-march=core-avx2 -mavx2 -O2 -pipe"
$ export CXXFLAGS="${CFLAGS}"
$ export MAKEFLAGS="-j3"

# note: this is for ThinkPad x240

Update all base packages to the latest version

$ kiss update

Start rebuilding all packages

$ kiss build

Build userspace tools

# required for mounting drives
$ kiss build e2fsprogs eudev

# requires for connecting to WiFi
$ kiss build wpa_supplicant
$ kiss install wpa_supplicant

# required for connecting to the internet
# (wifi and ethernet) (dynamic ip addressing)
$ kiss build dhcp
$ kiss install dhcpcd

Configure and build the kernel

This step involces configuring and building your own Linux kernel. If you have not done this before, below are a few guides to get you started.

• KernelNewbies
• Gentoo wiki
• Linuxtopia

The Linux kernel is not managed by the package manager. The kernel is managed manually by the user.

NOTE: KISS does not support booting using an initramfs. When configuring your kernel ensure that all required file-system, disk controller and USB drivers are built with [] (Yes) and *not[m] (Module).

Download the kernel sources

You can find the latest version at https://kernel.org

$ wget https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.3.6.tar.xz

Extract the kernel sources

$ tar xvf linux-5.3.6.tar.xz

# change directory to the kernel sources
$ cd linux-5.3.6

Configure the kernel

NOTE: You can determine which drivers you need to enable by Googling your hardware. NOTE: If you require firmware blobs, the drivers you enable must be enabled as [m] (modules). You can also optionally include the firmware in the kernel itself.

# install 'linux-firmware' if you require firmware
# blobs for your hardware
$ kiss build linux-firmware
$ kiss install linux-firmware

# generate a default config with *most* drivers
# compiled as `[*]` (not modules)
$ make defconfig

# open an interactive menu to edit the generated
# config, enabling everything extra you may need.
$ make menuconfig

# store the generated config for reuse later
$ cp .config /path/to/somewhere

Here’s my kernel config that i used for ThinkPad x240

Processor type and features  --->
  Processor family (Intel Core AVX2)
  <*> CPU microcode loading support
  [*] Intel microcode loading support
Power management and ACPI options  --->
  [*] ACPI (Advanced Configuration and Power Interface) Support  --->
    <*> Battery
    <*> Video
  CPU Frequency scaling  --->
    Default CPUFreq governor (performance)
    <*> 'performance' governor
    x86 CPU frequency scaling drivers  --->
      [*] Intel P state control
[*] Networking support  --->
  <*> Bluetooth subsystem support  --->
    Bluetooth device drivers  --->
      <*> HCI USB driver
  <*> Wireless  --->
    <*> cfg80211 - wireless configuration API
    <*> Generic IEEE 802.11 Networking Stack (mac80211)
  <*> RF switch subsystem support
Device Drivers  --->
  Misc devices  --->
    <*> Intel Management Engine Interface
    <*> ME Enabled Intel Chipsets
  SCSI device support  --->
    <*> SCSI disk support
    [*] Probe all LUNs on each SCSI device
  <*> Serial ATA and Parallel ATA drivers  --->
    <*> AHCI SATA support
  [*] Network device support  --->
    [*] Ethernet driver support  --->
      [*] Intel devices
        <*> Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support
    [M] Wireless LAN  --->
      <M> Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
      <*> Intel Wireless WiFi MVM Firmware support
  <*> I2C support  --->
    I2C Hardware Bus support  --->
      <*> Intel 82801 (ICH/PCH)
  <*> Hardware Monitoring support  --->
    <*> Intel Core/Core2/Atom temperature sensor
  [*] Watchdog Timer Support  --->
    <*> Intel TCO Timer/Watchdog
  Multifunction device drivers  --->
    <*> Intel ICH LPC
    <*> Realtek PCI-E card reader
  <*> Multimedia support  --->
    [*] Media USB Adapters  --->
      <*> USB Video Class (UVC)
  Graphics support  --->
    <*> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
    <*> Intel 8xx/9xx/G3x/G4x/HD Graphics
      [*] Enable modesetting on intel by default
      [*] Enable legacy fbdev support for the modesettting intel driver
    Console display driver support  --->
      <*> Framebuffer Console support
  <*> Sound card support  --->
    <*> Advanced Linux Sound Architecture  --->
      [*] PCI sound devices  --->
        <*> Intel HD Audio  --->
          [*] Build HDMI/DisplayPort HD-audio codec support
  [*] USB support  --->
    <*> xHCI HCD (USB 3.0) support
    <*> EHCI HCD (USB 2.0) support
  <*> MMC/SD/SDIO card support
    <*> Realtek PCI-E SD/MMC Card Interface Driver
  [*] X86 Platform Specific Device Drivers  --->
    <*> ThinkPad ACPI Laptop Extras
  [*] IOMMU Hardware Support  --->
    [*] Support for Intel IOMMU using DMA Remapping Devices
    [*]  Enable Intel DMA Remapping Devices by default
    [*] Support for Interrupt Remapping
[*] Cryptographic API  --->
  <*> AES cipher algorithms (AES-NI)

Device Drivers ->
  Character devices ->
    <*> TPM Hardware Support ->
      <*> TPM Interface Specification 1.2 Interface / TPM 2.0 FIFO Interface

Build the kernel

# '-j $(nproc)' does a parallel build using all cores
$ make -j "$(nproc)"

Install the kernel

NOTE: Ignore the LILO error, it’s harmless.

# install the built modules
# this installls directly to ```/lib``` (symlonk to ```/usr/lib```).
$ make modules_install

# install the built kernel
# this install directly to ```/boot```
$ make install

# rename the kernel
#  substitute VERSION for the kernel version you have built
$ mv /boot/vmlinuz /boot/vmlinuz-KERNELVERSION
$ mv /boot/System.map /boot/System.map-KERNELVERSION

Install grub

Build and install grub

$ kiss build grub
$ kiss install grub

# also needed for UEFI.
$ kiss build efibootmgr
$ kiss install efibootmgr

Setup grub

# BIOS
$ gtub-install --target=i386-pc /dev/sdX
$ grub-mkconfig -o /boot/grub/grub.cfg

# UEFI
# replace 'X' with its mount point
$ grub-install --target=x86_64-efi --efi-directory=/path/to/mounted/efi --bootloader-id=GRUB
$ grub-mkconfig -o /boot/grub/grub.cfg

Install init scripts

This is the final “mandatory” step.

$ kiss build baseinit
$ kiss install baseinit

Enable the community repository

The KISS community repository is maintained by users of the distribution and contains packages which aren’t int he main repositories. This repository is disabled by default since it’s not maintained by the KISS developers.

# clone the repository to a location of your choosing.
$ git clone https://github.com/kisslinux/community.git

# add the repository to the system-wide 'KISS_PATH'.
# the 'KISS_PATH' variable works exactly like 'PATH'.
# each repository is split by ':' and is checked in
# the order they're written.
#
# add the full path to the repository you cloned
# above.
#
# NOTE: The subdirectory must also be added.
# example: export KISS_PATH=/var/db/kiss/repo/core:/var/db/kiss/repo/extra:/var/db/kiss/repo/xorg:/path/to/community/community
$ vi /etc/profile.d/kiss_path.sh

# spawn a new login shell to access this repository
# immediately.
$ sh -l

Sreenshot