Arch Linux Desktop Configuration (Post Install)

Рет қаралды 8,137

Күн бұрын

Пікірлер: 9

@micleh 3 жыл бұрын

I like your workflow and is similar to mine, i.e. reinstalling every so often to avoid bloat, making installations reproducible via a GitHub repo and amending the scripts (additions and deletions). Your GitHub scripts are really helpful to improve mine. Thanks.

@patomackcodes4093 4 жыл бұрын

Really enjoyed the setup. I am going to work to get towards reproducible setups as well. Love the idea that the configuration is independent from the hardware. Makes a hard drive failure or trading up to a different machine easy.

@michal1693 Жыл бұрын

Thank you, this is very informative. Hope for more videos from you. alias h='history' alias x='startx' alias systemclt='systemctl' alias sct='systemctl' #alias c='sh wayland.sh' alias psg='ps aux | grep' alias e='exit' alias mkdir='mkdir -pv'

@Oswee 3 жыл бұрын

I would suggest to invest a little bit into transforming those scripts into Ansible playbooks. It's not easy and takes some time and discipline, but once it's done, you have a nice collection of reproducible roles to spin up a fresh setup with the tools and configs you like.

4 жыл бұрын

Excellent! I should automate my Arch config, as well, just so I can restore it in case of a disaster. I do have timeshift snapshots, but those may be gone, too in case of a serious hardware failure. I'm thinking it might be a better idea just to document the configuration process (writing down exactly what I'm doing and why) instead of putting it all in a script, because the script will grow huge and I *will* forget what it does. Restoring it all might be a pain, but at least I'll know what I'm doing. When it comes to AUR helpers, yay is the one I use. I really like it, especially since it offers to display the PKGBUILD file before installing anything. And with trustworthy AUR packages, it can be really fast and automatic. It also keeps track of updates, which is really nice.

4 жыл бұрын

@@joshrosso Yes, I restored timeshift snapshots on both my Arch desktop, but especially on my Manjaro laptop, since Manjaro updates can break things in rather spectacular ways. Good experience so far with it, I wholeheartedly recommend it. For me, timeshift is mostly an insurance that, if I have a deadline with some project and I run an update that messes things up, and the software I depend on stops working, I can easily and quickly revert the machine to the state before the update, and finish what I'm working on. With a rolling distro on a production machine, I think having something like that is necessary. Especially on Manjaro where every update is a YOLO update, often several gigabytes in size. :-D That said, I never tried restoring a timeshift snapshot from one install to another, though. Let's say, my root HDD fails and I install Arch on a new HDD and then try to restore a timeshift snapshot. I have no idea whether that would work...