On Tue, May 03, 2005 at 10:55:39AM +0200, Werner Schalk wrote:
> Hi,
> 
> I re-installed all the vserver stuff and rebuild my images, however my 
> problem 
> still exists. After starting a copied vserver I get:
> 
> # vserver test321 start
>  * Caching service dependencies...
>  * Setting DNS domainname to network.local...                                 
>                                        
> [ ok ]
>  * Starting syslog-ng...                                                      
>                                         
> [ ok ]
>  * Loading key mappings...

not supposed to happen in a guest

> Couldnt get a file descriptor referring to the console
>  * Error loading key mappings

not supposed to happen in a guest

> /sbin/rc: line 250: rc_splash: command not found                              
>                                         
> [ !! ]
> 
>  * Mounting network filesystems...                                            
>                                         
not supposed to happen in a guest

> [ ok ]
>  * Starting vixie-cron...                                                     
>                                         
> [ ok ]
>  * Starting local...                   
> 
> My system is Gentoo, and I am still using util-vserver X on 
> 2.6.11-rc3-vs1.9.4. My USE flags do include "vserver" and portage overlay is 
> set to /usr/local/portage (both inside the vserver). When I execute mc inside 
> the vserver I also get "mc subshell.c: couldn't open master side of pty       
>                                     
> pty_open_master: No such file or directory"

is /dev/ptmx present inside the guest?

> Any ideas what might cause this? Bene?

best,
Herbert

> Bye and thanks,
> Werner
> _______________________________________________
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to