Hi everyone.

My push of:
    3340 bootroot auto size
is a minor flag day for those using Distro-Constructor:
    - with their own finalizer scripts
    - with their own custom bootroot

If you use DC in one of these ways, please read on...

*** If you write your own finalizer scripts: ***

Please note that now there are 5 arguments automatically passed to them 
(in addition to any specified in the manifest for a particular script).  
These arguments are:
    1) Manifest Reader Socket: Passed to ManifestRead to get manifest data
    2) Package Image Path: Path to the package image area where IPS
       packages are loaded to create a system image
    3) Temporary Directory: Used during the building process
    4) Bootroot Build Area: Area where bootroot is built
    5) Media Directory: Area where finished media are deposited.

*** If you create your own custom bootroot: ***

Please note that the bootroot is now autosized.  The manifest contains a 
new entry:
    img_params/output_image/bootroot/size_pad_mb
which specifies a number of extra megabytes to add to the bootroot's 
automatically-determined size.  The default is 10Mb.

Note also that the file system into which the bootroot is set no longer 
sets aside the UFS default of 10% of space for system use only.  The 
entire file system is available to all users.  This may lower the 
ultimate size requirements of the bootroot (the / file system on the 
live system), depending on applications supported by the live system.

Please send any questions to caiman-discuss.

    Thanks,
    Jack


Reply via email to