Hi Karen,
I have some comments and questions. Overall, I really like the concept
(it will most certainly simplify the netboot text installer path, and
eliminate some failure scenarios for those use cases).
5.2: Under destination, are you proposing that "/a" be hard-coded? I
would think that the temporary mountpoint used by the installers should
be controlled by the installers, and that we wouldn't want DC to have
knowledge of that.
For other values in the sample, (such as "dev" as an install dir), when
this file is generated at DC build time, will they be pulled from an XML
template? Coded as part of the checkpoint ('constants' in the Python
file)? Or pulled dynamically from somewhere else?
For "{cdrom.mountpoint}", since for some scenarios (net-booted text
install primarily), it's not really a "CDROM", would a different name
for the variable be more appropriate? Alternatively, would it make sense
to diverge physical media from netbooted media here (i.e., create a
separate .zlib of items that would have been on .cdrom for the
net-booted case)?
5.3: Can you clarify why this belongs under /.cdrom/.media-transfer/ vs.
other potential locations, such as, for example, the vendor-packages
directory? For net-boot, I'm concerned about being reliant on files not
in the boot archive or existing .zlibs.
5.3.2: Rather than splitting the registration path; can we leverage the
registration path? We have support for registering *functions* as well
as *classes* - so long as whatever it is returns an instance of a
checkpoint, whether it's a class constructor or function doesn't matter.
So, would it make sense to register a function that will decide which
kind of checkpoint to return?
5.4.3: For similar reasons to my comment on 5.3, does this software.xml
actually belong in the boot archive or an existing .zlib?
5.5: For step 4, would it make sense instead to enhance manifest reader
to support this use case? Or is a separate DOC instance better? Is this
process done by the installer, or by a checkpoint, or as part of
registration?
- Keith
On 01/14/11 10:55 PM, Karen Tung wrote:
Hi,
Please review my proposed design of cpio-based transfer for
the GUI and Text Installer.
I checked the file into the caiman-docs gate under media-transfer
directory.
You can also access the design doc directly here:
http://src.opensolaris.org/source/xref/caiman/caiman-docs/media-transfer/media-transfer.pdf
Please provide your comments by next Friday 1/21/2011.
Thanks,
--Karen
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
