Skip to content

OpenRC migration #17

@magiruuvelvet

Description

@magiruuvelvet

I initially only choose systemd out of habit and laziness (because that's what everyone else is using™), and because of bad experience writing services in shell script. Back in the days I migrated from Arch Linux to Gentoo because I was fed up with binary distros in general. systemd is becoming worse and more bloated with each release, and I froze it at some old version due to compatibility issues. Due to growing concerns about security I want to give OpenRC an honest chance. I also think not using systemd in this era, where it is aggressively pushed, might be interesting to find out how well or poor software handles the absence of it.

Steps that need to be taken: TODO

  • evaluate whether the default/linux/amd64/23.0/llvm profile inherits the merged-usr feature - I want to keep my system in merged-usr mode.
  • CGroups stuff
  • use sys-auth/seatd instead of pulling in elogind
    • evaluate KDE operability
  • use sys-apps/systemd-utils[boot,tmpfiles,udev] from the systemd stack
    note: systemd-boot is the only (?) boot loader than can be successfully compiled and executed on amd64 bare metal with a pure LLVM toolchain, as it doesn't contain weird GCC/binutils hacks and assumptions. there are options that work with LLVM toolchains today, but for compatibility I will stick with systemd-boot for the time being.
  • use app-admin/syslog-ng or app-admin/rsyslog as replacement for the systemd journal. I like my logs accumulated into one central place.
  • implement service scripts for PipeWire and WirePlumber to run in system mode

Notes:

  • initramfs handling needs to be reworked. I'm currently rolling my own initramfs with dracut.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions