home.social

Search

298 results for “UniversalBlue”

  1. @LightKind @vuuc Even if you’re not a gamer. You can also try getaurora.dev. Also made by #universalblue. Works the same as Bazzite but is more a workstation OS.

  2. One of the big things I like about the #UniversalBlue world is the openness -- especially the sharing of information.

    Once I realized that #Bluefin and Bluefin LTS both updated on a weekly cadence, that made me want to switch from LTS to regular.

    docs.projectbluefin.io/changel

    I wasn't so worried about changing kernels and packages as I was by the frequency of updates.

    Specifically I wanted to get away from daily updates (#Tumbleweed-based #Aeon is VERY dynamic).

    Weekly is more what I want.

  3. @steltenpower @matv1 Yup, maar verandering bij ICT is vaak ervaren.

    Voorbeeld: Bij 3 collega’s op hun oude laptops (2019) Aurora van #universalblue geïnstalleerd. Firefox en Edge. Edge om gemakkelijker vanuit thuis ‘op school’ te werken. Voor al het anderen Firefox. (Eentje wilde Chrome,… 🤢) LibreOffice, VLC, etc.

    Heb ik gedaan omdat ik het leuk vind. En zonde als die dingen niet meer gebruikt zouden worden.

    Reactie: Huh,.. dit werkt net als Windows?
    Me: Yep, en beter voor je privacy. 🥳

  4. BananaFin, my mix of project Banana (immutable KDE/Aurora) and BlueFin, is reaching finalization.Tomorrow some more testing (have brew and flatpak install my own applications upon first boot), but it is all running very smoothly. Aside from this being my hobby as well, you'd just install this and get on with it. And yes, it's a bootc container, from the cloud, secure boot enabled and it runs flatpaks and systemd. And very well, thank you!
    #universalblue

  5. @mattdm @sozutovo @fedora Even in Fedora Atomic upgrades are not automatic. Someone has to press a button. In my experience watching people using any computing device, many people do not see or care about notifications. People will fall on EOL OS image for years unless you do yearly support.

    So, I'd substitute #UniversalBlue in this response.

    Lack of automatic updates is the reason #Fedora #Silverblue is not my first recommendation to beginners, preferring #EndlessOS or #UBlue instead.

  6. @mattdm @sozutovo @fedora Even in Fedora Atomic upgrades are not automatic. Someone has to press a button. In my experience watching people using any computing device, many people do not see or care about notifications. People will fall on EOL OS image for years unless you do yearly support.

    So, I'd substitute in this response.

    Lack of automatic updates is the reason is not my first recommendation to beginners, preferring or instead.

  7. @mattdm @sozutovo @fedora Even in Fedora Atomic upgrades are not automatic. Someone has to press a button. In my experience watching people using any computing device, many people do not see or care about notifications. People will fall on EOL OS image for years unless you do yearly support.

    So, I'd substitute #UniversalBlue in this response.

    Lack of automatic updates is the reason #Fedora #Silverblue is not my first recommendation to beginners, preferring #EndlessOS or #UBlue instead.

  8. @mattdm @sozutovo @fedora Even in Fedora Atomic upgrades are not automatic. Someone has to press a button. In my experience watching people using any computing device, many people do not see or care about notifications. People will fall on EOL OS image for years unless you do yearly support.

    So, I'd substitute #UniversalBlue in this response.

    Lack of automatic updates is the reason #Fedora #Silverblue is not my first recommendation to beginners, preferring #EndlessOS or #UBlue instead.

  9. Switched to Bluefin DX over Fedora Silverblue and while everything was a bit more painful to customize for me because it has so much more stuff preinstalled and floating around in it, I will say once that was done it's been more enjoyable to use on the whole. I like using brew for CLI packages and flatpak for apps and that's all setup for me out of the box. Bazaar for flatpaks is interesting. It still feels pretty young but is worlds faster than gnome software. It doesn't feel as newbie friendly but that's fine for me and I specifically chose the developer focused version so I'm sure that has something to do with it.
    #UniversalBlue #ublue #ProjectBluefin #FedoraSilverblue #Fedora

    P.S. Dinosaurs are rad!

  10. finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now

    that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for

    for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests

    #UniversalBlue #BlueBuild

  11. ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite

    there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: github.com/zelikos/zeliblue/pu

    #UniversalBlue #BlueBuild

  12. I've merged my experimental COSMIC image into Zeliblue's main branch

    it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR

    main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)

    #UniversalBlue #BlueBuild #COSMICDesktop

  13. COSMIC desktop alpha is out, uBlue has been doing builds of COSMIC base images

    so what better way to check out COSMIC than setting up a spin of my custom image

    #UniversalBlue #BlueBuild #COSMIC

  14. finally got around to setting up ISO builds for Zeliblue again, since uBlue switched over to offline ISOs a while ago

    next step would be for me to maybe finally show the Zeliblue page on my website some love, and provide a download link... zelikos.dev/apps/zeliblue

    ...but for now, just having the ISO builds in CI again is great

    #UniversalBlue #BlueBuild

  15. spent the evening working on a new branch for Zeliblue: porting everything from BlueBuild to instead be based around uBlue's own image-template stuff. this was all for the sake of experimenting, to evaluate differences between the two approaches of doing a custom uBlue image

    tl;dr:
    the extra flexibility of the latter approach is enticing, but there's a lot more to learn vs using BlueBuild's YAML-based approach to customizing things

    #UniversalBlue #BlueBuild

  16. Someone told me Ultramarine Linux was looking to work with Universal Blue.

    Well, that's a dumb idea. There have been 4 other developments that tried to work with Universal Blue, but UB sort of help kill off their development. UB is no bodies friend. They'll have you working for them with nothing in return, pretty quickly.

    #UniversalBlue #Linux #Ultramarine #UltramarineLinux

  17. finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now

    that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for

    for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests

    #UniversalBlue #BlueBuild

  18. finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now

    that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for

    for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests

    #UniversalBlue #BlueBuild

  19. finally got around to adding in default flatpaks as part of my ISO builds for Zeliblue, just like how Bluefin and Bazzite do it, so the first-boot experience on my image is a lot nicer now

    that is only for the ISOs from the Github action, tho, which I don't (currently) provide public downloads for

    for rebasers and otherwise, there's also now a `restore-default-apps` `just` command (also like Bluefin and Bazzite have) to do as the name suggests

    #UniversalBlue #BlueBuild

  20. did some more refactoring in Zeliblue related to adding the `testing` tags recently. I revamped what came with the BlueBuild template into a reusable build action w/ + separate stable and testing builds

    `testing` builds daily + on commits to main (same as before)

    `stable` images are now strictly built and pushed daily at a set time. I've thought about making them weekly instead a la Bluefin, but for now I prefer daily

    github.com/zelikos/zeliblue/tr

    #BlueBuild #UniversalBlue

  21. ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite

    there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: github.com/zelikos/zeliblue/pu

    #UniversalBlue #BlueBuild

  22. ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite

    there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: github.com/zelikos/zeliblue/pu

    #UniversalBlue #BlueBuild

  23. ok so alongside the brief stint on Bluefin and borrowing more stuff from it, I also switched Zeliblue over to use the fsync kernel à la Bazzite

    there's no "custom kernel" module in BlueBuild right now, but we do have a containerfile module, so, here's how that's going: github.com/zelikos/zeliblue/pu

    #UniversalBlue #BlueBuild

  24. I've merged my experimental COSMIC image into Zeliblue's main branch

    it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR

    main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)

    #UniversalBlue #BlueBuild #COSMICDesktop

  25. I've merged my experimental COSMIC image into Zeliblue's main branch

    it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR

    main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)

    #UniversalBlue #BlueBuild #COSMICDesktop

  26. I've merged my experimental COSMIC image into Zeliblue's main branch

    it's still mostly experimental since COSMIC is still in alpha, but it does mean new builds will happen daily instead of only when I pushed to the initial PR

    main changes I have for it vs upstream uBlue base image are including most of the GNOME apps I use in Zeliblue, to fill in the gaps in default apps that COSMIC has (such as a web browser or an audio/video player)

    #UniversalBlue #BlueBuild #COSMICDesktop