9:48 Rpm-ostree will keep only your last 2 deployments/images by default. Although you can pin a deployment and keep more than 2 (sudo ostree admin pin )
Correction: that lxqt image defeaults to something called Weston, which is a bug in the image. LXQT looks differently, but the outcome would be the same. If you like this content, consider leaving a like! It really helps the channel! So does following me on Mastodon! fosstodon.org/@thelinuxcast
This is the future. It is now. Re-installing an OS is the worst thing anyone can ever do. I hope Silverblue+ublue+Flatpaks helps solve this forever. Flatpaks are radical and should be default for all OS's. An automated bootstrapped mechanism can be used for corporates, home users and gamers too.
Great timing! I just switched to an immutable Fedora distro on my desktop computer. It is a new experience to say the least. I am using the Sericea distro witch is the immutable Fedora with the Sway desktop. Ublue sounds very interesting, and I can't wait to get right into it! The reason that I switched to an immutable distro is actually because it came to me in a dream last night. It's crazy the kinds of ideas that can come to you when you are asleep. My laptop runs Void Linux and has been for a while. That is the machine that I rely on, where as my desktop is the one where I distro hop without caring about backing up any files. It is also my gaming machine where I prioritize performance. Then my laptop is the one where I do not need to conserve my resources and that is the one that I use to self host things. I do that as well as keeping files on it. It all works out perfectly. Not sure why but it is very satisfying.
I recently made 4 images (kde, gnome, cinnamon and sway) based on ublue, in- and excluding my preferred software, with sericea even including a separate Copr repo. It ain't that difficult, you'll get through it. Just set-up a separate git repo for the purpose, fork ublue in there, and above all read tfm ;-) It ain't complicated. Most of all: have fun!
I really liked this video! I’ve been building my own OS image based on Silverblue, by maintaining a Containerfile in my dotfiles repo with different build targets for GNOME and Hyprland. I’m really looking forward to your video of you building your own because I’d love to compare methodologies!
ublue is similar to nixos in that you can make your own system. They do it in very different ways and have different philosophies. Vanilla OS sound like if will offer something similar. These types of distros are new and segmentation here can be good. It allows these technologies to develop and compare them. I am excited for these.
nixos is okay but its containerization of appas and system directories became a nightmare when it comes to system paths. i could only tolerate nixos for 3 weeks and now its sitting and collecting dust
@@ibm450 That can be a problem. All of these projects are going have pros and cons. That is why it is nice having several technologies coming into this space. It means that you can find one that works best for you.
Actually I think we need machine specified immutable base, then we can specify anything we want. Not in config files, else a nice installer, and we don't need package manager anymore. If we do specified kits that is predefined, or make your own, you are done basically.
I'm using this on my work laptop. Rebasing is easy. I have not had any issues with my home file. Their approach is using a devops type CI/CD process for operating system images. I think the primary user target now is developers. I think it could be great for imaging computers at schools or scientific organizations. In the container config you can layer in nonflatpak applications.
That LXQT one looks like it's actually Weston. I don't think they had it named right, or they accidentally put Weston in there. That did not look like LXQT at all to me, but totally looked like Weston.
That is awesome. However your lxqt environment was I think Weston. Probably wanted to select lxqt from sddm. Thanks a lot though. This kinda "nixifies" Silverblue!
@@TheLinuxCast yes in fact if you install the lxqt spin of Fedora (not silverblue) by default it boots into Weston. Must confuse a lot of new users! lol
If you like that you should give nixos a spin, its very similar except you have fine control over your system with the config file, you can even create a custom session if you want, you can even install their unstable rolling release channel alongside their stable channel, so you can reboot into and run a fixed release distro, or reboot into and run a rolling release distro, its awesome. oh and that wasn't lxqt.
You last topic talking about other inmutable systems like vanillaos. Ublue has distrobox shipped with it allowing installation from arch and Ubuntu then exporting it to base system. More commands then vanillaos but does the same thing.
These kinds of technologies have the potential to unify Linux and make what is now a distro into an image. Great stuff I think would simplify so many things and make Linux more approachable in many ways. Hope nobara will be an image for example.
im really into fedora silverblue and having everything as flatpak with no host access. flatpak already has its own open/save file/dir dialog that auto gives permission to the app for the file or dir. i use devcontainers for development so i dont trash the system with development related things also your dev envoriment for a project just runs, your project just builds on any system, etc. i dont like everything just hanging around, i feel like i have no control on what is happening on my system with 100 different random hidden stuff in the home dir that i have no idea what uses them. - flatpak gives you more control on your system - devcontainers lets keep development related stuff away from your host system - and fedora silverblue enforces you to use them
Don't understand what is the advantage here. On openSUSE I just have to logout of gnome, e.g., and login to kde. No reboot needed. I have a list of about 5 desktops and 4 or 5 window managers that i can logout/login to.
yes, but you have to set that up during install. If you were to do so after you've installed SUSE, you'd have a harder time of it. And I never said it was traditionally impossible, just not as easy as one line and a reboot. Also, you get the other immutable benefits.
I know that you've done nixos recently. and don't get me wrong ublue seems like a cool project. but this seems to me no different then nixos minus the nix language and having the FULL immutability like ublue. I understand nix does stuff differently compared to "normal" linux. but even if you are moderately ok with editing a config the nix language is simple enough to do what you did in this video with no issues and I would argue more easily. I guess for me I don't understand dislike of nix when it is basically this with changes to how it handles /usr and /etc and some other things but with little work does the same thing.
@@Nerve556 I WAS a developer, years ago. And to be honest, it was more superficial stuff that I did. I just took a base Puppy, took out the apps I didn't like, added the apps I made it pretty. I did less under the hood stuff, although I had to compile more apps than I can recall. Nevertheless breaking things is how I learned how to fix them and gain more understanding of how Linux works. I always have at least one backup distro for when things break.
@@Nerve556It doesn't take much time to restore if something breaks if you know what you are doing. I also never had unbootable system because of update, even on arch.
@@Nerve556 Because nothing is hassle free, learning nix also takes time, hundreds times more time than just fixing your current install. You can also rollback with btrfs, it depends on your particular usage and what devops skills you developed dealing with linux.
If you think Linux is so awsomw try working with arduino and cnc projects I am always having to return to windows to get things done Linux is still 2nd rate.
yeah, it sure is@@alexstone691, it fits my needs well since i have the memory of a fish and the focus of a child filled to the brim with sugar, so i have a reliable way to restore my base system, specially since i pavkaged my own install script in copr
For real? `systemctl reboot`? What else did SystemD NOT YET assimilate? What about the good old `sudo reboot` or `sudo shutdown -r now` if anyone else except me remembers. lol.
I don't understand the usability of this feature... Is it DOUBLE TROUBLE, triple trouble or what? I ONLY NEED ONE that allows customizing MY WAY. What kind of Linux user doesn't have DE preference and wants to have them all? And to add it all to GRUB menu... epic overkill. Hard pass here.
Immutable distros are not for normal Linux users, they are for regular people that would like to use Linux on their PC, this type of people are completely different type of users. Regular user don't want to hop distro every week, don't want to even see a terminal because he would freak out, they want a working PC with understandable UI/UX, harder to break the better.
Containerization is a fantastic way to have your cake and eat it too. Wanna mess around with traditional PPA's without consequence from the safety of a container? Update without worry? Who wouldn't enjoy that? Keep the host lean and mean. This illusion that somehow customization disappears is kind of silly. Composability is at the very heart of it. Also giving every installed application unlimited access to everything on the disk by default just isn't going to cut it anymore. The benefits of that separation go far beyond the use cases of regular people.
@@jackelofnar And? Fedora still is a community project. Isn't like everyone working on it is a Red Hat employee. That's why not every technology Fedora uses ends up in RHEL
For all the people commenting about NixOS… since it can build Docker images, how about using NixOS to build the base OS layer? Or is that going too far?
In my opinion, Nixos has a lot of overheads and a terrible installer that prevents users from formatting or setting up other efi systems that are already installed on the SSD in a proper manner. There is a lot of clutter that accumulates during nixos build-switching, and if the trash isn't removed, it uses up a lot of space, much like system restore on Windows. I am aware that auto garbage and store optimisation may be enabled in the configuration files, however the administrative overheads associated with setting up NixOS are simply not worth it. Furthermore, on ad hoc systems, it is not totally reproducible. I also have to admit that, often, the Nixos Wiki is not that helpful.
1) I couldn't run my bash scripts because some of them have #!/bin/bash shebang (this is also quite common on the internet). 2) I couldn't compile some projects from github it is very convoluted and hard to setup, you basically better do everything through nix lang, or don't bother with nixos at all. Because of these reasons the interest in nixos died for me.
9:48 Rpm-ostree will keep only your last 2 deployments/images by default. Although you can pin a deployment and keep more than 2 (sudo ostree admin pin )
Correction: that lxqt image defeaults to something called Weston, which is a bug in the image. LXQT looks differently, but the outcome would be the same.
If you like this content, consider leaving a like! It really helps the channel! So does following me on Mastodon! fosstodon.org/@thelinuxcast
nixos is an immutable distro that is very customizable
you can do something very similar on nixos too
Why is this comment not pinned?
I know something else that is immutable. The quality of Matt's videos. 😀The never fail to inform and entertain.
Lets be honest, he has a ton of low quality low effort videos there and he admitted it's easier for him to just rand about things
This is the future. It is now.
Re-installing an OS is the worst thing anyone can ever do.
I hope Silverblue+ublue+Flatpaks helps solve this forever. Flatpaks are radical and should be default for all OS's.
An automated bootstrapped mechanism can be used for corporates, home users and gamers too.
When NixOS?
Without a doubt..... Jorge Castro and the UniversalBlue team - including Aurora...... Are amazing and stable. Give them both a try.
Great timing! I just switched to an immutable Fedora distro on my desktop computer. It is a new experience to say the least. I am using the Sericea distro witch is the immutable Fedora with the Sway desktop. Ublue sounds very interesting, and I can't wait to get right into it! The reason that I switched to an immutable distro is actually because it came to me in a dream last night. It's crazy the kinds of ideas that can come to you when you are asleep.
My laptop runs Void Linux and has been for a while. That is the machine that I rely on, where as my desktop is the one where I distro hop without caring about backing up any files. It is also my gaming machine where I prioritize performance. Then my laptop is the one where I do not need to conserve my resources and that is the one that I use to self host things. I do that as well as keeping files on it. It all works out perfectly. Not sure why but it is very satisfying.
Universal Blue is my new favorite toy.
We love you. Please keep going.
I recently made 4 images (kde, gnome, cinnamon and sway) based on ublue, in- and excluding my preferred software, with sericea even including a separate Copr repo. It ain't that difficult, you'll get through it. Just set-up a separate git repo for the purpose, fork ublue in there, and above all read tfm ;-) It ain't complicated. Most of all: have fun!
I really liked this video! I’ve been building my own OS image based on Silverblue, by maintaining a Containerfile in my dotfiles repo with different build targets for GNOME and Hyprland. I’m really looking forward to your video of you building your own because I’d love to compare methodologies!
you're using hyprland on fedora? how?
@@livb4139 Copr repo I'm pretty sure
ublue is similar to nixos in that you can make your own system. They do it in very different ways and have different philosophies. Vanilla OS sound like if will offer something similar. These types of distros are new and segmentation here can be good. It allows these technologies to develop and compare them. I am excited for these.
nixos is okay but its containerization of appas and system directories became a nightmare when it comes to system paths. i could only tolerate nixos for 3 weeks and now its sitting and collecting dust
@@ibm450 That can be a problem. All of these projects are going have pros and cons. That is why it is nice having several technologies coming into this space. It means that you can find one that works best for you.
Actually I think we need machine specified immutable base, then we can specify anything we want. Not in config files, else a nice installer, and we don't need package manager anymore. If we do specified kits that is predefined, or make your own, you are done basically.
I'm using this on my work laptop. Rebasing is easy. I have not had any issues with my home file. Their approach is using a devops type CI/CD process for operating system images. I think the primary user target now is developers. I think it could be great for imaging computers at schools or scientific organizations. In the container config you can layer in nonflatpak applications.
This is amazing! Every distro should have this!
That LXQT one looks like it's actually Weston. I don't think they had it named right, or they accidentally put Weston in there. That did not look like LXQT at all to me, but totally looked like Weston.
Yep that wasn't lxqt
The only issue I found rebasing from one desktop to another is that it clutters your .config folder.
I'm on Nobara and can switch between Gnome and KDE at login screen, no fuss.
You are clearly misunderstanding the OSTree purpose.
That's so cool! What happens to things you installed via ostree when you rebase?
That is awesome. However your lxqt environment was I think Weston. Probably wanted to select lxqt from sddm. Thanks a lot though. This kinda "nixifies" Silverblue!
Yeah, apparently that is a bug with the image, and as I've used neither I didn't realize. I've made a correction in the comment section
@@TheLinuxCast yes in fact if you install the lxqt spin of Fedora (not silverblue) by default it boots into Weston. Must confuse a lot of new users! lol
you can pin deployments to keep them, Otherwise only the previous one is retained
If you like that you should give nixos a spin, its very similar except you have fine control over your system with the config file, you can even create a custom session if you want, you can even install their unstable rolling release channel alongside their stable channel, so you can reboot into and run a fixed release distro, or reboot into and run a rolling release distro, its awesome. oh and that wasn't lxqt.
Finally good job Matt you need to go for full silverblue and do all by hands and use Gnome atleast 6 months no cheating on it
Matt its a bit like distrobox,GVM.
You last topic talking about other inmutable systems like vanillaos. Ublue has distrobox shipped with it allowing installation from arch and Ubuntu then exporting it to base system. More commands then vanillaos but does the same thing.
These kinds of technologies have the potential to unify Linux and make what is now a distro into an image.
Great stuff I think would simplify so many things and make Linux more approachable in many ways. Hope nobara will be an image for example.
Try to rebase to the Kera image - looks interesting for a web desktop. Bazzite uses the kde plasma desktop like the steam deck.
Does Bazzite have that console like interface from Steam Deck as well? Or it is just a modified Plasma Desktop?
im really into fedora silverblue and having everything as flatpak with no host access.
flatpak already has its own open/save file/dir dialog that auto gives permission to the app for the file or dir.
i use devcontainers for development so i dont trash the system with development related things
also your dev envoriment for a project just runs, your project just builds on any system, etc.
i dont like everything just hanging around, i feel like i have no control on what is happening on my system
with 100 different random hidden stuff in the home dir that i have no idea what uses them.
- flatpak gives you more control on your system
- devcontainers lets keep development related stuff away from your host system
- and fedora silverblue enforces you to use them
One of these days I'll remember to leave a like on the video BEFORE you remind me
Don't understand what is the advantage here. On openSUSE I just have to logout of gnome, e.g., and login to kde. No reboot needed. I have a list of about 5 desktops and 4 or 5 window managers that i can logout/login to.
yes, but you have to set that up during install. If you were to do so after you've installed SUSE, you'd have a harder time of it. And I never said it was traditionally impossible, just not as easy as one line and a reboot. Also, you get the other immutable benefits.
I know that you've done nixos recently. and don't get me wrong ublue seems like a cool project. but this seems to me no different then nixos minus the nix language and having the FULL immutability like ublue. I understand nix does stuff differently compared to "normal" linux. but even if you are moderately ok with editing a config the nix language is simple enough to do what you did in this video with no issues and I would argue more easily. I guess for me I don't understand dislike of nix when it is basically this with changes to how it handles /usr and /etc and some other things but with little work does the same thing.
I think the same thing it is too constrained
I'd rather break my distro then use an immutable one, but that's just the way I am.
@@Nerve556 I WAS a developer, years ago. And to be honest, it was more superficial stuff that I did. I just took a base Puppy, took out the apps I didn't like, added the apps I made it pretty. I did less under the hood stuff, although I had to compile more apps than I can recall. Nevertheless breaking things is how I learned how to fix them and gain more understanding of how Linux works. I always have at least one backup distro for when things break.
@@Nerve556It doesn't take much time to restore if something breaks if you know what you are doing. I also never had unbootable system because of update, even on arch.
@@Nerve556 Because nothing is hassle free, learning nix also takes time, hundreds times more time than just fixing your current install. You can also rollback with btrfs, it depends on your particular usage and what devops skills you developed dealing with linux.
If you think Linux is so awsomw try working with arduino and cnc projects I am always having to return to windows to get things done Linux is still 2nd rate.
it's not a pop os? Oo
I installed silverblue 37 rebased to 38 then to kinoite 38
i mantain my own Ublue custom repo, that it will update to fedora 39 instantly without losing my changes and my compositor that is from copr
@@luizansounds i was considering this but seemed like too much work and ublue was too new for my taste
yeah, it sure is@@alexstone691, it fits my needs well since i have the memory of a fish and the focus of a child filled to the brim with sugar, so i have a reliable way to restore my base system, specially since i pavkaged my own install script in copr
I thought people weren't allowed to like Fedora right now?
Varies person to person
fedora is actually upstream of RH not downstream so its ok to like them
people won't like to contribute to fedora due to redhat, so expect more bugs in future
@@debiprasaddas9699moron
@@JahidulIslamwow you showed him
For real? `systemctl reboot`? What else did SystemD NOT YET assimilate? What about the good old `sudo reboot` or `sudo shutdown -r now` if anyone else except me remembers. lol.
`sudo reboot` and `sudo shutdown -r now` still work.
@@JorgeCastro of course they do. That was never my point lol
I don't understand the usability of this feature... Is it DOUBLE TROUBLE, triple trouble or what? I ONLY NEED ONE that allows customizing MY WAY.
What kind of Linux user doesn't have DE preference and wants to have them all? And to add it all to GRUB menu... epic overkill. Hard pass here.
How remove an image?
There are instructions on the ublue site.
@@TheLinuxCast ok tks.
Immutable distros are not for normal Linux users, they are for regular people that would like to use Linux on their PC, this type of people are completely different type of users. Regular user don't want to hop distro every week, don't want to even see a terminal because he would freak out, they want a working PC with understandable UI/UX, harder to break the better.
Containerization is a fantastic way to have your cake and eat it too. Wanna mess around with traditional PPA's without consequence from the safety of a container? Update without worry? Who wouldn't enjoy that? Keep the host lean and mean. This illusion that somehow customization disappears is kind of silly. Composability is at the very heart of it. Also giving every installed application unlimited access to everything on the disk by default just isn't going to cut it anymore. The benefits of that separation go far beyond the use cases of regular people.
Since I don't trust Redhat anyone Fedora is dead to me.
fedora isn't based on RHEL
@ddman7867 it's upstream from RHEL.
Yep, dirty move from redhat, and very hypocritical too.
@@jackelofnar And? Fedora still is a community project. Isn't like everyone working on it is a Red Hat employee. That's why not every technology Fedora uses ends up in RHEL
For all the people commenting about NixOS… since it can build Docker images, how about using NixOS to build the base OS layer? Or is that going too far?
In my opinion, Nixos has a lot of overheads and a terrible installer that prevents users from formatting or setting up other efi systems that are already installed on the SSD in a proper manner. There is a lot of clutter that accumulates during nixos build-switching, and if the trash isn't removed, it uses up a lot of space, much like system restore on Windows. I am aware that auto garbage and store optimisation may be enabled in the configuration files, however the administrative overheads associated with setting up NixOS are simply not worth it. Furthermore, on ad hoc systems, it is not totally reproducible. I also have to admit that, often, the Nixos Wiki is not that helpful.
1) I couldn't run my bash scripts because some of them have #!/bin/bash shebang (this is also quite common on the internet).
2) I couldn't compile some projects from github it is very convoluted and hard to setup, you basically better do everything through nix lang, or don't bother with nixos at all.
Because of these reasons the interest in nixos died for me.
Silverblue is pointless
As, they say, was this comment.