I can concur with Kai Blin re: the ls command parsing behaviour in smbclient. I tested the smbclient ls command on a working Hardy system against the same IOmega NAS that is giving me problems (under Intrepid) and it produces the same results, so I don't think that it is related to the ERRHRD -39 problem.
All I know about the embedded server in the IOmega NAS is that it is some kind of linux server. The embedded linux on the NAS also handles some other "slight of hand" such as transparently breaking files larger than 4 GB into smaller pieces. It does this because it only will work as a NAS if its hard drive is formatted as FAT32. IOmega claims that FAT32 gives it the broadest range of compatability since Windows, Mac OS and Linux/Unix can all read and write that format. The NAS also has a local USB2 port, as well as a 10/100 ethernet port, so the embedded linux must have a fairly complete communication suite. Thierry, would it help if I set my NAS up in a DMZ off my router so that it is exposed to the great unwashed internet? Maybe you would be able to test against it then? I'd have to experiment a bit to see what IP address it would end up with so you could access it via smb, but 'm willing to give it a try. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
