Re: [rox-users] ROX-Filer, NFS and .DirIcon problem

[thilo <th...@th...>]

Thanks for the reply. Unfortunately, my situation is different,
since neither directory nor .DirIcon are world writeable (but
user- and group-writeable). The problem persists (on the NFS
share): as soon as I change the ownership of directory or
.DirIcon to another user (privileged or not), ROX stops
displaying the .DirIcon as the folder icon.

Setting the folder icons in another way is not an option, as i
would like them to be available to any client mounting the NFS
share. Also, the icons in question are album covers for my
music collection, which I would like the upnp server to deliver
on a per directory basis. Thus, I thought both ROX and the
upnp server could both use the .DirIcons.

Regards,
Thilo Ernst

On Sun, Oct 21, 2012 at 08:58:46PM -0500, Laverne Schrock wrote:
>    I think that you're not quite correct. I've been doing some playing around
>    on my TinyCore Linux box and it doesn't seem to be an issue
>    with readability, but rather an issue of writebility.  
>    If the directory is world-writable then the .DirIcon isn't used, but the
>    world-write privilege on the .DirIcon doesn't matter. 
>    On my machine, if I'm a non-privileged user and the Directory and .DirIcon
>    are both owned by root and universally readable; then everything is fine.
>    As soon as the directory is world-writable then the default icon is
>    displayed instead of the custom one. It doesn't matter if the .DirIcon
>    file is world-writable as long as the directory isn't.
>    Is this info helpful?
>    It seems to be some sort of security feature. The side effect is that you
>    can't have AppDir or use .DirIcon on a drive that has a format that
>    doesn't support file permissions. (e.g. NTFS )
>    Here is a link to the section in the ROX-Filer manual that contains
>    information for a possible
>    workaround: http://rox.sourceforge.net/Manual/Manual/Manual.html#id2507256
>    Cheers,
>    Lvern