Skip to content
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

[Feature request] Allow initgfx to work on read-only root filesystems #85

Open
probonopd opened this issue Apr 2, 2021 · 0 comments
Open

Comments

@probonopd
Copy link
Contributor

probonopd commented Apr 2, 2021

In helloSystem, we would like to have a system that can be booted from truly read-only media such as DVD-ROM.

Setting Up FreeBSD for Read-Only Booting makes it seem like it is possible to boot FreeBSD from read-only media. Looks rather simple! Exactly what we would like to use.

But then, initgfx currently assumes it can write in many places.
Currently helloSystem needs a giant workaround that copies the whole system into RAM, just to make initgfx work. We also tried to use unionfs but could not get it to work with initfgx.

So the question is:
Would it be possible to change initgfx in a way so that it only writes in /var/run?
One could symlink the files/directories it needs to write to /var/run.

After all, I think that conceptually any data that initgfx touches is transient in nature, it is auto-generated on the fly and cached, but should not be persisted. So, exactly what /var/run is for?

@probonopd probonopd changed the title [Reature request] Allow initgfx to work on read-only root filesystems [Feature request] Allow initgfx to work on read-only root filesystems Apr 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant