Rick,

> So if you happen to have a shell script that does a 'modprobe vmcp'
> before doing a 'vmcp' command, it should re-direct stderr (of the
> first part) to /dev/null.
You guessed it - but how about this:

  which vmcp >/dev/null 2>&1
  if [ $? != 0 ]; then
    modprobe vmcp
  fi

    -Mike

On Thu, Oct 9, 2014 at 11:44 AM, Rick Troth <[email protected]>
wrote:

> It goes back /four years/. Wow.
>
>
> On 10/01/2014 08:29 AM, Christian Borntraeger wrote:
> > Its an kernel change. the vmcp kernel part is now always builtin.
> >
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f73a2b03c59b95a3ee8eebcc127350c77c950e87
> > This has changed with 2.6.35. (SLES11 has a change on top that
> reintroduces the modular build for SP1 to make this behave as the original
> GA version).
>
> [facepalm]
> This is sad.
> I don't think I can blame the IBMers for getting tired of customer
> confusion, but this is a case of mucking the tech for a political
> reason. (Here "political" because they're forcing the hand of the
> distributors for failing to configure a better module list.)
>
> From the commit ...
>
>     "There have been too many cases where people were missing the 'vmcp'
>     device node and unable to send z/VM CP commands. So let's make sure
>     that on distros it will always be present."
>
>
> I hate to see the loss of the CONFIG_VMCP=m option. But there's been
> consistent "INITRD abuse" for more than a decade, things which should be
> static but are left as loadable. This is what comes of it. And now SUSE
> layers a patch on top of the official kernel ... puh-leeze!!
>
>
> On 10/01/2014 08:13 AM, Michael MacIsaac wrote:
> > # *modprobe vmcp*
> > modprobe: FATAL: Module vmcp not found.
> > # *vmcp q t*
> > TIME IS 08:09:48 EDT WEDNESDAY 10/01/14
> >
> > Is this a change in the s390-tools, or just a RHEL 7 thing?
>
> Good practice to ignore certain errors from 'modprobe', and this is a
> prime example. So if you happen to have a shell script that does a
> 'modprobe vmcp' before doing a 'vmcp' command, it should re-direct
> stderr (of the first part) to /dev/null. If there's an actual error, the
> latter command will fail and will clue the user that something's wrong.
> Think about it.
>
>
>
> --
>
> Rick Troth
> Senior Software Developer
>
> Velocity Software Inc.
> Mountain View, CA 94041
> Main: (877) 964-8867
> Direct: (614) 594-9768
> [email protected] <mailto:[email protected]>
>
> ----------------------------------------------------------------------
> 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/
>

----------------------------------------------------------------------
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/

Reply via email to