The idea is to have m5 sums associated with each downloadable file, correct?
FreeBSD stores the md5 sums as part of their 'ports' structure so that when a file is downloaded, the md5 sum can be verified to ensure correct download. (including resumed downloads).
Jens Geile wrote:
Take a page out of the FreeBSD ports structure handbook:
In fact, the more I think about it, the more features are added to the current unattended application setup, the more you will be approaching a a binary downloading ports structure siminlar in concept to the FreeBSD ports tree (which I like, doesn't require nasty modifications to core OS system for using on a different platform), or say Gentoo's portage structure (which I don't like, which does nasty things to the poor OS, core OS things should _NOT_ be part of the ports tree, binary patches for Windows yes, entire OS system, _NO_).
Could it be that you totally misunderstood me? I don't get what this last part has to do with "my" idea. >.> I only wanted to check the md5 checksums of the files downloaded with the prepare script to make sure that they didn't get corrupted in case they were resumed with "wget -c".
- jens
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
