Read the rest of the paragraph and also the next paragraph if you haven't yet.
If that didn't answer your query, do you oppose the following statement found on Gentoo's wiki:
"systemd is a modern SysV-style init and rc replacement for Linux systems."
And if so, why?
Thank you for the reply!
Are you referring to use those packages as default?
I don't understand why this is relevant. But, to answer your question, a modern system should already be on systemd, Wayland and PipeWire unless one has (for some reason) ideological qualms with systemd or if the maturity of Wayland isn't quite ready for their specific needs.
The "should" used earlier isn't used as my personal bias or whatsoever. It's simply the default found on the upstreams projects. GNOME and KDE (the most popular DEs) default to Wayland. PipeWire has become default for at least GNOME (even on Debian). And systemd is the default on almost all Linux systems.
Furthermore, this set of software is not a random set for which Fedora happens to be the first to adopt. In fact, these are crucial parts of how we interact with Linux; these constitute the backbone if you will.
Afaik Fedora OS is not even rolling release
Firstly, no one refers to Fedora as Fedora OS. Secondly, Fedora's release cycle is often referred to as semi-rolling release. With that, it's meant that some packages arrive as they come (very close to how rolling release operates). However, other packages only arrive with the next point release. Though, Fedora has its Fedora Rawhide branch that operates as its rolling release branch.
However, the fact that you mention this, means that we have misunderstood eachother. I don't claim that new versions/updates arrive first on Fedora. I don't even claim this for any of the earlier mentioned packages. However, what I do mean is that Fedora is the first to adopt these technologies in the first place. So, the first release/version of systemd, PipeWire, Wayland etc was released on Fedora. Then, within months or years, it was adopted by other distros as well.
so I cannot fathom how it has packages earlier than the typical bleeding-edge candidates.
See previous paragraph. And, you don't need to fathom it; I'm just stating the facts. If you do seek a reason, it's related to Fedora's relation to Red Hat and how most of these technologies originate from efforts coming from either Red Hat employees or made possible through their funding. Then, when it comes to testing those things, Fedora acts as their guinea pig. That's why Fedora is sometimes referred to as Red Hat's testing bed distro. This doesn't only come with its positive side, because it may also come with a negative impact to its stability. However, if one is interested in what's next for Linux, then there's no alternative to Fedora.
Why are you mixing Fedora Atomic with the regular Fedora Distro?
Because OP actually was in praise of Fedora after using Fedora Kinoite (i.e. Fedora Atomic KDE). And then, you critiqued it (i.e. Fedora) for having no selling points. So, it was rather ambiguous.
Furthermore, Fedora has actually mentioned (for at least two and a half years now) that they intend for Fedora Atomic to be the future of Fedora. So, in a few years of time, what we'll refer to as Fedora will simply be Fedora Atomic of today. Take note that this doesn't mean that traditional Fedora will cease to exist. Rather, it will be referred by a different name (perhaps Fedora Classic (but I actually don't know)).
...how is something like this objectively valid?
Alright, I made a couple of claims:
"It’s also the most mature attempt.";
First of all, we'd have to properly define what "Nix'ify" even means or what I used it for. So, in the simplest of terms, I meant it as "Taking design elements of NixOS and applying them to an existing product. And then publishing/releasing it as a new product."
So, basically every distro that's commonly referred to as 'immutable' and that's originated from or has loose relations to an existing distro applies. Therefore, something like Guix System does not apply; because it's an entirely new project with nothing that pre-existed it without its NixOS influences. On the other hand; Fedora Atomic, openSUSE MicroOS Desktop and the upcoming Ubuntu Core Desktop definitely do apply. (If the upcoming Serpent OS is "Solus v2" then we can also mention that one here). The addition/admission of distros like Arkane Linux, AstOS, blendOS, MocaccinoOS, Nitrux and Vanilla OS (to name a few) is murky, but (for the sake of argument) we'll not exclude these.
So, a proper study of their relative maturity would require a lot more effort than either of us is willing to put into. But, I made the claim based on the following (in alphabetical order):
(And finally) Rate of 'Nix'ification'; Atomic -> Reproducible -> Declarative. These stages are passed through by aspiring 'immutable' distros when Nix'ifying.
For example, from almost its inception, Fedora Atomic was atomic and had a healthy portion of reproducibility. With the relatively recent transition to OCI (for updating etc), it also became (somewhat) declarative and further improved its reproducibility.
Likewise, we see similar developments in other projects:
Fedora Atomic has (almost) completed/finished its "Nix'ification". While the same can be said about other projects, this does not apply to all of them. Hence, even if Fedora is not necessarily the best at this, it definitely finds itself amongst the frontrunners.
"Derivatives like Bazzite are the product of this endeavour."
This is simply a fact. Bazzite is only possible because of Fedora Atomic.
"From the OG distros, only openSUSE (with its Aeon) has released an attempt."
I define OG distros as the big, independent distros that will probably never lose their relevancy. Think of Arch, Debian, Fedora, Gentoo, NixOS, openSUSE, Slackware, Solus OS, Void etc. For the sake of argument, we could include all independent distros. Out of these; Fedora, openSUSE, Solus and Ubuntu are the only ones for which we know their team/organization are actively working to erupt an 'immutable' distro while (originally) their distro followed a traditional model. Ubuntu Core Desktop has yet to release and the same applies to whatever Solus is cooking. From openSUSE, we have openSUSE Aeon (and Kalpa) and for Fedora we got its own 4 atomic spins. Furthermore, we got dozens of derivatives based on Fedora Atomic. So once more, this is just factual.
"However, it seems to be less ambitious in scope and vision."
This is definitely a loaded claim. I'll answer this in my next comment.
I understand you like Fedora
Exactly. But it's on merits. On the other hand, it seems as if you dislike Fedora for some reason. However, it's unclear to me as to why that is.
but you make claims without any proof or just pure opinion based.
I can back up (almost) every claim I'm making (as you should have noticed by now). Not citing sources or whatsoever is due to laziness and because I don't think you'll check those sources anyway (like how you seemingly didn't check if the earlier mentioned software indeed were first adopted on Fedora and if so; why). However, if you want me to cite sources on statements I make, then please mention the exact statements I'm making and I will back those up with sources.
It's also peculiar that you make uninformed guesses or claims without backing them up yourself. Nor do you feel compelled to look up if the unsure statement/claim is even correct or not in the first place. Though, I should at least compliment you for being honest/transparent when making unsure claims/statements!
Yet, I'm still waiting for you to name a distro with more impressive unique selling points 😜.
What’s your end goal here?
Incoming XY problem.
I want to prevent myself from reinstalling my system. The trick I came up with involved the use of files that couldn’t be disk cloned. However, if it’s far far easier to accomplish it through other means, then please feel free to enlighten me on this.
You try to keep files just on that one media without any options to make copies of them?
Yes.
Or maintain an image which has enforced files at their directories?
No, not necessarily.
And against what kind of scenarios?
Protecting myself from myself. That's where the password requirement comes in: I can send a delayed message to myself that holds the password. The end result shouldn't in the absolute sense prevent full access for always. Unlocking the protection should be possible and should require the involvement of the earlier mentioned password that is received through a delayed message. That way, those files can be accessed eventually, but only after I had intended to.
ACLs and SELinux aren’t useful as they can be simply bypassed by using another installation and overriding those as root
Excellent! I didn't know this. Thank you for clarifying this for me!
Only thing I can think of, up to a degree, is to use immutable media, like CD-R, where it’s physically impossible to move files once they’re in place and even that doesn’t prevent copying anything.
The files should remain on the same disk that I run my OS from. So, unfortunately, this doesn't quite help me. Thank you regardless!
Understood. Thank you!
It has been my pleasure!
and joined their discord in preparation.
That will definitely help out a lot. Well thought!
Welcome on board 😉.
Seems interesting. Got any sources to read up on? Thanks in advance!
It's definitely a hidden gem. Enjoy!
First of all, if you'll be using Bazzite, then become familiar with its documentation. Other sources may not necessarily translate that well to Bazzite due to Fedora, Atomic, OCI and SELinux (to name a few). Though, some other sources may benefit you as long as it doesn't contradict with Bazzite's own documentation.
so, what are your tips and tricks for a new linux user?
Bazzite is on Fedora Atomic's model, hence you should become familiar with the built-in rollback mechanism. Furthermore, it's possible to keep deployments around. Therefore, if anything, consider utilizing this on your first deployment; just in case.
Pinning said deployment is possible with the sudo ostree admin pin <insert number> command after installation. The number can be deduced through the rpm-ostree status command. The first deployment's corresponding number is 0 and for each deployment found below you just have to increase the number by one to find its corresponding number. So, the 4th deployment corresponds to the number 3. Btw, you can pin multiple deployments. So there's no opportunity cost involved. Finally, you can unpin a deployment with -u. So sudo ostree admin pin -u <insert number>
as a final question, what got you into using linux over windows or mac?
I was never a mac user in the first place. As for Windows, a hardware failure was causing more issue on it than on Linux. So that was the direct cause. But the reason I got interested into Linux initially and what has kept my interest are privacy and freedom respectively.
Interesting!
So, I guess that at least one of the following 'transitions' is 'blameworthy':
I guess I'll pass out on it for now. Thank you though!
I’d like to know if it works for you now. I only ran the commands from the post and everything worked ootb
Aight. Let's give it a go:
Well..., for some reason it didn't work. FWIW, I'm on the bluefin-dx-main-userns-hardened image as provided by secureblue.
That makes a lot more sense. Thank you for clarifying!
So..., you don't think it will make a difference. However, you do affirm that whatever CachyOS does is noticably better than the rest.
Perhaps more importantly, have you actually measured 1% lows or 0.1% lows on games. And did you compare how different distros fared in this regard?