I'm not quite getting why I can't update the SUNWinstalladm-tools package, 
which is what the Flag day bug is saying I need to do, it does not say I have 
to upgrade the server OS.

You are saying that I have to update the entire operating system, just to 
upgrade that package, that is making installs to different client machines 
depend on the OS running on the server...  My x86 ai client machine cares what 
version of OS my sparc ai server is running?  Am I the only person who sees 
something wrong with the design here?

Mr. Ceri Davies - Staff Engineer (Software) 
Sun Microsystems - Data Management Group
Ceri.Davies at Sun.com 
W:(303) 272-7810 (x77810)
H:(303) 442-2795
Typically work from home on Fridays




On Jan 21, 2010, at 11:46 AM, Shawn Walker wrote:

> On 01/21/10 12:41 PM, Dave Miner wrote:
>> On 01/21/10 12:39 PM, Ceri Davies wrote:
>>> I am running 111b (osol0906) on my sparc install server, since we
>>> only run x86, I do not want to upgrade this machine. I am trying to
>>> upgrade my machine to the osol1003-131 kernel posted yesterday on
>>> nana. 1) I did try a pkg install installadm, and it did not upgrade,
>>> which I find odd, since its been June/July since I upgraded, its
>>> there really no newer installadm I can use without having to upgrade
>>> my entire install server?
>>> 
>> 
>> See the following flag day:
>> 
>> http://hub.opensolaris.org/bin/view/Project+caiman/Flag+day+bug+8347%2D6092
>> 
>> which took effect as of build 128. You can't serve current AI clients
>> from pre-128 AI servers.
>> 
>> We're not in the business of back-porting changes like this to the last
>> release; if you will be using the /dev train, you will likely run into
>> flag days such as this periodically because of the need to continue
>> developing the technology. Long-term, there'll be greater stability, but
>> we're not there now.
> 
> And even if the AI client was back-ported, the pkg(5) system currently 
> doesn't guarantee that sort of backwards compatibility either.  Meaning, you 
> can't necessarily use a pkg(5) client from a newer OS build to install an 
> older OS build.  Even if the install succeeds, the resulting system may not 
> be usable by the older pkg(5) client that gets installed.
> 
> The only compatibility pkg(5) attempts to guarantee is that a new client can 
> be used with an image created by an older one.
> 
> -- 
> Shawn Walker


Reply via email to