Jack Schwartz wrote:
> Hi Dave.
>
> On 12/03/09 15:27, Dave Miner 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
>>>
>>> * 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?
>>>
>>
>> I would be quite surprised if we are still able to install on 512 MB
>> systems with this proposed change.
> Yes. This is why I was asking if anyone had any other ideas...
>> Do you have some experimental results with an image built as proposed?
> Yes. My first crack at building a live CD image with new DDU bits
> (which failed because I didn't add the /var/pkg/state tree and didn't
> allocate extra space) generated a ramdisk size of 164831K. The one
> created with these changes had a bootroot of 261215K.
>
> It appears that a 512Mb system cannot boot the second image. It's been
> stuck at a black screen for several minutes now...
>
Then we need to explore other options, as 512 MB is a product
requirement we'd strongly like to keep. I recommend taking this
discussion up with Shawn.
Dave
