twiner VS calamares

You need to ensure that you have write access to the directory in which you clone a repository. I do have access, I could create directories and files, and I even ran an instance of Syncthing, synced a "folder" with another computer running Syncthing. It's just that git was having trouble. Following is what I see on the console: bash-5.1# git clone https://github.com/myTerminal/twiner.git Cloning into 'twiner'... remote: Enumerating objects: 450, done. error: unable to get random bytes for temporary file: No such file or directory error: unable to get random bytes for temporary file: No such file or directory fatal: Unable to create temporary file '/var/twiner/.git/objects/pack/tmp_pack_XXXXXX': No such file or directory remote: Counting objects: 100% (22/22), done. remote: Compressing objects: 100% (18/18), done. fatal: fetch-pack: invalid index-pack output

Getting to know Linux better from my initial days with beginner-friendly distributions to stepping into the manual installation of Arch (pacstrap), Debian (debootstrap), and Void (xbps) has taught me a lot more of Bash than I would have expected from myself. I now also maintain my personalized setup scripts along with my dotfiles. Furthermore, I also created twiner as a re-usable tool (that tries to be a lot of things at the same time), which "sort of" helped me deepen my understanding of Bash a little bit more.

Now that we have a running Linux system, we can bring in my custom setup scripts and set up the rest of the system with a little help from twiner.

I never had a proper introduction to shell scripting before and as far as I remember, my first shell script was indeed the simple packages installation script for my Linux setup. Needless to say, I started improving my setup scripts and soon realized that most of the scripts that I was writing could be re-used. Around the same time, due to my failure of being able to run a regular Linux distribution on my Dell Precision T3600 desktop due to the incompatibility of the super-old hardware with the latest Xserver packages, I literally had to learn setting up a command-line Linux for graphical use. More configuration meant adding more code to my setup scripts, and all this extra code was a perfect candidate for my library of functions for Linux setup and this led me to create twiner.

The reasons for wanting /boot to be unencrypted are varied. Maybe you want (much) faster boot time, or maybe you want to use a nice GRUB or Plymouth theme, or you use GRUB in a Multi-Boot scenario where you don't want/need to go through encryption first. Encrypting the /boot partition offers that extra .002% of security by protecting against Evil Maid attacks (https://en.wikipedia.org/wiki/Evil_maid_attack), but comes with several tradeoffs which may not justify using it when it doesn't really apply to 99.998% of peoples' threat model. We can debate this here, but I feel like this has been pretty extensively covered online (e.g. https://github.com/calamares/calamares/issues/1311) so feel free to do a search if you want to learn more. This guide is for people who are aware of the potential security risks, but for whom an Evil Maid attack is not something they need to worry about. Is this you? Cool! Read on...

Nitrux provides an eponymous Linux desktop distribution based on Debian. It uses the Calamares installer and includes the NX Desktop built on the KDE Plasma 5 desktop environment and MauiKit Applications.

You can add your own scripts or programs to this environment to make the installation process easier. There are a few third party distro agnostic installers you could include as well such as calamares.

But making an installer is hard to do from scratch. So you may want to modify an existing one, such as the one that elementaryOS uses, or the general-purpose calamares framework, in which case your installer is bound by the terms of their license to the extent you modified or are redistributing their code.

They use the Calamares installer which is also used by a bunch of other distros. https://calamares.io/

Yes, it is the Calamares installer. It is more straightforward than the Debian Installer in terms of questions and won't get too much into technical details that may overwhelm a newcomer and/or a non-technical person. The Debian installer is a bit more overwhelming, with the benefit of being a lot more flexible than Calamares.

I decided to try KDE and reinstalled my system from scratch. I chose encrypted Btrfs volume with Swap to disk and hibernation. Hibernation didn't seem to work at first and I had errors during the boot saying something about 'openswap'. So I started googling and found this issue on github. I fixed 'keyfile_device_mount_options' in '/etc/openswap.conf' as someone suggested there and it seems to help. I don't have any errors on boot and hibernation KINDA works.