Kir,<br><br>Thanks for all of your help and valuable information. As a learning exercise I too am trying to build my own fedora-core-4 templates using RedHat's "server" install as a baseline I noticed the dummy package you mentioned below, but I also noticed vzdev throws things off a bit as well. It advertizes the 'dev' capability without a version. RedHa't own udev specifies a version of
3.2-7 and some packages request that. I ended up going through a painful exercise of iteratively removing packages from my template's .list file and an exclude statement in my yum.conf to get around the conflicts. <br><br>
Would it be possible to get the spec files for both packages?<br><br>Thanks,<br><br>Chris<br><br><div><span class="gmail_quote">On 11/21/05, <b class="gmail_sendername">Kir Kolyshkin</b> <<a href="mailto:kir@sw.ru">kir@sw.ru
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Eric,<br><br>First, when submitting a bug report or a problem description please
<br>always try to be as specific as possible. In this case it would be<br>helpful if you tell exactly the packages you have installed, the<br>commands you use to do that etc.<br><br>Second, the problem is xorg-x11 requires kernel-drm thus kernel is about
<br>to be installed but it conflicts with our 'dev' package. If you have<br>used vzyum or yum it just bails out telling there is a conflict.<br><br>Anyway, to solve the problem some trick is needed. The trick is to have<br>
a package installed which claims it provides kernel-drm = 4.3.0 so<br>xorg-x11 dependencies will be satisfied. So I have an updated version of<br>dummy package (which is created just for those tricks) that does just<br>that; it is attached.
<br><br>What you need to do with it is:<br>1. Place it to /vz/template/fedora-core/4/i386/vz-addons/ directory.<br>2. cd to that directory and run createrepo as root (if you do not have<br>createrepo installed you can take rpm from
<br><a href="http://linux.duke.edu/projects/metadata/generate/)">http://linux.duke.edu/projects/metadata/generate/)</a><br>3. Update template cache by running vzpkgcache (check that this very<br>version of dummy package is put into cache), then create a new VPS and
<br>go on from there (vzyum VPSID install xorg-x11 vnc-server).<br><br>Restoring your existing VPS would be a bit more complex...<br><br>Eric L. Sammons wrote:<br><br>>First, let me start by stating I am fairly new to OpenVZ. Now, last night I
<br>>tried to use the pre packaged template for Fedora-core-4-default, which worked<br>>fine, then I attempted to install vncserver + X11. These installs all seemed<br>>to work fine, I did notice that a new fedora kernel was installed. Well, at
<br>>some point I decided to vzctl restart <vpsid> and it seemed the image started,<br>>but I could not access it via ssh or vzctl enter. When hardware 0 reboots it<br>>shows OpenVZ starts, but that VPS 101 fails to start.
<br>><br>>So any idea how I might set up X11 under a VPS? Also, along the same note, is<br>>there a good reference on how to build my own template?<br>><br>>Thanks!<br>><br>>_______________________________________________
<br>>Users mailing list<br>><a href="mailto:Users@openvz.org">Users@openvz.org</a><br>><a href="https://openvz.org/mailman/listinfo/users">https://openvz.org/mailman/listinfo/users</a><br>><br>><br>><br>
<br>--<br>Kir Kolyshkin <<a href="mailto:kir@sw.ru">kir@sw.ru</a>> ICQ 7551596<br><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@openvz.org">Users@openvz.org</a><br>
<a href="https://openvz.org/mailman/listinfo/users">https://openvz.org/mailman/listinfo/users</a><br></blockquote></div><br>