On Thu, 9 Oct 2014, Rick Troth wrote:
> Good practice to ignore certain errors from 'modprobe', and this is a
> prime example.
?? 'Good practice to ignore' ??
> 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.
Why burden the administrator with needing to understand the
politics of what the initscript writer should be doing?
If I understand what you are saying, I think you are off base.
I cannot really see that it ever makes sense to hide debugging
information, rather than writing tests to catch and use the
knowledge that message imparts
If a given facility is in a module
lsmod [modulename]
will inventory if a given module is
loaded without the need for:
2> /dev/null
quieting
If a given facility is no longer a module, one can also see
that with it is absent:
depmod -a -n -v | grep -c (modulename)
which will return a value of zero when it is built in, and
non-zero when it is a module
('find' on the /lib/ hierarchy will also do so, but depmod is
smart enough to only look at the modules relevant to the
running kernel)
-- Russ herrold
----------------------------------------------------------------------
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/
