Hi Jeffrey,
jeffrey huang wrote:
> Hi, Jan,
>
> Thanks very much of detailed steps. I will have a try on SPARC to see
> if can also download manifest and do auto-install, seems it is still
> working in progress.
>
> Are you aware of the developing schedule, that is around what time we
> can have testable image?
To be honest, I am not sure - I will let Sundar comment,
since he is aware of what the current state of all pieces
needed to put together fully working image is.
Thank you,
Jan
>
> Great Thanks
> Jeffrey
>
>
>
> jan damborsky ??:
>> Hi Jeffrey,
>>
>> I think Mary is on vacation, so I will try to answer
>> your questions.
>>
>>
>> jeffrey huang wrote:
>>> Hi, Mary,
>>> I saw you already boot the sparc AI client.
>>
>> At time of being, you can boot sparc microroot from disk,
>> boot from net is currently work in progress.
>>
>> In order to boot from disk, you need to have disk formatted
>> with UFS filesystem (I have Nevada 102 installed on AI client).
>>
>> Then you can copy sparc microroot on that disk and boot it from
>> OBP in following way (assuming it is located in /sparc.microroot):
>>
>> {14} ok boot disk -kv -F /sparc.microroot
>>
>>
>> The list of things which are currently work in progress:
>> * net boot + DHCP
>> * mechanism for passing information about location of
>> AI net archives and service name to AI
>> * IPS sparc repo
>> * ICT stuff
>>
>> However, this list is evolving. The best approach
>> to keep track of changes is to follow discussions on
>> this mailing list.
>>
>> What can be tested:
>> * booting microroot from disk
>> * dowloading and mounting AI archives
>> * target discovery
>> * target instantiation
>> * pkg(1M) operations
>>
>>
>>> Can you share me how to get this done, including:
>>> - The environment: a sparc or x86 as AI server,
>>
>> Only x86 AI server is supported at time of being.
>>
>>> which client you are using T1000 or T2000?
>>
>> I have successfully tried on T1000 and T5220.
>>
>>> - Are you using SUNWinstalladm-tools on sparc or x86, where you get
>>> it? from slim_source?
>>
>> To give the example, I use following configuration:
>>
>> AI server:
>> * x4100 installed with 2008.11
>>
>> AI clients:
>> * T1000 (8GB RWM)
>> * T5220 (1GB RWM)
>>
>> AI server is configured in the same way as for x86 client,
>> just using ai-dec5.iso (or aisparc_200mb_pad.iso).
>>
>>> - where is sparc iso image? like ai-dec5.iso?
>>
>> Karen recently released new image for testing
>> (available only internally):
>>
>> /net/osol-bldsp/rpool/ktung/dc-ai200/media/aisparc_200mb_pad.iso
>>
>> Modified microroot can be downloaded from following location
>> (available only internally):
>>
>> /net/10.18.138.30/rpool/ai/test/sparc.microroot
>>
>> Modifications done:
>> * workaround for bug 5281 applied
>> * live-fs-root modified (needs to be accommodated for other
>> testing environment)
>> - network interface configured
>> - location of AI net archives hardcoded
>> - it can be pulled from following place (available only internally)
>>
>> /net/10.18.138.30/rpool/ai/test/live-fs-root.sparc
>>
>> Please feel free to let me know if you have more questions
>> or need more information.
>>
>> Thank you,
>> Jan
>>
>>>
>>> I need to setup the env to dev sparc test case?
>>>
>>> Great Thanks
>>> --
>>> Jeffrey
>>>
>>> bugzilla-daemon at defect.opensolaris.org ??:
>>>> http://defect.opensolaris.org/bz/show_bug.cgi?id=5821
>>>>
>>>>
>>>> Mary Ding <mary.ding at sun.com> changed:
>>>>
>>>> What |Removed |Added
>>>> ----------------------------------------------------------------------------
>>>>
>>>>
>>>> CC| |mary.ding at sun.com
>>>>
>>>>
>>>>
>>>>
>>>> --- Comment #2 from Mary Ding <mary.ding at sun.com> 2008-12-16
>>>> 10:35:55 ---
>>>> This is the notes that I had in regards to miniroot after dcfs is
>>>> integrated
>>>> for sparc, but it might also apply to microroot for sparc:
>>>> If you want to modify the miniroot in place after the system boot,
>>>> you can do
>>>> th
>>>> is:
>>>>
>>>> # mount -o remount,rw /
>>>> #
>>>>
>>>> That's because you can't write to a compressed file. You can remove
>>>> the file you want to replace and then write the new one in its place
>>>> after remounting root rw.
>>>>
>>>> So something like:
>>>>
>>>> mount -o remount,rw /
>>>> cp /usr/sadm/install/bin/pkginstall
>>>> /usr/sadm/install/bin/pkginstall.exec
>>>> cp /usr/sadm/install/bin/pkgremove
>>>> /usr/sadm/install/bin/pkgremove.exec
>>>> rm /usr/sadm/install/bin/pkginstall /usr/sadm/install/bin/pkgremove
>>>> cp /tmp/debug/pkginstall /usr/sadm/install/bin
>>>>
>>>>
>>>
>>> --
>>> Great Thanks & Best Regards
>>>
>>> ---
>>> Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683
>>> Solaris QE Group Email: jeffrey.huang at sun.com
>>> China Engineering & Research Institute, Sun Microsystems
>>> 7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China
>>>
>>> ------------------------------------------------------------------------
>>>
>>>
>>> _______________________________________________
>>> caiman-discuss mailing list
>>> caiman-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
>>
>
> --
> Great Thanks & Best Regards
>
> ---
> Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683
> Solaris QE Group Email: jeffrey.huang at sun.com
> China Engineering & Research Institute, Sun Microsystems
> 7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China
>
