Nope, no help. I gave "other" write permissions for the Volume, all enclosing folders, and the image file itself, but SD behaves the same. Also tried with and without "ignore permissions on this volume" on the fileserver. My user account does own the image, btw.
Interestingly, SD also seems to be reverting the permissions of the image file:
Code:
[p17:/Volumes/LaCieDisk/superduper] trevyn% ls -la
total 224793504
drwxrwxrwx 4 trevyn 501 264 24 Sep 01:27 .
drwxrwxrwt 26 root admin 840 23 Sep 16:55 ..
-rw-rw-r-- 1 trevyn 501 85289406464 24 Sep 05:35 newpb.sparseimage
-rw-rw-r-- 1 trevyn 501 29804843008 24 Sep 10:14 p17.sparseimage
[p17:/Volumes/LaCieDisk/superduper] trevyn% chmod o+w p17.sparseimage
[p17:/Volumes/LaCieDisk/superduper] trevyn% ls -la
total 224793504
drwxrwxrwx 4 trevyn 501 264 24 Sep 01:27 .
drwxrwxrwt 26 root admin 840 23 Sep 16:55 ..
-rw-rw-r-- 1 trevyn 501 85289406464 24 Sep 05:35 newpb.sparseimage
-rw-rw-rw- 1 trevyn 501 29804843008 24 Sep 10:14 p17.sparseimage
(...attempt to run SD...)
[p17:/Volumes/LaCieDisk/superduper] trevyn% ls -la
total 224793504
drwxrwxrwx 4 trevyn 501 264 24 Sep 01:27 .
drwxrwxrwt 26 root admin 840 23 Sep 16:55 ..
-rw-rw-r-- 1 trevyn 501 85289406464 24 Sep 05:35 newpb.sparseimage
-rw-rw-r-- 1 trevyn 501 29804843008 24 Sep 10:14 p17.sparseimage
[p17:/Volumes/LaCieDisk/superduper] trevyn%