ptitSeb: That's not completely right.
A PND itself is read-only. That's true. But it's loop-mounted with an overlay (unfortunately I can't recall the name of that mechanism right now) so any changes you do to the mounted-pnd will be saved to the appdata-folder. So as far as I can tell what F_slim is trying to do SHOULD work.
For example if you use "touch /mnt/utmp/<dir>/<filename>", then that file will be created in the mounted umnt-directory. It will not be stored in the pnd though, but in the appdata-folder. Or if you change rights or ownerships then these changes are not in the pnd, but I THINK will result in copying all changed files to the appdata-folder with their changed parameters. Last example: If you delete a file in /mnt/utmp/<dir>/ then the file will not be deleted in the pnd, but an entry will be stored in the appdata-folder that the next time the pnd will be mounted, this deleted file will not appear in "/mnt/utmp/<dir>".
F_slim: You could try to "cd /mnt/utmp/cdevtools1000/" and do a "touch f_slim-test.txt" and see if it works. Probably it will not for the same reason that prevents you from installing. also try and show the output of "ls -ld /mnt/utmp/cdevtools1000/" and "ls -ld /mnt/utmp/cdevtools1000/*".
For me it looks like this, since "lmx" is my username:
$ ls -ld /mnt/utmp/cdevtools1000/
drwxrwxrwx 9 lmx lmx 4096 Dec 24 15:32 /mnt/utmp/cdevtools1000/
If all these file are owned by "root" instead of your user, then indeed try to copy the pnd to an "linux-native" filesystem and see what it changes.
A PND itself is read-only. That's true. But it's loop-mounted with an overlay (unfortunately I can't recall the name of that mechanism right now) so any changes you do to the mounted-pnd will be saved to the appdata-folder. So as far as I can tell what F_slim is trying to do SHOULD work.
For example if you use "touch /mnt/utmp/<dir>/<filename>", then that file will be created in the mounted umnt-directory. It will not be stored in the pnd though, but in the appdata-folder. Or if you change rights or ownerships then these changes are not in the pnd, but I THINK will result in copying all changed files to the appdata-folder with their changed parameters. Last example: If you delete a file in /mnt/utmp/<dir>/ then the file will not be deleted in the pnd, but an entry will be stored in the appdata-folder that the next time the pnd will be mounted, this deleted file will not appear in "/mnt/utmp/<dir>".
F_slim: You could try to "cd /mnt/utmp/cdevtools1000/" and do a "touch f_slim-test.txt" and see if it works. Probably it will not for the same reason that prevents you from installing. also try and show the output of "ls -ld /mnt/utmp/cdevtools1000/" and "ls -ld /mnt/utmp/cdevtools1000/*".
For me it looks like this, since "lmx" is my username:
$ ls -ld /mnt/utmp/cdevtools1000/
drwxrwxrwx 9 lmx lmx 4096 Dec 24 15:32 /mnt/utmp/cdevtools1000/
Code:
$ ls -ld /mnt/utmp/cdevtools1000/*
-rwxr-xr-x 1 lmx lmx 2341 Sep 28 23:43 /mnt/utmp/cdevtools1000/PXML.xml
-rw-r--r-- 1 lmx lmx 538 Oct 28 13:56 /mnt/utmp/cdevtools1000/Trolltech.conf
-rw-r--r-- 1 lmx lmx 47661 Sep 13 07:16 /mnt/utmp/cdevtools1000/cdevtools.jpg
-rw-r--r-- 1 lmx lmx 4156 Sep 13 07:17 /mnt/utmp/cdevtools1000/cdevtools.png
drwxr-xr-x 3 lmx lmx 55 Sep 6 12:17 /mnt/utmp/cdevtools1000/etc
drwxr-xr-x 2 lmx lmx 4096 Sep 30 18:47 /mnt/utmp/cdevtools1000/init
drwxr-xr-x 2 lmx lmx 26 Sep 5 08:46 /mnt/utmp/cdevtools1000/lib
-rw-r--r-- 1 lmx lmx 7777 Sep 28 23:30 /mnt/utmp/cdevtools1000/readme.txt
-rwxr-xr-x 1 lmx lmx 50 Sep 11 07:23 /mnt/utmp/cdevtools1000/start.sh
drwxr-xr-x 8 lmx lmx 4096 Sep 10 16:39 /mnt/utmp/cdevtools1000/usr
If all these file are owned by "root" instead of your user, then indeed try to copy the pnd to an "linux-native" filesystem and see what it changes.
Last edited by a moderator: