Gonna take a bit. The dudes been doing the releases for over a year, everything they touched is suspect now even if nothing earlier is known. Also some other associated accounts have been doing shady stuff too.
And that’s just one project that had a burnt out maintainer who welcomed some help from this guy. There are probably others. The hobby project becoming a core piece is a big issue.
When upgrading to the beta, does it become the stable release once that’s out via regular dnf package upgrades? Or are you then on some kind of beta channel that you have to switch back from?
You’ll want to use the terminal and run “sudo dnf upgrade”. If there’s any issues after that, just run “sudo dnf distro-sync” to ensure everything’s using the final release repo’s. The sync command is strongly recommended but not always necessary.
Hopefully DNF5 gets in for F41, especially since it was supposed to get in as the default for the current release, F39. If anyone’s curious, here’s the vote for deferring: pagure.io/fesco/issue/3039
And the reasoning given by the DNF5 team for targeting F41 instead of F40: …fedoraproject.org/…/EYE2JY537OM7GFW46EK7YIBLHJ52… (though fesco also wanted to keep it in F41 to not disturb the mass branching from F40 to RHEL 10)
It has been a while since I used fedora. I believe the last time was fedora 31 and heard murmurings of a dnf rewritten in c++ to be faster. Glad they actually pulled it off.
If you are a modder that wants to do stuff like replace the kernel, add in rust coreutils etc, then I think NixOS is indeed better. Have not used it but really want to try.
Image based Distros are just perfect for people that want to have perfectly reproducible bugs, or in general not many.
It is a good community concept, but tbh a preset of shared Nix config files could do the same thing too, with ease. Just dont deviate from those configs and you will have multiple people with the same systems.
Damn, rust really embrace the “Hey, Can I copy your homework?” Meme. I like rust btw, it’s just funny how often I see something along the line of “it’s like X, but in rust!”
This shows something else. The traditional languages are all more common than Rust.
I suppose Go could be a good competitor, and I read a thread comparing C=Go, C++=Rust.
I just see a lot more rust in many projects, and it is well integrated with GTK for example. I also know of several drivers and modules written in Rust.
At least in Linux, Go seems to be used for WebTech more than for other things.
I am interested in a discussion about that, as I would like to learn one of these languages, but Rust seems to have a better ecosystem with more adaption, ready GUI toolkits, a Linux Desktop, multiple GTK apps etc. in the making, while for example “Fyne”, Go GUI toolkit (that I found in the Flatpak “Rymdport”) doesnt even have Wayland support yet.
Exactly. The concept is great, but my Guix system (Nix fork from GNU) is already reproducible and capable of rollbacks and transactional upgrades (and declarative system configuration !)
The learning curve is quite steep tho (the Nix leaning curve is even higher, at least it used to be IMO). If the sway spin of Atomic Fedora was available earlier I probably wouldn’t have switched tbh. Both solutions are great.
Overall I’m quite happy with my Guix configuration. I’ve got roughly the same configuration on all my systems with ease, all config files (also sway for example) in the same language: Guile Scheme (LISP dialect), and the whole thing is in git. I don’t imagine going back to a regular distribution anytime soon.
Scheme is a more mature and more expressive language than Nix imo. And you can write your home configs in scheme too.
The differences aren’t that big, nix is great but I find (at least I did two years ago) the documentation a bit confusing. Both are great. I like scheme a lot better than Nix (the language), and the tooling is a bit less confusing to me.
Agreed. I used to use Silverblue and it was very stable but did not solve all the problems that Nix addresses. Once you experience the first reinstall with NixOS you will wonder why we did things any other way. It’s amazing to just run one command and have things set up exactly how you like.
Fedora may receive backing from RH, but it’s still community-ran. Similar to how Linux itself is backed by the likes of Google/Meta/Huawei/etc but is isn’t ran by them.
And they didn’t close-source RHEL. I don’t like the license changes they made either, but calling it closed source is inaccurate.
If you’re a customer of theirs, you can see the source code. The license customers agree to is certainly a restriction, but it’s not all of a sudden closed/proprietary software.
And finally, despite that recent move, RH remains probably the biggest contributor to desktop Linux. If you want to avoid their work… good luck. It’s literally everywhere.
I’m saying their source code is available to its users for auditing, changing, redistributing without risk of being sued for intellectual property violations.
That’s fine as far as the GPL goes. It doesn’t have to be public to non-users.
You’re basically saying that something isn’t wet, it just has water on it.
I’m saying their source code is available to its users for auditing, changing, redistributing without risk of being sued for intellectual property violations.
We’re saying the same thing, you just refuse to attach “closed source” to its definition. So answer me this: can anyone freely use it? Can only licensees use it? If the answers are no and yes respectively, that’s closed source.
I’m saying nothing of the sort.
You absolutely are. You’re using the word’s definition (source code available only to licensees), but won’t say the actual word (closed source).
No, we aren’t saying the same thing, because you’re talking nonsense and I am not.
Closed source means computer programs whose source code is not published except to licensees
Nowhere in your link does it actually say that. And amusingly, by that definition, software where the source code isn’t provided to licensees isn’t closed source. What? So software where the code is a total black box that nobody other than the programmer knows isn’t closed source in your mind?
But here’s something it does say:
Proprietary software is software that grants its creator, publisher, or other rightsholder or rightsholder partner a legal monopoly by modern copyright and intellectual property law to exclude the recipient from freely sharing the software or modifying it
Let’s go through the two listed criteria, shall we?
Legal monopoly to exclude the user from sharing the software: RHEL doesn’t have this. They can’t sue anybody for sharing the code.
Legal monopoly to exclude the user from modifying the code: RHEL doesn’t have this. RHEL users are free to modify the code as they wish.
Saying “if you clone and republish RHEL, taking advantage of our work to undercut us with minimal effort, we reserve the right to not have you as a continued customer” is perhaps against the spirit of many open source licences, on that I agree, but it’s a far cry from being closed source. RHEL isn’t like MacOS or Windows.
It’s hard for me to take you seriously when it does and I literally copy/pasted from the link. Even if you don’t read the whole page, you can’t even do a CTRL+F correctly.
It literally doesn’t. Please stop lying. Everybody can see you lying. It just makes you look like even more of an idiot. You don’t want to look like even more of a idiot, do you?
I’ve used your own source to dismiss your argument.
But here’s another, just to drive the point home even more:
Calling me a liar (when it’s easily provable I’m not, I even included a screenshot for you) devolving to insults, calling me a kiddie and an idiot? If you can’t even formulate an argument without insults and you fail twice to read a link, yep, we’re done. Enjoy your day/night.
Jorge Castro has been the head of this project and I am excited by his vision. Bluefin aims to be the immutable desktop distro with the most sane defaults that also supports Nvidia.
It’s a mascot for brand recognition purposes, just like Tux the penguin. I don’t quite understand what the problem is. I feel like if I were to call anything about it weird, it would be the use of a derpy, chonky dinosaur rather than the gender of said derpasaurus.
if I were to call anything about it weird, it would be the use of a derpy, chonky dinosaur
Bluefin is a Deinonychus antirrhopus, a theropod dinosaur whose name means “terrible claw”. Discovered in the 1960s, she revolutionized our understanding of dinosaurs. Before Deinonychus, dinosaurs were often seen as slow, dim-witted creatures. However, she shattered these misconceptions, offering insight into the dynamic world of hot-blooded, rapidly evolving animals that were masters of their domain. We aim for our desktop to embody a similar nimbleness. Power and adaptability.
Yeah I had a similar experience when logging on to Sway - I had no clue what to do. Did you ever figure out how to bring up a menu or launcher? All I could do after googling was launch a terminal
I feel that I am 50:50 on it, immutable at least conveyed more information about what it is while Atomic feels a lot more “buzz-word-y” and does not convey as well what it means. Regardless, I’d say the bigger issue is keeping the old Silverblue & Kinoite names, they really should change them even if it means having a ~2 year period of having “Formerly Silverblue / Kinoite”.
Issue is that Immutable also conveyed a different type of information. When I first heard of it, I genuinely thought it was something like DeepFreeze for Windows
Are you familiar with the concept of “atomicity” in relation to database systems? It’s actually a very appropriate term, and the article touches on its use over “immutable”.
Good that these finally have a unified name now, rather than people just being expected to know that Fedora + [obscure mineral you probably haven’t heard of] means immutable, plus having no idea of what mineral corresponds to what DE.
Silverblue and Kinoite are cool names, but really they should be renamed to Fedora Gnome (or Workstation, to line up with their standard desktop naming) Atomic, and Fedora Plasma Atomic, like they’ve done with Onyx >> Budgie Atomic
I understand why they wouldn’t want to suddenly change the branding of existing projects though.
I understand why they wouldn’t want to suddenly change the branding of existing projects though.
I’m not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won’t immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.
fedoramagazine.org
Active