- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Just use rEFInd to easily overcome bootloader coups
Easy solution if you only have one SSD: instead of installing Windows as your second OS, install a different Linux distro.
And while you’re at it, install a third distro
deleted by creator
Why stop there?
If I dual boot windows, I tend to disconnect my Linux drive any time I do anything on the Windows side. Even installing Windows fresh using default settings, it managed to completely erase my Linux disk to put the Windows bootloader on it even though I selected a completely different disk for the Windows OS. Won’t be making that mistake again. And by mistake I mean dual booting Windows. That pile of spaghetti code gets a VM.
… on a proxmox host in another room.
I got used to windows overwriting the MBR and could generally work around that. But the last time I tried windows/Linux dual boot, it was windows that got caught in a recovery loop after a windows update. Linux was fine. I was impressed at how thoroughly Windows had killed itself on a basic unmolested install. At that point I decided I was done with windows on bare metal unless it was the only thing running. Windows goes in the virtual sandbox or plays by itself.
windows installing its bootloader on a completely separate drive is such a weird and fucking idiotic issue for it to have.
Ugh, that’s so annoying. Every time windows updates i have to open the BIOS and put ubuntu first on the boot order so it doesn’t skip grub.
I Also have a drive that i can access on both linux and Windows and every so often Windows will make it inaccessible on Linux because it didn’t fully unmount the drive.
It’s crazy that the OS has access to the BIOS in a R/W mode at all. Gaping security hole.
deleted by creator
Every panel would be the same for you regardless of the brand of your laptop, no?
deleted by creator
I assume since we’re talking about Linux bootloader you aren’t running macos, but Linux.
deleted by creator
MacOS updates* have never broke my Asahi
*May have to do with the fact I haven’t booted into MacOS since installing Asahi
They actually did for some people a couple of months ago.
Dual boot issues like this is why I stopped using windows not in a VM.
I gotta give dual booting a shot. I need windows for my college’s crappy exam software, but I also can’t afford another laptop just for Linux
It’s worth it lol, though watch out you may find yourself dreading opening windows
I just use a VM for windows apps that don’t work through wine
I haven’t had to use any exam software recently, but in the past when I did I remember reading that it can detect when the host is virtual and will not run in a VM. Fortunately at the time I still had a windows laptop lying around, but I’d have a real problem if one of a courses now tried to do this.
Windows managed to brick itself when I booted for the first time in a month. I only wanted it for the Karafun app, but I guess I can live without it.
i have two other possibilities at hand, that do not involve two SSDs:
- don’t use intentionally broken software in the first place ;-)
- use another device for bootloader, could be a readonly CD or a usb drive, PXE/bootp could also do it.
And if your company wants you to use rotten software, they also want you to give them the delays, downtimes and annoyances that naturally come with rotten decisions, just keep that in mind.
Here is one thing to remember and why i call it rotten software and rotten decisions:
Microsoft offers a free “blame the ransomware people” to any CTO who just wants to receive money without working at all or not having to “think” during work. That same CTO can get a bonus after “solving” the ransomware issue and then: “look how ‘invaluable’ that CTO is to the company” he “worked” for month ( yelling at engineers he previously told to install rotten software???) and resolved the ransomware issue!! This is same to those who work. no law has ever given people that many payed breaks from work as “rotten software” vendors did. and if you made a mistake and did not get trained before, you could blame bot beeing trained.
Look at it from a “fingerpointer” point of view, one cloud always blame someone else for everything and the only one to blame is too big to fail and also untouchable due to their army of darkness lawyers. thus anything happened? no one could be guilty AND be held responsible. Also if one is slow at work, and so is his OS, obviously easy to blame someone else again.
so microsoft offers a “solution” to “boss wants you to work more and quicker” but remember, that same boss only “needs” a cover for his own ass to be able to point to someone else and the ones creating the rotten software do deliver that ;-)
i do not know any better wording for such a situation than “rotten” thus i name it so.
That’s why we need two ssds for dual boot
And one day, we will have updates that will tell us “Windows have fixed a drive with partition table issues.”
Don’t wait for that day. Unplug all secondaries before booting into Win
i need to remove my windows boot drive from my workstation, but it lives in a rack. And has a temperament. Sometimes when losing power shit just refuses to boot for like an hour, eventually it randomly boots. Still unsure why. Could be anything really. Best guess is bad cmos battery though. Could be slightly bunged bios, could be marginally fucky cpu. Who knows. It’s fine when shutdown with power for long periods of time though.
Gotta love modern hardware, if only 7 segment displays weren’t a 300 dollar privilege.
Windows actually works better in a vm on Linux than on bare metal. And it’s got a much smaller chance of breaking my PC that way too.
Linux actually works better inside WSL in Windows.
Linux running inside WSL on Windows is the only thing that makes Windows usable.
Linux running inside WSL on Windows is the only thing that makes Linux usable.
FIFY
deleted by creator
Nooooooo!!!
🤮
This is dangerous misinformation.
This is the correct information.
I know for a fact that my company’s build process is twice as slow on Windows/WSL than on vanilla Linux. We have benchmarks from many different user environments.
I have to use Windows for work, so this is how I got it setup and MS still makes it difficult with updates lol.
deleted by creator
i use a different drive for my windows installation because that happened to often,
and i swear it once managed to wipe the bootloader on the linux drive.i have no idea how it did that,
but i avoided starting windows using the grub entry since then.Having two drives is sometimes not enough, either. I have no idea why, but anytime Windows installs for the first time or goes through a major update (not the small security patches, but the periodic feature releases) there’s a random D20 dice throw to determine if it will randomly decide to create the bootloader and recovery partitions in another drive, even though your main installation isn’t there.
I kid you not, Windows 10 once decided that my external SSD enclosure was the best place to put the bootloader.
This happened to me! Did an update, unplugged my eSATA and BAM! Can’t find bootloader. I literally, physically facepalmed when I realized what happened. At least the old one still worked from the primary.
I’ve done a ton of Linux updates and this has never happened to me once (yet).