Systemd Alternatives

systemd reviews and mentions

• Bypassing Bitlocker using a cheap logic analyzer on a Lenovo laptop
  3 projects | news.ycombinator.com | 24 Aug 2023

  > The vulnerability also applies to other encryption systems using the TPM, like LUKS disk encryption.

  No, this is a Bitlocker problem. Systemd LUKS disk encryption uses encryption on the bus by enabling TPM encrypted sessions: https://github.com/systemd/systemd/commit/acbb504eaf1be51572...

• Version 5 of systemd-free Debian remix Devuan is here
  2 projects | news.ycombinator.com | 21 Aug 2023

  The code just has to tolerate a period where journald's starting but not yet available, since it's PID1 which starts journald, to avoid deadlock. Chicken-egg problem.

  There's assumptions throughout PID1 that journald is the logger, units which log get journald deps added:

  https://github.com/systemd/systemd/blob/v254/src/core/unit.c...

  Salient point being, this is all journald-coupled, not some abstracted logging concept you can substitute with any other thing.

  The problem with supporting a journald-less mode as some first class thing is it's basically a degraded functional state.

  2 projects | news.ycombinator.com | 21 Aug 2023

  > You literally don't need to use those features to use systemd. There's no requirement on journald or systemd-resolved if you just want to use systemd as an init.

  Unit/Service file syntax controls per-service logging, PID1 is rather tightly coupled to journald in implementing those features.

  Hence the service manager explicitly checks that journald is running at startup:

  https://github.com/systemd/systemd/blob/v254/src/core/manage...

  Other components like resolved and networkd are optional however.

• Installing Debian bookworm without systemd
  2 projects | news.ycombinator.com | 19 Jul 2023

  I was finally coming around to systemd. Then they broke my laptop.

  https://github.com/systemd/systemd/issues/25269

  I'm still livid at this Luca guy gaslighting people on the "correct" behavior of a feature people were using for years already. They re-purposed an existing sleep mode and changed it entirely to mean something else. Originally you would set a timeout that your laptop would suspend and then hibernate. They changed it to mean that your laptop suspends until your battery hits 5% and then hibernates. As if people want to open their laptop the next morning only to have no battery left.

  Ironically, the stated reason for this change was to "prevent data loss". Guess what they did? They introduced a bug in this "fix" that guaranteed your laptop would not wake from hibernate. You had to reboot the damn laptop each time you woke from hibernate because it would get stuck on a black screen, thus "losing" your data. I "lost" more data from their stupid fix than anything else.

  They admit the original feature was broken because it didn't take into consideration for battery percent. Fine. But there was absolutely no reason to change the behavior. You can do both! The only reason I can think of is you just like being an incredible asshole to people. Which is obvious from that thread. Do they even use a laptop? Why would I want a dead battery next time I open the lid???

• Cool but Obscure X11 Apps
  7 projects | news.ycombinator.com | 13 Jul 2023

  Lennart earned himself a reputation for thinking his own shit doesn't stink, closing bugs against his software as NOTABUG or WONTFIX even when his software was flagrantly at fault.

  Here is one particularly egregious and clearcut example: https://github.com/systemd/systemd/issues/6237

  tl;dr: a systemd service configured to run as a user who's username started with a digit (e.g. the username '0day') would instead run as root. Lennart initially closes the bug report and refuses to fix it because he thought such usernames weren't acceptable, despite the kernel and most linux utilities permitting it and handling it gracefully. A good engineer with a shred of humility would take this report seriously, even if he thought other systems shouldn't be permitting the circumstance. To see the lead engineer of a project so important to linux take such a childish stance on a security-related bug was infuriating and demoralizing.

  This is just one example, which didn't take anybody by surprise. It's his modus operandi. May the gods have mercy on Microsoft for hiring him.

• Which alternative for slirp4netns in rootless containers is better?
  5 projects | /r/podman | 9 Jul 2023
• Need ideas on how to suspend then hibernate (on systemd 252)
  2 projects | /r/linux4noobs | 2 Jul 2023

  Are you sure about that? Neither the upstream changelog for version 252 nor the Debian changelog mentions that. In fact, the upstream changelog explicitly mentions a change about suspend-then-hibernate (if it really had been "taken out", then surely they wouldn't have implemented that change and mentioned it in the changelog). And the systemctl(1) man page in Debian does mention suspend-then-hibernate, as does systemctl --help.

  2 projects | /r/linux4noobs | 2 Jul 2023

  Here is the Github PR to get suspend-then-hibernate working on systemd 252: https://github.com/systemd/systemd/issues/25269

• Will Red Hat Bring Back CentOS?
  2 projects | /r/redhat | 1 Jul 2023

  NetworkManager not renewing DHCPv6 lease on CS8 [0]

• “Support for System V scripts now deprecated; will be removed in future release”
  4 projects | news.ycombinator.com | 28 Jun 2023

  He made the commit that added this deprecation notice

  https://github.com/systemd/systemd/commit/7474097d51907c5cc1...

• A note from our sponsor - SonarLint
  www.sonarlint.org | 23 Sep 2023

  Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today. Learn more →