this post was submitted on 19 Apr 2024
890 points (98.7% liked)

linuxmemes

24254 readers
2034 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    890
    systemdeez nuts (sh.itjust.works)
    submitted 11 months ago by silverchase@sh.itjust.works to c/linuxmemes@lemmy.world
    206 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] woodgen@lemm.ee 35 points 11 months ago (3 children)

    How the fuck is login and "the command line" still working? Maybe they did not reboot.

    [–] why@lemmy.sdf.org 24 points 11 months ago

    The reboot probably sent him straight to a virtual console.

    [–] ozymandias117@lemmy.world 12 points 11 months ago (1 children)

    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

    [–] mexicancartel@lemmy.dbzer0.com 4 points 11 months ago (1 children)

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

    [–] redcalcium@lemmy.institute 2 points 11 months ago (1 children)

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

    [–] mexicancartel@lemmy.dbzer0.com 2 points 11 months ago (2 children)

    Maybe because its still not a broken state? They could still add init files ig

    [–] ozymandias117@lemmy.world 1 points 11 months ago (1 children)

    (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

    [–] mexicancartel@lemmy.dbzer0.com 1 points 11 months ago (1 children)

    I mean you still can use cli? So you can technically make an init file and boot?

    [–] ozymandias117@lemmy.world 1 points 11 months ago (1 children)

    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

    [–] mexicancartel@lemmy.dbzer0.com 1 points 11 months ago (1 children)

    How are you running apt then?

    [–] ozymandias117@lemmy.world 1 points 11 months ago (1 children)

    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

    [–] ulterno@lemmy.kde.social -1 points 11 months ago

    As long as you can run vim, gcc and make, it's not broken.

    [–] possiblylinux127@lemmy.zip 6 points 11 months ago

    initramfs recovery shell or they are trolling