dotfiles VS twiner

This is how I do it, and I get maximum control over the installation.

I have a very similar setup, but I use my custom wrapper over startx. Nothing fancy though: https://github.com/myTerminal/dotfiles/blob/master/.scripts/linux/mt-desktop-mode

I've used Arch for a while before switching to Debian and then Void. I still install my system using chroot (I did debootstrap for Debian too), so I did read the Wikis (and still do) and keep looking to install other distros the "Arch way".

I've been using this and this and I don't really care anymore.

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.

I start from here and then it takes me to this, eventually to i3wm.

I've been maintaining my own dotfiles on GitHub for over seven years now (and probably have also overdone it at some point of time) and though I've had some small challenges to use them across machines, I've never experienced something as big that I'll need a third-party "dotfiles management" tool to take care of that for me. I sync it through my GitHub account and pull updates regularly. Fun fact: I've also been able to use the same one across macOS, Linux, and even Windows at work!

All that we need for this step resides under here and fortunately, with all the scripts arranged as an independent Bash program, we'll only be running a single command and the scripts will take care of the rest for us.

At one point, I eventually started maintaining a single bash file in my GitHub dotfiles with the command and so there was no need to maintain spreadsheets anymore. This arrangement also allowed me to document the commands required to configure additional package sources and remained as a single file for quite a long time until one day it all of a sudden exploded into multiple smaller files each for its own purpose.

My setup is pretty-much automated as you can see here. I also have been keeping a separate partition for my home for years now, most of the data within being synced via Syncthing on several devices, and then I use pCloud for super-huge files. With BTRFS, the home now remains in the same partition as a dedicated sub-volume and I'm liking it till now.

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.