Is there a network filesystem which was designed specifically for AmigaOS? Which will work on AmigaOS4?
I seem to recall there was one a long time ago, but I don't know what it was called, nor whether it works on AmigaOS4...
Note that SMB(FS) & FTP(Mount) are not designed for AmigaOS (as they do not support Amiga file comments, nor file protection bits, etc) so they are not what I am looking for.
Yes, there is. Envoy. Version 3 (or better 3.1) works here and is my main network setup for *all* my AmigaOS and MorphOS systems. Fast, easy, transparent. I use SMB only if I have to (i.e. transfering files to Windows PC). Sad thing is that it only can be obtained as a used copy (f.ex. eBay).
Yes, there is. Envoy. Version 3 (or better 3.1) works here and is my main network setup for *all* my AmigaOS and MorphOS systems. Fast, easy, transparent. I use SMB only if I have to (i.e. transfering files to Windows PC). Sad thing is that it only can be obtained as a used copy (f.ex. eBay).
where does one obtain a copy? is it still commercially available?
NetFS looks like it might be suitable, and IntuitionBase lists it as fully compatible... Looks a little fiddly to set-up, but probably not as bad as Samba!
EDIT: I can't get it to work, and the error message isn't very helpful :( . But I',m no expert on configuring TCP/IP stack for servers.
ChrisH wrote: NetFS looks like it might be suitable, and IntuitionBase lists it as fully compatible... Looks a little fiddly to set-up, but probably not as bad as Samba!
Definitely not. It's really easy, in fact. I'm using it between all my Amigas (except the Sam460ex, where for some reason I can't make the client side work).
Quote:
EDIT: I can't get it to work, and the error message isn't very helpful :( . But I',m no expert on configuring TCP/IP stack for servers.
Tell us what the "not helpful" error message says, and what you have done to set it up.
I used Envoy for a while. I had my A1500 sharing out files to my A1200 and A600. It worked quite well but I don't think Envoy plays nicely with other TCP/IP stacks. I should look into it again...!
No - the last maintainer was Heinz Wrobel and it is sadly not available anymore. But - as I already mentioned - there are good chances to obtain a copy from the usual secand hand places. I got my two CDs from ebay.
@Spirantho
It plays very nice beneath Roadshow or Genesis, never got any problem with this. It is my everyday network filesystem since years.
(Of course "serverIPaddress" is actually the real IP address.)
Buf if the server is activated, then it gives a different error message, suggestting it is getting further: Quote:
> netmount serverIPaddress Data_ Data2 can't receive data from server, errno 0
("Data_" is the device name of a partition on the server, although I also tried the volume name "Data" without any change. "Data2" is an unused name on the client, since it also has a "Data_" partition.)
As far as "what you have done to set it up", I tried to follow the installation instructions, but it assumes AmiTCP so I had to try to adapt it to RoadShow:
On the client & server I added "2500, tcp, amiganetfs" to Services in Sys:Prefs/Internet. And on the server I added "Yes, amiganetfs, Stream, No, Sys:C/netfs-server" to Servers.
To keep it simple I installed all files on both machines. So on both client & server I installed "netfs-server" to Sys:C, and "netfs-handler" to Sys:L . I also installed "netmount" to somewhere in the command path.
Buf if the server is activated, then it gives a different error message, suggestting it is getting further: Quote:
> netmount serverIPaddress Data_ Data2 can't receive data from server, errno 0
("Data_" is the device name of a partition on the server, although I also tried the volume name "Data" without any change. "Data2" is an unused name on the client, since it also has a "Data_" partition.)
You should add the colons to the volume/device names, like so: "netmount servername_or_ip Data_: Data2:". At least I always do that, and I think it is required. As for the server_name_or_ip parameter above, using an IP address is probably fine, but I always maintain host names of my machines in all their hosts files, so I can refer to them by name, also in the netmount command. I's just a matter of convenience, as I wrote, it should work fine with the IP address as well.
Quote:
As far as "what you have done to set it up", I tried to follow the installation instructions, but it assumes AmiTCP so I had to try to adapt it to RoadShow:
On the client & server I added "2500, tcp, amiganetfs" to Services in Sys:Prefs/Internet. And on the server I added "Yes, amiganetfs, Stream, No, Sys:C/netfs-server" to Servers.
I believe the usual place for such a server is somewhere in Devs; personally I have created Devs/Servers and put it there. But again, that should not make a difference to whether it actually works.
Quote:
To keep it simple I installed all files on both machines. So on both client & server I installed "netfs-server" to Sys:C, and "netfs-handler" to Sys:L . I also installed "netmount" to somewhere in the command path.
Sounds fine to me. I have the server configured in Prefs/Internet, Servers page, on all my machines; that way, I can always on one machine decide to netmount a drive on one of the others.
So, the main thing I found was the missing colons mentioned above; try adding those and let's see if that takes care of it.
Understandable and informative error messages are not a core feature of AmigaNetFS ...
BTW, I have changed the port number from 2500 to somehing else on all my machines (no, I'm not telling to what ). This protects (a bit) from prying eyes when at events etc.
ChrisH wrote: @nbache I found the problem - somehow "netfs-server" was missing the Executable flag! So it now appears to work (untested how well it works).
Great! Sometimes solutions are simpler than we imagine .
Quote:
The missing colons seem to make no difference.
Right, re-checking the manual I can see that they are not required. I should probably get used to that and save a couple of keystrokes each time.
Quote:
One problem was that NetMount appears to expect netfs-handle to be in AmiTCP:L, so I have to use the HANDLE keyword to tell it to use L: instead.
This is strange. I don't use HANDLE in my netmount commands, and I don't have any AmiTCP: assign, but only L:, in which netfs-handler is located. Maybe NetFS056 was coded to be backwards compatible with the earlier use of L:. At least, it works fine here.
Quote:
You mean you put a server executable in Devs?!?
Yes, that's where it makes the most sense to me. Not in Devs itself, of course, but in a subdirectory called Servers. Guess it's partly a matter of taste.
BTW, I just remembered one of the things that don't work: You cannot edit a file with NotePad on the remote machine. Using CygnusEd works fine.
I think the problem is related to the packet types which have not been implemented (as stated in the NetFS docs), at least the error message is about an unknown packet request type.
It would be great to get access to the source code of AmigaNetFS, partly for an OS4 port, partly to solve issues like these, and maybe work on improvements to security etc. in general.
The last maintainer was/is Heinz Wrobel - who sometimes still helps poor peole like me to use Envoy with OS4.1. It was sold by Schatztruhe AFAIK. Envoy was the "official" network file system marketed by Commodore for their Amiga range systems. But who actually *owns* Envoy - I don't know. Maybe Heinz knows...
@cha05e90 Not sure, but I think it may be different: Quote:
now after more than 13 years of no development, the sources of ch_nfs are finally released under the GPL with the full permission of its initial author "Carsten Heyl". Also renamed the project to "aNFS" to make it easier to distinguish between the old AmiTCP based ch_nfs and the new general Amiga oriented NFS client. And hopefully we will be able to get the sources compiled quickly again so that development can continue and we may even move the NFS client forward to be compatible to NFSv3 or even NFSv4 in future. Let it roll! :)
The last maintainer was/is Heinz Wrobel - who sometimes still helps poor peole like me to use Envoy with OS4.1. It was sold by Schatztruhe AFAIK. Envoy was the "official" network file system marketed by Commodore for their Amiga range systems. But who actually *owns* Envoy - I don't know. Maybe Heinz knows...
Anybody - how does one get in touch with Heinz Wrobel?
Is AmigaNetFS the same thing as (or at least similar to?) this Amiga NFS thing that is available on sourceforge or are they entirely different things?
No, they are not the same.
The Sourceforge project is for the Amiga port of the "real" NFS with Unix origins, whch on AmigaOS was originally called ch_NFS and came with (or at least was made for) AmiTCP.
NetFS or AmigaNetFS is AFAIK coded from scratch, and implements a much simpler and more Amiga-ish solution to the same basic problem: Mounting stuff on another machine as if it was in a local filesystem. It was written by Timo Rossi, who in the latest version's doc file mentioned that the source code might be available at some point in time. But this was back in the nineties, and I haven't heard anything about it since. I haven't done anything to research it either, though.
Anybody know the whereabouts of Timo Rossi and/or the source code to AmigaNetFS?
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
). This protects (a bit) from prying eyes when at events etc.
.
