On Friday, 25 July, 2003, Tom Pollerman wrote:
> > "man cpio" *grin* cpio is not specific to Red Hat Linux. ;)
Hehe Michael you're right of course, my bad. I don't know why my
twisted mind thought there might be anything specific to the
output of rpm2cpio ;)
> > Really, rpm2cpio gives you access to a cpio archive inside the rpm.
> > Try something like
> >
> > mkdir test ; cd test
> > rpm2cpio glibc-2.3.2-27.9.i686.rpm | cpio -id
> > --no-absolute-filenames
> >
> > to extract the files inside. You could also extract them within your
> > top-level directory and overwrite what's installed.
Ok I have tested it and it works perfectly, even doing the symlinks.
Now I have gathered all the relevant rpms I would use to restore the
system to the old state, ie :
binutils-2.11.90.0.8-12.i386.rpm
glibc-2.2.4-32.i386.rpm
glibc-common-2.2.4-32.i386.rpm
glibc-devel-2.2.4-32.i386.rpm
RPM agrees to prepare the job with this list of packages so there
must be no conflicts. If only it didn't segfault just after that.
Another weird thing is this :
# ldd /bin/rpm
not a dynamic executable
So I don't see how RPM is affected by all this...
Anyway I am ready to fire 'rpm2cpio /tmp/*.rpm | cpio -idv' in the
root directory with those 4 rpms, but I am a bit afraid. Most utils
are linked to one of the libs that will be replaced by this command,
including rpm2cpio and cpio themselves. Is there a chance everything
might break even more in the process of cpio'ing the 4 packages? I
suppose I have no other choice so I will eventually have to do.
I know I might sound over-careful but since the rest of the system
is still working I cannot risk to break ssh, qmail, apache, ncftpd
who are still mostly fine...
> Might Midnight Commander:
>
> /usr/bin/mc
>
> be able to do the install? I see where mc displays the files inside a
> .rpm (including CONTENTS.cpio), and also gives an "install" and an
> "upgrade" executable. You just highlight the RPM file in Midnight
> Commander and <enter>.
> Perhaps you can get the 'proper' glibc RPM to the remote stystem and
> then fix it in that manner. You could make a "test" install of some
> other .rpm, perhaps a game, just to see how it works.
Thanks for the idea Tom :-) The problem is that mc is not installed
yet and it requires many other libraires, including X11, which
are not installed either. I have tried to install the mc package
using cpio, but the lack of librairies makes it useless ;-)
Also I need to install 4 RPM packages at once, which I am not sure mc
would allow me to do. It might even simply launch the RPM system and
I would be stopped for the same reason.
Thank you a ton again everyone who is trying to help me :-)
Olivier
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
