Re: 7.2 Install of SO52 Problems.sdm

Michael, Thanks for the response.

I'm still convinced that depmod -ae is responsible for the SO52 install 
failure, but I see your point that libstu569li.so is an SO52 compressed 
library - not a RH7.2 lib.

I did try the combination of copying the bin files on the CD to a HDD 
partition, then try the install from the HDD. Once depmod had been run 
SO52 would not install. I got the same error as I did from the CD.

Leaving those copied files on an unreformatted partition during a second 
OS install allowed them to install correctly before depmod -ae was 
invoked as root.

I found out that depmod can be run as a user, but it fails as follows:

depmod -ae 
depmod: Can't open /lib/modules/2.4.7-10/modules.dep for writing>  

Is it possible to manually change modules.dep with an editor to ensure 
that only that file gets changed? 

I could diff the before and after. Depmod runs for quite a while on this 
old system, So it would appear that it's doing more than a simple text 
file entry change.

This is probably not worth a lot of effort. I'm using SO52 now and a 
second OS reload is not prohibitively painful for me.

I you think this is worth pursuing farther, I'm willing to spend some 
time to resolve the root cause here.

Regards,

FrankK


>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 5/4/03, 7:16:15 PM, Michael Fratoni <[email protected]> wrote 
regarding Re: 7.2 Install of SO52 Problems.sdm:


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> On Sunday 04 May 2003 03:38 pm, FrankK wrote:
> > I need a way to repair libstu569li.so after it gets "dented" by depmod
> > -ae. Note here that I am replying to my own original post to add more
> > information.
> >
> > Regards, FrankK
> >
> > Details Follow:
> >
> > I am now convinced that this SO52 install problem was caused by my
> > prior invocation as root of depmod -ae. That invocation was
> > necessitated by the CD drive not being recognized by the kernel as a
> > valid block device - which I also posted.
> >
> > This is a catch 22 situation for a virgin install where the CD drive is
> > not properly recognized. The remedy to fix the drive problem renders
> > libstu569li.so unusable for Star Office 5.2 CD install.

> 'depmod -ae' being related to the problem isn't at all likely.

> As part of the normal boot process, 'depmod -a' is run (You'll see a line
> similar to "Finding module dependencies...    OK")
> Adding the -e flag simply forces depmod to report any unresolved symbols.

> Depmod simply finds module dependencies, and writes them to a file in the
> /lib/modules/ tree.
> I don't know what the problem with the star office library might be, but
> I'm reasonably certain that depmod isn't modifying any libraries.

> - --
> - -Michael

> pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
> Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
> - --
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)

> iD8DBQE+tZ8/n/07WoAb/SsRAtfBAJ44mwcO+eUvd4HfTokTFEM0cdVxxQCggVl/
> m/8HkrRSju6zdT8YFbzI6Io=
> =WbFh
> -----END PGP SIGNATURE-----



> _______________________________________________
> enigma-list mailing list
> [email protected]
> https://listman.redhat.com/mailman/listinfo/enigma-list