This isn’t something that happened to me. I’m just wanting to know, when your haiku broke, what was it like and could you say it was more hard harder to fix haiku than it was if you were to break your windows or Linux?
Btw this was a shower thought that I thought about at 7 o’clock right now in the shower
Haiku is super easy to fix, as long as you don’t damage your /boot/system/packages directory, which is rather uncommon.
When you start your computer, before you see the Haiku bootscreen, repeatedly press the space key as fast as you can.
You should get into the Haiku Bootloader, where you can select a previous state (before breaking changes were installed).
Select one, continue booting and your Haiku should work again.
That said, this hasn’t happened to me when I was just using the computer, but I sometimes break stuff when developing.
Haiku is usually quite stable, even the nightlies.
Happened to me when packaging a library which broke the whole system, took about a year untill I was able to launch it again when booting up the laptop, every time got “no boot partition found” IIRC.
In the end deleted the 2 Haiku partitions, re-created them and things were on par again, I “think” having the second partition as BFS somehow blocked Haiku from finding it’s boot partition?
There isn’t much in my system partition but a few configuration files. All my work and data is on separate volumes. So in the unlikely case that my system partition is hopelessly broken, I could just reinstall it from scratch and be up and running in a few minutes.
On my work computer where I run Linux, there are all sorts of configuration patches all accross the system. I won’t be able to replicate them all. On my homeserver it’s even worse, with some patches being overwritten by system updates.