This issue was caused by a cloning error on my part. I rebuilt the
certificate for LINUXSMT using the following procedures:
http://www.novell.com/support/php/search.do?cmd=displayKCdocType=kcexternalId=7006024
Now all is well and I move on to the next stage. Thanks everyone.
Peter
From:
On 10/14/2011 at 05:08 PM, Ron Foster at Baldor-IS rfos...@baldor.com
wrote:
It sounds logical, but the line in the yast update screen implies SP4. For
example,
*slesp4-SPident *Recommended update for SPident
*recommended*7441-0*
Ron,
What does rpm -q
Shane,
am Sat, Oct 15, 2011 at 09:32:34AM +1000 hast du folgendes geschrieben:
Detach/attach is the only time Linux forces a re-read of the data
actually on the disk for the R/O systems, so you need to sync on the
R/W system, then detach/attach on the R/O systems to pick up the
actual
SPident-0.9-74.36.1
From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
[mp...@novell.com]
Sent: Sunday, October 16, 2011 12:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Yast not auto selecting all security and recommended patches
On 10/16/2011 at 10:09 PM, Ron Foster at Baldor-IS rfos...@baldor.com
wrote:
SPident-0.9-74.36.1
That is the most current version of SPident for SP4. So, I don't know why it's
showing up in the list of available patches, but it's clear that it's already
installed.
This is only one of a
