On Saturday 14 January 2006 16:46, Benedikt Boehm wrote:
> On Saturday 14 January 2006 16:08, Michael S. Zick wrote:
> > On Sat January 14 2006 08:59, Michael S. Zick wrote:
> > > On Sat January 14 2006 06:40, Oliver Welter wrote:
> > > > eyck wrote:
> > > > >> afair, you have to ssh into the box to use screen.
> > > > >> vserver <name> enter and issuing a screen command does not work.
> > > > >
> > > > > it's not that it doesn't work, it's that it easier and safer to
> > > > > tell people 'just ssh into your guest' instead of explaining how to
> > > > > make it work.
> > > >
> > > > As I dont have SSH running inside the guest and I am not afraid of
> > > > some work, how :)
> > >
> > > You could try making it 'by hand' - but that would only work for the
> > > pts that you create by hand. Also recall, that on that system, you are
> > > using udev and /dev is probably mounted in /tmpfs, not as persistent
> > > files on the hard disk.
> > > Gentoo gives you three ways to handle a missing device (follow the
> > > directions for a missing /dev/console or /dev/null).
> > >
> > > But what you want to handle is dynamic devices (pts 0...254) in the
> > > guest with a device creation system that runs in the host.
> > >
> > > First, grab all the udev manuals you can lay your hands on...
> > >
> > > The 'stock' system scripts are creating devices in '/dev'; modify to
> > > create them also in /<vserver>/<guestroot>/dev
> > >
> > > Sorry, I don't know how only what.
> >
> > Scratch that - - here is how:
> >
> > Each udev rule can call an external script - write one that hardlinks the
> > just created /dev/pts/xx to a /<vservers>/<guestroot>/dev/ptx/xx
> >
> > Now all you have to do is figure out 'which vserver' to create the link
> > in.
> >
> > Mike
i missed that you link it in the root path of the vserver.. probably it works,
but it looks more like a workaround, than a fix..
>
> The thing is, you normally don't run udev inside a vserver, because you
> don't have CAP_MKNOD...
>
> the problem with /dev/pts entries not appearing on vserver ... enter is
> that the vserver prorcess only migrates to the context and replaces itself
> with bash, so there is no login process and no terminal devices are created
> by devpts filesystem (in contrary to the ssh attempt)...
>
> i don't know a solution for this atm, but if anyone can help, i'd
> appreciate it
>
> Bene
>
> > > Mike
> > >
> > > > Oliver
> > >
> > > _______________________________________________
> > > 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
>
> _______________________________________________
> 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
Received on Sat Jan 14 15:48:44 2006