Psst! Hey you! If you'd like to watch a video instead, check this out:
I really like Linux.
I love customizing my stuff, having full control ...
For further actions, you may consider blocking this person and/or reporting abuse
Instead of doing it this way, you can enable a systemctl service
paccache.timerThat's good to know, thank you!
I just star using arch for a few months.
The reason I choose it because it only install required things to run os in my machine and the only things I install manually are firefox, code oss, a requirement for garbage bin, thing about sound and thing about reading an USB/external hardisk.
The only thing I customize are hide all the menu in terminal and context menus as much possible.
Like everything else, life and computing are both based on a combination of availability, circumstances, interests and skills.
I've used plain Arch Linux in the past and from a functional point of view, it's as close as anything (including Gentoo Linux and Linux From Scratch) at getting very close to PRECISELY what you put into it; balanced against this "truth" are the number of commands, effort, and time it takes, the more you build from the most fundamental starting point.
I HAVE tried it both ways. For me, the benefits (and time) did NOT justify the effort. For me, I did not feel that I gained a sufficient amount of efficiency, and since I'm able to figure things out when I need to do so, it doesn't bother me that I don't know every possible thing about every single app (or byte of information). Others may wish to go there: "all of the credit to you for your effort".
I personally find both Cachy OS and Endeavour OS to be excellent implementations of Arch Linux. They save me time, still give me plenty of flexibility, and they look and function quite well. They also complement the other collections of mostly Debian-based systems, plus one instance of Slackware CURRENT. That gives me different systems (and packaging methods) to use, different appearance, but one thing in common: I can build or rebuild any of them with moderate effort in well under an hour, and all of them, if necessary, in about two hours, thanks to my collection of installable, mostly configured Flash Drive snapshots of several distributions.
So there's my high level overview of "doing it another way".
Your way is quite interesting, but I choose another path. Among the readers, I imagine that we have thirty or forty different approaches, possibly more than that, and I'm pretty sure they all meet our own individual needs and interests.
I think when is mentioned "productivity", is better focus on how setup Arch to just "work" and not how to customize "login screen".
I am able to get a lot of "productivity" in Arch, and one of the biggest advice I can give is:
BTW, in your script for clean packages you could use
yay -Sccc
To clear all cache of Packman and yay.
Great points! I completely agree—when it comes to boosting productivity with Arch, keeping the system lean and functional is far more beneficial than over-customizing things like the login screen. Installing only the essentials and updating regularly really keeps the setup efficient, and choosing a desktop environment that adapts to your workflow rather than forcing you to tweak it is key. Also, thanks for the tip on using yay -Sccc to clear cache—it’s a handy command for maintaining a clean system. Your approach perfectly embodies the philosophy of a productive Arch setup 😄
Thanks for the tip!
Have you considered utilizing time shift to create auto snaps for each update so that if there were ever an issue during an automated package update you would have a method to bring your system back to a working state. That was always my concern with automating updates, although it is rare I have always been of the opinion it was best to retain control over the time and situation the device updates. Timeshift offers a method to utilize BTRFS and grub boot loader to save your snapshots so that they are available form the grub in the off chance that part of your system were to break. All in all great stuff, have a similar script I run but have spread the updates out to every 48 hours and just after my work day. Cheers!
I do really like that idea. To be fair, I don't completely automate that script (but with timeshift, maybe I should!)
the youtuber typecraft has a pretty succinct video walking through the setup, sometimes if I don't set it up and something happens I kick myself because its so easy
Your article starts with you love Linux the goes on a journey of building a desktop environment from scratch and ends with your giving up for a Mac. You also mention early on that if someone just wants productivity, they should buy a Mac. This article is super flawed because you as an author immediately kill your article before it begins. Then you proceeded to suggest Arch Linux to what I can only assume would be a target audience of Mac users. No, one does not need to subscribe to Apple to be productive, that might be the most asinine dev article premise I've read this whole year. There are numerous distros that are better suited to this purpose than Arch.
It's just a bit of sarcasm 😄
Is it Systemd free?
Why not run that script using a cronjob instead of doing it manually each month?
I want to make sure everything works after an update. Nvidia drivers have a habit of being a little bit self-destructive every now and then.