Sparkie86•

This might be useful to deploy in industrial controls environments.

10
jack123451•

Or on Grandma's PC. The read-only root prevents her from accidentally breaking the base system, while the ostree foundation lets one "factory-reset" the system to the distro maintainers' image. With some additional work this has the potential to approach ChromeOS's robustness.

12
Sparkie86•

That is absolutely right. I've been looking for a non-windows solution to deploy HMI's in the same cost-range given that I do custom work, may as well make my own HMI's.

3
schallflo:fedora:•

I've actually set up my stepdad's PC to run Silverblue. He likes it.

1
dead10ck•

Someone commented on the article:

I think one thing that should be done is messaging where Silverblue isn’t useful or is going to work against power users.

For example anyone doing OS development, like fedora devs, kernel devs, library devs etc are totally going to fail using silverblue. I’d really appreciate if there was some better messaging around the severe limitations using silverblue would have on a typical fedora packaging workflow or any of the lowlevel OS devs.

I agree with this completely. Flatpak and Docker have their own limitations and shortcomings. The article itself says that the value proposition of Silverblue is:

it allows you to concentrate on your work and not on the operating system you’re running.

Using Docker for some things, Flatpak for others, and for the rest having to reboot any time you need to modify the underlying OS, seems like a lot more thinking about the OS than just dnf install.

9
swick_OP•

OS development, like fedora devs [...] library devs

Toolbox allows you to do most development tasks. Modifying the base system is simply not required in most cases. It might be a bit more complex though in some situations.

kernel devs

You can load your modules from anywhere, most dev doesn't even require rebooting or can be done in a VM. If you work on bring up you usually have dedicates hardware since rebooting every time you test changes would disturb the workflow too much.

I’d really appreciate if there was some better messaging around the severe limitations using silverblue would have on a typical fedora packaging workflow or any of the lowlevel OS devs

I believe the person writing this doesn't realize how much can be done and how small the limitations actually are if you actually try to use it.

12
nmikhailov•

Toolbox allows you to do most development tasks.

Ok, so with toolbox I can get normal fedora inside my sb.

So why would I bother with sb at all if I can just install normal fedora in the first place?

In case I need something incompatible I can still make container/vm in normal fedora.

So maybe there are some big benefits to SB? Lets see.

What are the benefits of an immutable OS? One of the main benefits is security. The base operating system is mounted as read-only, and thus cannot be modified by malicious software. The only way to alter the system is through the rpm-ostree utility.

I don't understand security argument - malicious software with root rights can just modify ostree storage directly.

Another benefit is robustness. It’s nearly impossible for a regular user to get the OS to the state when it doesn’t boot or doesn’t work properly after accidentally or unintentionally removing some system library. Try to think about these kind of experiences from your past, and imagine how Silverblue could help you there.

Robustness is good, but it comes with high costs and 'unintentionally removing some system library' shouldn't be a big problem for a power user anyway.

Rollbacks and such can be achieved on fs level with btrfs/zfs.

3†
swick_OP•

I don't understand security argument - malicious software with root rights can just modify ostree storage directly.

Granted, the reasoning for better security in the article is flawed. The immutability makes it easier to configure LSMs well and improves the ability to detect malicious modifications.

Robustness is good, but it comes with high costs

Which high costs?

'unintentionally removing some system library' shouldn't be a big problem for a power user anyway.

Are you only quoting the arguments you don't agree with? I have seen people do a lot of stupid things with their system which describe themselves as power users, so I won't dismiss this argument.

Either way: with traditional package managers updates can and do break the system, you can't easily be on a nightly and stable version at the same time, changing the DE often leaves things in a semi-usable state. Things like that are my understanding of instability.

I know of lots of instances where an Ubuntu/Fedora/Arch/Debian update broke the system for someone. I don't know of anyone who ever had a problem with a Chrome OS update.

Rollbacks and such can be achieved on fs level with btrfs/zfs.

Being btrfs/zfs exclusive is probably the reason why almost nobody actually has this system set up.

7
dead10ck•

Which high costs?

If you use Docker with any regularity, you know there are all kinds of gotchas. Lots of tools require a real non-root user. Lots of them require a locale. You have to clean up images and volumes. If you want to share files with your OS, you have to think about mounting volumes, especially if you want to use a GUI tool (is it even possible to run a GUI IDE from inside a container?). If your development involves making Docker containers, you can't do that from inside Docker itself. I don't know which of these issues Toolboxes takes steps to alleviate, but these are the kind of costs that exist, and there are certainly others involved with Toolboxes, which haven't really been communicated at all.

Other costs are having to install your software in 3 different places (toolboxes, Flatpak, rpm-ostree) with the latter requiring reboots. It is strictly more work to think about how your workstation is set up.

I have seen people do a lot of stupid things with their system which describe themselves as power users, so I won't dismiss this argument.

I have used Linux for software development, both for work and personal use, for over 10 years, 7 of them with Linux as my primary OS, mostly with Arch, and now more recently Fedora. I have had all kinds of desktop hardware and laptops. I update all my system software on a daily basis. I have never once broken my system with an update, or messing up a critical config.

1
disrooter•

As a power user and software developer I would love more distro like Silverblue. My dream is KDE Neon shipped with OSTree and all apps shipped with Flatpak. But there are still many things to fix before getting there

4
schallflo:fedora:•

There's already a treefile for the KDE version of Silverblue on pagure.io, it just isn't being built right now.

https://pagure.io/workstation-ostree-config/tree/master

1
schallflo:fedora:•

Ok, so with toolbox I can get normal fedora inside my sb.

So why would I bother with sb at all if I can just install normal fedora in the first place?

Ideally, you'd use the VS Code flatpak with remote development in a toolbox. In that case, the solution to "holy shit I fucked stuff up in my dev environment" is to reinstall your compiler in a fresh toolbox and be done with it.

Could that be done without an immutable base system? Yes. Would you actually do that in a mutable base system? Probably not.

and 'unintentionally removing some system library' shouldn't be a big problem for a power user anyway.

it's not a big problem for me, but it does take longer than selecting an older commit at the bootloader.

2
[deleted]•

Toolbox has been 100% broken on every system I've tried it on for months.

1
masteryod•

It's made for:

  • developers - non kernel ones, the hipster ones, they don't care about the OS, they want easy access to multiple tools in multiple versions

  • RHEL clients - transactional upgrades with rollback bitches! They don't care about the OS either. They want their solution to work and OS maintenance is a pain to them.

  • casual users - they don't care about the OS, they are scared and tend to break stuff, all that matters is a web browser and to keep everything hidden from them

But mostly it's a testground for future RHEL. People who care about their OS like admins, tinkers, pro users, graybeards are a dying breed. And the fact that the computers are getting soooo complicated is not helping.

6
disrooter•

Using Docker for some things,

You are supposed to use Podman and other tools to manage a development environment based on containers

Flatpak for others,

Well, software development and consuming apps are very different task, why are you surprised we have Flatpak for desktop apps and containers for software development?

and for the rest having to reboot any time you need to modify the underlying OS,

You are not supposed to modify the system, it would update automatically and you won't need to care about it. If for some reason you need to touch the system to accomplish a task that is something that need to be fixed in some way to a point that rebooting to apply changes would be very unusual.

seems like a lot more thinking about the OS than just dnf install.

Let's be honest, as always complains are by people that like their comfort zone and don't want to learn something new that could be much better.

In this case if you are into software development you would understand that immutable OS + sandboxed apps platform + containers is a basic modern architecture.

Linux distributions as a sea of ​​packages without a conceptual subdivision of system and user applications and without a platform for third-party applications can be very good for servers and in fact there Linux distributions have ~ 97%. Maybe it's time to realize that this architecture is not good for a personal computer? Perhaps the reason why Linux distributions do not conquer the desktop market is this? And what did Google do with Android on mobile? But just this, it has separated the operating system distributed in its entirety and not by a combination of packages and the user is supposed to add the software that he needs through a third-party app platform.

4
CameronNemo:linux:•

for the rest having to reboot any time you need to modify the underlying OS

Or modifying the stack VM or test hardware instead, which is hopefully what kernel devs et al are doing.

2
saivert•

I have been running Silverblue since early February 2019 so I have gotten a bit familiar with it.

The biggest feature is the immutable base system and the atomic upgrades with quick rollbacks that isn't dependent on a particular storage subsystem to work.

There are downsides however. While you can do a lot of things in the toolbox container anything involving direct hardware access is a no go.

But it is still early and toolbox is under very active development and more features for making life on Silverblue easier for pro users is expected.

If you have bad discipline and tend to make a lot of changes and install and uninstall software, basically play around a lot with the system then Silverblue can be the medicine to force you to keep a stable system.

2
lordcirth•

Looks cool. However I question the value of making a layer on top of rpm to add this functionality. The Nix package manager, and NixOS, have this built in. While it's a lot more work to switch to Nix, I expect it would be better in the long run than adding a Silverblue layer over the existing system.

-2†
MindlessLeadership:fedora:•

It's not a layer on top of rpm, it uses ostree. There's a system that allows rpms to be installed though.

21
_paperd_•

Nix and silverblue aren't quite the same. silverblue delivers its base system as one immutable package. In Nix there are default packages, but you can add or strip away as much as you want.

11