Python • Effect of "Enable/disable read-only file system" on SUDO PIP installs

I'm looking for some insights here. I have a RPI 3b+ running Buster deployed as a weather station. I enabled "Enable/disable read-only file system" in RASPI-CONFIG. The result is that / is RW and /boot is /RO.

Normally, I install PIP libraries in my local account. However, for one program I need to run the Python program under root under SYSTEMD. For these I duplicate the PIP installs needed as SUDO PIP while under 'Enable/disable read-only file system'. All works well until I reboot and lose the SUDO PIP since I enabled 'Enable/disable read-only file system'. Yes, I know I should change this deployment to work under Python Virtual Environment.

So, from observing the behavior, but with the lack of documentation, it looks like 'Enable/disable read-only file system' turns / into a RW virtual file system. I can't find much except it says 'Enable/disable read-only file system' makes root read-only. I do remember at some point understanding that 'Enable/disable read-only file system' puts changed files into a memory based file system but can't seem to find that reference.

So, looking for confirmation and any additional insights into 'Enable/disable read-only file system' and SUDO PIP.

Thanks

Statistics: Posted by DS256 — Sun Jun 16, 2024 12:48 pm

---