Woke up today and fought #Linux because I edited my #fstab folder last night through a gui app instead of through #vim or something. I figured #KDEPartitionManager would have fixed the inconsistencies itself but I guess I expected too much of it.
The thing is, I don't think you should even HAVE to mess with fstab or mess with mount points. This should be handled by default much like it is in #Windows.
I also figured it would just throw up an error about being unable to mount the HDD due to conflicts in fstab and boot the drives that are otherwise fine, but nope. Just gonna boot into emergency mode.
Your average user isn't going to just boot a recovery partition of #linux to do a minute's worth of minor editing to fix their computer if it's something like this. They'll probably assume it's just broken.
Rather than putting it on the user to fix something that should be a basic feature, this should be a QOL thing that #Linux devs try to address.
Linux has come so far since I started using it in the mid 2000s that I think it would be silly if this issue was never addressed.
Basic stuff should NEVER require editing a config file.
@Moondancer0X "Users could conceivably want to legitimately do the dangerous thing, so let's not bother putting up a guardrail at all" is a really common sentiment among the elitist old guard computer nerds.
The 99.9% of the time that you don't want to fall into the chasm is totally disregarded.
Maddie ♾️
Urzl