I am doing a little experimenting with running openSUSE in a chroot jail. I'm basically after a compiler environment. I have been doing this with a couple versions of openSUSE and it works quite well. I have just tried setting this up in a slightly different way, and I have encountered a strange thing. I want to be sure I have not overlooked anything. I have unpacked the contents of the JeOS KVM image for 15.1 (current download) to a directory. I am unpacking it this way because I do not really need the cow file. I'm just after a minimal install to get things going. The chroot directory is exactly the tree in the cow file. Just in a directory instead of a cow file. I can chroot into the directory and do lots of things (having first mounted the system's /dev, /proc and /sys folders, and copying the system's /etc/resolv.conf). I can install software with zypper (the stuff I will need to be able to compile things). Here is the strange thing: If I add a package with zypper, it installs fine. zypper continues to know that the package is installed. The package functions as expected. If I ask rpm about the package, it does not think it is installed. Why would the two programs not have the same idea about what is installed? I have never installed software into a chroot directory that contains a complete openSUSE install. So maybe this is how it has always been. I'm not sure where to start looking. I guess I can stick to using zypper and skip looking at rpm. But something worries me about this. A problem waiting to happen. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org