This is a discussion on Mounting Zipslack's umsdos filesystem via nfs ? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi - rather a long post, but maybe the details will allow somebody to help me solve my problem... ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi - rather a long post, but maybe the details will allow somebody to help me solve my problem... I'm running Zipslack from Slack Version 10 on 2 PCs and trying to share files between them via NFS. First I found that Zipslack didn't include nfsutils - so I installpkg'd it. Now it seems that the umsdos filesystem that Zipslack uses just isn't mountable via nfs. Has anybody actually done it? And how? Details of my configuration, and what IS working: On PC1 192.168.0.2 - Zipslack is installed on my single hard disk - the C: drive On PC2 192.168.0.3 - Zipslack is installed on my Zip drive - the D: drive. From PC1 I have been able to mount the PC2 C: drive via NFS, so I am confident that I have the basic setup and daemons running OK. On PC2 I first mounted the C: drive at mountpoint /dosc fstab entry is: /dev/hda1 /dosc vfat noexec,umask=022 0 0 Then in /etc/export /dosc *(rw,no_root_squash,sync) Then on PC1 I made a mountpoint /mnt/toshiba And did an NFS mount OK from PC1: mount 192.168.0.3:/dosc /mnt/toshiba This works fine - I can see all the files on PC2's C: drive from PC1 But when I try to anything in the umsdos filesystem I always get an error when I try to mount. Example: mount 192.168.0.3:/usr /mnt/toshiba gives the error mount: 192.168.0.3:/usr failed, reason given by server: Permission denied I have noticed that when I rerun exportfs -vra that /usr doesn't seem to get loaded into the kernel, as I see this message: exporting *:/dosc exporting *:/usr reexporting 192.168.0.2:/dosc to kernel So - any ideas ? |
| |||
| On Sun, 15 Aug 2004 19:21:55 +0100, geep wrote: > Hi - rather a long post, but maybe the details will allow somebody to help > me solve my problem... A fortnight later, along comes /me ... > I'm running Zipslack from Slack Version 10 on 2 PCs and trying to share > files between them via NFS. > First I found that Zipslack didn't include nfsutils - so I installpkg'd it. How about portmap? ZS includes it, but is it enabled and running? > mount: 192.168.0.3:/usr failed, reason given by server: Permission denied And you checked the logs on 192.168.0.3? -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
| ||||
| Thanks for the reply. Since I made the post I installed Slack10 on PC2's hard drive via NFS from PC1's CD. I was able to NFS mount PC1's CD from PC2. (PC2 is an old laptop without a CD). But I still can't NFS mount the UMSDOS filesystem on PC1 from PC2. I am pretty sure that PC1's portmapper is running OK, as NFS to PC1's CD works OK. (Can't check at present - PC1&2 off - several cables need to be moved - it's late - tomorrow...) As I am still interested in knowing if NFS mounting of UMSDOS is possible, which logfiles should I be checking ? (NFS mount of PC2's hard drive from PC1 works fine). (I did find that I was able to use SAMBA to smbmount PC1's UMSDOS filesystem from PC2). |
| Thread Tools | |
| Display Modes | |
|
|