Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What is Silverblue?

fedoramagazine.org

Post reply on HN
Print view View original

11–20 of 140 posts

Re: What is Silverblue?

#11

Post by lugg »

curioussavage wrote: post #7
lugg wrote: post #4

Earlier quoted context omitted.

Flatpak uses kernel namespaces (like docker) to run software with a bundled set of libraries. From their FAQ: > Flatpak mostly deployed as a convenient library bundling technology early on, with the sandboxing or containerization being phased in over time for most applications. I don't really know if sandboxing is worth it for me. Running everything inside docker cotnaienrs sounds like an absolute nightmare when it c…

I’ve been running many applications as flatpaks for over a year without issue. Troubleshooting is not too bad either imo.

Flatpak should be ok, I think when it's run inside inaccessible containers it won't be. Are the files sandboxed off from the user running in flatpak?

Re: What is Silverblue?

#12

Post by pcr910303 »

lugg wrote: post #2

Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.

Not trying to be sarcastic, but opinions like this make me sure that the Desktop Linux won’t fly.

> I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac.

Re: What is Silverblue?

#13

Post by lugg »

viraptor wrote: post #10
besulzbach wrote: post #6

> The operating system is delivered in images that are created by utilizing the rpm-ostree project. The main benefits of the system are speed, security, atomic updates and immutability. The article never mentions speed (or performance) again. Is the OS somehow expected to be faster because it is mounted read-only?

No, I wouldn't expect this system to be faster in a meaningful way. Actually maybe a bit slower since fewer libraries will be cached / memory mapped between applications if they carry their own copies.

I'd love to see stats on how many libraries are really shared, I'd imagine it might be less than you hope (other than the big graphical ones)

Re: What is Silverblue?

#14

Post by ghostpepper »

silisili wrote: post #9

As a Linux user from the 90s, I welcome this change. RPM Hell and its Debian equivalent are real and painful things. When disk space was a premium, system dynamic linking made sense. Today, it absolutely does not. rpm-ostree is a bit ugly. Snap has the right idea of doing both system services and apps. Fedora should do the same.

While I can appreciate the security advantages of snap packages, I can't help but resent the fact that the output of the mount command is now polluted with dozens of lines unrelated to mounted disks.

Re: What is Silverblue?

#15

Post by ww520 »

This is great, especially for atomic update and rollback of the OS. I remember a particular painful instance of OS upgrade. I did the yum update command in the login shell and forgot to do it in a screen session. The login shell got killed after a period of inactivity, in the middle of the OS update. Afterward the OS was beyond repair; couldn't roll back or move forward. Had to reinstall.

I wished something like silverblue existed back then.

Re: What is Silverblue?

#16

Post by KUcxrAVrtI »

silisili wrote: post #9

As a Linux user from the 90s, I welcome this change. RPM Hell and its Debian equivalent are real and painful things. When disk space was a premium, system dynamic linking made sense. Today, it absolutely does not. rpm-ostree is a bit ugly. Snap has the right idea of doing both system services and apps. Fedora should do the same.

>system dynamic linking made sense

I too look forwards to having to manually updated all security patches for each binary in the system.

Re: What is Silverblue?

#17

Post by KUcxrAVrtI »

pcr910303 wrote: post #12
lugg wrote: post #2

Flatpaking all the things? I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac. Convenient to install sure, but as a user its a nightmare to maintain/update. All people on Linux really need is an xdg-open standard for opening a package manager / running an install command.

Not trying to be sarcastic, but opinions like this make me sure that the Desktop Linux won’t fly. > I'm not sure why there is this push for Linux to have the "download and double click" install experience of windows / Mac.

There isn't a desktop any more, we might as well be trying to make Linux for the mini computer if you're chasing the desktop market.

Re: What is Silverblue?

#18

Post by axaxs »

KUcxrAVrtI wrote: post #16
silisili wrote: post #9

As a Linux user from the 90s, I welcome this change. RPM Hell and its Debian equivalent are real and painful things. When disk space was a premium, system dynamic linking made sense. Today, it absolutely does not. rpm-ostree is a bit ugly. Snap has the right idea of doing both system services and apps. Fedora should do the same.

>system dynamic linking made sense I too look forwards to having to manually updated all security patches for each binary in the system.

Would you rather each update of said binary be dependent on the author or some volunteer? That's how you get Debian stable.. No thanks.

Re: What is Silverblue?

#19

Post by axaxs »

ghostpepper wrote: post #14
silisili wrote: post #9

As a Linux user from the 90s, I welcome this change. RPM Hell and its Debian equivalent are real and painful things. When disk space was a premium, system dynamic linking made sense. Today, it absolutely does not. rpm-ostree is a bit ugly. Snap has the right idea of doing both system services and apps. Fedora should do the same.

While I can appreciate the security advantages of snap packages, I can't help but resent the fact that the output of the mount command is now polluted with dozens of lines unrelated to mounted disks.

Agreed on that front. That's really my biggest issue with snaps.
Post reply on HN