Hi Karen,

Quick question below.

Karen Tung wrote:
> Hi Sue,
> 
> I did a "grep" on all the files containing "microroot" in the 
> slim_source gate.
> Here's my suggestion on all the non-AI and non-ICT files:
> 
> ----------------------------------------
> ktung at ox {4105} pwd
> /code/slim_source/usr/src
> ktung at ox {4114} find . -exec grep -il microroot {} \;
> ./lib/libict_pymod/ict.pyc
> ./lib/libict_pymod/ict.py
> ./lib/libtransfer/transfer_mod.py
> ./lib/libtransfer/transfer_mod.pyc
> 
>  > No code change needed in transfer_mod.py.  The references to microroot
>  > in this file is in the comment only.  Good to update the comment to
>  > say root_archive make it consistent with rest of the gate.
> 
> ./cmd/installadm/docs/scenario.html
> ./cmd/installadm/installadm-common.sh
> ./cmd/installadm/installadm.h
> ./cmd/installadm/installadm-common
> ./cmd/installadm/setup-sparc.sh
> ./cmd/installadm/installadm.c
> ./cmd/installadm/setup-sparc
> ./cmd/slim-install/listcd/listcd.c
> 
>  > No code change needed in listcd.c.  The reference to microroot is in 
> the comment only.
>  > Good to update the comment to say root_archive.
> 
> ./cmd/distro_const/auto_install/ai_post_bootroot_archive
> 
>  > Perhaps we can remove this whole script all together?  It's for 
> setting the sticky
>  > bit on the bootroot.  We think setting the sticky bit on the bootroot 
> is not needed.
>  > See bug 5789.  If we want to leave this script, and deal with the 
> stick bit change later,
>  > then, need to determine whether it is x86 or sparc and set it 
> accordingly.
> 
> ./cmd/distro_const/docs/manifestfile.html
> 
>  > search and replace all instances of x86.microroot to root_archive
> 
> ./cmd/distro_const/utils/grub_setup.py
> 
>  > search and replace all instances of x86.microroot to root_archive
> 
> ./cmd/distro_const/DC_defs.py
> 
>  > change sparc.microroot and x86.microroot to root_archive

Wouldn't it be better to replace BR_SPARC_FILENAME and BR_X86_FILENAME with 
BR_FILENAME and make corresponding changes in bootroot_archive.py? Seems 
cleaner 
that way.

Sue


> 
> ./cmd/distro_const/slim_cd/slim_cd_x86.xml
> 
>  > search and replace all instances of x86.microroot to root_archive
> 
> ./cmd/distro_const/slim_cd/all_lang_slim_cd_x86.xml
> 
>  > search and replace all instances of x86.microroot to root_archive
> 
> Thanks for making the changes.
> 
> --Karen
> 
> Jack Schwartz wrote:
>> Hi everyone.
>>
>> Bug 5787 microroot name shouldn't be ISA specific
>>
>> needs to be fixed ASAP.  I will be upping the priority accordingly and 
>> re-assigning it to Sue since the AI changes are tricky.
>>
>> It touches different parts of the slim_source gate: libict, installadm 
>> and DC.  To expedite getting this bug fixed, I would like Joe, the 
>> expert of libict; and Karen, the DC lead, to reply to this email to 
>> state in detail what/where the changes are, so that Sue can do the 
>> needful.  Hopefully the changes for ICT and DC are just 
>> search-and-replace type changes.  If not, please elaborate.  The 
>> intent is that this parallelism will help get the bug changes done 
>> quicker.
>>
>> Once Sue has a gate ready (should be tomorrow sometime), Joe, Karen, 
>> Sue and myself will help test it out.  Again, parallelism should save 
>> time.  Once proven, the webrev will go out as usual.  The intent is to 
>> push by the end of the week.
>>
>> We will use the name "boot_archive", since that is  consistent with 
>> current installed systems.
>>
>> I will be filing a bug (to be fixed later) to change "bootroot" to 
>> "boot_archive" in DC, so we are consistent on all 3 fronts: AI images, 
>> installed images and DC.
>>
>> For identification of the ISO as a SPARC or X86 type, one will need to 
>> check the /platform directory.  i86pc won't exist on SPARC, and 
>> sun4[u/v] won't exist on x86.
>>
>> Thanks everyone for your help.
>>
>>     Thanks,
>>     Jack
>> _______________________________________________
>> caiman-discuss mailing list
>> caiman-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>   
> 


Reply via email to