* You should make sure that Fedora Core kernels don't take precedence over the vserver kernels, do this by adding exclude=kernel to /etc/yum.repos.d/fedora-updates.repo. It might look something like this when you're done: |
* You should make sure that Fedora Core kernels don't take precedence over the vserver kernels, do this by adding exclude=kernel to /etc/yum.repos.d/fedora-updates.repo. Same relates to yum as Daniel supplies a more secure and patched chroot-Version.
* The repos might look something like this when you're done: |
exclude=kernel kernel-smp |
exclude=kernel kernel-smp yum |
http://muh.at/dhozac/fedora/$releasever/vserver/$basearch |
*Once the repository is added issue the following command to install the vserver kernel.
**For Single processor systems |
* Once the repository is added issue the following command to install the vserver kernel.
** For Single processor systems |
**Or for SMP systems |
** Or for SMP systems
*** Hint: x86_64 on FC5 is always smp, so use kernel only on that |
* Hint: Daniel provided a chroot yum in his repository which supplies several security patches, his util-vserver packages honor this - so you should use his .chroot version (see [above]). |
** Hint: For software install to your guest it naturally needs working internet access and dns resolution to download its packages.
** 2nd Hint: Changes to package management can only be done when guest is not running. |
vserver gast running && vserver gast stop |
** system-config-date (if you want to easily set a timezone for the guest) |
* Caution: On FC4/FC5 Guests, pam authentication (also used with openssh) enables "pam_loginuid.so" in the /etc/pam.d/* files. Comment those out as they are not necessary and will not load within a guest anyway. This probably is also necessary on updates later on, if the configs get changed. You therefore may add the following command line to a cronjob file or your software update script: |
* Caution: On FC4/FC5 guests, pam authentication (also used with openssh) enables "pam_loginuid.so" in the /etc/pam.d/* files. Comment those out as they are not necessary and will not load within a guest anyway. This probably is also necessary on updates later on, if the configs get changed. You therefore may add the following command line to a cronjob file or your software update script: |
*You are now booted into your brand new VServer. A few things need to be set up before you can get going however |
* You are now booted into your brand new VServer. A few things need to be set up before you can get going however |
*Create a shadow file within the guest and check it for errors: |
* Create a shadow file within the guest and check it for errors: |
*Set a root password. |
* Set a root password. |
</code>
* Change the guest timezone: Since FC5 deprecates the textmode system-config-date and depends it on X (which relates to ~60 "overhead RPM's"!), use the following info to change timezone in textmode (if required): ** identify your timezone location from /usr/share/zoneinfo ** copy this file to /etc/localtime (replacing the file there) - that's it ** example: <code> cp -f /usr/share/zoneinfo/Europe/Vienna /etc/localtime |