How to make Write File System?
At least in a directory/www/
The administrator-panel would be desirable to Russify.
i have de same probleme to write a file index.php in /www/
root@WRT-N:/www# touch index.php touch: index.php: Read-only file system
First of all, let's try to figure out what might be the actual goal here, shall we? ;) I can think about a few possibly-related alternatives, each with their own set of advantages and/or caveats (see notes bellow):
PROS: when you're done with your changes, you're done - already flashed onto your device ;)
CONS: needless to say, each build/flash/test cycle can take quite a while to complete… not to mention there's lots of things that could go wrong such as (but not limited to) breaking the entire webUI because of a simple/single typo that got left behind on some page/script and even bricking your router (in fact, those things happened to me countless times in the past… until I eventually learned about some alternatives)
PROS: it's an easy, fast and quick way to validate/verify small changes, run some tests and/or simply include new files/contents being served by the webserver on your router (only cost is the amount of RAM taken by your files, since /var and /tmp are actually non-persisent ramfs mounts)
CONS: noticed that extra '/ext/' in the URL? This means basically two things: (1) your 'original' www contents can still be accessed via their original/regular URLs, but (2) sometimes that could be a problem, specially when/if we have references to any js/css/cgi (and those might be found under /, not under /ext). Also, just like the suggestions below, any changes you make won't be persisent across reboots (which can actually be a good thing, depending on what you're trying to do/accomplish).
PROS: you can actually replace the entire www tree and run your tests… if make a mistake and cannot get your web interface to render due to a typo, you could just reboot your router and everything returns to normal. Also, if you have a device with an USB port… you could use an external hard-or-flash-drive to store your www root (and even restart httpd automagically with your new/updated contents with just a few scripts)
CONS: you should be careful about killing/restarting the httpd process (more specifically, what is the 'current' PATH when firing it up)
PROS: you can use/try different sets of httpd versions/binaries, different www roots, etc…
CONS: same as above
Hope this helps ;)
Well the "goal" in my situation is to stop the cifs client in insisting on a username/password.
I have a NAS that runs without username/password and that I want to keep that way. So maybe it is not secure, but it is good enough for me, and I should have the choice if I want to use usernames/passwords with my fileshares. Unfortunately whoever wrote /www/admin-cifs.asp included a line
if ((!v_length(user, quiet, 1)) || (!v_length(pass, quiet, 1))) return 0;
and I'm quite convinced that all it would take to fix this problem is to comment out this line. Easy done, but can't save it.
Followed a suggestion on another forum to run the command "mount -n -o remount,rw /" but it doesn't change anything.
Please offer a solution, thanks.
I tried method 2, but it gives me Error 500 read error. I chmod the wwwext to 777 it still says read error. :(