Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Fedora 34 and RHEL 8/clones Developer Workstation Setup Script (github.com/david-else)
14 points by indigodaddy on July 17, 2021 | hide | past | favorite | 8 comments


I have been leveraging `ansible` to store my development workstation setup since I found out that playbooks can be applied locally pretty easily. It removes a lot of script maintainence burden even though there are cases we still need to resort to manually written script. `ansible` is declarative, and idempotent. It reads easier than a procedural script (even to someone that has not used ansible before), and can make cross-platform easier.


I still use my first bash script, what is the maintenance you're telling about? (I'm serious)


Same here!

Something often overlooked, well written Ansible can be largely indifferent to the distribution. People tend to hone in on the idempotent aspect

I find my roles and custom facts are often useful; usually for things I wouldn't have guessed


Fedora 34 default workstation setup contains some bloat. I decided to use minimal install and then added necessary packages. I excluded gnome-software (along with packagekit, flatpak), X server (I'm using wayland), gnome-classic and some other packages. RAM consumption went from 1.5GB to 1GB after boot which is significant saving for me, considering that I only have 16 GB.

I have no idea why those packages are not optional. Dnf is perfectly fine for package management. Eating lots of memory for no reason is weird.


Fedora 34 Workstation (GNOME) with only gnome-software and packagekit removed idles at 650MB.

This is because the Fedora repositories are very large due to all their extra metadata and the inefficiencies of the yum packagekit backend. GNOME Software also always keeps its UI loaded even when not open.

You might also want to free up some space afterwards: sudo rm -rfv /var/cache/packagekit

PackageKit is nice because it allows (not so great [1]) offline updates. GNOME Software is nice because it allows your typical user to update and install software.

[1] https://gitlab.gnome.org/GNOME/gnome-software/-/issues/181


Offline updates are doable with dnf:

    dnf offline-upgrade download
    dnf offline-upgrade reboot
I'm not completely sure, but I think that gnome-software just uses those commands.

Those commands are provided by python3-dnf-plugin-system-upgrade package which is installed by default in workstation set.


Offline updates via dnf and packagekit are handled via systemd afaik.

gnome-software never directly calls dnf, it is solely a frontend for packagekit (and flatpak and fwupd).


Of extra note, X uses more memory then Wayland (as long as you have no X apps open), and classic is enabled through the use of shell plugins which also uses more memory compared to regular.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: