Releases · systemd/systemd
github.com
The systemd System and Service Manager . Contribute to systemd/systemd development by creating an account on GitHub.

Systemd 254 released and now has a new soft-reboot option:

    * A new "soft-reboot" mechanism has been added to the service manager.
      A "soft reboot" is similar to a regular reboot, except that it
      affects userspace only: the service manager shuts down any running
      services and other units, then optionally switches into a new root
      file system (mounted to /run/nextroot/), and then passes control to a
      systemd instance in the new file system which then starts the system
      up again. The kernel is not rebooted and neither is the hardware,
      firmware or boot loader. This provides a fast, lightweight mechanism
      to quickly reset or update userspace, without the latency that a full
      system reset involves. Moreover, open file descriptors may be passed
      across the soft reboot into the new system where they will be passed
      back to the originating services. This allows pinning resources
      across the reboot, thus minimizing grey-out time further. This new
      reboot mechanism is accessible via the new "systemctl soft-reboot"
      command.>
  • Toribor@corndog.socialEnglish
    461·
    11 months ago

    If I’m understanding this right it seems like a good fast way to test that services start up properly without doing a full reboot so that’s pretty nice.

  • throwawayish@lemmy.ml
    19·
    11 months ago

    Hard-reboots are no longer required on Silverblue when installing or upgrading packages (besides kernel) through rpm-ostree. Arguably one should only sparingly rely on rpm-ostree for installing packages. But it’s great to have access to soft-reboot when setting up a new system.

  • Atemu@lemmy.mlEnglish
    72·
    11 months ago
    • Support for System V service scripts is now deprecated and will be removed in a future release. Please make sure to update your software now to include a native systemd unit file instead of a legacy System V script to retain compatibility with future systemd releases.

    Why is this being removed?

    I wouldn’t use it but it certainly seems handy for a quick hack and also for people who are used to the old ways.

    • dr_robot@kbin.social
      34·
      11 months ago

      Maintaining legacy options is always maintenance overhead or things you need to work around when implementing new features. I suspect that they’ve concluded that not enough people use it anymore to justify the overhead.

      • PM_ME_UR_PCAPS@lemmy.mlEnglish
        13·
        11 months ago

        Yeah it’s not like service files are difficult to write. They’re certainly easier than sysv init files

  • Chais@sh.itjust.worksEnglish
    3·
    11 months ago

    Does that mean we will be able to update graphics drivers without a full reboot if the kernel didn’t update?

    • treadful@lemmy.zipEnglish
      112·
      11 months ago

      I don’t think any graphics drivers run in user-space, so probably not.

      • Backslash@feddit.de
        3·
        11 months ago

        Yes they do, Mesa being one. Only the close to the metal stuff and Kernel-DRM is handled in kernel space, most of the heavy stuff is done in user space.

        • treadful@lemmy.zipEnglish
          2·
          11 months ago

          Where’s the line you’re drawing? And what would be the “heavy stuff” in user-space?

          I’m far from a kernel expert, but I still have the i915 module loaded into the kernel on this bad boy, which I think most people would call a driver.

    • Zamundaaa@discuss.tchncs.de
      2·
      11 months ago

      You could always do that. If you update Mesa, any applications you start after updating will use the new version of Mesa

  • spez@sh.itjust.worksEnglish
    63·
    11 months ago

    So is this like that windows ‘fast boot’ or whatever it’s called thing?

    • bamboo@lemm.ee
      251·
      11 months ago

      It is nothing like that. Windows fast boot is just fancy resume from hibernation.

      • aksdb@feddit.deEnglish
        8·
        11 months ago

        It’s a mix. It hibernates what would be the result of a systemd soft-reboot, before user space starts up again.