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

(Question) Filesystem persistence #126

Open
hardBSDk opened this issue Oct 29, 2022 · 1 comment
Open

(Question) Filesystem persistence #126

hardBSDk opened this issue Oct 29, 2022 · 1 comment

Comments

@hardBSDk
Copy link

NomadBSD persistence covers everything? even root filesystem?

Or it act like all LiveISO persistence where it save the settings/files but don't change the packages of root filesystem (packages of the .iso remain untouched, the system runs on memory).

I mean, it act exactly like a normal hard disk installation where you change everything from the ground?

@mrclksr
Copy link
Member

mrclksr commented Oct 31, 2022

NomadBSD persistence covers everything? even root filesystem?
[...]
I mean, it act exactly like a normal hard disk installation where you change everything from the ground?

Everything is writeable and changes will remain on the flash drive (except for /tmp and /var/log which are mounted via tmpfs).
The installed packages/ports under /usr/local are stored in a uzip image (ro), but there is /data/usr/local (rw) mounted on top of /usr/local via unionfs. Changes you make to /usr/local will be written to /data/usr/local which is located on the flash drive. This is just a technical detail. From the user's perspective /usr/local is rw.

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

2 participants