Welcome, Guest. Please login or register.

Author Topic: NFS or Samba and long file names  (Read 893 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline cpfutureTopic starter

  • Full Member
  • ***
  • Join Date: Feb 2006
  • Posts: 246
NFS or Samba and long file names
« on: October 11, 2015, 04:18:33 PM »
Hi,

I'm running WB3.1 on an A500 with an accelerator and an X-Surf network interface and I've used both ch_nfsc (an NFS client) and SMBFS (a Samba client) to access files on my NAS.

Here's the thing: I have PFS3 installed so I have long filename support on my A500. Problem is, ch_nfsc does not seem to support long filenames so any filenames longer than 30-ish characters long that reside on the NFS mount get truncated. I am using the latest version that is on Aminet (1.02).

SMBFS does support long filenames (yay!), but due to its single threaded design it is cumbersome in use. If I'm playing an 8SVX/IFF file off my NAS using SMBFS any other access to the share is delayed for a looooong time. I'm using the version of SMBFS that is available on Aminet.

So my question is this: Is there any NFS or SMB client for 68K Amigas that:

- supports long filenames
- AND doesn't suffer from "single threaded" design

I guess I could use both ch_nfsc and SMBFS depending on what I want to do, but I'd rather just stick to one client.

I read somewhere that ch_nfsc was developed further past the 1.02 beta that is on Aminet right now, but that was only available for the non-GPL'ed 4.x versions of AmiTCP. Anyone know if those versions of ch_nfsc support long filenames?

Thx in advance for any hints, tips or pointers you might have!
:)

Offline cpfutureTopic starter

  • Full Member
  • ***
  • Join Date: Feb 2006
  • Posts: 246
Re: NFS or Samba and long file names
« Reply #1 on: October 11, 2015, 04:33:59 PM »
Replying to my own thread here. The access to the SMBFS share by more than one process isn't that bad after all (after some more experimentation), so I think I can probably live with using SMBFS quite well.

Still, if anyone knows a better solution: I'm all ears :)