I had my PC not booting anymore because of a mount in fstab that ddidnt exist anymore. If it wouldve had the nofail flag, booting would still work. I think it has no disadvantages to set the flag, right? Or should it be opt-out? For sure I think it should be default, to prevent such a thing, as a dracur shell is pretty intimidating.
ping
I would be a bit reluctant to force it on for everybody without an ability to opt out Perhaps we could add it to the list of available options in the mount point dialog? Right now it is not exposed at all, we only have ro, users, noauto, noatime, nodiratime, sync, noexec and relative. Or is that not sufficient?
I think that would be a good idea. I would pre-enable that though, as it can cause a lot of trouble
Git commit 4232098e33115aad1e1174e87661214dffec6adb by Andrius Štikonas, on behalf of Thomas Bertels. Committed on 04/04/2024 at 00:06. Pushed by stikonas into branch 'master'. Enable nofail by default for / and /home Enable nofail by default when the mount point is / or /home Apart from those, nofail mounts let the system boot normaly. M +4 -0 src/gui/editmountpointdialogwidget.cpp https://invent.kde.org/system/partitionmanager/-/commit/4232098e33115aad1e1174e87661214dffec6adb
The are was a typo in the commit and the merge request, obviously, it's: Enable nofail by default *except* for / and /home Enable nofail by default *except* when the mount point is / or /home