•  AutoTL;DR   ( @autotldr@lemmings.world ) BEnglish
    7•8 months ago

    This is the best summary I could come up with:

    While delayed by several weeks compared to their initial release goals, today marks the availability of Fedora 39 as a wonderful upgrade to this popular Linux distribution.

    Fedora Workstation 39 makes use of the GNOME 45 desktop for having all of the latest open-source desktop capabilities, the LibreOffice 7.6 office suite, LLVM 17 compiler stack available, and many other updated packages available.

    Fedora 39 is shipping with the Linux 6.5 kernel although newer versions will come down as stable release updates.

    Fedora 39 also has various toolchain upgrades such as GCC 13.2 with GNU Binutils 2.40, Glibc 2.38, and other updates.

    I’ve also been running Fedora Workstation 39 on my main production system already: the Lenovo ThinkPad P14s Gen 4 with AMD Ryzen 7 PRO 7840U.

    I’ll be delivering some additional Fedora 39 Linux benchmarks in the coming days on Phoronix.

    The original article contains 211 words, the summary contains 141 words. Saved 33%. I’m a bot and I’m open source!

  •  DidacticDumbass   ( @DidacticDumbass@lemmy.one ) English
    4•8 months ago

    I am thinking of switching from Linux Mint to Fedora. I have always liked Fedora, but have been bitten by some BS like NVIDIA drivers not working and some programs only available as a .deb file (I know about alien… or do I?)

    I love GNOME DE, has that modern “I work on a spaceship” feel.

    I mostly do music production and some gaming, so pipewire seems intriguing.

    Here is the real question: Should I got Silverblue? I just learned about distrobox, so maybe that is my solution for programs I cannot get through flatpak?

    •  skilltheamps   ( @skilltheamps@feddit.de ) 
      5•8 months ago

      You can install silverblue, and then rebase to ublue ( https://universal-blue.org/ ). Specifically to the “silverblue-nvidia” variant, and you should get a nice silverblue experience without any of the nvidia struggles, as people at the ublue project take care of that stuff for you.

      And yes, distrobox is the goto solution to run stuff that is basically ubuntu-only, or by extension bound to any distro variant / version and not flatpak. This includes graphical applications. Distrobox works great, I do all my work in it.

          •  DidacticDumbass   ( @DidacticDumbass@lemmy.one ) English
            2•8 months ago

            Oh, I totally misunderstood the OS. I was under the impression that using os-tree should be totally avoided for anything other than necessary system programs, and all other software should be installed with flatpaks or containers.

            I now understand that using os-tree for some programs is inevitable, and I should embrace it, though still catiously to maintain as clean of an OS as possible for maximum longevity.

            •  alt   ( @alt@lemmy.ml ) 
              1•8 months ago

              I was under the impression that using os-tree should be totally avoided for anything other than necessary system programs

              Interaction with ostree directly shouldn’t occur that often; with sudo ostree admin pin *number* (and its -u option) probably being the commands your average Joe should interact with. You probably meant rpm-ostree.

              and all other software should be installed with flatpaks or containers.

              It’s indeed true that initially Fedora intended flatpaks should be preferred. If the software isn’t available there, then Toolbx(/Distrobox) is used to access it through a container. And if all else fails, then it’s layered through the rpm-ostree command.

              I now understand that using os-tree for some programs is inevitable, and I should embrace it, though still catiously to maintain as clean of an OS as possible for maximum longevity.

              You’re getting the drill! Though, I wonder why you weren’t able to rebase to uBlue and had to resort to installing the Nvidia drivers through RPM Fusion instead. It’s fine as long as it works, but I imagine that some issues might arise eventually. So consider sharing the steps you took so that the community might help out; perhaps even over at uBlue Discord. You could also just share it here if you will.

              •  DidacticDumbass   ( @DidacticDumbass@lemmy.one ) English
                2•8 months ago

                Honestly, I just followed the steps here: https://rpmfusion.org/Howto/NVIDIA#OSTree_.28Silverblue.2FKinoite.2Fetc.29

                I was diligent about following the configuration guide first: https://rpmfusion.org/Configuration

                I think the key is restarting at every step it asks you to, and maybe after anything that seems major or is a prerequisite for another set of program installs. I mean, I got a black screen the first time, but after a hard reset, it just worked.

                No doubt UBlue is probably a lot easier. I did not realize I could have just downloaded the ISO instead of trying to rebase, but I like what I am running.

                Anyways, doing it the hard way is helping me learn the intricacies of an immutable system, so I am having fun.

                •  alt   ( @alt@lemmy.ml ) 
                  1•8 months ago

                  Ah, I got it now thanks for the explanation!

                  Indeed, in your case acquiring uBlue through its ISO was probably the best option; but I’m glad to hear that it worked out in the end!

                  Anyways, doing it the hard way is helping me learn the intricacies of an immutable system, so I am having fun.

                  Well said!

                  Just in case; consider the following:

                  • Pin your current working deployment with the aforementioned sudo ostree admin pin 0 command. After which it remains accessible regardless unless you unpin it later on. This should allow you a working deployment if all else fails and thus a safe haven to rely on.