News for hackers. Stuff that matters.
[dead]
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by IgorPartola on Saturday March 13, 2021 @08:03PM (#26451758)
You know I feel that way about the Linux kernel. Everything is done by the Linux kernel developers and it’s shipped as one monolithic thing. Wouldn’t it be better to get drivers for networks cards from other places? Or have to pick from a list of memory management packages that get downloaded from GitHub on every reboot? And why do they include things like spin lock implementations? Should that be an NPM package? /s
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by badsectoracula on Monday March 15, 2021 @01:18AM (#26462849)
You're joking but having drivers separate from the rest of the Linux kernel and with a stable ABI would certainly help other OSes as well (e.g. ReactOS, Haiku).
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by viraptor on Saturday March 13, 2021 @08:52PM (#26452052)
> I suddenly have to use systemd-* over them.

You really don't. You have the choice to go with a distro which doesn't use them, or to mix&match yourself.

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by zbentley on Sunday March 14, 2021 @10:56AM (#26455923)
> Like, hell, what is systemd-boot and when and why it replaced grub2?

I've been really happy with systemd-boot; in my limited (used it on probably a dozen machines across several distros at this point) experience, it's better at autodetecting nonstandard images/locations than grub, and is vastly friendlier to weird partitioning schemes. It also has a much more minimal config surface than grub, which I like (since, across distros, I no longer have to learn a distro-specific set of nested/included grub config files and conventions, nor do I have to worry about what will be auto-regenerated when a distro does a kernel update versus what configs I need to edit by hand). However, that limited config surface may be a drawback to people who need to customize very esoteric boot cases.

I also aesthetically prefer systemd-boot's minimalism and focus on newer (UEFI) boot strategies compared to grub; the latter is huge in terms of functionality. A lot of that size is needed for rare cases and older boot configurations (and if you fall into either group, grub is what you should use), but it complicates the "happy path" on post-2010 computers.

https://en.wikipedia.org/wiki/Gummiboot_(software)

Re:Systemd 248 RC3: systemd-oomd is now considered fully sup... by candiddevmike on Saturday March 13, 2021 @11:17PM (#26452768)
I personally prefer systemd-boot over grub2, it's dead simple to configure and works really well for UEFI systems (and dual booting windows).