Hi everyone.
The issue I had with building SVR4 packages turned out to be caused by
an omission during my image build. I can now successfully install an
SVR4 package without moving the /var/sadm/install tree into the bootroot.
The issue was due to my not having deleted /var/sadm/install/.lockfile
after having done a pkgadd as part of my build process.
Thanks to Karen for steering me in the right direction on this.
Jack
On 12/03/09 15:13, 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
>
> * 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
