> <div id="jive-html-wrapper-div"> > > Hi Alexander.<br> > <br> > Please note that the DC manifest accepts a > non-negative padding value, > so there is no need to modify the scripts to enlarge > the bootroot.<br> > <br> > In XML, the field is<br> > <br> > distribution/img_params/output_image/bootroot/size_pad > _mb<br> > <br> > Thanks,<br> > Jack<br> > <br>
I modified /usr/sbin/root_archive script which developed to work with ready miniroot, therefore it requires to be modified for adding some free space for creating new boot_archive. Once again: /usr/sbin/root_archive have better calculation and compression, than DC bootroot_archive.py. In my test bootroot_archive.py get me 114mb miniroot with 38mb free space, /usr/sbin/root_archive with my hack (+20mb) - 90mb with 13mb free space. If I use /usr/sbin/root_archive's calculation size in bootroot_archive.py then I've got cpio errors. I found that /usr/sbin/root_archive use filelist and for each file do cpio and immediately fiocompress. DC bootroot_archive.py at first do cpio for all files, then call compress func, but this is function do 'cpio' again before fiocompress - why? Shure, in this case I've got "Not enough free space" error. I've commented compression call in bootroot_archive.py and inserted compression call from /usr/sbin/root_archive and I've got required 90mb boot_archive. Cheers, Alex -- This message posted from opensolaris.org
