-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fsck capability #32
Comments
While compiling fsck into booster's init probably won't be easy, the 2nd, systemd based method listed in wiki appears to work just fine, as long as you pass |
Implementing I think that This feature implementation is straight-forward and should not take much time. Though I work on a few long-overdue code refactoring to make unit-testing easier. Once it is done I'll look at the |
Sounds good! |
The only reason why booster mounts the root partition as RW by default is thats what If you want to mount it as read-only then pass |
Yeah, I know how this works :) |
Alright, This functionality is lightly tested. If you see any issues with it please let me know. |
If 'fsck' and 'fsck.<fs>' binaries are added to the image then booster actvates boot-time filesystem check. The check runs in non-interactive mode. It tries to fix any filesystem errors automatically. If it fails then boot stops. Closes #32
Does booster check ONLY root filesystem or all matching? I mean for example with ext4 root and FAT32 |
Booster does check
|
See https://wiki.archlinux.org/index.php/Fsck#Mechanism
The text was updated successfully, but these errors were encountered: