I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 1 Post
  • 172 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle




  • Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).

    This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s nosystemd repo, which allows to install components of the Debian stack without the enforced systemd dependency; and later libam-elogind-compat which aided shimming some of systemd’s requirements under elogind.

    Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).


  • None. On Alpine you can only use OpenRC and on Debian you can only use systemd. Most distros don’t let you change out the init system. If you want systemdless Debian look into Devuan.

    Fake news. On Debian you can use both sysvinit and openrc (I have six servers on sysvinit, tho I do actually intend to shift them to systemd later mostly because of the container management goodies).

    Judging from this post, I would say you should not be looking to change out your init system

    Mostly agreeing here. For selfhosting the init system matters barely any, since past the default distro setup one would be doing most of everything with Docker, Podman, etc. At that point, none of the usual Linux religious wars matter much (you can perfectl edit a compose file with nano).






  • Problems Linux itself has to overcome? Maybe two or three.

    • Hopefully I’m mistaken but apparently accessibility has been going down the last few years.
    • Settings that make sense to change should be exposed more adequately. No one should ever get a visual toggle to eg.: disable SELinux on their systray, but controls to adjust color profiles and screen “temperature” management should be more reachable and clear.

    Problems that are mistakenly attributed to Linux but that are actually for manufacturers, sellers and provisioners to take responsibility for and overcome? A good lot.

    • Sellers have to sell machines with Linux preinstalled. Getting a machine Linux-ready from factory is easy, but it’s only the commerces who can actually place them on a, ta know, selling point.
    • Sellers or manufacturers should actually advertise when their device works with Linux. If people have to guess whether their next buy even boots / plugs in, that’s a hindrance to commerce.
    • Hardware manufacturers are not providing adequate Linux support (FizzyOrange mentions the eternal issue of laptop battery management; Naiboftabr mentions stuff like “audio stops working”).
    • Developers have to get back to developing for Linux natively (rather than eg.: “develop for a trimmed down Windows version that runs on Steam”).
    • Developers of Linux itself need to provide a better “rescue mode” for when things inevitably go wrong. Something that boots up to a “guaranteed working state” that still has workable UI but with most or all customizations disabled.



  • lambalicious@lemmy.sdf.orgtoLinux@lemmy.worldDebian 13 releases today
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    8
    ·
    1 month ago

    I heard it was shipping libraries that capture all clipboard data and sent it to foreign servers unencrypted, and that this was being defended in the buglist as a feature, so I might actually skip this one at least until the first or second batch of security updates rolls on.

    For servers, it makes not much difference for me; where possible I either stick to Stable + Backports (which requires Backports in the first place) or jump right to Unstable.


  • Fedora 42 even eliminated X11 as an option (I think they’re reversing that stance now, though),

    This is one of the big problems Wayland and its proponents tended to have and still have in general:

    They insist on selling vaporware. Or on doing the Ubuntu thing where they just push dev onto production for the users to become unpaid tester workforce. And then they have the gall to complain that people notice things don’t work.

    Curiously enough, I don’t recall pulseaudio (another member of this “nu-linux” / Microsoft™ Linux trend) was like this. Sure, Fedora packaged it horribly, but I don’t recall it having been pushed as a default to prod when it was unusable.

    Or I am lucky to not have noticed. Oh well.