Thanks for your response. Yes, running RedHat 6.5. Trailing a CA Linux Connector product which uses VMCP to obtain guest & zVM Node.
That information was not available until run level '3'. Product reported back "NULLS" until multi user mode. RedHat support of no use. I found this which works except for Emergency run level: "You can specify additional modules to be loaded by creating a new <name>.modules file name in /etc/sysconfig/modules/ directory, where <name> is any descriptive name of your choice." This does a "modprobe" for VMCP, file: /etc/sysconfig/modules/ibm-vmcp #!/bin/sh # Load VMCP module # Insure /dev/vmcp does NOT exist, if it does # then vmcp previously loaded. # "!" = NOT there if [ ! -c /dev/vmcp ] ; then exec /sbin/modprobe vmcp >/dev/null 2>&1 fi Joseph Vitale Technology Services Group Mainframe Operating Systems Pershing Plaza 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell 917-903-0102 -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post Sent: Tuesday, January 20, 2015 4:49 PM To: [email protected] Subject: Re: Loading VMCP in single or emergency boot modes >>> On 1/20/2015 at 12:26 PM, "Vitale, Joseph" <[email protected]> >>> wrote: > Hello, > > Kernel module "VMCP" is loaded via /etc/rc.local but only in Mult-User > mode, run level "3". I would like to load it in earlier run levels, > say Single User mode. > > There should be a way to do that without a script in /etc/rc1.d. > > RedHat recommends I rebuild initramfs-2.6.32-431.el6.s390x.img via > /etc/dracut.conf. > > I would appreciate your advice on this. Based on your description, this is prior to RHEL 7. Please correct me if I'm wrong. At the points in system startup you're talking about, the root file system has already been switched to the "real" device that holds it. Putting something into your initrd would be a little superfluous since you would already have access to your real disk. To me, just typing "modprobe vmcp" when needed is far less of a hassle than doing just about anything else like setting up an init script. Or, if rc.local doesn't contain anything else, you could just execute _that_ manually. (Or if it doesn't have anything else you don't mind executing in runlevels S, 1, or 2.) Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
