Mike Gerdts wrote: > On 3/28/06, Casper.Dik at sun.com <Casper.Dik at sun.com> wrote: >>> Is it safe to simply add the few packages that are sun4v or T2000 >>> specific to a sun4u system (15k) to enable building a single sparc >>> flar? I'm not asking for an in-depth analysis here, just wondering if >>> you have a strong gut feeling one way or another. I *really* want to >>> have one sparc flar. >> I believe that this was possible before. >> >> (But note that our patch tools were broken for a while which regards >> to multiple versions of the same package which is what will happen) >> >> Casper > > I just noticed another snag on this one. It seems as though > flarcreate does not properly recognize which architectures are > available (or I got sun4v onto the disk in the wrong way...) > > As a quick and dirty test, I took a V240 that I had just imaged with a > S10 1/06 SUNWCXall flar. I then... > > # cd $media/Solaris_10/Product > # pkgadd -d . *.v > # flarcreate -SHc -n testflar /var/tmp/testflar > > In the header of /var/tmp/testflar appears the line: > > content_architectures=sun4u >
I'm sure that's grabbed directly out of uname; cross-architecture flar's aren't really accommodated by the current design, as I recall. > I expect this is going to lead to having jumpstart tell me that the > flar lacks the appropriate architecture support when I go to install > it on a sun4v box. > Yeah, that's what I'd expect. > This could be related to the warnings during pkgadd that "X package > pathnames are already properly installed." I suspect that was for > directories that were common to the *.u and *.v packages but have not > yet checked to be sure there were not more serious conflicts. > Looks like Casper answered this part. Dave
