On 11/21/2013 08:12 PM, Phil Blundell wrote:
On Thu, 2013-11-21 at 00:59 -0600, Mark Hatle wrote:
+# When using a read-only rootfs additional setup may be required
+# uncomment the following line to make bind start in read-only rootfs
+#ALLOW_ROOTFS_READ_ONLY="yes"
If the filesystem is read-only then it's going to be fairly difficult
for the user to uncomment this line on the target.
Hi Phil,
I think the user can remount it read-write or just do it at rootfs time.
Why would you ever want this variable to be set to anything other than
"yes"? If your filesystem is not in fact read-only then it isn't going
to have any effect, and if your filesystem is read-only then bind won't
work without it.
The purpose is to disable bind in a read-only file system by default.
But if user really wants it, they can set this value to 'yes'.
++ [ `is_on_read_only_partition /etc/bind` = "yes" ] && bind_mount
/var/volatile/bind/etc /etc/bind
++ [ `is_on_read_only_partition /var/named` = "yes" ] && bind_mount
/var/volatile/bind/named /var/named
Is it really necessary to mount a tmpfs at /etc/bind? Can't those files
just be relocated somewhere else?
I'm afraid not. At least I don't know how.
Best Regards,
Chen Qi
p.
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
