LinuxQuestions.org - Kernel 2.6 sharing USB disk via NFS

I've got an external disk mounted on /media/usb-storage-YA42H1MWE:0:0:0P1

I want to share this with another linux box (This disk is also plugged in to a Windows box sometimes -- it's a removable 250 GB USB disk so that's why it's got a FAT32 file system on it.).

Mount shows it's also on /dev/sda1 and it's a FAT32 file system.

I've also mounted on /sda1 on /media/extdisk type vfat and exported the directory OK

On the client side I can access the disk but whatever file permissions I give the directory I can only get READ access unless I'm Root.

2 Boxes Server greyfox @ 192.168.7.2
Client blackdog @ 192.168.7.3

Here's the status on the client side

jim@blackdog:~> mount
/dev/hda8 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/hda2 on /windows/C type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf8)
/dev/hda5 on /windows/D type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf8)
/dev/hda6 on /windows/E type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf8)
/dev/hda7 on /windows/F type ntfs (ro,noexec,nosuid,nodev,gid=100,umask=0002,nls=utf8)
/dev/hdc on /media/dvdrecorder type subfs (ro,nosuid,nodev,fs=cdfss,procuid,iocharset=utf8)
usbfs on /proc/bus/usb type usbfs (rw)
greyfox.site:/home/jim on /mnt/desktop type nfs (rw,addr=192.168.7.2)
greyfox.site:/media/extdisk on /mnt/linuxmaxtor type nfs (rw,addr=192.168.7.2)
greyfox.site:/home/jim on /mnt/jimsdesktop type nfs (rw,addr=192.168.7.2)
jim@blackdog:~>

The entry /media/extdisk shows clearly that the disk is READ WRITABLE -- so how do I get WRITE permission for a user rather than root.

Thanks

The Network aspect seems fine to me -- but I'm having real problems sorting out File access permissions.

I thought I'd be stuck the other way round. I'm using SUSE 9.1 on both boxes.

( I wonder if it has anything to do with the way hotplug USB is implemented -- there was a similar problem with using a Scanner as a normal USER -- there was a get around for that --but YOU (online update) has fixed it).