User Feedback :: File Editing



Quote
but the system that was chosen for knoppix and DSL, called "cramfs" does not support writing.


As far as I was aware, Knoppix and derivatives use cloop, or is that the same thing?

You are correct.

cloop is not the same as cramfs.

My bad.

They both do similar things in similar ways, but cloop seems to result in a higher compression ratio.

Sorry about that.

cbagger01,

I've run into more read only troubles despite the kindness of your instructions above. I boot up, configure the network with the supplied tool, enter "Enable Apt" and, sure enough there I see usr -> /ramdisk/usr in / as you'd mentioned. Trying to edit a style file in /ramdisk/usr/share/fluxbox/styles still brings read only objections though. What's wrong here, I don't get it.

jlowell

(1) You may need to be the 'root' superuser in order to be able to overwrite the symlink when you do your file save.

(2) Your program may try to follow the link back to it's ultimate target in the /KNOPPIX/usr directory.  To solve this, do the following:

Load your file into an editor.
While keeping the editor open, use emelfm or "sudo emelfm" to delete the /usr/share/fluxbox/styles symlink.
Then try and save the file.

Or you can do this:
Type 'sudo emelfm' to launch emelfm as 'root' user.
In the LEFT window pane, navigate over to the /KNOPPIX/usr/fluxbox/styles directory.
In the RIGHT window pane, navigate over to the /ramdisk/usr/fluxbox/styles directory.
Then DELETE the symlinks for the desired files in the RIGHT pane.
Go into the LEFT pane and highlight the desired files.
Click on the "copy" button in emelfm.  Real copies of these files will appear in the ramdisk directory.  You can then edit and save these files as you wish.

Keep in mind that the correct way to save an edited Fluxbox Style is to save it in the /home/dsl/.fluxbox/styles  directory instead of the /usr directory.

Read the whitebox.dsl info file for more details.  It is located in the mydsl testing area.

cbagger01,

OK, cbagger, mystery solved! :-)

The trick was learning that the files in /ramdisk were linked back to the same files in /KNOPPIX. Then it was simply a matter of removing the /ramdisk version of the file then copying back to the parent directory that same file in it's /KNOPPIX version. Pretty standard stuff. Being so new, I'd never have known about the connection of /ramdisk back to /KNOPPIX if you hadn't pointed it out to me. So the deed is done, style file edited. Thanks.

jlowell

Next Page...
original here.