HayadSont

joined 6 months ago
[–] HayadSont@discuss.online 4 points 3 months ago

My bad. Thank you for clarifying!

[–] HayadSont@discuss.online 2 points 3 months ago

My bad. Thank you for clarifying!

[–] HayadSont@discuss.online 5 points 3 months ago* (last edited 3 months ago) (5 children)

~~> plus sudden updates that nuke active applications.~~

~~This is not what's supposed to happen. If an app installed through flatpak is active while it's receiving an update, then the update is not supposed to affect the running application until it's closed/restarted.~~

Edit: Somehow I didn't realize the concern was raised against Snap and not Flatpak.

[–] HayadSont@discuss.online 3 points 3 months ago (1 children)

I agree that flatpak should just invoke flatpak uninstall --unused right after uninstalling a flatpak. I don't get why it doesn't do this automatically. Granted, some distro package managers (used to) operate somewhat similarly in that they required the autoremove option.

[–] HayadSont@discuss.online 1 points 3 months ago

They have their place, but they can’t really completely replace traditional distros.

As it stands, I kinda agree. But I truly wonder to what extent we might be able to close the current gap.

[–] HayadSont@discuss.online 17 points 3 months ago (5 children)

Would you mind elaborating?

[–] HayadSont@discuss.online 2 points 3 months ago (1 children)

I don’t remember how exactly this happened, but killswitch option in Linux ProtonVPN client somehow got broken in a way that I couldn’t connect to internet at all because killswitch was activated and couldn’t disable killswitch at the same time, I had to create another user and remove previous one. It also bombarded me with some errors regarding “kdewallet” that I don’t understand. Worth noting, I’ve been using this client with killswitch on many Gnome distros before and never had this issue anywhere else.

FWIW, the thing with killswitch it not due to Bazzite, nor KDE. There's a f*ck load of user reports all over the internet with different systems that have experienced the same thing; e.g. this one by a GNOME user on Pop!_OS. As for your criticism on kdewallet, I was also bothered by it the last few times I engaged with KDE Plasma. I suppose I was doing something wrong. Regardless, it was an unpleasant experience.

[–] HayadSont@discuss.online 4 points 3 months ago (2 children)

Packages are out of date even in the unstable branch (I know it’s unfair since it’s not trying to be a rolling release… but… but…)

Sure, some packages are outdated. But in terms of percentage of up-to-date packages, it's (AFAIK) the best out of any distro repo. And that's perhaps even more impressive of a feat when realizing it also sports the biggest repo. For actual stats: https://repology.org/repositories/statistics/pnewest

[–] HayadSont@discuss.online 2 points 3 months ago (1 children)

I wish you the best of luck at/with whatever you end up doing! May your system be protected from bit rot, config drift and/or problems caused by hidden state!

[–] HayadSont@discuss.online 1 points 3 months ago

Thank you! I'm looking forward to what y'all are cooking for us.

[–] HayadSont@discuss.online 1 points 3 months ago

Immutable structure creates difficulties for customization (more applicable to desktop systems than handhelds/custom consoles).

FWIW, it seems that 2/3 of Bazzite's user base uses it (primarily) as a game console anyways.

[–] HayadSont@discuss.online 2 points 3 months ago (3 children)

My apologies fam for not being able to help out much (if at all) 😅. FWIW, for related~ish reasons, I intend to explore the waters of NixOS within a couple of weeks. What are your plans?

 

The following gif demonstrates folding:

 

The following gif demonstrates folding:

 

The following gif demonstrates folding:

 

Included is the following disclaimer by the author:

  • This may not be representative of all types of Linux users. I’m sure this is not what your AWS engineer uses on EC2.
  • This may not be completely representative of all Linux gamers either. But I’d wage this is actually a good predictor where the market is going to shift. We saw first that Manjaro was getting the boot here first, before going under pretty much everywhere.
  • There may be some additional biases, due to whoever used ProtonDB.
  • Flatpak is NOT a distro, but that’s what Steam reports when it’s running on Flatpak, and Flatpak being distro independent we report it as a separate environment, if that makes sense. Feel free to ignore it if you wish.
  • Arch Linux is Arch Linux on desktop. The Steam Deck’s OS is reported as HoloISO, not Arch Linux, so stop trying to claim that Arch is first because of the Steam Deck! This is mainly data reported from desktop PCs, so no, SteamOS is not a thing at the moment on such machines. This may change as Valve starts providing official support beyond the Steam Deck.
 

Included is the following disclaimer by the author:

  • This may not be representative of all types of Linux users. I’m sure this is not what your AWS engineer uses on EC2.
  • This may not be completely representative of all Linux gamers either. But I’d wage this is actually a good predictor where the market is going to shift. We saw first that Manjaro was getting the boot here first, before going under pretty much everywhere.
  • There may be some additional biases, due to whoever used ProtonDB.
  • Flatpak is NOT a distro, but that’s what Steam reports when it’s running on Flatpak, and Flatpak being distro independent we report it as a separate environment, if that makes sense. Feel free to ignore it if you wish.
  • Arch Linux is Arch Linux on desktop. The Steam Deck’s OS is reported as HoloISO, not Arch Linux, so stop trying to claim that Arch is first because of the Steam Deck! This is mainly data reported from desktop PCs, so no, SteamOS is not a thing at the moment on such machines. This may change as Valve starts providing official support beyond the Steam Deck.
 

A video by SavvyNik that covers some of the highlights from the following recently published scientific article - Wolves in the Repository: A Software Engineering Analysis of the XZ Utils Supply Chain Attack

17
submitted 5 months ago* (last edited 5 months ago) by HayadSont@discuss.online to c/linux@lemmy.world
 

A video by SavvyNik that covers some of the highlights from the following recently published scientific article - Wolves in the Repository: A Software Engineering Analysis of the XZ Utils Supply Chain Attack

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects — those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects — those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

Fellow open-source enthusiasts,

We all have that mental backlog of promising projects — those distros, tools, and systems we keep tabs on but haven't yet deployed. Perhaps you're waiting for that mythical free weekend, lacking a spare/compatible device or just holding out until that one killer feature drops.

FWIW, my 'someday' list includes:

Operating Systems/Distros:

  • Gentoo – Source-based meta-distribution driven by Portage and USE-flags for near-granular control; binary packages also available if you'd rather skip marathon compile sessions.
  • Guix System – GNU's functional, declarative distro built with Guile Scheme.
  • MocaccinoOS – Image-based, container-built distro that originated from Gentoo/Sabayon but now uses the Luet package manager and OTA-like updates.
  • NixOS – Declarative Linux distribution using the Nix package language.
  • Qubes OS – Security-focused OS that uses Xen virtualization to compartmentalize your digital life into isolated environments with a unified desktop.
  • Spectrum – In-development security-oriented OS built on Nixpkgs using KVM-based microVMs for compartmentalization.

Desktop Environments/Window Managers:

  • COSMIC - System76's comprehensive Wayland-native desktop environment written in Rust.
  • Hyprland – Dynamic tiling Wayland compositor with scriptable layouts and impressive animations.

System Security/Firmware:

  • coreboot – Open source alternative to proprietary BIOS/UEFI firmware (though recent x86 still needs vendor blobs such as FSP/AGESA).
  • Heads – coreboot + Linux payload providing TPM-measured, tamper-evident boot for select laptops.
  • nix-mineral - NixOS module for convenient system hardening.
  • TrenchBoot – Framework for dynamic root-of-trust (DRTM) launches via Intel TXT, AMD SKINIT, or SEV-ES.

Applications/Tools:

  • Android Translation Layer - Run Android apps natively on Linux (still in early development).
  • Emacs – The self-extensible Lisp machine masquerading as a text editor; someday I'll embrace the config rabbit hole.
  • Olive – FOSS non-linear video editor in alpha.
  • systemd-sysext – Overlay read-only /usr and /opt (or /etc via confext) with extra images; extensions auto-activate at boot or can be merged/unmerged/refreshed live with a single command. Handy for immutable distros, though it’s additive-only and not a full package manager.

What open-source projects are you admiring from afar? Time to compare notes!

 

While this is an especially great development for the Fedora Atomic aficionados among us, I wouldn't be surprised if we'll be hearing a lot more from sysexts as (yet another) avenue for installing software, particularly on other atomic/immutable distros. The concept itself isn't new - Flatcar has been utilizing this approach for some time (and has been a significant influence on this Fedora initiative).

The gist would be that it basically allows installing software natively without the traditional rpm-ostree layering method. This approach eliminates both the lengthy installation times and reboot requirements typically associated with that process. Though, it doesn't seem to completely replace the conventional method as it comes with certain limitations (as per the developer):

They can not be used to:

  • install another kernel
  • install kernel modules
  • make changes to the initrd
  • make changes to /etc
  • add udev rules

For those wondering what is actually envisioned to be installed using this method, the software that's already available may shed some light 😉.

In any case, note that this is FAR from its final form. The (relative) complexity currently involved in installing and updating software reflects this clearly; don't expect shiny wrappers that will make all of us blissfully ignorant of the underlying complexity right away 😜.

 

While this is an especially great development for the Fedora Atomic aficionados among us, I wouldn't be surprised if we'll be hearing a lot more from sysexts as (yet another) avenue for installing software, particularly on other atomic/immutable distros. The concept itself isn't new - Flatcar has been utilizing this approach for some time (and has been a significant influence on this Fedora initiative).

The gist would be that it basically allows installing software natively without the traditional rpm-ostree layering method. This approach eliminates both the lengthy installation times and reboot requirements typically associated with that process. Though, it doesn't seem to completely replace the conventional method as it comes with certain limitations (as per the developer):

They can not be used to:

  • install another kernel
  • install kernel modules
  • make changes to the initrd
  • make changes to /etc
  • add udev rules

For those wondering what is actually envisioned to be installed using this method, the software that's already available may shed some light 😉.

In any case, note that this is FAR from its final form. The (relative) complexity currently involved in installing and updating software reflects this clearly; don't expect shiny wrappers that will make all of us blissfully ignorant of the underlying complexity right away 😜.

view more: next ›