On 07/15/09 01:01 PM, Jean McCormack wrote: > Jan Damborsky wrote: >> Hi Jean, >> >> Jean McCormack wrote: >>> Jan Damborsky wrote: >>>> Hi Jean, >>>> >>>> please see my comments below. >>>> >>>> Thank you, >>>> Jan >>>> >>>> >>>> > Requirements: >>>> > Provide the ability to create/select/preserve/delete/resize an >>>> extended partition and the logical drives. >>>> >>>> I think we might need to clarify what is the scope of 'resize' >>>> operation - >>>> based on the user experience with partitioning tools, it might be >>>> inferred >>>> that data are preserved in resized partition. Is it what is meant here >>>> or resize would refer to 'recreating with different size - no >>>> data preserved' ? >>>> >>> The data would not necessarily be preserved. >> >> ok. >> >>>> >>>> > Provide the ability for an interactive installer to >>>> create/preserve/delete/resize slices (sparc) >>>> >>>> Why this is planned only for Sparc ? Is this because scenarios >>>> calling for this functionality >>>> are applicable only to Sparc platform ? >>> That was originally why I put that restriction. We touched on this >>> briefly today and I believe I will >>> remove the sparc designation. >> >> ok. >> >>>> >>>> > Scope: >>>> > Provide install library support to mark a logical drive as a >>>> Solaris2 partition and set it as the active partition. >>>> >>>> I am not sure that this one is applicable - we might need to check >>>> with extended partition team, >>>> but it doesn't seem that mboot (boot loader installer puts into MBR >>>> in current implementation) was >>>> enhanced to search active logical drive. It seems ICT might need to >>>> put GRUB stage 1 into MBR >>>> instead of mboot if Solaris is installed on logical drive as stated >>>> in installgrub(1M) man page: >>>> >>>> ... >>>> -m Installs GRUB stage1 on the master boot sector >>>> interactively. You must use this option if Solaris is >>>> installed on an extended partition. >>>> ... >>> I will look into this further. >> >> Thank you. >> >>>> >>>> > Out of scope: >>>> >>>> It seems that other installer technologies (text installer, AI) are >>>> out >>>> of scope of this project and are to be handled by text installer >>>> and AI >>>> projects respectively - might this assumption be correct ? I think >>>> it might be helpful to capture this here. >>> Definitely out of scope. I can add that. >> >> Thanks. >> >>>> >>>> > Update fdisk to use libdiskmgt extended partition utilities >>>> >>>> To be honest, I am not quite sure if this requirement is related to >>>> this project, since it seems that Solaris fdisk(1M) was enhanced to >>>> handle >>>> extended partitions. How would be libdiskmgt engaged and how it would >>>> help to address requirements of this project ? >>> Sanjay and I talked about the fact that with our libdiskmgt changes >>> there might be code in both >>> fdisk and libdiskmgt that essentially perform the same >>> functionality. This code really belongs in libdiskmgt. >>> It would be nice if we could change fdisk but there just isn't time. >> >> As doing this doesn't seem to buy install technologies anything, >> I am still not quite convinced that it should end up on our task list. > After reading Sarah's very thorough response I'll need to discuss this > again with Sanjay. I agree with Sarah's analysis.
-Sanjay > > Jean > >> >> Thank you, >> Jan >> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
