Peter, I didn't take the time to look at the actual contents of the km_cpint.rpm, or I wouldn't have stopped where I did. (rpm -qlp km_cpint.rpm)
So, yes, you do have to compile the cpint source, but you're also going to need the corresponding kernel source to do that, since this is a kernel module (cd2/full-names/s390/kernel-source-2.4.7.SuSE-16.s390.rpm). I'm not sure why there are two different Makefiles, the cpint and module ones. I tried them both, and the parameters they use to do the compilation and link are different. I don't know enough to understand the implications, though. So, install the kernel source RPM, then go back and do a "make -f Makefile.module" and then a "make -f Makefile.module install" followed by the "depmod -a" just to be safe, and try it (yet) again. Mark Post -----Original Message----- From: Bishop, Peter G [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 11:50 PM To: [EMAIL PROTECTED] Subject: Re: Yast install (was re: cpint install question) Hi Mark, well all I can say is, prepare to be surprised... ;-) Here's what happened when I did what you suggested === vmsles1:/usr/src/kernel-modules/km_cpint # depmod -a vmsles1:/usr/src/kernel-modules/km_cpint # /sbin/cpint_load insmod: cpint: no module by that name found vmsles1:/usr/src/kernel-modules/km_cpint # cd /lib/modules vmsles1:/lib/modules # find . -name "cpint*" -ls vmsles1:/lib/modules # === I'm really stumped. Any value in just doing the make? Just for a sanity check here's the rpm status === vmsles1:/lib/modules # rpm -qa |grep cpint cpint-1.1.0-18 km_cpint-1.1.0-18 vmsles1:/lib/modules # === And a query on both packages === vmsles1:/lib/modules # rpm -qi cpint Name : cpint Relocations: (not relocateable) Version : 1.1.0 Vendor: SuSE GmbH, Nuernberg, Germany Release : 18 Build Date: Wed Oct 17 15:24:47 2001 Install date: Tue Jul 9 11:03:59 2002 Build Host: s390vm11.suse.de Group : Base/Kernel Source RPM: cpint-1.1.0-18.src.rpm Size : 36813 License: GPL Packager : [EMAIL PROTECTED] Summary : S/390 VM control program interaction Description : This package allows you to interact with the controlling VM from inside a Linux guest. Authors: -------- Neale Ferguson <[EMAIL PROTECTED]> vmsles1:/lib/modules # vmsles1:/lib/modules # rpm -qi km_cpint Name : km_cpint Relocations: (not relocateable) Version : 1.1.0 Vendor: SuSE GmbH, Nuernberg, Germany Release : 18 Build Date: Wed Oct 17 15:24:47 2001 Install date: Tue Jul 9 11:43:54 2002 Build Host: s390vm11.suse.de Group : Base/Kernel Source RPM: cpint-1.1.0-18.src.rpm Size : 295033 License: GPL Packager : [EMAIL PROTECTED] Summary : source for building the cpint module Description : Will be added to to build of the kernel rpms on S/390. Authors: -------- Neale Ferguson === Finally, here's all the "*cpint*" stuff there is === vmsles1:/lib/modules # find / -name "cpint*" -ls 382066 4 -rw-r--r-- 1 root root 3053 Aug 9 2001 /usr/src/kernel-modules/km_cpint/cpint.h 382067 4 -rwxr-xr-x 1 root root 596 Jun 26 2001 /usr/src/kernel-modules/km_cpint/cpint_load 382068 4 -rwxr-xr-x 1 root root 182 Jan 20 2000 /usr/src/kernel-modules/km_cpint/cpint_unload find: /proc/3444/fd: No such file or directory 206765 0 lrwxrwxrwx 1 root root 10 Jul 9 11:03 /sbin/cpint-post-insmod -> cpint-tool 206766 0 lrwxrwxrwx 1 root root 10 Jul 9 11:03 /sbin/cpint-post-rmmod -> cpint-tool 206767 4 -rwxr-xr-x 1 root root 1092 Jul 20 2001 /sbin/cpint-tool 206768 0 lrwxrwxrwx 1 root root 10 Jul 9 11:03 /sbin/cpint_load -> cpint-tool 206769 0 lrwxrwxrwx 1 root root 10 Jul 9 11:03 /sbin/cpint_unload -> cpint-tool vmsles1:/lib/modules # === Thanks again, yours in confusion but faith that this can be done, Peter Bishop CSS Mainframe Service Line EDS Asia Pacific phone +61 2 9378 0113 email [EMAIL PROTECTED] (the original message was lost, so below is a cut/paste job to reinsert it)... -----Original Message----- Peter, I don't know if the RPM does a "depmod -a" command or not (but it should have). You might try that and see if things improve. If not, try this: cd /lib/modules find . -name "cpint*" -ls and see what comes out. I would be really surprised if it wasn't there. To get YaST to install everything (which would be a tremendous waste of space, but that's your call), you need to go into the various options under "Choose / Install packages" and make sure everything is checked for installation. This could take a few minutes. Then start the installation of the packages, and come back the next day. Mark Post
