Mbbrutman wrote on, 00:14: The performance difference has an easy explanation. (And thanks for the report on the typo!) Reply 76 of 140, by konc But NetDrive should be more than adequate on a local area network. In general, FTP is always going to be faster, and it's going to be a lot faster across long distances. (This is a feature of the TCP sliding window.) I can't really do that here because you need to wait for reads to arrive and you don't want to send the next read or write without knowing if the previous write is done. Also, because FTP uses TCP it does not need to wait for the other side to acknowledge a packet before proceeding to send the next packet. The most I can send in a UDP packet is two 512 byte sectors (1024 bytes) while FTP can send about 1460 bytes in a packet. The performance difference has an easy explanation. What size is the image you're copying to? I think the directions mentioned something about certain sizes working better than others for efficiency/mapping purposes. (There is a small typo you might want to correct in some subsequent release, the output text of "netdrive serve help" lists the default port as 2022 instead of 2002) It doesn't really matter as I understand NetDrive isn't meant to replace FTP for simple file transfers but to cover edge cases and different scenarios, I'm just wondering. Is it normal that transfer speed is much slower with NetDrive than with FTP? ~300KB/s vs ~500KB/s on a 386-40 with a 10Mbps NIC. Although WinImage seems to ignore them when extracting files from the image, but that has nothing to do with NetDrive of course. A big plus is that it preserves file attributes, which I believe you cannot do with FTP. My use case is mostly creating drive backups into a single image file that's easy to update. Konc wrote on, 08:35: Excellent work again mbbrutman, thank you! Įxcellent work again mbbrutman, thank you! Next I'll export it via samba so I can just load whatever I want onto it from a workstation, and will probably setup multiple disk images based on what they contain. It's probably a really bad idea to try and write to it from the MS-DOS system while you're doing this but I like to live dangerously. I connect to it from my MS-DOS machine via: I can now navigate directly into my drive0.img at /mnt/dos0 and add/remove/manage whatever I need to like any other local filesystem. (this will return something like /dev/md0 - use that in the next steps) I haven't picked a good place yet so it's all in root's home directory (boo! hiss!)Īttach a "memory disk" (although really we're just mounting the hard drive image I just made) Go to the directory where you'll be storing your disk images. Here's how I did it - steps are probably very similar in Linux but using different programs/commands.įirst, I had to enable linux compatibility. I setup my FreeBSD server to mount my drive images into its local filesystem so it's easy to add stuff to them. I posted this over on VCFED ( … 03/post-1354721) copying it here:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |