Read only file system !-----Tomato 1.28

Discussion in 'Tomato Firmware' started by jenom, Jul 4, 2012.

  1. jenom

    jenom LI Guru Member

    Just installed Tomato 1.28, enabled and mounted a JFFS2 file system (1024/700)
    Using putty in windows xp, copied a small program into /root/..., also copied there a needed library file.
    However, this small program needs a library file in the /lib/... location, but when I tried to make a symbolic link between the library file in /root/.... to the /lib/.... (ln -sf /root/existing /lib/new), got an error message: Read only file system! ------the /lib is not writable ! :-(
    Is there any way to fix this problem ? remount ? change permission ? different way to create link ?
  2. jyavenard

    jyavenard Network Guru Member

    This is a read-only flash filesystem. You can't unmount it and make it writable.

    If you want to copy something in /lib, you'll have to recreate a new firmware image and reflash your router..

    Having said that, you can configure the path where libraries are looked for by setting an environment variable LD_LIBRARY_PATH, set it to another folder and start the program you want.
  3. koitsu

    koitsu Network Guru Member

    Why did you make a new post about this? I already explained it in your other thread, and for some reason you created this new one. (I'll see if I can track down a forum mod to delete this thread):

    You need to calm down and stop "going crazy" with all of this. Settle down, learn how some of this stuff works, or stick with OpenWRT (there's nothing wrong with that).
  4. jenom

    jenom LI Guru Member

    Thank for the info on LD-LIBRARY_PATH.
    My other post was about the serial port and this post is about Tomato's useless locked read only file system!
    Two topic, two thread, am I right ?
    Gone for now, back to the fully working OpenWRT !
  5. jyavenard

    jyavenard Network Guru Member

    Jeez.. Didn't know we needed some higher authority to police others here...
  6. mvsgeek

    mvsgeek LI Guru Member

    I read this thread because the subject explicitly addresses an issue that I encountered recently. I started reading the other thread despite the fact that the subject wasn't of much interest to me, but quickly gave up when I realised that the content was way over my head.

    I've copied the content of this thread in case it gets deleted, which I hope doesn't happen.
  7. koitsu

    koitsu Network Guru Member

    @jyavenard -- the problem (in my eyes) is that the OP copy-pasted part of an already-existing thread and started a new one for an ""issue"" which really isn't an issue at all. I wanted forum mods to determine if the (new) thread should be deleted or not as the issue was already being discussed in an existing thread.

    Sorry to sound like I'm prejudging, but I see this happen a lot on public forums. There are some folks who will make hundreds of new threads in a very short time, almost like they're hyperactive. It's very hard to control them and get them to settle down / step back and read + learn. I've been here on the Linksysinfo forum for a while (only recently have been posting) and I'm doing my best to help people, but it's very hard when you have someone who literally runs around with their arms flailing as a response, rather than slowing + calming down and spending the time to learn.

    OpenWRT works for him because the current stable branch uses a combination of squashfs and JFFS, where the JFFS partition is overlayed on top of the squashfs partition. Thus from a user perspective, the root filesystem (and pieces underneathe) are writeable.

    However, the trunk/development builds of OpenWRT have switched solely to squashfs. Pick an architecture and see for yourself:

    So the OP is going to get a rude awakening by choosing to think of this "as a bug" when it would benefit him greatly to actually understand the underlying technology/architecture. The next release of OpenWRT will behave the same. :)

    That's the thing about third-party firmwares -- you have to keep up on what's going to change/etc. (meaning there's a degree of responsibility that's required on the part of the user) vs. be rudely surprised when upgrading to the next release.
  8. pharma

    pharma Network Guru Member


    You need to chill. If you take a close look you will see 90% of the threads discuss issues already mentioned in previous threads, with slight variations. Sometimes people open new threads to get different opinions, sometimes the topic is slightly different, etc... Granted it may not be an issue, but at least he received a response from one of the firmware contributors/developers (jyavenard) which is what he may have been seeking - one of the benefits of having an open, public forum.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice