On 12/12/05, Ralph Shumaker <[EMAIL PROTECTED]> wrote:
> Lan Barnes wrote:
>
> >On Sat, Dec 10, 2005 at 10:14:08AM -0800, Ralph Shumaker wrote:
> >
> >>David Looney wrote:
> >>
> >>>using rpm with --root <directory>
> >>>
> >>>will install all files using the given directory as root, and the
> >>>database within root (i.e. not your system database).
> >>>
> >>By your terms "directory as root" and "within root", I assume you mean
> >>"directory as /" and "within /" respectively.
> >>
> >>If I'm understanding correctly, "rpm --root <directory> -i
> >>some-package.rpm" causes the rpm install of some-package.rpm to consider
> >><directory> to be / as far as it is concerned and all install operations
> >>take place within that root jail. And that includes creating a new rpm
> >>database within that jail. (It's not that I'm trying to be obtuse.
> >>Sometimes stupid details that seem so obvious to some are not so obvious
> >>to me. I /think/ I understand this. But with the chance of completely
> >>mucking up "rpm" itself on my system, I want to be completely sure
> >>before proceeding. The file I need (librpm.so.0) is only found within
> >>older versions of the rpm package itself. The "apt" rpm fails for that
> >>dependency.)
> >
> >I think this is right.
> >
> >>I just tried it. But "apt" still fails dependencies:
> >I thought the point of the exercise was to recover one file from the
> >install? Use --nodeps.
> >
I don't think this simple-minded approach has been mentioned:
$ rpm2cpio package.rpm > archive.cpio
will convert the file to a cpio archive file. Then you can use
$ cpio -it < archive.cpio
to list the contents of the cpio archive, decide what is the single
file you want to recover, and
$ cpio -idv file.you.want < archive.cpio
to extract it. (verbosely, creating directories if needed). Do this
somewhere off to the side, like starting in /tmp.
carl
--
carl lowenstein marine physical lab u.c. san diego
[EMAIL PROTECTED]
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
