DEV Community: Andreas Pappas

A 97.7% JavaScript Template Blog Website

Andreas Pappas — Tue, 17 Aug 2021 11:19:40 +0000

Hi there 👋

/// NOTE❗ This will be a large post

For 🌩️ fast instructions to get up and running with the project follow the 👇 README on the repo

As mentioned in the README.md page
of this repo, this post will serve to provide, detailed information and instructions about making this particular project your own.
i.e. modify it as you see fit, (to make it your own personal Blog or Portfolio page), learn which parts you should and shouldn't modify,
how to run and develop it locally, the prerequisites for doing so, how to deploy it using free hosting services like GitHub pages and netlify, how to
change the default domain name of those services and apply your own custom one and eventually get familiar enough with it so you could contriubute to it,
by implementing stuff from the Project Roadmap, if you feel like it! 😀

😰 Stuck?

Try submitting an issue on GitHub where friendly folks can try to help.

🏇 Let's get started

But first, let me take a selfie 🤳

Ok no.

First of all we need to discuss about what programs you need to have on your machine in order
to get this project up and running on a Local Development Environment.

But what is a Local Development Environment?

A local development environment allows you to run an exact copy of a project on your own computer. And, thanks to Git, you can sync your local copy with the published copy online too.

In other words, you—and whoever else you may want to collaborate with on your project—can break your project, then fix it, then break it some more, all on your own computer. Feel free to test and tinker to your heart’s content before ever releasing the new (and hopefully improved) version to the public.

⬇️ What Software Programs You will Need to Install

🦁's Blog uses a program called Eleventy (11ty) to build websites. Eleventy is a type of program known as a static site generator, which basically builds a fresh copy of your site everytime you save a change.
Both 🦁's Blog and Eleventy run on a program called Node.js under the hood. Node.js gives you a local JavaScript runtime environement, which basically means you can use software written in JavaScript on your computer.
Before programs like Node.js, JavaScript was pretty much confined to the browser. But now, thanks to Eleventy, you can use the same progmramming language to run a server, write your content, generate your site, and interact with users.

All three programs—Node.js, Eleventy, and 🦁's Blog—are free and open source software (FOSS), meaning the code is publicly avaialble.
In fact, you’re encouraged to remix your own local copy, create something new and worthwhile with it, and even suggest changes to the original source code.

Before getting to the installation part, first I suggest that you try to get familiar to using the so called 😱 Terminal.

💻 Accessing Your Terminal

Every operating system (Windows, macOS, Linux, etc.) comes with a text-based command line interface (CLI, console, or terminal) to enter commands you want your computer to run.
The CLI is a powerful tool for interacting with your personal workstation beyond the graphical user interface (GUI) with which you may be more familiar.
Of course, if you’ve ever used a computer without a mouse or touchpad, then you might feel right at 127.0.0.1 in the command line.
Intead of “pointing and clicking” with a mouse or touchpad 🖱️, you can “talk” to your computer from your keyboard ⌨️.
Keyboard commands are a really expressive and efficient way to accomplish a lot of tasks that are often outside the reach of the GUI.

What would be easier, searching on google for a program that you might want to install and click, scroll, drag, type stuff or,

simply, write a command on your terminal emulator by providing the name of the program that you want to install and let it do it's thing for you?

Here’s a 📝 list of the command line tools that come preinstalled with some of the most popular operating systems:

On 🐧 Linux, the default console is called Terminal.
On 🍏 macOS, the default console is called Terminal.app.
On 🏢 Windows, the default console has been Command Prompt for ages, but since Windows 10, you can now use a Linux-based tool called Windows Terminal.

If you’re on Windows, then I’ll assume you’re able to access the newer Linux-based Windows Terminal for entering commands.

⌨️ Entering Commands

Now that you have an idea of how useful your terminal is and how to access it, you can start learning your way around the command line interface.
Some of the most important skills to learn involve listing the contents of a folder or “directory” and moving from one directory to another.
Many commands depend on the directory in which you happen to be working at the time.
You can use the ls command to list the files in the current “working directory.”
Likewise, you can use the cd command the change from one directory to another:
Typing only cd will change to the top-level directory in your directory tree (often referred to as your home 🏡 directory).
To go down ⬇️ 📂 from the current directory to one inside it, you can type cd followed by the name of the directory you want to open.
For example, cd ./Downloads.
To go up ⬆️ 📂 from the current directory to another one outside it, you can type cd ../.
This command will go up one level from the current directory, for example, from Downloads back up to the directory from which you just came.
You can repeat the sequence ../ as many times as you need. Say you wanted to go up two levels: you could type cd ../../.

Once you’re comfortable listing a directory’s contents and moving from one directory to another, you have all the basic command line skills you’ll need to start setting up your local development environment
and install all the programs via it that we'll talk from now and on finally 😶.

⬇️ Installing git

I do strongly recommend that you learn what Version Control is.
Once you do that, I again strongly recommend that you learn to use and get as familiar as possible with the git version control system.

Git is widely used and a very very very strong tool and skill for a Software Engineer (and not only) to have.
Also you'll need it to get on your machine this very project itself! 🦁

The following 2 guides are the official ones and probably the best that explain simply and clearly how to get git installed,
based on the operating system that you're using.

1️⃣ link
2️⃣ link

📚 Learning git

The following 👉 GitHub git guide is a really good guide to get you started into learning git and how you can combine it with a git online service like GitHub.

But, you can also use browser based online 👉 games to keep your attention a bit more while diving into the more advanced parts of it.

Now that you're familiar with git and GitHub it's time to get 🦁's Blog copy from it's repository.
Or you can fork it as well and then git clone it from your own fork.

The procedure to do so would like like this 👇 (but I'm sure at this point you already knew how to do it, it's just an excuse to use asciinema).

Alright, so what's next?

⬇️ Getting Node.js

Now that we have cloned the project locally on our machine we need Node.js to get it running on our Local Development Environment.

This again depends on the operating system that you're using but you can follow the official instructions via this 👉 link.

At this point I will provide some instructions that I personally know works best to get the latest stable version of Node.js and npm on Linux operating systems (whichever distribution you might be using).

/// NOTE❗
The following instructions might look a bit advanced or complicated but they're not. Read 'em and follow carefully and you should be good to go.

ℹ️ About

nvm is a version manager for node.js, designed to be installed per-user, and invoked per-shell. nvm\ works on any POSIX-compliant shell (sh, dash, ksh, zsh, bash), in particular on these platforms: unix, macOS, and windows WSL.

⬇️ Install & Update Script

To install or update nvm, you should run the [install script]

> $ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash

> $ wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash

Running either of the above commands downloads a script and runs it. The script clones the nvm repository to ~/.nvm\,
and attempts to add the source lines from the snippet below to the correct profile file (~/.bash_profile\, ~/.zshrc\, ~/.profile\, or ~/.bashrc\).

❗ The following is ONE command, copy paste it as a whole.

> $ export NVM_DIR="$([ -z "\${XDG_CONFIG_HOME-}" ] && printf %s "\${HOME}/.nvm" || printf %s "\${XDG_CONFIG_HOME}/nvm")"
> [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm

🗒️ Additional Notes

If the environment variable $XDG_CONFIG_HOME\ is present, it will place the nvm\ files there.
You can add --no-use\ to the end of the above script (...nvm.sh --no-use\) to postpone using nvm\
until you manually use\ it.
You can customize the install source, directory, profile, and version using the NVM_SOURCE\, NVM_DIR\, PROFILE\, and NODE_VERSION\ variables.
Eg: curl ... | NVM_DIR="path/to/nvm"\. Ensure that the NVM_DIR\ does not contain a trailing slash.
The installer can use git\, curl\, or wget\ to download nvm\, whichever is available.

🧰 Troubleshooting on Linux

On Linux, after running the install script, if you get nvm: command not found\
or see no feedback from your terminal after you type command -v nvm\, simply close your current terminal,
open a new terminal, and try verifying again.
Alternatively, you can run run the following commands for the different shells on the command line:

bash: source ~/.bashrc\

zsh: source ~/.zshrc\

ksh: . ~/.profile\

These should pick up the nvm\ command.

☑️ Verify Installation

To verify that nvm has been installed, do:

> $ command -v nvm

which should output nvm\ if the installation was successful. Please note that which nvm\ will not work, since nvm\
is a sourced shell function, not an executable binary.

⬇️ Installing node with nvm

To get the latest LTS version of node and migrate your existing installed packages, use

> $ nvm install 'lts/*' --reinstall-packages-from=current

Then you should have the latest and stable version of nodejs on your system
as long as the npm package manager that comes with it.

✅ Verify installations:

> $ node -v

> $ npm -v

At this point we have node on our system. It's finally time to get our project running locally.

Get into the project's directory (as showcased in the previous gif above after cloning) and then:

⬇️ Install the project dependencies with npm

> $ npm install

🏃 Run the project locally and head to the browser to view it

> $ npm run dev

Open your browser and type in the address bar:

> http://localhost:8080/

Here's a video demonstrating the above instructions:

Congratulations❣️ after all this 🎉 you managed to get the project running locally on your machine!

So, we managed to install all the dependencies, learn about git, GitHub and version control and a bunch more stuff,
as well as run the project on our machines, in our Local Development Environment.

What are the next steps 👣 to take you might ask?

Well, the first thing to do is to get your hands dirty and dive into the project itself, experimenting and playing with it.
As the project is written entirely with 🍦 JavaScript, you might want to learn some of it, if not already familiar with it,
so you can swim 🏊 a little easier into the code itself. As mentioned before the project itself is hugelyy documented,
either on the GitHub repository (inside every repository you should find a seperate README.md file explaining what's important to know),
as well as the code itself contains inline documentation!

So with knowing some basics of the JavaScript programming language, reading the available documentation and playing / experimenting with the code itself
you should be good to go!

/// NOTE ❗ On my following 👉 GitHub Repository
you should find the basics of the JavaScript programming language, written in a tutorial-like form
which should get you able while reading it, to get more familiar with it and learn it.
Currently it is written in a fast pased style and it's not hugely detailed, but I do plan making it a free e-book
for the very purpose of learning the JavaScript programming language and diving deep into it as possible
So, stay tuned 📻 for it!

Now, as this blog post has already become huge, I want to mention fast 2 last things that you might want to do with the project.

First you might want to customize it a bit and make it more personal.
You'll have to get your hands dirty as mentioned to be able to do that, but as a fast reference you can try the following:

📝 Edit ./_data/site.json with your site’s information. Don’t be scared. You can change just about any text inside single quotes without breaking anything ('Safe to edit'). If you get stuck, please file an issue on GitHub where someone friendly can help.
(Optionally) 📝 Edit .eleventy.js with your configuration preferences.
❌ Delete the contents inside the quotes after the return statement in the /shortcdes/getting-started.js file.
Basically this is the terminal that you see on the home page. If you want to keep it but put your own information instead go down on the file and edit the text inside the .then() methods.
Else, you can delete it completely and write markdown inside the backticks of the return statement or do write whatever HTML, CSS, JavaScript you want, as I've already done.

In ./content/pages and ./content/posts/, you can edit or delete any of the files ending with the .11ty.js or .md extensions.
To create a new page or post, I recommend copying and pasting one of these files to a new one until you get the hang of it.

To preview your changes in the browser you'll have to do run the project as we did above. (see the terminal video) 👆

Simply run:

> $ npm run dev

And head to http://localhost:8080/ in your browser

For publishing your own copy of the project as well as using your own custom domain name,
I'll write detailed instructions on a separate blog post and reference it here when it's done,
as this already got huge enough.

For a fast reference you can have a look 👉 here

Or use the following button 👇 which will create a fork of the repository on your own GitHub profile and publish that fork directly to your netlify account to which you will have to login via your GitHub profile.

Enjoyed the article? Did you like the project? Learned something from it?

If so,

A ⭐ on the GitHub page, would be of a great help and much appreciated!

Thank you. 🙏

©️ 2021 <Andreas><\Pappas>

The #include <> preprocessor statement.

Andreas Pappas — Fri, 30 Jul 2021 19:22:11 +0000

Hi there 👋

The first sentence that I want to write here is the following,

The #include preprocessor statement, all that it does is literally copy and paste the contents of the header file specified after the #include <> into our file, on the particular line of our file that we placed that statement.

🙃 Alright then, keep reading and you might do so!

Remember my first sentence that the preprocessor statement #include all that does is take the file that is specified after it and literally copy paste it's content into our .cpp file?

Well let's prove that.

Let's say we have the following C++ code,

File: addNumbers.cpp

int addNumber(int x, int y) 
{
    return x + y;
}

Simply we wrote a function that takes as input 2 integers and returns their sum.

If we try to compile the above code, it should compile successfully without any errors.

Now let's say that we forget the closing brace at the end of our code, so it looks like this:

int addNumber(int x, int y) 
{
    return x + y;
                        /// <--- notice the closing curly brace missing on this line.

If we compile the below code we should get an error that we do miss a closing curly brace on line 4.

How can we fix that?

Either we can simply edit the file and add back our closing curly brace, or we can get a bit crazy and prove our very first statement of the #include preprocessor statement literally copy pasting into our addNumbers.cpp file the content of the header file that is after our include statement.

So let's create a header file.

File: closingBrace.h

Yeah, exactly, our closingBrace.h file simply contains one character. The closing curly brace itself --> }

Now take a look at the below code,

int addNumber(int x, int y) 
{
    return x + y;
#include "closingBrace.h"

What do you think will happen if we compile this file?

Well, it will compile properly without any errors.

Why is that?

Well, if you create the 2 files above in Microsoft Visual Studio and compile them, you can then see in your project a file with the extension .i in particular you will see a file called: closingBrace.i

What this file is, is simply a file that is generated by the Microsoft Visual Studio compiler and it simply contains the contents of the output of the preprocessor instead of directly creating the object file from our C++ source file.

How to generate the .i preprocessed file?

To generate a preprocessed file (.i file), just add "-EP -P" to the compile option, and recompile the original .cpp file. You can also generate a .i file directly from the "Prepocessor" property in Visual Studio*:

Right click the file name, and click properties
Click Preprocessor\Generate Preprocessed File\Without Line Numbers (/EP /P)

If you recompile from a command window, the .i file will be created under the current directory. if you recompile from within the Visual Studio* IDE, the .i file will be created under the directory where the original source file is located.

Well if you go on and open that file you will see the following contents:

int addNumber(int x, int y) 
{
    return x + y;
}

Does it remind you of anything?

Well that was the proof that the preprocessor translated our #include "closingBrace.h" statement into a simple } character. And that is because it literally copy pasted the contents of the closingBrance.h file and replaced our #include statement with that content, and since we simply had only a } inside that file, that's what it copy pasted on that particular line that we placed our statement.

And that's all there is to it about the #include preprocessor statement and also about how we do use header files aka .h files in C++!

I hope you enjoyed the article and learned something new today as I myself did!

I've also started writing down a C++ course on my GitHub account on the following 👉🏻 repository, so you can check it out if you want to learn more cool stuff about how C++, it's compiler and linker do work and also best practices about writing fast and efficient C++ code.

I will be doing blog posts on several parts of the above course like this one in general, but if you want the A-Z of it then you can check the above repository mentioned!

Obviously contribution and corrections are much more than welcome!

You can also check if you wish so my recently made 📖 Blog website for more computer science but not limited to, related content and keep an eye 👀 on it as soon, I will make it's repository public with in depth detail on how you can also use that particular Blog website to customize it and use it as a template to make it your own if you like it and wish to do so❗

Thank you. 🙏

©️ 2021 <Andreas><\Pappas>

Install Artix Linux

Andreas Pappas — Fri, 26 Mar 2021 23:30:17 +0000

Greetings, in this very first article of mine, I will try to showcase how to install an Arch like Linux distribution, in particular, Artix Linux aka The Art Of Linux from scratch. (i.e. from a base .iso image)
I will try to explain everything that is non trivial without getting into much depth. For that you can always reference the Artix wiki.

The purpose of this article is to get your hands dirty, on trying and experimenting with installing a Linux Distribution from scratch and thus get a better understanding of the beauty of UNIX operating systems, in particular Linux and also get a better understanding on how operating systems work behind the scenes. (We're not going to do an Operating Systems computer science course here and of course we're not gonna use C to modify or even write a Linux kernel here, but you will get the point later on...)

As this is a minimal Linux installation, I've kept this article minimal as well. (i.e. without any pictures (except the one below ^.-)). The reason for that being is, that you need to dive in, reading carefully what's going on and experiment in your own machine and not simply follow an image slideshow and copy paste some commands. If you fail your very first installation that's totally perfect. Everyone fails! Get your hands dirty and try all over again, fail again and try again. That is exactly how it will stick to your brain and thus you'll gain the knowledge!

I will also showcase at the end of this article how to install a bootstrapping script for those who want a ready to go graphical environment after a minimal / base Linux installation.

And the journey begins...

So, first thing to do is go to Artix Linux Download page and choose a base install .iso image. (since we want to build it from scratch). ~> link
You could also select an image with an already installed desktop environment, but we're not going to do that here.

There are 3 base images to download:

openrc
runit
s6

And basically those are 3 different init systems of the Artix distribution. (you can find more info on the Artix wiki)

Once we download an image, we then want to put it onto a usb drive and make it bootable.
If we open a tty (terminal) and run in:



$ lsblk

We should see the hard drives that we already have in our system. After we can put into our computer the usb stick and run again the same command to find out how is our system labeling the usb stick. Usually it's something like sd followed by another letter. So for example, our main hard drive would have the label of sda and when we put into our usb then it might be named sdb. And so it's file location should then be: /dev/sdb. To make sure we can also check the capacity of each drive.

Now, once we make sure that we have recognized which is our usb drive, then we want to make it bootable with our .iso image.
To do that, we first need sudo privileges and then we can run the following command:



$ dd if=our_iso_image_here.iso of=output_file_to_write_the_image status='progress' #if we want to see a progress bar

# so an example of the above explanation: 

$ dd if=arix-base-runnit-20200214-x86_64.iso of=/dev/sdb status='progress'

And now we have a bootable usb stick with the Artix runnit image and we can boot from it from our computer and begin the installation.

First, we have to login as root and the credentials for that are:



Username: root
Password: artix

Or we could login as the artix user and then do: sudo su



Username: artix
Password: artix

So once we have done that, we first have to make sure if our computer is running UEFI or Legacy Boot.
Most new machines will have uefi but to make 100% sure we should run the following command:



$ ls /sys/firmware/efi/efivars

If you SEE stuff come up then the computer is using UEFI
If you DON'T see stuff come up then the computer is using Legacy Boot

So if you get something like: ls: cannot access /sys/firmware/efi/efivars: No such file or directory, then YOU ARE NOT using UEFI.

At this point we need to make sure that we are connected to the internet! Strongly recommended to be hooked via ethernet cable, but in case you don't have one you can use the command: iwd to be connected to a wifi network and it should come already pre-installed on the iso image.

To check if you have internet connection, you can ping a website like:



$ ping artixlinux.org

and it should return responses and thus that mean you're connected to the internet.

Now by running lsblk we should find the hard drive of the computer that we want to install the Artix Linux on. Again we can recognize it by it's capacity size.

Once we find it we should run the following command to begin the disk partitioning.



$ fdisk /dev/sda

# /dev/sda is the (example) disk that we want to install Artix on

In our example guide here, we're going to delete EVERYTHING from the hard drive and partition everything from scratch, but you could if you want keep your home partition (if you haven't backed it up) and just create in the next steps the root and the boot partition.

Now, after executing the fdisk command a prompt will come up asking us which partitions we want to delete.
If we simply type in: d, it will delete the default partition mentioned inside the parenthesis and then we should type in d 2 more times to delete the remaining partitions as well.

If we type in: p at any given time it should display us our partitions. Of course if we delete them all we won't have any.

Now we're going to make our new partitions.

First type in: n to start creating a new partition.

The first partition that we always want to make is the boot partition.
First it asks for partition number ~> just press enter without typing anything
Then it asks for first sector ~> again simply press enter without typing anything
And now it asks for the Last sector and how big you want it to be, usually here people give 512M but we're going to give 1G, so we just have to type in: +1G.

Then it will ask us if we want to remove a signature. If the disk you're installing in was empty from the beginning just press no, but if it contained something before and you're re-partitioning it, you gotta type in: Y.

Now, if we press p we can view the partition we just created.

Next, we're going to make 2 more partitions.

The next one is the root partition.

So, we first type in n to make a new partition, then on partition number and first sector we simply press enter without typing anything and on the last sector which asks the size of the root partition, we're going to give ~> +40G.

Now, it might or might not ask again to remove the signature and the same thing as mentioned above applies.

Now, we're going to create our 3rd and last partition which is our home partition.

So, again type in n and press enter 3 times and then it will automatically fill the rest of the space for the home partition and at this point if we press p we can see the 3 partitions we created.

And now we can type in: w to write the newly created partitions and now we have an empty hard drive with the 3 partitions we created and we should be back to the shell logged in as root.

Now, we can type in lsblk and see our hard drive and the partitions that we formated with their respective sizes.

The next thing we want to do is start putting file systems on these partitions so we can put files on them. (note that everything in linux works with files)

So now we will start by making our home partition and that should be: /dev/sda3 to be in ext4 file system format.
To do that, type in:



$ mkfs.ext4 /dev/sda3

Important note: we're going to format everything in this particular guide in an ext4 file system format, BUT if you're using an UEFI system (you can find that out by the command we run above) then you want to format the BOOT partition in fat file system format and then the home, root partitions in ext4.
But in our case we're going to follow the Legacy boot system and we're going to format all the 3 partitions in ext4 file system format.

Alright, and now it will take a while and once finished then we can make the root partition to be in ext4 file system format by running:



$ mkfs.ext4 /dev/sda2

And once that is finished as well we're going to do the same for our boot partition by running:



$ mkfs.ext4 /dev/sda1

!! If you're using UEFI then to format your boot partition in fat file system format you can use:



$ mkfs.fat -F32 /dev/sda1

And now we're done creating our file systems on our partitions and we're ready to start adding files on them!

And so now basically we're going to mount our partitions the way we want them to be mounted and then install our operating system which is basically one command and after that we're going to make a couple of changes and we're done!

Now, we first want to take the root partition and mount it to /mnt
To do that we run:



$ mount /dev/sda2 /mnt

And now we're going to make 2 directories inside /mnt, one for the home and on for the boot partitions.



$ mkdir /mnt/home
$ mkdir /mnt/boot

And now we can mount our other 2 partitions.



$ mount /dev/sda1 /mnt/boot
$ mount /dev/sda3 /mnt/home

And now we can run lsblk and we'll see our partitions mounted to where we mounted them. (basically where it's supposed to be mounted)

And now basically we're ready to install our operating system, and we will do that with the following command in which basically we're going to tell it where exactly to install the operating system and then we're going to tell it what exactly we want to install. (remember that you should be connected to the internet)
Note that the below command is for the runit init system of the Artix Linux. You will need to install different things for s6 or openrc. (Head to the installation guide on artix linux wiki to find out what should be done)



$ basestrap /mnt base base-devel runit elogind-runit linux linux-firmware vim curl gcc git # and basically whatever other program you want here to be installed.

And now once the above command is done, we basically have an operating system installed on our hard drive, but we can't boot to it because we haven't set yet a bootloader and a couple of other things, so we're going to first set a bootloader.

So basically when we reboot our computer it we need to tell it in what ourder our moun points should be. i.e. in simple manners the boot partition to the boot mounting point, the home partition to the home mounting point etc...

So, if we run:



$ fstabgen /mnt

We will see where everything should be mounted.
Now we want to give a couple of options to this command:



$ fstabgen -U /mnt >> /mnt/etc/fstab

What -U tells it it's that it should read the partitions based on their UUID and not on the sda,sdb,sdc letters because those might be different on different computers but their UUID's are unique and so we definetely want it to be like that, and then we append that to the fstab file in the /etc so each time we reboot the computer knows where everything is mounted when it boots again.

And now we need to run the following command, and basically we then should be inside the actual installed operating system and not on the bootable usb drive.



$ artix-chroot /mnt

Probably we'll get prompted to the default shell which is sh but if we run: bash we should get to the bash shell with all it's features etc...

Now, what we want to do is edit the mirrorlist file and basically what we want to do in that file is move on top of the file the mirrors which are closer to the country we live in. (simply for better pings and ms and so on...)
To do that:



$ vim /etc/pacman.d/mirrorlist

Now we might want to set our local time zone.
To do that we'll create a simlink to the /etc/localtime and the command for that is:



$ ln -sf /usr/share/zoneinfo/your_time_zone_here /etc/localtime

And now if we run:



$ ls -l /etc/localtime

It will display our local time, actually where we set our system to be located...

And we might also want to update our hardware clock to be in sync with what we set above..



$ hwclock --systohc

And now we're going to open up the following file:



$ vim /etc/locale.gen

To set our system and keyboard main language.
How?
Simply uncomment the one that corresponds to your language, for example en_US (both UTF-8 and ISO)

And then you save the file and run:



$ locale-gen

And then we're going to create a new file:



$ vim /etc/locale.conf

And basically you want to type in: LANG=en_US.UTF-8 and then save the file.

And now we're going to install some essential packages.



$ pacman -S networkmanager networkmanager-runit

Now we want to tell Artix to start network manager every time we boot up. (This again will be different for runit, s6, openrc)

To do that:



$ ln -s /etc/runit/sv/NetworkManager /etc/runit/runsvdir/default/

And basically that's how you tell runit to automatically start a service every time you boot up.
Also, inside the directory ~> /etc/runit/sv/ you can find all the services that you can tell runit to start automatically on boot and that's where the NetworkManager is located.

Important note Actually the only time that you link a service to the /etc/runit/runsvdir/default/ is on the very first installation time as we're doing right now. BUT, you should from the moment the system is installed and on to simlink services only to the: /run/runit/service!!!

Now, we want to edit the following:



$ vim /etc/hostname

And basically we add on the 1st line (the file should be empty) the name of the computer that we want it to have. ex: desktop

Save the file and then edit:



$ vim /etc/hosts

And add in there the following lines:
(you can find more info on the details on the Artix wiki installation guide)



127.0.0.1    localhost
::1          localhost
127.0.0.1    desktop.localdomain desktop # <~ desktop is the name we gave to our computer in the hostname file.

Save the file.

And now finally we're going to make our machine bootable by installing a bootloader.

i.e. grub in this particular guide but you can choose any bootloader that you like.



$ pacman -S grub 

# note here that if you want to sometime do a dual boot on your machine you need to install the program: os-prober as well.
# also if you run UEFI instead of Legacy Boot you need to install as well: efibootmgr

Now we need to set up grub (this command will again be different for UEFI vs Legacy Boot)

For Legacy Boot:



$ grub-install --target=i386-pc /dev/sda # <~ your hard drive that you're installing the system, check with: lsblk

For UEFI:



$ grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

Dual boot with windows 10 (optional)

at this point I want to add a couple of steps in case you want to dual boot your artix (arch) linux installation with windows 10.

It is a prerequisite that you have already installed windows 10 in a separate partition from our above 3 created Linux partitions BEFORE starting the Linux installation.

So for example you could have a /dev/sda4 partition with windows 10 installed in it.

It's best practice when you want to dual boot, to first install Windows 10 on your empty disk drive and then allocate from inside windows some free space for your Linux installation.

But, if you had already Linux installed, then it's still possible to do the dual boot. First backup your /home directory to an external hard disk drive by providing the following command:



$ rsync -a --delete --quiet --progress /path/to/backup /location/of/backup

-a, indicates that files should be archived, meaning that most of their characteristics are preserved (but not ACLs, hard links or extended attributes such as capabilities)

--delete, means files deleted on the source are to be deleted on the backup as well

Here, /path/to/backup should be changed to what needs to be backed-up (e.g. /home) and /location/of/backup is where the backup should be saved (e.g. /media/disk).

And after doing so you should then boot with your bootable artix usb stick and delete the /home partition with fdisk so you can create some free space for your windows 10 installation. After deleting the /home partition, you should have some empty free space of some GB's and you can create 2 new primary partitions as we did above, 1 for the new /home directory for Linux and the other 1 for the Windows installation. So assuming that the 4th partition is named /dev/sda4 (you know now how to find that), you should boot from your Windows 10 bootable usb stick and install Windows on that particular partition. After doing so, windows will take over Grub so you want be able to see your Linux installation and your computer will automatically boot to windows, now is the time to use your Linux bootable usb stick again and follow the procedure of the Linux installation of this article from the beginning (deleting the 1,2,3 partitions and re-creating them again without touching at all the partition 4 (which is the windows one) and then follow the following 3 last commands and you will have both operating systems on your machine). Then you can use your /home backup to bring everything back on your Linux installation.

As mentioned above, if you want to dual boot any arch distribution with any other operating system, you need the program: os-prober. You can install it either earlier when we installed our base programs with basestrap or even at this point we're right now by typing:



$ pacman -S os-prober

!!! NOTE, there is a case that os-prober might not detect your Windows 10 installation automatically (in our next steps), so for it to do so you need to install as well the following program as well:



$ pacman -S ntfs-3g

Now, at this point if we run the command



$ os-prober

We should see that it detects our Windows 10 installation on your 4th partition and then after generating the grub configuration file with the below command we should see that it contains our Linux installation and our Windows installation and we're good to go!

If we reboot now, we should see grub with our Linux, Windows installations!



$ grub-mkconfig -o /boot/grub/grub.cfg

And last thing to do is to set up a password!



$ passwd

And at this point we're done and you just managed to install Artix linux from scratch, congratulations!

Now... after all this work your face should be like ~> 😑
Because you'll find out that you booted up and you just have a plain dark tty (terminal).
But! That is exactly the magic of installing a linux operating system without a pre-installed desktop environment and have all the setup we did above be made automatically by the image, just to get a better understanding of what's exactly going on behind and the scenes and thus have a better "connection" with your own machine that you built from scratch (well not 100% from scratch, because obviously you didn't write all the C code of all the commands that we run and of course we already had a ready Artix Linux distribution image and thus a linux kernel, so the whole Kernel is written by someone else, but yeah you get the point...)

And now what? Are we stuck with a plain tty?

Well, no if we don't want to. We can now start installing a graphical environment or our own window manager and our preferable shell and a display manager (login screen) and basically whatever else program you want or even a desktop environment with those pre-installed just to learn how to play with them and how they operate and to be able to configure everything yourself and that's exactly the magic of Linux!

Or at this point you could even run a bootstrapping script that someone else has written and basically what this is, it's a shell script that installs automatically everything that is mentioned in the above lines + some extra configurations of the person that wrote the script + their dotfiles and so on...
Basically this will get you up and running with a complete graphical environment, but of course with configurations of that person that you'll have to learn how to use or modify them to your liking.

I'll provide right here a script that I personally really like as promised in the beginning of this article, and it's called LARBS and it is written by Luke Smith.
You can find information on installation and more ~> here.

Basically, after you're done with the Artix installation you simply run the below commands and follow the UI and you'll have your fully nice and ready to go operating system with all the functionalities and configurations and programs that Luke had in his bootstrapping script! Of course you're free to change everything (recommended) to your liking or learn to use his system if you like it and keep it as is.



# should be run as root

$ curl -LO larbs.xyz/larbs.sh
$ bash larbs.sh

or:



$ git clone https://github.com/LukeSmithxyz/LARBS.git
$ cd LARBS/ 
$ ./larbs.sh

Author: Andrew Pappas

Thank you!