-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Question: read-only root filesystem #32
Comments
Looks like there isn't anybody else doing this. I'll close this since it's not actually an issue. |
Fair enough. For what it's worth: joeyparrish@b3cfadd#diff-c59b8b8fa77cc3c4ea5682ccf394fe53 |
Also, is there a better place for me to ask questions? A mailing list or forum or something that would be preferable to github's issue tracker? |
pi-gen doesn't exactly have an active user base to justify a mailing list or a forum. I am happy to answer questions here, but if I don't have an answer and nobody else chimes in, I will close the issue after a while. |
I'd definitely use this feature if it were available. I'll try to work @cashpipeplusplus' existing work into a PR with an option controlled by the config file. Is that something that you'd consider merging? |
JFYI, if read-only were to be an option, there would be better ways to do it than what I did in my fork. For example, in my fork, I made it a goal replace stage 3 and leave the rest as-is, to make rebasing easier. That means I'm undoing certain parts of earlier stages, rather than changing those stages themselves. |
The idea is that the stages themselves are separate from build system. The stages provided here are a starting point for people who want to customise the official raspbian image for their needs or to track development and see upcoming changes. I don't see how a read only option in config fits in with the above. I think it works best as a fork. |
I'm trying to modify pi-gen to create an image which mounts
/
and/boot
read-only. This means, for example, removingresize2fs_once
. In a nutshell, I'm trying to take the steps in this article and do them at generation time so that the system is read-only from the very first boot.Has anyone tried this, or am I in new territory? I'm sure I'll get it working eventually, but I wanted to see if anyone has any experience here before I spend too much time hacking away at it.
The text was updated successfully, but these errors were encountered: