On Tue, 08 Feb 2011 07:41:43 -0500 (EST), Carlos Bodra wrote:
>
> Checking documentation from Debian 6.0, chapter 2 - Supported Hardware I
> can read:
> ...
>
> Can I assume that now we can run this version on a z10 processor?
I guess I don't understand your question. Have you tried to run
earlie
Hi Mark,
It returns the following:
sysconfig-0.50.9-13.60.1
yast2-sysconfig-2.13.9-0.3
kernel-default-2.6.16.60-0.74.7
Thanks,
Doug
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Mark Post
Sent: Thursday, February 10, 2011 9:53 PM
To: LINUX-390
>>> On 2/11/2011 at 01:14 PM, "Lester, Doug" wrote:
> sysconfig-0.50.9-13.60.1
> yast2-sysconfig-2.13.9-0.3
> kernel-default-2.6.16.60-0.74.7
Those are pretty current levels, so the fix for the bug is already on your
system. This brings us back to what Helmut suggested:
ls -la /sys/bus/ccwgrou
Mark,
Thanks for mentioning Helmut again. It didn't register the first time
that I never saw his response.
My apologies to Helmut and Dave. For some reason, I never received your
emails. I just found them by looking at
http://www2.marist.edu/htbin/wlvgl?L=LINUX-VM&LOG=LOG1102.
Dave,
During th
>>> On 2/11/2011 at 04:17 PM, "Lester, Doug" wrote:
> Helmut,
>
> I think you are on to something. I didn't find anything of much help
> using "dmesg". "lscss |grep -i 3200 " and "lscss |grep -i 3201" show the
> devices, but "ls -la /sys/bus/ccwgroup/drivers/lcs/" does not.
>
>
> How do I get
Mark,
Thanks, but I get the following error:
#echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group
echo 0.0.3200,0.0.3201 >
/sys/bus/ccwgroup/drivers/lcs/g<.0.3200,0.0.3201 >
/sys/bus/ccwgroup/drivers/lcs/group
-bash: echo: write error: Invalid argument
I also tried with the '"' at the
>>> On 2/11/2011 at 05:29 PM, "Lester, Doug" wrote:
> Thanks, but I get the following error:
>
> #echo 0.0.3200,0.0.3201 > /sys/bus/ccwgroup/drivers/lcs/group
>
> echo 0.0.3200,0.0.3201 >
> /sys/bus/ccwgroup/drivers/lcs/g<.0.3200,0.0.3201 >
> /sys/bus/ccwgroup/drivers/lcs/group
> -bash: echo: w
Mark,
This is the lscss output. How do I tell if it is in LCS mode?
Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs
--
0.0.3200 0.0.1103 1732/01 1731/01 80 80 FF 0200
0.0.3201 0.0.1104 1732/01
>>> On 2/11/2011 at 05:57 PM, "Lester, Doug" wrote:
> This is the lscss output. How do I tell if it is in LCS mode?
I don't know yet, or even if it's possible from this display.
> Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs
> -
Hello dears,
I have set up a test machine to use crpto card... my wish is using that
with sshd... so, i installed :
• openssh
• openssl
• openssl-ibmca
• libica
• z90crypt
made changes on openssl.cnf to use libica engine, load z90crypt module and
after that i get openssh from source rpm and re
Rogério,
Chapter 7 "Verification for usage of library libica to access CPACF" in "
First experiences with hardware cryptographic support for OpenSSH with
Linux for System z" at
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101690
provides a suggestion.
thanks Mike, i will take a look this right now :)
On Sat, Feb 12, 2011 at 12:23 AM, Michael O'Reilly wrote:
> Rogério,
>
> Chapter 7 "Verification for usage of library libica to access CPACF" in "
> First experiences with hardware cryptographic support for OpenSSH with
> Linux for System z" at
Another way of telling is to transfer a LARGE file with your
pre-crypto sshd and again with your post-crypto sshd. Just watch the
difference it makes in your favorite z/VM performance monitor. You
won't necessarily realize an improvement in throughput, but the amount
of CPU consumed drops conside
Some of you folks might find this useful. It implements all but 1 of
the SMAPI functions in a single bash script. In addition, it supports
TCP/IP via bash's builtin /dev/tcp support and IUCV via the embedded
smiucv program that you can build using "smcli smiucv".
Documentation is slim, so you'l
14 matches
Mail list logo
