Glad you noticed. It is a chicken and egg to include a hash on install media that then itself gets hashed. Don't expect bsd.rd to happen. X is another matter. It's not realistic to build X everytime base is built; for that and for other reasons, the X hashes cannot (yet) be included in the bsd.rd.
Since you asked, I would recommend you not waste your time trying to figure this out. Penned by Peter J. Philipp on 20090516 23:42.43, we have: | Hi, | | I tested the installer from May 14th and noticed that downloaded sets get | checked against sha256. Nice job! However there is bsd.rd which doesn't | get checked and neither do the "x*" packages. | | I understand that the checksum of bsd.rd can't be created before the bsd.rd | image is finished, but I'm left wondering that perhaps at the cost of | pretty looks a warning be put in place that says "warning set bsd.rd will | not be checksummed". | | Let me know if I should break my head over writing this change in | install.sub. | | Regards, | | -peter -- Todd Fries .. [email protected] _____________________________________________ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | "..in support of free software solutions." \ 250797 (FWD) | \ \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt
