Edit /etc/eventmanager and use the right ACCESS_MODE and UMASK_MODE. UMASK_MODE is just 777 xorg ACCESS_MODE (or simply put, UMASK_MODE + ACCESS_MODE must be equal to 777).Barbol wrote:Hi! I'm having difficulties when mounting linux partitions in fatdog. I have a disk with many partitions, some of them containing another OS. Everytime I mount one of them, fatdog changes the permissions of the root directory in that partition to 770. It makes me broke two ubuntu based systems until I realize what was happening. Fortunately, once discovered the cause, the solution was easy, just restoring the permissions. Now I'm doing a chmod before unmounting, but that's not comfortable.. What could be happening and how is it fixable?
There is a GUI for this using Fatdog Event Manager from Control Panel, but it only allows you to choose between two values: 770 and 750. On another note, Fatdog also chgrp the mountpoint to the current user's group. If you really really don't like this and want to disable this, edit /usr/sbin/fatdog-drive-icon-mount-helper.sh but then you're on your own.
Fatdog uses udev directly for drive icons. Whenever gparted runs, it reads the drive in a such a way that forces the kernel to re-read the partition table (=not surprising for a partition table editor...), and thus kernel will issue udev "change" event. Fatdog responds to this change event by re-drawing the icons; unfortunately there is no way to ensure that the events are received in any particular order. Other puppies don't have this issue because they don't use udev directly, they use a daemon (pup_event_frontend) to poll for changes instead.Another annoying thing occurs when running gparted. It tooks the drive icons, passes through a blender and throw them in aleatory order on the desktop. Never noticed that behavior by gparted before..
IndeedGreat 2013 evereyone!!! Barbol