I am experimenting with using uftp/uftpd to multicast Linux disk images from one machine to a whole room of other machines. I created the image with "dd" under Linux. I was able to make this work, but have a few suggestions.
1) On the server, I had to call the image "sda". On the client, I had to use "-D /dev". This way, the server could write to /dev/sda on the client. It would be useful if on the server I could call the image whatever I want, and be able to have the server pass a name to the client. Looking at the man page again, it's possible this may already be possible by using -D /dev/sda on the server? This may allow me to call the image on the server whatever I want and pass no -D option to the client.
2) The clients all failed immediately because /dev is on a ramdisk which doesn't have enough "space" to write. Of course /dev doesn't have enough space, but /dev/sda does. It would be nice if the client had an option to disable the space check. I just removed the line of code, and it worked great, but now I'll have to do that every time there's a new release.
3) When the client failed above, it removed the block device /dev/sda. Under normal circumstances when working with a file, this might be fine, but when working with a device, it doesn't make sense. Rather than add device support to uftp, it would be nice if there was an option to tell the client not to remove failed files.
Thanks for making this great software available. It saved me a whole lot of time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
I am experimenting with using uftp/uftpd to multicast Linux disk images from one machine to a whole room of other machines. I created the image with "dd" under Linux. I was able to make this work, but have a few suggestions.
1) On the server, I had to call the image "sda". On the client, I had to use "-D /dev". This way, the server could write to /dev/sda on the client. It would be useful if on the server I could call the image whatever I want, and be able to have the server pass a name to the client. Looking at the man page again, it's possible this may already be possible by using -D /dev/sda on the server? This may allow me to call the image on the server whatever I want and pass no -D option to the client.
2) The clients all failed immediately because /dev is on a ramdisk which doesn't have enough "space" to write. Of course /dev doesn't have enough space, but /dev/sda does. It would be nice if the client had an option to disable the space check. I just removed the line of code, and it worked great, but now I'll have to do that every time there's a new release.
3) When the client failed above, it removed the block device /dev/sda. Under normal circumstances when working with a file, this might be fine, but when working with a device, it doesn't make sense. Rather than add device support to uftp, it would be nice if there was an option to tell the client not to remove failed files.
Thanks for making this great software available. It saved me a whole lot of time.