Hi Karen.
On 12/03/09 15:39, Karen Tung wrote:
> Jack Schwartz wrote:
>> Hi everyone.
>>
>> With the latest IPS changes, it appears that the slim CD's root
>> filesystem needs an additional ~96 Mb. "pkg install" needs the space
>> when installing additional packages. I believe this is due to the
>> push for 12409 and 12340.
>>
>> The 96 Mb breaks down to ~46Mb needed to read the /var/pkg/state/...
>> tree into memory so it is changeable, and another ~50Mb* used to copy
>> it as part of the pkg install operation. The slim CD manifest needs
>> the following changes:
>> - specify the /var/pkg/state tree as bootroot-resident
>> ("ramdisk-resident")
>> - specify an additional 50Mb space via
>> img_params/output_image/boot_archive/size_pad_mb
> If you specify /var/pkg/state in the "boot_archive_contents" list.
> All the files that need to
> be included should be brought in automatically, and the
> boot_archive_archive.py finalizer script
> should dynamically calculate the needed space. Why do you need to
> specify an additional 50mb space
> in size_pad_mb?
Yes, it is true that the original /var/pkg/state files are brought into
the bootroot. However, when one pkg installs a package, stuff gets
copied. When I first ran pkg install without changing the bootroot, the
traceback included shutil.copytree. The actual IOError didn't specify
the errno that I could see, but the error string had a list which
included all three large files in /var/pkg/state/known.
Then, when I just included /var/pkg/state tree in the bootroot but added
no extra space, the pkg install still failed. When I added extra space,
it succeeded.
Part of the reason for this email is to inquire if, perhaps, I can just
bring in some of the files, or cut some of the space. Anyone have some
suggestions?
Thanks,
Jack
>
> Of course we still have the problem of the boot_archive increasing so
> much in size as a result
> of including /var/pkg/state.
>
> --Karen
>
>
>>
>> * 50 Mb used to allow a little extra space for installed packages,
>> etc. 46 Mb may be sufficient.
>>
>> Not sure if there may be a better strategy to handle this, as this
>> will impact the minimum memory requirement of systems being able to
>> run a live CD (whether slim or AI). Any ideas?
>>
>> On a related subject, in order to install an SVR4 package, the
>> /var/sadm/install directory tree needs to be brought into the
>> bootroot as well. This tree is very small however (~16kb).
>>
>> Please send any comments before Monday AM. I'll file a bug on this
>> (for manifest changes or whatever else is decided) once discussion
>> (if any) settles out.
>>
>> Thanks,
>> Jack
>> _______________________________________________
>> caiman-discuss mailing list
>> caiman-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>
