Why does the Unix file type of /root/.icons/ROX differ between FD64-v903 and earlier versions? [Solved]

[tatemono]

The command 'file /root/.icons/ROX' displays '/root/.icons/ROX: symbolic link to /usr/local/apps/ROX-Filer-jun7/ROX' in FD64-v902 or earlier. However, that command displays '/root/.icons/ROX: directory' in FD64-v903. I would like to know why the change made.

[jamesbond]

With the old symlink model (902 and before), if you want to add/replace MIME icons, you will have to update /usr/local/apps/ROX-Filer-jun7/ROX/MIME (because of the symlink).

After the change (903 onwards), ROX will use icons in /root/.icons/ROX/MIME if they exist, if not, it will still fallback and use icons in /usr/local/apps/ROX-Filer-jun7/ROX/MIME.

Are you having an issue because of the change?

[tatemono]

Are you having an issue because of the change?

No, I am not having any issues because of the change. I am just curious about it. Thank you, @jamesbond, for the explanation.

[jamesbond]

Ok, glad to hear that.

To make it clear, the /root/.icons/ROX symlink is created by ROX-Filer itself when it was run, if there is nothing else already exists (hence if you check 902 basesfs, you will not find the symlink there). We pre-created the directory /root/.icons/ROX and include that in 903 basesfs, to prevent the automatic creation of this symlink; and thus enable the per-user ROX MIME icons (as explained before).

If you're using a savefile/savedir from older Fatdog, that symlink would probably is already exist in your savefile/savedir and it will override the directory that exists in the basesfs, so you wouldn't even notice that things have changed. If you want to make use of the change then you need to delete the symlink in the savefile/savedir as follows:

Code: Select all

# rm /aufs/pup_save/root/.icons/ROX
# aufs_reval