On Thu, 30 Sep 2004 18:31:00 +0200, Peter Oberparleiter <[EMAIL PROTECTED]> wrote:
> Trust zipl :) If it exits with a return code of 0, it should be safe > to assume that the IPL record was written according to the provided > configuration. If you're not sure about a new configuration, use the > multiboot feature to be able to switch back to a working one. If your code does not work we have another problem. I referred to the CP load map that show the timestamp of each object deck included in the nucleus. This is about verifying the work you should have done. Telling someone to do it twice will not decrease the chance he may forget to do it... ;-) > I agree that putting the information into the bootmap file wouldn't be > too hard, but I don't like the implications: zipl would need to > be able to read bootmap files, put a version tag on the current format, Well, zipl would read the blocks pointed to currently by the bootstrap that sits in the IPL record (which happen to be a bootmap file).. If zipl could, upon writing the IPL record, store some extra stuff (maybe the output of 'ls -l' for each of the files included) most of it is done. Sure, you're right that it would be great if the layout of the extra stuff were documented to allow for non-human consumption. -- Rob van der Heij rvdheij @ gmail.com ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
