Martin, although you're right about this Unix filesystems nature, hal is now automounting them in a dynamic mountpoint (like /media/disk), and so it is the responsible of assigning the right permissions on that mountpoint. The problem is that the permissions are too strong, so anybody except root couldn't write on the filesystem.
The workaround could be to fix hal so it assigns 777 permissions BY DEFAULT in the mountpoint, so the filesystem have read/write permissions *by default* into the filesystem to anybody. Later, if the sysadmin wants, he could do chmod, chown or even touch the /etc/fstab file if he wants to fine-tune the mount permissions & options, weakening the default permissions.
Martin, although you're right about this Unix filesystems nature, hal is now automounting them in a dynamic mountpoint (like /media/disk), and so it is the responsible of assigning the right permissions on that mountpoint. The problem is that the permissions are too strong, so anybody except root couldn't write on the filesystem.
The workaround could be to fix hal so it assigns 777 permissions BY DEFAULT in the mountpoint, so the filesystem have read/write permissions *by default* into the filesystem to anybody. Later, if the sysadmin wants, he could do chmod, chown or even touch the /etc/fstab file if he wants to fine-tune the mount permissions & options, weakening the default permissions.