this post was submitted on 30 Oct 2023
781 points (95.2% liked)
linuxmemes
21210 readers
50 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'm not talking about dual booting but other Linux bootloaders during the installation. I've not had a Windows installation for several years now. If you don't know whether you encrypted your drives or not, then you likely didn't. Either way, if they are it makes figuring out their correct ID's quite complicated and confusing, which was part of the issue. All the related guides to that topic sort of assumed I already knew what the hell I was doing, hence why I tried to ask for help.
In my Installer grub was not the default bootloader but I had a selection and picked grub since that's what I know.
Not knowing what id your drives have sounds very problematic no wonder you had troubles. I wish you best of luck with your new setup though :)