• ozymandias117@lemmy.world
    link
    fedilink
    English
    arrow-up
    12
    ·
    6 months ago

    I was curious too, so I tried it in a virtual machine

    It half installed sysvinit, systemd failed to get fully removed, and apt gave up due to too many post-install errors

    The reboot threw me into an init that asked for me to specify the runlevel (since there wasn’t anything in init.d)

    I guess they didn’t understand the difference between that question and a logged in shell

    My guess before trying it was that they somehow got stuck in Grub’s shell

          • ozymandias117@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            6 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@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                6 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