Mike,
Mike Gerdts wrote:
> On Mon, Nov 17, 2008 at 8:05 PM, Glenn Brunette <[EMAIL PROTECTED]> wrote:
>> Jeff,
>>
>> This actually hits on a similar request that I have (but for different
>> reasons). I would like a stable interface from which I could tell
>> the update revision of a system.
>
Glenn Brunette writes:
> This actually hits on a similar request that I have (but for different
> reasons). I would like a stable interface from which I could tell
> the update revision of a system.
We have no such thing. It's not clear to me how such a thing would
work. Suppose someone install
Mike Gerdts wrote:
> When really important features are released as new
> packages "genesis patches" are delivered to deliver the feature.
Sometimes, but not always. In fact, I'd have to say "usually not". The
Genesis technique is not without its problems, and is considered
controversial.
Hi
I'd agree with James, the update revision is sometimes a blurry picture,
ie
cat /etc/release will tell me that my system is 1/06 ( update 1 if I
remember correctly )
but if I have applied the latest jumbo kernel patch 137137-09 I
essentially have a lot of the u6 functionality ( a lot but not
On Tue, Nov 18, 2008 at 11:30 AM, Enda O'Connor <[EMAIL PROTECTED]> wrote:
> So sometimes an update might be meaningless, ie
> I can have an x86 FCS system ( from cat /etc/release )
> but it has grub,zfs and all the latest zones functionality, just by
> adding 137137-09, plus the near 30 patches re
Hello,
we're having an issue migrating a zone from one server to another.
Server A has Solaris 10 x86 05/08 and hosts zone X (spare-root zone).
Server B has just been acquired and installed with Solaris 10 x86 10/08
and hosts a number of zones created locally.
We would like to move zone X from A
Christophe Dupre wrote:
> Hello,
> we're having an issue migrating a zone from one server to another.
>
> Server A has Solaris 10 x86 05/08 and hosts zone X (spare-root zone).
>
> Server B has just been acquired and installed with Solaris 10 x86 10/08
> and hosts a number of zones created locall
Mike Gerdts writes:
> On Tue, Nov 18, 2008 at 11:30 AM, Enda O'Connor <[EMAIL PROTECTED]> wrote:
> > To me they probably need a patch automation tool to tell them what is
> > currently available in terms of patching, and they see what they need
> > from that.
>
> Interface changes always have an a
Thanks Jerry for the quick reply. I am making progress, but no cigar (yet). Now
I have:
zoneadm: zone 'X': ERROR: attempt to downgrade package SUNWgtar, the source had
patches but this system does not
It does not give me a patch number, so I can't add it to the bad_patches file.
Or maybe it d
Hi Christophe
In the zone being attached: zonepath/root/var/sadm/pkg/SUNWgtar/pkginfo
file there should be an entry for PATCHLIST=
could I see this, and also the one from the target system's global zones
pkginfo.
Enda
Christophe Dupre wrote:
>
> Thanks Jerry for the quick reply. I am making p
Christophe Dupre wrote:
>
> Thanks Jerry for the quick reply. I am making progress, but no cigar
> (yet). Now I have:
>
> zoneadm: zone 'X': ERROR: attempt to downgrade package SUNWgtar, the
> source had patches but this system does not
>
> It does not give me a patch number, so I can't add it
From the global zone:
PATCHLIST=
From zone being attached:
PATCHLIST=139100-01
So I guess I need to install 139100-01 in the new server's global zone ?
That makes sense - the original server was 05/08 but had received a
recommended cluster in early october, so it is probable that it received
12 matches
Mail list logo
