The behaviour of 'vmcp' is a little different.
May not matter. To some it does. Consistency is a nice thing.
I wrote an hcp.rx Regina script which loads an rxdiagrc.so
module to drive either interface. Does not perform the loading of
the kernel module but issues CP commands with either CPINT or VMCP
and ... [drum roll] ... behaves the same way with either. Yessss!
Could be trivially modified to issue an 'insmod' or 'modprobe'.
http://pb.casita.net/pub/rxdiagrc/rxdiagrc-0.5.tar.gz
-or-
http://pb.casita.net/pub/rxdiagrc/rxdiagrc-0.5.tar
Enjoy!
One thing I find annoying, and I apologize to Christian
for mentioning it here before telling him privately, is that VMCP
performs a belt-and-suspenders check that you are in fact "root".
With CPINT, the sysadmin can elect to 'chmod' the device file
so that a group may issue CP commands. Not so with VMCP and
"rxdiagrc.so" cannot get around that.
-- R;
On Wed, 25 Apr 2007, Kyle Smith wrote:
> If the cpint kernel module wasn't built for the specific kernel
> version that SLES 10 is running the module won't load and you'll get
> an error like that.
>
> Do you have to use cpint specifically, or would the new vmcp tool &
> module be an option? It should be available by default with SLES 10:
>
> modprobe vmcp
> vmcp q stor
>
> ks
>
>
> On 4/25/07, Peter E. Abresch Jr. - at Pepco <[EMAIL PROTECTED]> wrote:
> > I have the following installed on a newly installed sles10x:
> >
> > cpint-kmp-default-2.5.3_2.6.16.21_0.8-3.2
> > cpint-2.5.3-3.2
> >
> > However, when I issue any HCP command, I get the following:
> >
> > linuxm01:/var/log/YaST2 # hcp q stor
> > Open: No such file or directory
> >
> > Even when I run:
> >
> > linuxm01:/etc/init.d # ./cpint.init start
> > insmod: can't read 'cpint': No such file or directory
> >
> > What am I missing?
> >
> > Peter
> > This Email message and any attachment may contain information that is
> > proprietary, legally privileged, confidential and/or subject to copyright
> > belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is
> > intended solely for the use of the person(s) to which it is addressed. If
> > you are not an intended recipient, or the employee or agent responsible for
> > delivery of this Email to the intended recipient(s), you are hereby notified
> > that any dissemination, distribution or copying of this Email is strictly
> > prohibited. If you have received this message in error, please immediately
> > notify the sender and permanently delete this Email and any copies. PHI
> > policies expressly prohibit employees from making defamatory or offensive
> > statements and infringing any copyright or any other legal right by Email
> > communication. PHI will not accept any liability in respect of such
> > communications.
> >
> > ----------------------------------------------------------------------
> > 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 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 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
