Greetings; (Posted to VMESA-L and VSE-L and LINUX-390)
- - Now in its sixth year! - - Includes VSE and linux/390!
I have set up a public service web page at
http://www.eskimo.com/~wix/vm/
for posting positions available and wanted for VM, VSE and linux/390.
Please visit the web
Glen,
I understand the MVCL now. I also understand some of the set up that was
done in CP years ago.
Thank you,
Paul Hanrahan
I've been seeing a lot of tdb problems during our SuSE trial when it
comes to Samba. Over time a tdb or two inevitably becomes corrupt,
sometimes in just an hour or two. I ran tdbtorture, a tool that comes
with the samba source, and got errors left and right. On intel, the
tdbtorture suite just
In preparing to install a new guest I have created the sles8 exec file and
dowloaded the necessary files. I have done this numerous times already in
the same manner. This time however I am getting an error that I have not
seen yet. When I execute sles8 the following appears:
HCPCSP053E ALL not
Eric,
post us your SLES8 exec, you have forgotten a quote or something
similar...
Regards/Cordialement/Gruss/Saludos
John Cassidy Dipl.-Ing (Informatique)
S390 zSeries Systems Engineering
Schleswigstr. 7
D-51065 Cologne
EU
Tel: +49 (0) 221 61 60 777 . GSM: +49 (0) 177 799 58 56
I suspect that either the files didn't get get downloaded as binary, or
that you downloaded image for the kernal image instead of
vmrdr.ikr. (File vmrdr.ikr gets downloaded as SLES8 IMAGE, so doing it
from memory it's easy to get the wrong file...)
Lee
At 06:41 AM 12/18/2003, you wrote:
In
Also, you must make sure that they are a RECL of 80 for a RDR file.
Dave
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Lee
Stewart
Sent: Thursday, December 18, 2003 7:56 AM
To: [EMAIL PROTECTED]
Subject: Re: Problem booting SLES 8 for Install
I
My FTP process follows:
ftp server
binary
locsite fix 80
get vmrdr.ikr sles8.image
get initrd sles8.initrd
asc
get parmfile sles8.parm
quit
I have just downloaded all the files again and still get errors when
trying to boot for install.
Thanks!
Eric Sammons
(804)697-3925
FRIT - Unix Systems
We are getting a new z900 and would like the three linux partitions running on the X47
partitions to come up and run there. One of the SuSe Linux partitions is running on
an OSA Express Card port 1. The card cannot be moved to the new machine. Is there a
way to change the SuSe Linux to use
OK, you should do the suggestion as a previous post and post your exec that punches
the files to the reader.
Dave
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Eric Sammons
Sent: Thursday, December 18, 2003 8:12 AM
To: [EMAIL PROTECTED]
Subject: Re:
You could try using the pam_unix2.so module instead of pam_ldap.so.
pam_unux2.so will call pam_ldap.so under the covers if you modify
/etc/security/pam_unix2.conf.
Hope it helps. sal
OK here is my sles8 exec file:
*** top of File ***
/**/
'close rdr'
'spool rdr all'
'spool punch * rdr'
'punch sles8 image a (noh'
'punch sles8 parm a (noh'
'punch sles8 initrd a (noh'
'change rdr all keep nohold'
'ipl 00c clear'
*** End of File ***
One other thing I should note, this is my
What mods should I make to the pam_unix2.conf file. This is the first I
have heard regarding a modification to this file.
Thanks!
Eric Sammons
(804)697-3925
FRIT - Unix Systems
Sal Torres/SBC Inc. [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
12/18/2003 09:30 AM
Please
All,
I spoke to Suse and they will be posting something to the forum later
today. However, I will say at this point that the LPAR based pricing post
is incorrect. Straight from Suse's mouth, the pricing will remain CPU
based for the mainframe. So, if you have 4 LPARS all running off the
It looks like my pam_unix2.conf file already has references to ldap. So
now my questions are:
1. Do I remove pam_unix.so and pam_ldap.so and use pam_unix2.so instead?
2. What will using pam_unix2.so buy me. The issue with expired passwords
I believe goes back to the ldap. I have actually found
*** Reply to note of Thu, 18 Dec 2003 09:31:16 -0500 (EST/CDT)
*** by [EMAIL PROTECTED]
I think that YaST does it for you if you select LDAP. I found out
about it by looking at the source code for pam_unux2.
(pam-modules rpm).
sal
Eric Sammons [EMAIL PROTECTED] writes:
What mods should I make
Might I suggest that you PURGE your RDR before you run the EXEC. If you can not do
that, then you'll have to ORDER the RDR correctly before attempting to IPL.
Dave
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Eric Sammons
Sent: Thursday, December 18,
Try to set the shadow last change to zero. pam_ldap is supposed to
expire the account:
...
if (session-info-shadow.lstchg == 0)
{
/*
* Adhere to convention of a shadow last change
* value of 0 implying that the password has
* expired. Apparently this is
That was it, I went back to the orginal SLES8 docs to verify and in fact I
had a typo in my generated documentation.
Thanks for catching that...
Eric Sammons
(804)697-3925
FRIT - Unix Systems
David Booher [EMAIL PROTECTED]
Sent by: Linux on 390 Port [EMAIL PROTECTED]
12/18/2003 10:05 AM
I have done that and it sort of worked. It seemed to take on the
characteristics there after of a ACL problem. By changing the acls I get
different behavior; however, I can't seem to find the right acls that
cause the implementation to work.
Do you have this working? Can I ask what your LDAP
Try this.. this one works on whatever flavour of z/VM you want:
'VMFCLEAR' Clears the screen for legibility.
'CLOSE 00C'Close all open files in the reader - for purging.
'PUR RDR ALL' Empties (purges) the VM reader.
'CP SP PUN * RDR' Moves the
We are getting ready to move our VM/SUSE installations from an EMC DASD box to an IBM
Shark DASD box. I have two questions.
1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned above
the 32MB line.
2. Are there any issues using 3390-9's with VM/LINUX.
Thanks for
You must be an MVS person :). VM has never had a problem with UCB
numbering. 3390-9's work just fine too.
Marcy Cortes
Wells Fargo Services Company
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gene
Walters
Sent: Thursday, December 18, 2003 09:14
To:
On Thu, 2003-12-18 at 11:13, Gene Walters wrote:
We are getting ready to move our VM/SUSE installations from an EMC DASD box to an
IBM Shark DASD box. I have two questions.
1. Does anyone know of any issues with Linux/VM when the DASD UCB's are genned
above the 32MB line.
Above the 32MB
Ila wrote that the z900 has an OSA Express Card port
1
On the zSeries, they combined two OSA cards on one
physical card and the card is assigned two chpid. Each
connection on the OSA card you see is port 0 of a
different chpid.
Check with your FE or whomever does your iocds. You
should have 2
It looks as though those are there for architectures where someone has
implemented spinlocks in assembler code. There are also generic routines
written in C for everyone else. While it would be a bit of a performance
enhancement to have one for Linux/390, it doesn't appear to be a
requirement.
Is there anyone out there with z/OS, the z/OS NFS server, DFSMS/MVS and
Linux who would be willing to try an experiment for me? I have an idea wrt
to file-level backups w/o requiring TSM/MVS, but limited access to a z/OS
system (and not much expertise with SMS policy definition).
Failing that, is
Hi all...
We have a Linux image (SLES 8 under z/VM 4.4) that has a time/date
problem. The system hardware clock on the processor runs LOCAL time; the
timezone offsets in the SYSTEM CONFIG file are zero; and the VM time is
correct -- local time. When installing SLES 8, the user specified the
28 matches
Mail list logo
