mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: April 22 2006,23:45 |
 |
sorry...i typed the wrong path. It's /etc/init.d/mkwriteable. It's not the same as toram, and it's not really documented anywhere. It's automatically run if you install a myDSL package with a *.dsl filename, but can also be run directly by root (sudo /etc/init.d/mkwriteable) or forced to run during boot with the "dsl write" boot option.
What it does is open up the /usr, /bin, and /sbin directories so you can write to them. These directories start off as symlinks to the read-only knoppix filesystem, and the script replaces the symlinks with copies of the original directories. However, most of the files within those directories remain symlinks to the files in /KNOPPIX, so you would need to overwrite the symlinks with copies of the /KNOPPIX/something/* files if you want to modify them. I'm not sure if the firefox files fall into this category. The re-linking of the directories' contents as a replacement for linking the directories themselves is a sort of tradeoff so you can still write, but your ram isn't being sucked up by having the whole decompressed filesystem copied into it.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|