Digital Parasite
06-22-2003, 08:14 AM
With Phase I, it was easy because you just dumped the structures you had finished on a disk/CD/USB key and the client could continue on. But with Phase II, you have to take all the files, upload the results and then bring back the new filelist.txt file to continue. Since my Internet machines are in a different location that means I can't continue until I bring the updated filelist.txt back the following day and will lose a night's work.
I have a couple of suggestions for improving the current method of sneaker netting that will allow you to keep your anti-modification technology in the filelist.txt file. Is there any way you could consider adding one/both or some derivative of this to the next/future release?
1. Have a -sneakerflush or similar switch that would update the filelist.txt file as if a successful upload had just completed and wipe all unecessary "uploaded" files. The idea is that I would copy all the necessary files to my removable media (like the current sneaker net method), run this switch, and then restart my DF client so it could continue. Then I sneaker net the disk to my Internet machine and upload the results after which I can just ignore the files left over since they are no longer needed.
2. Similar to 1 above, but when you used -sneakerupload it would copy the necessary files to an upload/ directory first, then update the filelist.txt like above and delete any uncessary files. That way the sneaker netter could just copy the files from the upload/ directory to disk, get the client to continue on, and bring the disk to an Internet machine at their leisure.
These features would be REALLY helpful for dealing with 10 offline machines.
Jeff.
I have a couple of suggestions for improving the current method of sneaker netting that will allow you to keep your anti-modification technology in the filelist.txt file. Is there any way you could consider adding one/both or some derivative of this to the next/future release?
1. Have a -sneakerflush or similar switch that would update the filelist.txt file as if a successful upload had just completed and wipe all unecessary "uploaded" files. The idea is that I would copy all the necessary files to my removable media (like the current sneaker net method), run this switch, and then restart my DF client so it could continue. Then I sneaker net the disk to my Internet machine and upload the results after which I can just ignore the files left over since they are no longer needed.
2. Similar to 1 above, but when you used -sneakerupload it would copy the necessary files to an upload/ directory first, then update the filelist.txt like above and delete any uncessary files. That way the sneaker netter could just copy the files from the upload/ directory to disk, get the client to continue on, and bring the disk to an Internet machine at their leisure.
These features would be REALLY helpful for dealing with 10 offline machines.
Jeff.