baselayout-vserver is supposed (because under developpement) to replace baselayout on gentoo vservers, not on the host. It's purpose is to workaround access restrictions especially to hardware (network board, ...) managed in a completely differnet way on vservers. In fact you create nearly empty /etc/init.d/xxx files.eschoeller wrote:Does baselayout-vserver get installed on the host or on the vserver? I have it installed on the vserver, (i had the original sys-apps/baselayout installed for some reason - the USE variable didnt merge sys-apps/baselayout-vserver for some reason). If anyone has any suggestions please let me know:
So, to use it, you have to allow emerge to access it (it is still in ~x86 only) :
Code: Select all
echo "sys-apps/baselayout-vserver ~x86" >> /etc/portage/packages.keywordsand emerge baselayout-vserver, update the config files and so on.
Take care, I had to face some difficulties on my oldest vserver:
_ the /etc/init.d/net file were not created, instead I still found a /etc/init.d/net.lo and a /etc/init.d/net.eth0. Maybe I had the same problem before but I did not noticed.
_ the /etc/init.d/serial file had not been modified, so the old workaround "is_vserver_guest" function was still present causing an error during the startup. Due to the fact that I am not using any serial stuff, I workaround in doing "rc-update del serial"
_ the update from baselayout version 1.9 to 1.11, include major updates in the way /etc/rc.conf and /etc/conf.d/rc are used (keymaps, ...), the first reboot can be annoying if you do not take care when updating your configuration files.
Good luck
herka
[edit]
BTW I still have the following warning
Code: Select all
WARNING: could not determine runlevel - doing soft halt
(it's better to use shutdown instead of halt from the command line)
shutdown: /dev/initctl: No such file or directory
init: /dev/initctl: No such file or directory





