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 -----Original Message----- From: Bishop, Peter G [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 7:25 PM To: [EMAIL PROTECTED] Subject: Re: cpint install question Hi again, thanks Mark - I installed that package (I was expecting it to already have been installed) and still found no cpint.o. When I say "installed that package" I simply mean via Yast. Perhaps that is the wrong method? It's a bit frustrating when the tools don't work as expected, but of course the expectations are part of the problem ;-). I am assuming that somehow my "complete" installation isn't complete, so I'm going to do it again as that's what I really want (not mucking around in the depths of half-installed packages that should have been done as part of the "big bang"). My method for creating a complete install base is to go to a SuSE mirror ftp site and get directories from the /suse/s390/sles7-beta/31-bit/cd[1,2]/suse/ tree. I hope the use of the regular expression is correct just there, [1,2] to indicate getting directories from both CDs (directory names cd1 and cd2). I didn't want to get all directories, simply to save space and time, but I now think that may have been a false economy. So even though I'm going to run servers, I am now going to get the graphics, spelling, and everything. The question then is - how do I tell Yast to install it all? The usual selections don't seem to include a "gimme the lot" option. And it seems from a reading of the manual that if you're not careful changing configurations then packages can end up being deleted, which may or may not have happened here. Once again, thanks for everyone's time. I'll get the hang of this eventually... Peter Bishop CSS Mainframe Service Line EDS Asia Pacific phone +61 2 9378 0113 email [EMAIL PROTECTED] -----Original Message----- Subject: Re: cpint install question Peter, You also need to install the km_cpint.rpm. That's the one that has the actual cpint.o module. (km=kernel module). I didn't realize it was broken up into two RPMs until just now. Once you have that installed, then the other pieces should start working better. Mark Post
