If you depend on third party modules you'll end up with third party maintenance - we didn't purposely decide to break this we don't work at Nvidia.

Heya! I'm one of the ublue maintainers. I run the Project Pavilion at KubeCon, any chance you're going? I love to talk about this stuff in real life! Our project is based on bootc, which is going into sandbox into the CNCF, so there's lots of stuff to talk about!

I would say it is the methodology. To distill it a bit more in the context of bazzite and universal blue:

• Focus on automation (we do this via gitops) - everything is driven by git
• Declarative definitions: all the components of the base images (the kernel, base packages, etc. are all defined up front), and then the custom images (bazzite) do the same thing on top of that. That makes it easier for someone else to start with a small thing and "make my own bazzite" either from scratch, off of a base image, or if you want to just FROM bazzite you can start from there.
• Iterate fast: basically be able to change anything in the OS and rebuild on the spot locally as fast as possible.
• Everything is an OCI artifact

The noto fonts are in the main images, which bazzite is built from: https://github.com/ublue-os/main/blob/main/packages.json

Feel free to file issues there!

She only suggested a small “news channel” built into the OS.

Yeah we're working on that here: https://github.com/ublue-os/bluefin/issues/1485

The failure with secure boot afterwards is news to me, we'll investigate, thanks!

/etc is completely writeable. This is why we don't use the term "immutable distros" because Bazzite and the rest of universal blue are neither immutable nor distros.

(This is why Fedora moved to the term Atomic)

bluefin co-maintainer here. espanso is a hard one, we have an open issue on getting it to work because it'd be something awesome to include. We might end up needing to package it but haven't had a chance to look deeper into the issue.

Been there and done that. It's better to just not have the host OS break in the first place.

My Ubuntu installs are extremely reliable, both on desktops and servers.

Probably because you're an experienced user, not everyone has the same skillset.

Most people aren't system administrators and they end up with broken computers for the most basic tasks. It's one of the major reasons why people hate using Linux desktops.

And even if you're an experienced sysadmin you can't account for the entropy that accumulates on traditional OSes. 18.04 -> 20.04 -> 22.04 doesn't end up being the same as a 22.04 clean install. This is a huge problem, especially for people who don't know how to manage linux systems. And the people who do manage systems at scale don't want that behavior either.

I go over this in this video: https://www.youtube.com/watch?v=hn5xNLH-5eA

But day to day I'm in an ubuntu container and using "normal" package management, I just don't do it on the host.

I am unsure of the status of KDE offhand, I'm getting a bit north of 5 hours when on a plane and on wifi.

I would love to find some script or tool that can just grab all my logs and chart them out so people can share their results in a more reliable manner because I suck at keeping track of this kind of stuff by hand.

Here maybe it's easier if I just paste in the differences:

• Ubuntu-like GNOME layout.

  • Includes the following GNOME Extensions:
    • Dash to Dock - for a more Unity-like dock
    • Appindicator - for tray-like icons in the top right corner
    • GSConnect - Integrate your mobile device with your desktop
    • Blur my Shell - for that bling

• GNOME Software with Flathub:

  • Use a familiar software center UI to install graphical software

• Built on top of the the Universal Blue main image

  • Extra udev rules for game controllers and other devices included out of the box
  • All multimedia codecs included
  • System designed for automatic staging of updates
    • If you've never used an image-based Linux before just use your computer normally
    • Don't overthink it, just shut your computer off when you're not using it

• Starship is enabled by default to give you a nice shell prompt

• Solaar - included for Logitech mouse management along with libratbagd

• Tailscale - included for VPN along with wireguard-tools

• zsh and fish optional

• Built-in Ubuntu user space

• Ctrl-Alt-u - will launch an Ubuntu image inside a terminal via Distrobox and your home directory will be transparently mounted for the Ubuntu image to access

• A BlackBox terminal is used just for this configuration

• Use this container for your typical CLI needs or to install software that is not available via Flatpak or Fedora

• Optional ubuntu-toolbox image with Python, and other convenience development tools. just distrobox-bluefin to get started. To configure just follow the guide.

• Optional universal image with Python, Node.js, JavaScript, TypeScript, C++, Java, C#, F#, .NET Core, PHP, Go, Ruby, and and Conda. just distrobox-universal to get started

• just assemble shortcut to declaratively build distroboxes defined in /etc/distrobox/distrobox.ini

• Refer to the Distrobox documentation for more information on using and configuring custom images

• GNOME Terminal - Ctrl-Alt-t - will launch a host-level GNOME Terminal if you need to do host-level things in Fedora (you shouldn't need to do much).

The difference between silverblue and your image is that silverblue is signed by fedora and yours isn’t.

Of course Fedora only signs Fedora images, we sign our own images.

There’s no reason for anyone but you to use the image. Even if I were to us tailscale and fish, I’d be better off with silverblue.

Then use Silverblue! If you don't understand the features of something then you might not be the target audience!