Twonky configuration on read-only diskpart
Options
WhizNick
Posts: 2 Freshman Member
Hi,
I want to change the view-definitions.xml file of Twonky media server, which I could in the past. However after the latest firmware upgrade or because of a new install after a disk upgrade, it's on a read-only file system. Direct editing or copying back and forth is not allowed now. How can I make it read/write or in another way configure Twonky?
#NAS_Feb_2020
I want to change the view-definitions.xml file of Twonky media server, which I could in the past. However after the latest firmware upgrade or because of a new install after a disk upgrade, it's on a read-only file system. Direct editing or copying back and forth is not allowed now. How can I make it read/write or in another way configure Twonky?
#NAS_Feb_2020
0
Accepted Solution
-
You have 2 options. You can bindmount a writable file on that file:<code>mount --bind /path/to/rw-location/view-definitions.xml /path/to/ro-location/view-definitions.xml</code>A problem here is that, I think, you'll have to restart twonky to get it read. Maybe sending a HUP signal will do.Or you can remount the ro partition readwrite.<code>mount -o remount,rw /firmware/mnt/sysdisktouch /firmware/mnt/sysdisk/mount.sda1.rw.flagreboot</code>After a reboot the /usr/ tree will be rw. This will last until you remove the mount.sda1.rw.flag file and reboot. You must remove the file before attempting a firmware update, as it blocks proper update.A problem could be that the read-onlyness of the /usr tree can hide bugs. I think the major part of the ZyXEL specific files in /usr/ are not really tested on an rw filesystem.
0
All Replies
-
You have 2 options. You can bindmount a writable file on that file:<code>mount --bind /path/to/rw-location/view-definitions.xml /path/to/ro-location/view-definitions.xml</code>A problem here is that, I think, you'll have to restart twonky to get it read. Maybe sending a HUP signal will do.Or you can remount the ro partition readwrite.<code>mount -o remount,rw /firmware/mnt/sysdisktouch /firmware/mnt/sysdisk/mount.sda1.rw.flagreboot</code>After a reboot the /usr/ tree will be rw. This will last until you remove the mount.sda1.rw.flag file and reboot. You must remove the file before attempting a firmware update, as it blocks proper update.A problem could be that the read-onlyness of the /usr tree can hide bugs. I think the major part of the ZyXEL specific files in /usr/ are not really tested on an rw filesystem.
0 -
Thank you very much, Mijzelf!!
Sorry for the late reply, I only saw your quick answer yesterday.
I tried the bindmount option and that seemed to work nicely.0
Categories
- All Categories
- 383 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 80 Nebula Status and Incidents
- 5.1K Security
- 76 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 907 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 209 Service & License
- 335 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 894 Nebula FAQ
- 415 Security FAQ
- 233 Switch FAQ
- 205 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 73 About Community
- 62 Security Highlight