• @[email protected]
    link
    fedilink
    English
    411 months ago

    Yeah i remember debian installs sysvinit if you apt remove systemd and installs systemd if you apt remove sysvinit

    • @[email protected]
      link
      fedilink
      211 months ago

      haha why does debian bother adding this rule if the system will be left in broken state anyway

        • @ozymandias117
          link
          English
          111 months ago

          (As the tester above) It is a broken state

          It failed to install the initscripts package because apt bailed out

          apt —fix-broken install got you a little closer, but the screenshot didn’t say they tried that

          My bet is this worked when systemd was first introduced, but since there’s not much use for it now, and sysvinit is deprecated, it just doesn’t accidentally work anymore

            • @ozymandias117
              link
              English
              111 months ago

              You can’t - it’s just asking what runlevel to launch, and there are no files for any runlevel

              You’d need to add init=/bin/sh through grub at that point

                • @ozymandias117
                  link
                  English
                  111 months ago

                  I didn’t after breaking it and rebooting

                  I restored the snapshot from before breaking the system and tried to see what would happen if I didn’t just reboot after apt bailed out