> From: Svante Signell <[EMAIL PROTECTED]>
> - Can chroot be used sucessfully? I did not have any luck.
> - Which libraries, executables (statically and dynamically linked) and
> support files are needed to run rpm v4 sucessfully?
> - What to do when an executable has an absolute path to a supporting
> program built in, and that program is available on the /hdroot, not
> on the mounted root directory from the CD (which is also read-only)?
If you mean rpm itself, there is a "--root" option which will enable
it to access the mounted disk system properly (if you have separate
partitions for /var and/or /usr then you will need to make sure you
mount these in the right places).
Example:
Rescue image booted. Your installed system (hd partitions) mounted
under /mnt/something, you can use rpm like this:
rpm --root /mnt/something --install --force /path/to/something/glibc-x.y.z-r.i386.rpm
If you know for sure it's an issue with space on the partition, and
not the rpm database filling up /var, then you could always use the
same approach to remove a couple of less important packaged, and you
could even rpm --erase --force the existing glibc if that will help
to free up the space. I'd suggest removing glibc-devel and -profile
to make some room.
> - Is it possible to remount the hard disk root on / and the CD hard
> disk root somewhere else?
Short answer, no; long answer, yes, because that's how initrd works,
but that's very technical and you don't want to try and do that while
you're working this out from a rescue disk.
> Svante
>
--
/* Bill Crawford, Unix Systems Developer, ebOne, formerly GTS Netcom */
#include "stddiscl.h"
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
