888
systemdeez nuts
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Apr 2024
888 points (98.7% liked)
linuxmemes
21280 readers
711 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- 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.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
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
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
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 fork-bomb your computer.
founded 1 year ago
MODERATORS
Run installation media and copy systemD over to the system
For real though, if you break ANYTHING in Linux, it can probably be repaired through live image on your flash drive.
I use BTRFS, and it randomly decided to corrupt like half of the system packages on my system after an update, but all I had to do to fix it was boot into a live environment and run a command to reinstall everything on my system. :P
Its been pretty stable for me
Same 7 years with no issues
Using btrfs for past 6 months in my kde environment, doesn't encountered any problem like this. Pretty stable
It's only really a problem if I try upgrading while low on space and also having disk compression enabled
No probably about it
Or just use the recovery shell. They did say they could log in.
Is it possible to chroot from a livedisk and reinstall systemd from that? I'd imagine the Internet connection would work just fine.