openbox - can't modify theme or menu

[gandouet]

HI from France

i'm new here and i've tested this rc
i made a fresh install on usb stick with unetbootin
here is my boot option

label ubnentry0
menu label tinycore
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tce=sdb1 home=sdb2 opt=sdb2 waitusb=5 max_loop=255

sdb1 is fat32 , sdb2 is ext2

problem : i mount openbox extension and it runs fine (directly without specifying cheat code)

but i cannot modify theme or menu as rc.xml autorun.sh or menu.xml are declared read only

i saw this was fixed in past release what is the status now?? or do i make a mistake??

[bmarkus]

HI from France

i'm new here and i've tested this rc
i made a fresh install on usb stick with unetbootin
here is my boot option

label ubnentry0
menu label tinycore
kernel /boot/bzImage
append initrd=/boot/tinycore.gz quiet tce=sdb1 home=sdb2 opt=sdb2 waitusb=5 max_loop=255

sdb1 is fat32 , sdb2 is ext2

problem : i mount openbox extension and it runs fine (directly without specifying cheat code)

but i cannot modify theme or menu as rc.xml autorun.sh or menu.xml are declared read only

i saw this was fixed in past release what is the status now?? or do i make a mistake??

Can you write your home directory as user tc? I guess /mnt/sdb2 is writable by root only as well as /home/tc.

[gandouet]

Hi Marcus
Sorry for the delay in the answer

After tests yes i can write in /home/tc as tc user
i can write in .config folder and other subfolders (including openbox)

but i cannot modify the xml files (rc and menu also autostart)
it says always read only file system

the extension is mounted not installed is it coming from there?

[bmarkus]

but i cannot modify the xml files (rc and menu also autostart)
it says always read only file system

the extension is mounted not installed is it coming from there?

These files in /usr/local/etc/xdg/openbox are symlinked to the loop mounted erad-only original, tehrefore you can't write them. Temporary solution to install it, which means tehse fiels will be copied to RAM and writeble.

The proper solution is to change the extension and always copy these files to RAM instead of symlinking to make them writable independently of installation type.

[althalus]

You could also just remove the symlink and copy in the file that the link was pointing to.