Hi Dave.
Dave Miner wrote:
>>
>> 1) Not sure what extra things DC needs to do to provide for a live-image
>> installable image or a repo-installable image. It will need to include
>> an installer, but how does that fit with the manifest?
> I would think the installer is just one or more packages that are
> included in the image.
>
OK. For now I'll assume that the proper installer will just be included
in the distribution based on having the correct included packages.
>> 2) Disk and network parameters for installation are still TBD.
>>
>> 3) There are some things which cannot be known by the DC but which are
>> needed by it. For example, if someone specifies they want a certain
>> locale, I don't want to hardwire into DC a package name delivering that
>> locale. For maintainability, these things will have to go into a
>> manifest. I'm thinking of putting them into a manifest different than
>> the one for user-specified parameters. That way if the supported locale
>> list changes, one can just upgrade their DC and get the changes without
>> worry of overwriting or having to merge the user's existing
>> user-specified parameter manifest.
> I don't think that we should assume package name == locale. Files for
> specific locales might be tagged as such and aggregated into larger
> packages. But we need some feedback from g11n on what they're actually
> going to do.
>
That's not what I meant. Actually what I was trying to say is that DC
must accomodate that it *cannot* know the correct package (via it's name
or anything else) for a given locale. What I was proposing was to have
an additional file that specifies this mapping of correct package names
to locales, so that DC doesn't have to hardwire such information. This
file can be used also for any other similar release-specific knowledge.
>
>> Assumptions:
>> ------------
>>
>> 1) When installing from the live image that all parameters are AS-IS
>> from the live image. (e.g. same users, files, locales, etc)
> I suppose, though I'm wondering what effect this assumption has?
>
DC can support setting parameters in a live image install as it does for
a repo install. I thought a live image install just cpio-ed stuff out
of the running system root and onto disk. If this is the case, wouldn't
it be hard for the installer to possibly undo parameters from the
running system and replace them with the changed bits? I guess that's
the installer's domain...
So, for now, DC will feed whichever installer exists on the live image,
the same set of install parameters.
>> Other items:
>> ------------
>>
>> 2) I have added a query for the zfs compression type and level for the
>> live CD and installed image.
>>
>>
>
> I think you mean that this is just the setting of the compression
> parameter, which combines the algorithm and level.
>
I have three things to say/ask:
1) Well, actually, I was thinking type is one of (none, lzjb, gzip) and
level was 0-9. Is this incorrect?
2) For the live image, do I need to compress both the whole image and
the microroot? I think both since the microroot gets loaded before it
can mount and use the rest of the image, correct?
3) I assume ZFS compression is only for the installed image. It's lofs
compression for the live images and microroot, right? If so, what kinds
of compression types (e.g. lzjb and gzip) does lofs offer?
Thanks,
Jack
