brace yourself : I am about to "over-communicate" :-P
> We chose not to include the md5 sums of the unzipped files, because we
> figured that the zip format's built-in checksum would be adequate to make
> sure the files are properly uncompressed. unzip won't leave a broken
> uncompressed file around.
>
> We could include the unzipped md5 values as well, but I'm not sure how it
> would be useful since the unzipped chunks are only intermediate files
> anyway. Once combined into the single DVD image, the md5 for the DVD ISO
> image can be used to validate the image.
The issue is that the Sun Download Manager automagically unzips those files
and then leaves the DVD part A or B or C on the filesystem with no way to
verify that they are correct. The user has to *assume* that all went well.
If the user concatonates all three parts to form the DVD iso image and then
runs openssl dgst -md5 or /opt/csw/bin/gmd5sum or digest ( or whatever ) to
get the MD5 sum it will a half hour before he/she knows that the data is
borked.
I, for one, have a machine here that burns DVD's with dule 400MHz Pentium
III in it and I really don't enjoy waiting 30 minutes to find out that the
DVD can not be built. Even worse .. I have to go login to the SDLC again
because it will only allow me to download once and thus I have to login
again. Worse still is that we can not just take these "Community Edition"
files and mirror them out here in the community.
So ... to make a long story short ... the more info you can provide up front
the better.
Or people can look here :
http://www.blastwave.org/docs/OpenSolaris/index.html
but that link is not easy to find at a site that is all about open source
software for the community ( my fault and I can fix that ) and that page can
not be found from the Sun or OpenSolaris website anywhere and certainly not
from the one page that talks about open source software for Solaris :
http://www.sun.com/software/solaris/freeware/
Dennis
