Filesystem on NanoBSD is left read/write at first bootup after package reinstallation
It should be read only by the end of the boot process, but it doesn't seem to be making that change when packages were reinstalled during that boot.
Updated by Jim Pingle over 10 years ago
- Status changed from Feedback to New
The filesystem is mounted noatime, so even if it's left rw, it still isn't touched except when the system wants to write out things like the config, which it switched to rw to do anyhow. It should still be fixed at some point before release, but it isn't as critical as it looks.
Updated by Jim Pingle over 9 years ago
- Target version set to 2.1
Seems we need to revisit this again... If a NanoBSD upgrade reinstalls packages, once again it tends to completely hose the system these days until you reboot. Sometimes the GUI will not respond, many processes still sig11, and so on.
Updated by Phillip Davis over 9 years ago
I have also seen this behaviour - both filesystem RW and sig11 process exits. Now I know it is not just me I will look harder and see if there are any interesting things in logs before rebooting, try to work out what combinations of packages etc have the symptoms.