-
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
Mounting /boot read-only #10
Comments
interesting thought about /boot being read-write after boot. I didn't consider it and I don't know. re /boot/firmware, if you haven't already made changes, I guess changing line 63 and and 93 in rootwork would do the trick, ie line 63 from and line 93 from If you're able to make those changes and it works ok, send me a pull request and I'll add them in. I'll test on a raspbian to make sure it doesn't cause any problems, but I don't see how it would, it should silently ignore /boot/firmware as it doesn't exist on raspbian. |
I submitted PR#11 which fixes the |
I noticed in
rootwork
that the/boot
partition is remountedrw
and thenro
on exit, but I don't see where/boot
is mountedro
to begin with. On Rasbian, is the/boot
partition actually mountedro
after a reboot but before runningrootwork
?Just a note - mounting
/boot
asro
may not be that important because nothing should write to it during normal operation, only during things like kernel updates. However, I don't know what risk power failures would pose.Related to this, to support Ubuntu Server and other systems that use
/boot/firmware
rather than/boot
(see issue #9), therootwork
script needs to be updated - perhaps to use/boot/firmware
if it is a mountpoint, and otherwise use/boot
.@chesty - I want to add to others' comments about how valuable this project is for long-term RPi stable operation. We appreciate the time and energy you've contributed to write, test, publish, and support this project.
The text was updated successfully, but these errors were encountered: