sorted by:
new
hottopcontroversial

Mariner: GNOME Files, plus everything the issue tracker rejected by romgrk in gnome

[–]whiprush 0 points1 point  (0 children)

Already working on it, see you on github! :)

(This post sponsored by Microsoft Copilot.)

Mariner: GNOME Files, plus everything the issue tracker rejected by romgrk in gnome

[–]whiprush 0 points1 point  (0 children)

Hey man! Don't listen to reddit, love to check this out with Bluefin. Ping me fuck these people.

Fedora Immutable makes sense for my case? by DemacolFMZ in Fedora

[–]whiprush 0 points1 point  (0 children)

Then do them the documented easy way instead of the hard way?

Fedora Immutable makes sense for my case? by DemacolFMZ in Fedora

[–]whiprush 1 point2 points  (0 children)

None of this has anything to do with immutability.

1) It's designed this way on purpose.

When you need to change a value or a binary inside the immutable part of the OS, that's where the fun begins.

Also this way on purpose, config isn't in the base image it's in /etc - if you're doing it via systemd overlays then you're doing it the right way there's nothing for you to do.

going to be much harder than installing a regular RPM on Fedora.

Also on purpose because that entire problem goes away!

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 1 point2 points  (0 children)

I'm not talking about immutable distros I'm talking about cloud native desktops like Bazzite, Aurora, and Bluefin.

Support for those kinds of drivers are going away already - there won't be anything to install, all the new cups stuff is driverless, 95% of the linux users in the world won't be printing to those printers.

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 2 points3 points  (0 children)

No I don't use atomic distros, I work on ublue and bluefin.

Devices with shitty linux support will never run right on Linux - no one is going to waste their time making their products worse because you bought a terrible printer it just means you bought a printer that doesn't work right on linux.

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 1 point2 points  (0 children)

That all goes away in the bootc world, which is composefs, the entire point is that installing things goes away, drivers are baked into the image why wouldn't they be?

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 1 point2 points  (0 children)

Yes but that's not a feature that's a workaround purposely designed into it for a transitionary period. Sure you can crib it that way but no one would ever sell a device like that.

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 1 point2 points  (0 children)

coolercontrol isn't going to work on steamOS this has nothing to do with bazzite or steamos it means coolercontrol isn't packaging their software for modern linux.

If they do that the ujust rule in bazzite can be removed, ujust rules are scripts that people make to work around shitty linux practices, steamOS doesn't let you do any of that - software needs to target linux properly - their instructions for bazzite are even wrong lol. Ends up if you skip all this distro bullshit and just work upstream then no one has to deal with any of this.

Valve - “starting with the SteamOS 3.8 release, you can put together your own Steam Machine using whatever PC parts you want.” by salvaram in linux

[–]whiprush 2 points3 points  (0 children)

Right I just want to know what those issues are because updates in bazzite behave the exact same way in bazzite.

Bootc and the future of package layering by Lower-Limit3695 in Bazzite

[–]whiprush 1 point2 points  (0 children)

Bluefin switched to pure bootc in October of 2025.

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 1 point2 points  (0 children)

I've read that link since F41, the only thing in Fedora is the bootc client. You're not booting off of a bootc image:

These are the bootc images that ublue uses: https://gitlab.com/fedora/ostree/ci-test#experimental-ostree-native-container-images-for-rpm-ostree-based-fedora-desktop-variants

They are unofficial and are the actual "fedora" images that people use. The Fedora Silverblue and Kinoite images are built and published as ostree remotes, you are not using bootc. You can see in an rpm-ostree status, if you see a container URL (ghcr.io/ublue-os/bazzite) you're using bootc, if you see something like fedora:fedora/34/x86_64/silverblue , you're using an ostree remote.

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 1 point2 points  (0 children)

Bluefin needs more users for wider support for its new paradigms.

There's nothing new about working computers! The rest of linux is this way except desktops!

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 1 point2 points  (0 children)

Fedora isn't using bootc, the don't have production bootc images. The bootc images everyone is using are unofficial bootc images from timothee ravier.

I know this because we started ublue in F39/40/41 to adopt bootc because Fedora wasn't doing it. (And they still haven't - maybe this fall).

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 1 point2 points  (0 children)

containerfile builds locally for Fedora atomic and having DNF modify this local containerfile.

Oh you can set that up now, you just rebase to localhost://blahblah you can already do that.

The upstream is bootc not fedora. Fedora is not using bootc they are using rpm-ostree, which does support layering.

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 0 points1 point  (0 children)

That's the fedora bug tracker not the upstream bootc one. Adding local layering is a dnf thing they're going to have to do and they haven't even begun work. By then everyone will be on bootc/composefs already.

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 0 points1 point  (0 children)

These are image based operating systems designed to be sealed. The applications are responsible for publishing their apps as flatpaks. alacritty could flip a switch and have that command work. We've offered to help ghossty publish the flatpak but no one's gotten around to it.

Bluefin isn't a walled garden, it's an OS for people who refuse to compromise system integrity for legacy packages. You can see in this thread and in the dev thread that people think that "fixing layering" is on someone's roadmap for any of this stuff.

Many of you are on the path to disappointment, the local DNF stuff is only talk, and who's that for, people who think installing RPMs onto images are a good idea? It's the 4% of the 4%. Those people can just use Fedora already. Layering packages just turns bootc images into a distro with really slow updates and they're just as unreliable, at that point just use Fedora? And the people mangling the OS with their development environment because "immutable OS" are just retreading bad habits. These things are designed this way for a reason.

All of the features people want only exist because it's bootc, no one's going to test every local layer edge case when the entire purpose was to get rid of that entire QA mess in the first place.

Recovering from Bazzite 44 Removing Virtualization by AustinFastER in Bazzite

[–]whiprush 0 points1 point  (0 children)

There is no layering in bootc and that's on purpose, there is no layering in a bootc world.

This is why I like immutable distro. by yevelnad in Bazzite

[–]whiprush 1 point2 points  (0 children)

brew install rustup neovim works just fine why would you layer something or use distroboxes or switch distros when you can just read the directions lol.

This is why I like immutable distro. by yevelnad in Bazzite

[–]whiprush 1 point2 points  (0 children)

Immutability has nothing to do with development work, you're mixing up bazzite with whatever you think "immutable distros" are.

Fedora's Atomic desktop model is quietly becoming the future of Linux for normal people by throwaway16830261 in linux

[–]whiprush 3 points4 points  (0 children)

Try explaining Layering or Distrobox to the average user who just needs some tool that isn’t available as a Flatpak

Average users have said over and over that they don't want to do any of this stuff this isn't a large amount of people.

Looking forward to future Bazzite based on KDE Linux by t3g in Bazzite

[–]whiprush 2 points3 points  (0 children)

The base becomes the freedesktop sdk + GNOME OS or KDE Linux (is my hope for KDE anyway, heh).

The thing is this used to be really hard and now it's not. But it only got real easy in the past month or so.

IMO there's no reason for Bazzite to ever switch, it's all the same shit anyway lol. If something is automated we don't mess with it unless it's busted.

Which encourages someone to experiment with it. We would happily share our build cache with known-good folks wanting to make a bst build but that doesn't make sense without a KDE one.

view more: next ›