Hide Forgot
In the previous versions of Fedora, setting the READONLY=yes flag in /etc/sysconfig/readonly-root file caused the system to protect the file system drive making it readonly. In fedora 15 alpha it makes tmpfs but does not set the system drive to readonly. Fedora 15 Beta How reproducible: Edit /etc/sysconfig/readonly-root Set READONLY=yes Set TEMPORARY_STATE=yes Actual results: File system is still writable Expected results: File system to be read only Additional info: Worked on Fedora 14
We apply the options from /etc/fstab on your root fs during boot. Maybe you don't use ro on / in fstab? Please paste your fstab.
Created attachment 489072 [details] More Info and fstab Attached is fstab, We never used the ro flag for Fedora14 or 11 (same fstab) and they changed to the file system readonly. Setting the ro flag is an acceptable solution , since it was different , we thought it might be a bug. Thanks
So, does it work if you add ro to the flags in fstab? If so I guess I can close the bug?
It does work for us, however setting it to ro in fstab breaks other services like samba. Just wanted to point that it works different from past version. so if you want to close it , its up to you. Thanks for your help.
(In reply to comment #4) > It does work for us, however setting it to ro in fstab breaks other services > like samba. It does? In which way? Can you elaborate? > Just wanted to point that it works different from past version. Yupp, it does. We are trying to get rid of duplicate options though and standardize this across distributions. And I think listing "ro" in fstab is the nicest and most natural way to configure this.
The smb and nmb service don't start because the smb and nmb scripts in /etc/rc.d/init.d are checking to see if /etc/samba/smb.conf is writable. We got smb starting by adding /etc/samba/smb.conf to rwtab. Still working on getting nmb running , it fails with following log errors : [2011/03/31 16:50:38, 0] nmbd/nmbd.c:863(main) nmbd version 3.6.0pre1-64pre1.fc15 started. Copyright Andrew Tridgell and the Samba Team 1992-2010 [2011/03/31 16:50:38.432996, 0] lib/util_sock.c:876(open_socket_in) bind failed on port 137 socket_addr = 192.168.1.14. Error = Cannot assign requested address [2011/03/31 16:50:38.433546, 0] nmbd/nmbd_subnetdb.c:104(make_subnet) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.1.14 for port 137. Error was Cannot assign requested address [2011/03/31 16:50:38.433647, 0] nmbd/nmbd.c:977(main) ERROR: Failed when creating subnet lists. Exiting.
(In reply to comment #6) > The smb and nmb service don't start because the smb and nmb scripts in > /etc/rc.d/init.d are checking to see if /etc/samba/smb.conf is writable. ... That's a bug in that code, not in the readonly root code. I'll file that.
Do you think our nmb startup problem is a bug?, should I open a new bug ? Thanks
OK, then I guess I can close this?
Yes, please file a bug against samba for the "Cannot assign requested address" issue.