this post was submitted on 30 Jun 2023
125 points (100.0% liked)
linuxmemes
21222 readers
37 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
sudo
in 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!
founded 1 year ago
MODERATORS
I feel like it’s harder to break the bootloader these days. All my dual-booting escapades worked fine, I still have most of my hair, and there’s no way my Linux skills have improved that much.
I think that the major issue with the bootloader is when a user confuses the device file for the entire drive (
/dev/sda
) with the device file for the partition (/dev/sda1
), whch is not entirely unreasonable for a new user who doesn't understand the naming system to do. Like,mkfs.ext4 /dev/sda
rather thanmkfs.ext4 /dev/sda1
. Then you overwrite the entire drive, starting with the MBR, rather than the contents of a partition with your new filesystem.