Twonky configuration on read-only diskpart
Options
WhizNick
Posts: 2
Freshman Member
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
- 439 Beta Program
- 2.8K Nebula
- 202 Nebula Ideas
- 126 Nebula Status and Incidents
- 6.3K Security
- 514 USG FLEX H Series
- 328 Security Ideas
- 1.7K Switch
- 84 Switch Ideas
- 1.3K Wireless
- 49 Wireless Ideas
- 6.9K Consumer Product
- 288 Service & License
- 458 News and Release
- 90 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 4.3K FAQ
- 34 Documents
- 85 About Community
- 97 Security Highlight
Guru Member