Udev should handle this automatically. Like I said in the previous note, however, it can take up to 10 seconds for the device node to appear. Race conditions of this type appear to be common during rc.sysinit, and also affect fcp devices, particularly when you use them in combination with LVM and/or multipath. Red Hat supposedly has a fix either available or coming soon.
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Monday, July 02, 2007 2:54 PM To: [email protected] Subject: Re: [LINUX-390] vmcp during boot results in Error: Could not open device /dev/vmcp: No such device >>> On Mon, Jul 2, 2007 at 2:32 PM, in message <[EMAIL PROTECTED] rg>, Susan Zimmerman <[EMAIL PROTECTED]> wrote: > Hi Mark. > > I noticed /sys/class/misc/vmcp was 10 63 > > OSA-LNX1:~ # cat /sys/class/misc/vmcp/dev > 10:63 > > So I deleted /dev/vmcp and manually created the node > > as 10 63 > > and now it works just fine. In addition to what Adam said about making sure to rebuild your initrd and re-run zipl, be careful of what you've done here. On one of my test systems, the device node is 10:61, so it can vary from system to system. If you rmmod the vmcp module, the device node _should_ go away. When you modprobe it again, it should appear dynamically. 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 -------------------------------------------------------- This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing. -------------------------------------------------------- ---------------------------------------------------------------------- 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
