>>> On 10/16/2011 at 10:09 PM, Ron Foster at Baldor-IS
>>> 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 number of rea
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 Sun, 16 Oct 2011 23:09:39 +0200 Philipp Kern wrote:
> erhm, no. It waits for the I/O to complete and blocks. Sadly sync
> will also block for all filesystems to be flushed, not just the one
> you want to be in sync. Forcing it is kind of the point of the
> [f][data]sync calls.
Yeah I know t
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
> > act
>>> On 10/14/2011 at 05:08 PM, Ron Foster at Baldor-IS
>>> 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 SPident" re
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=displayKC&docType=kc&externalId=7006024
Now all is well and I move on to the next stage. Thanks everyone.
Peter
From:
