On Fri, Dec 12, 2003 at 12:46:55PM -0500, Robert P. J. Day wrote: > > > -----Original Message----- > From: Paul Nasrat <pauln@xxxxxxxxxxxx> > > > Berkeley db does not support nfs mounts on Linux I believe so you can't access rpmdb > > http://www.sleepycat.com/docs/ref/env/remote.html > > > Paul > > but i'm not installing across an NFS mount. i'm installing the RPM on > my *local* host. once that's done, that resulting directory is NFS-mounted > to be the root filesystem for the embedded system. i'm hoping i understood > your reply and that i explained why it's not an issue. i think. Ok. It was my misunderstanding. rpm -ivh --nodeps --ignorearch --root=<root fs dir> minicom-ppc.rpm I would imagine this would work if you do an rpm --root=<root fs dir> --initdb >From the man pages: --root DIRECTORY Use the file system tree rooted at DIRECTORY for all operations. Note that this means the database within DIRECTORY will be used for dependency checks and any scriptlet(s) (e.g. %post if installing, or %prep if building, a package) will be run after a chroot(2) to DIRECTORY. > at the moment, because the actual root filesystem is just an NFS-mounted > directory on my local host, i can have the test board up and running and > still make local mods to change that "remote" root filesystem. OK, I got my wires crossed somewhat :) Also using --root is different to relocations, as it does the chroot. Paul _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
