Why is /usr/pbi Read-Only?

[Azlan]

So, I am ecstatically about pfSense 2.1 because it includes my favorite VPN daemon, tinc, in the package manager.
The configuration is fairly straight forward, quite similar to the linux version, but i cant get it to work.
Then i decide to try some troubleshooting in shell:

[2.1-RELEASE][admin@pfSense.localdomain]/root(22): tincd -D -d5
Cannot open config file /usr/pbi/tinc-amd64/etc/tinc/tinc.conf: No such file or directory
Failed to read `/usr/pbi/tinc-amd64/etc/tinc/tinc.conf': No such file or directory

[2.1-RELEASE][admin@pfSense.localdomain]/root(23): find / -name tinc.conf
/usr/local/etc/tinc/tinc.conf

[2.1-RELEASE][admin@pfSense.localdomain]/root(24): ln -s /usr/local/etc/tinc /usr/pbi/tinc-amd64/etc/
ln: /usr/pbi/tinc-amd64/etc//tinc: Read-only file system

[2.1-RELEASE][admin@pfSense.localdomain]/root(25): wha??

Ok, so it turns out that /usr/pbi is read-only, and im sure its for a good reason.
the command tincd -D -d5 allows me to see debug output.

is there any way i can the configuration file "tinc.conf" into the location that it wants so i can do troubleshooting?

[Azlan]

i found my answer!

https://doc.pfsense.org/index.php/Remount_embedded_filesystem_as_read-write