https://web.archive.org/web/20230112002240/https://beefymira...
Personally I feel a good way to get involved is to test updates in bodhi for those packages you care about, or to take part in the process that happens around release time where we go through several freeze cycles and have 'blocker bugs' that need their fixes to be validated: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
At least 6 years ago, this was not entirely true: a package happened to build only because, by happy accident, the builder had a dependency installed by something else. Since the dependency was not in its Build-Requires:, the build would fail in COPR, which really used a clean room. A case of being saved by the alphabetic order, I guess?
Maybe they have updated Koji since.
It's definitely possible that one of a packages build dependencies pulls in something that a package /should/ depend on and then when it drops it suddenly the build fails. That's why I think we mostly want 'autogenerated' BuildRequires nowadays that are generated based on the upstream source or packaging format to make that less of a figuring out excercise.
For example, I tried to config gpsd to use another port, nothing would work; systemd quietly overrides gpsd's configfile and required additional systemd incantations to change what should have been easy. And the man pages are a mess
And journalctl makes me want to pull my hair out; just let me grep a regular file - discovering namespaces is a nightmare
Some programs can crash when all their files are suddenly swapped for new ones. I've seen multiple linux systems bork themselves during an update because the update itself caused the desktop session to crash, which caused the update process to be interrupted just as it was modifying some crucial files, thus rendering the system unbootable.
https://suckless.org/sucks/systemd/
https://without-systemd.org/wiki/index_php/Arguments_against...
> he systemd project has many different components but they're independent
They _are_ dependent. It's one codebas, and even if you somehow separated it - you would still only have systemd-specific, systemd-dependent replacements for _actual_ independent components.
They all depend on systemd and won't work with anything else, nor on any other operating system either.
>> The proof this site is misnamed is that a post criticizing systemd gets downvoted, probably by people who have never questioned why an [[ init system ]] needs to become half the operating system.
So no, I didn't bring it up.
I find the whole argument kind of dumb anyway. People talk about this as if it was a violation of the "Unix Philosophy" when Unix and BSD are developed even moreso in the same way - the init system is sitting in the same repo as the libc, the kernel, and the entire rest of the OS. Linux is alone amongst operating systems in making core system components swappable like to that degree in the first place. It's fine to like that kind of flexibility, but a bit silly to act as though that approach is fundamentally superior. If you want to use non-systemd tools, use a non-systemd distro, that is your choice. Just quit whining about 99.9999% of the other software users on the planet not catering to it.
No, it is not my choice, because I'm not talking about my PC at home, but rather what organizations use - commercial companies, universities, schools, NGOs etc. And also what users are taught to handle and work with.
But it's not even that: I want systemd to be _dropped_ as a default part of the main Linux distributions. I want only the people who explicitly prefer systemd, to use systemd, and not the rest.
As for the "dumb argument" etc. - what you're saying is that because the different BSD distros are monolithic, then not only should Linux become that way, but - all of the lower-level Linux userspace, above the kernel, should just be handed over to the benevolent oligarchy of the systemd people.
That's a bad idea, both in principle, and also in practice, due to the innumerable problematic design and implementation choices systemd has taken - which developers and sysadmins/power-users did not mandate, agree to or support.
If there was a complaint about how systemd complicated builds and tests in a specific way the commenter could name, that'd be valid. Just finger-wagging is tiring after how many, 10 years?
It's similar for systemd. It's a poor architectural choice and it needs to be undone. And that's ignoring the personal drama surrounding it over the years which, indeed, needs to be let go by now.
As for topicality: This post is about the "sausage" that is a distribution. Following this metaphor and mentioning a problem with a certain kind of sausage is on-topic.
I had a service complaining about the root file permissions which changed between Fedora versions [1]. I was never able to figure out what produced the file system image but thanks so this guide I know where to start looking now.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=2402944#c1